Windows 8 and 8.1 Forums


About 7 BSOD in under 2 hrs? What the heck is going on

  1. #1


    Posts : 6
    Windows 8.1

    About 7 BSOD in under 2 hrs? What the heck is going on


    I know it says the thing about nVidia but I dont know how to downgrade to another version



    System Information (local)


    Computer name: GAMING
    Windows version: Windows 8.1 , 6.3, build: 9600
    Windows dir: C:\Windows
    Hardware: ASUSTeK COMPUTER INC., M5A97 R2.0
    CPU: AuthenticAMD AMD FX(tm)-8320 Eight-Core Processor AMD586, level: 21
    8 logical processors, active mask: 255
    RAM: 10629001216 bytes total




    Crash Dump Analysis


    Crash dump directory: C:\Windows\Minidump

    Crash dumps are enabled on your computer.

    On Fri 2016-02-12 01:08:59 GMT your computer crashed
    crash dump file: C:\Windows\Minidump\021216-24859-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x14E2A0)
    Bugcheck code: 0x7F (0x8, 0xFFFFF8010491AE70, 0x490995F, 0xFFFFF80102CC63A8)
    Error: UNEXPECTED_KERNEL_MODE_TRAP
    file path: C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: This bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



    On Fri 2016-02-12 01:08:59 GMT your computer crashed
    crash dump file: C:\Windows\memory.dmp
    This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
    Bugcheck code: 0x7F (0x8, 0xFFFFF8010491AE70, 0x490995F, 0xFFFFF80102CC63A8)
    Error: UNEXPECTED_KERNEL_MODE_TRAP
    Bug check description: This bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



    On Thu 2016-02-11 22:39:09 GMT your computer crashed
    crash dump file: C:\Windows\Minidump\021116-19640-01.dmp
    This was probably caused by the following module: nvlddmkm.sys (nvlddmkm+0x47BBED)
    Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8002AF5ABED, 0xFFFFD000271F5500, 0x0)
    Error: SYSTEM_SERVICE_EXCEPTION
    file path: C:\Windows\system32\drivers\nvlddmkm.sys
    product: NVIDIA Windows Kernel Mode Driver, Version 361.75
    company: NVIDIA Corporation
    description: NVIDIA Windows Kernel Mode Driver, Version 361.75
    Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
    A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 361.75 , NVIDIA Corporation).
    Google query: NVIDIA Corporation SYSTEM_SERVICE_EXCEPTION



    On Thu 2016-02-11 22:30:25 GMT your computer crashed
    crash dump file: C:\Windows\Minidump\021116-21593-01.dmp
    This was probably caused by the following module: nvlddmkm.sys (0xFFFFF8014AED2E92)
    Bugcheck code: 0xD5 (0xFFFFCF802DDFCE48, 0x1, 0xFFFFF8014AED2E92, 0x0)
    Error: DRIVER_PAGE_FAULT_IN_FREED_SPECIAL_POOL
    file path: C:\Windows\system32\drivers\nvlddmkm.sys
    product: NVIDIA Windows Kernel Mode Driver, Version 361.75
    company: NVIDIA Corporation
    description: NVIDIA Windows Kernel Mode Driver, Version 361.75
    Bug check description: This indicates that a driver has referenced memory which was earlier freed.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
    A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 361.75 , NVIDIA Corporation).
    Google query: NVIDIA Corporation DRIVER_PAGE_FAULT_IN_FREED_SPECIAL_POOL



    On Thu 2016-02-11 22:21:13 GMT your computer crashed
    crash dump file: C:\Windows\Minidump\021116-22875-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x14E2A0)
    Bugcheck code: 0xC2 (0x7, 0x1200, 0x82010D, 0xFFFFC001C50474F0)
    Error: BAD_POOL_CALLER
    file path: C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: This indicates that the current thread is making a bad pool request.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



    On Thu 2016-02-11 21:42:40 GMT your computer crashed
    crash dump file: C:\Windows\Minidump\021116-16625-01.dmp
    This was probably caused by the following module: win32k.sys (win32k+0x28312C)
    Bugcheck code: 0x3B (0xC0000005, 0xFFFFF960003E912C, 0xFFFFD00023B84E60, 0x0)
    Error: SYSTEM_SERVICE_EXCEPTION
    file path: C:\Windows\system32\win32k.sys
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: Multi-User Win32 Driver
    Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
    The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



    On Wed 2016-02-10 18:11:56 GMT your computer crashed
    crash dump file: C:\Windows\Minidump\021016-16593-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x14E2A0)
    Bugcheck code: 0x18 (0x0, 0xFFFFC000406F9900, 0x10, 0x14)
    Error: REFERENCE_BY_POINTER
    file path: C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: This indicates that the reference count of an object is illegal for the current state of the object.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



    On Sat 2016-02-06 19:43:23 GMT your computer crashed
    crash dump file: C:\Windows\Minidump\020616-29453-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x14E2A0)
    Bugcheck code: 0x3B (0xC0000005, 0xFFFFF801D75B7848, 0xFFFFD00023BD6EA0, 0x0)
    Error: SYSTEM_SERVICE_EXCEPTION
    file path: C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



    On Thu 2016-02-04 17:41:44 GMT your computer crashed
    crash dump file: C:\Windows\Minidump\020416-19734-01.dmp
    This was probably caused by the following module: nvlddmkm.sys (nvlddmkm+0x76FDC)
    Bugcheck code: 0xD1 (0x5B8B49C3, 0xA, 0x1, 0xFFFFF801D00EAFDC)
    Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
    file path: C:\Windows\system32\drivers\nvlddmkm.sys
    product: NVIDIA Windows Kernel Mode Driver, Version 361.75
    company: NVIDIA Corporation
    description: NVIDIA Windows Kernel Mode Driver, Version 361.75
    Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
    A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 361.75 , NVIDIA Corporation).
    Google query: NVIDIA Corporation DRIVER_IRQL_NOT_LESS_OR_EQUAL



    On Wed 2016-02-03 17:06:56 GMT your computer crashed
    crash dump file: C:\Windows\Minidump\020316-25734-01.dmp
    This was probably caused by the following module: dxgmms1.sys (0xFFFFF800F747D2CE)
    Bugcheck code: 0xD1 (0x0, 0x2, 0x0, 0xFFFFF800F747D2CE)
    Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
    file path: C:\Windows\system32\drivers\dxgmms1.sys
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: DirectX Graphics MMS
    Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
    The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.





    Conclusion


    10 crash dumps have been found and analyzed. A third party driver has been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:

    nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 361.75 , NVIDIA Corporation)

    If no updates for these drivers are available, try searching with Google on the names of these drivers in combination with the errors that have been reported for these drivers. Include the brand and model name of your computer as well in the query. This often yields interesting results from discussions on the web by users who have been experiencing similar problems.


    Read the topic general suggestions for troubleshooting system crashes for more information.

    Note that it's not always possible to state with certainty whether a reported driver is responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.

      My System SpecsSystem Spec

  2. #2



    BSOD Kernel Dump Analyst
    Posts : 2,274
    Windows 10 Pro
      My System SpecsSystem Spec

  3. #3


    Posts : 5
    Windows 7


    It's going to recommend that you install new drivers but it can also be an incompatibility issue with your current drivers.

    In a case like this, try to restore using Sys Restore.

    If that doesn't work (and let's be honest it's Sys Restore...) then you'll want to re-format the computer and go through each driver update one-by-one. A pain, but if you use a snapshot program like Comodo Time Machine or Rollback Rx you can just revert back when you find the culprit.

    Once you find out which update caused this, I'd contact the company to see if there's a fix, if this is a known issue, etc. At worst, you'll have to hold back on installing that update until a new one comes out.
      My System SpecsSystem Spec

  4. #4


    Posts : 6
    Windows 8.1


    Quote Originally Posted by TheITGuru View Post
    It's going to recommend that you install new drivers but it can also be an incompatibility issue with your current drivers.

    In a case like this, try to restore using Sys Restore.

    If that doesn't work (and let's be honest it's Sys Restore...) then you'll want to re-format the computer and go through each driver update one-by-one. A pain, but if you use a snapshot program like Comodo Time Machine or Rollback Rx you can just revert back when you find the culprit.

    Once you find out which update caused this, I'd contact the company to see if there's a fix, if this is a known issue, etc. At worst, you'll have to hold back on installing that update until a new one comes out.
    Yeah I updated all my drivers and it seemed to help a bit, which is nice, then I removed a old ram stick that I had in and that seemed to remove the problem completly, sure I got some internal power blue screen thing a few days ago but ever since that it doesnt seem to blue sccreen anymore!
      My System SpecsSystem Spec

  5. #5



    BSOD Kernel Dump Analyst
    Posts : 2,274
    Windows 10 Pro


    Quote Originally Posted by TheITGuru View Post
    It's going to recommend that you install new drivers but it can also be an incompatibility issue with your current drivers.

    In a case like this, try to restore using Sys Restore.

    If that doesn't work (and let's be honest it's Sys Restore...) then you'll want to re-format the computer and go through each driver update one-by-one. A pain, but if you use a snapshot program like Comodo Time Machine or Rollback Rx you can just revert back when you find the culprit.

    Once you find out which update caused this, I'd contact the company to see if there's a fix, if this is a known issue, etc. At worst, you'll have to hold back on installing that update until a new one comes out.
    Why would the OP want to re-format the system? In the state the OP started with can also check each driver and looking at the variance of the error codes it may or may not be drivers at all.
      My System SpecsSystem Spec

About 7 BSOD in under 2 hrs? What the heck is going on
Related Threads
So a a day ago I woke up, turned on my computer, and was surprised at how long it took to turn on. It took, like, 30 minutes to get to the desktop screen (I have Pokki so it goes to metro for a seconds and then automatically goes to the desktop). It took its sweet time trying to load steam and...
One heck of a problem. in General Support
Ok so I'll cut straight to the stuff that matters: When I turn the PC on, I boot to the Windows 8 Login screen and I see a message every cold boot that says something to the effect of "Wrong DVI Cable Connected. Please Connect the cable that came with your monitor" and the stuff on the screen...
The heck?! in General Support
OK, so here's the deal. My dad purchased a brand new 17" Dell laptop (17R) with Core i7, 8GB of RAM... and it came with, of course, Windows 8. So, we purchased an extra Windows 7 HP x64 OEM licence for it. So, I decided to check it (Win8) out before formatting it back to Windows 7. (I'm...
So I had this Bluetooth mouse that I only used occasionally. After installing Windows 8, I tried turning it on only to find that it was wasn't functioning. So, naturally I thought of pairing it once more. Unfortunately, the god damn thing just wont show up! I have a feeling it's because I had that...
RTM is ugly as heck in General Support
Just installed the leaked RTM. No aero glass. Inactive windows are gray. Taskbar is transparent, but there is no blur. I can post screens later, but it's much worse than the RP. If any other people here are interested in helping me fix this, and have some skillz, we should try to work this...
$999.99 app, what the heck? in Software and Apps
Windows Store is an upcoming digital distribution platform developed by Microsoft Corporation as part of Windows 8 for Metro style apps. The Windows Store will also allow developers to advertise their desktop apps. It will support both free and paid applications, with the paid applications...
Ok, this has bothered me long enough! So I thought that I'd line my live account with my windows account. Bad move! Now I'm stuck with windows live services ALWAYS bloody signing me into my old account no matter how many times I hit that gal dang delete button. So, now that I got that out...
Eight Forums Android App Eight Forums IOS App Follow us on Facebook