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

K

Krugiztar

New Member
Messages
6
[FONT=Segoe UI, Arial]I know it says the thing about nVidia but I dont know how to downgrade to another version



System Information (local)
[/FONT]
[FONT=Segoe UI, Arial]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


[/FONT]
[FONT=Segoe UI, Arial]
Crash Dump Analysis
[/FONT]
[FONT=Segoe UI, Arial]Crash dump directory: C:\Windows\Minidump[/FONT]

[FONT=Segoe UI, Arial]Crash dumps are enabled on your computer.
[/FONT]
[FONT=Segoe UI, Arial]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: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x14E2A0)
Bugcheck code: 0x7F (0x8, 0xFFFFF8010491AE70, 0x490995F, 0xFFFFF80102CC63A8)
Error: [FONT=Segoe UI, Arial]UNEXPECTED_KERNEL_MODE_TRAP[/FONT]
file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
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.


[/FONT]
[FONT=Segoe UI, Arial]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: [FONT=Segoe UI, Arial]ntkrnlmp.exe[/FONT] (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x7F (0x8, 0xFFFFF8010491AE70, 0x490995F, 0xFFFFF80102CC63A8)
Error: [FONT=Segoe UI, Arial]UNEXPECTED_KERNEL_MODE_TRAP[/FONT]
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.


[/FONT]
[FONT=Segoe UI, Arial]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: [FONT=Segoe UI, Arial]nvlddmkm.sys[/FONT] (nvlddmkm+0x47BBED)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8002AF5ABED, 0xFFFFD000271F5500, 0x0)
Error: [FONT=Segoe UI, Arial]SYSTEM_SERVICE_EXCEPTION[/FONT]
file path: C:\Windows\system32\drivers\nvlddmkm.sys
product: [FONT=Segoe UI, Arial]NVIDIA Windows Kernel Mode Driver, Version 361.75 [/FONT]
company: [FONT=Segoe UI, Arial]NVIDIA Corporation[/FONT]
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: [FONT=Segoe UI, Arial]NVIDIA Corporation SYSTEM_SERVICE_EXCEPTION[/FONT]


[/FONT]
[FONT=Segoe UI, Arial]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: [FONT=Segoe UI, Arial]nvlddmkm.sys[/FONT] (0xFFFFF8014AED2E92)
Bugcheck code: 0xD5 (0xFFFFCF802DDFCE48, 0x1, 0xFFFFF8014AED2E92, 0x0)
Error: [FONT=Segoe UI, Arial]DRIVER_PAGE_FAULT_IN_FREED_SPECIAL_POOL[/FONT]
file path: C:\Windows\system32\drivers\nvlddmkm.sys
product: [FONT=Segoe UI, Arial]NVIDIA Windows Kernel Mode Driver, Version 361.75 [/FONT]
company: [FONT=Segoe UI, Arial]NVIDIA Corporation[/FONT]
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: [FONT=Segoe UI, Arial]NVIDIA Corporation DRIVER_PAGE_FAULT_IN_FREED_SPECIAL_POOL[/FONT]


[/FONT]
[FONT=Segoe UI, Arial]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: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x14E2A0)
Bugcheck code: 0xC2 (0x7, 0x1200, 0x82010D, 0xFFFFC001C50474F0)
Error: [FONT=Segoe UI, Arial]BAD_POOL_CALLER[/FONT]
file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
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.


[/FONT]
[FONT=Segoe UI, Arial]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: [FONT=Segoe UI, Arial]win32k.sys[/FONT] (win32k+0x28312C)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF960003E912C, 0xFFFFD00023B84E60, 0x0)
Error: [FONT=Segoe UI, Arial]SYSTEM_SERVICE_EXCEPTION[/FONT]
file path: C:\Windows\system32\win32k.sys
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
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.


[/FONT]
[FONT=Segoe UI, Arial]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: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x14E2A0)
Bugcheck code: 0x18 (0x0, 0xFFFFC000406F9900, 0x10, 0x14)
Error: [FONT=Segoe UI, Arial]REFERENCE_BY_POINTER[/FONT]
file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
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.


[/FONT]
[FONT=Segoe UI, Arial]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: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x14E2A0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF801D75B7848, 0xFFFFD00023BD6EA0, 0x0)
Error: [FONT=Segoe UI, Arial]SYSTEM_SERVICE_EXCEPTION[/FONT]
file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
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.


[/FONT]
[FONT=Segoe UI, Arial]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: [FONT=Segoe UI, Arial]nvlddmkm.sys[/FONT] (nvlddmkm+0x76FDC)
Bugcheck code: 0xD1 (0x5B8B49C3, 0xA, 0x1, 0xFFFFF801D00EAFDC)
Error: [FONT=Segoe UI, Arial]DRIVER_IRQL_NOT_LESS_OR_EQUAL[/FONT]
file path: C:\Windows\system32\drivers\nvlddmkm.sys
product: [FONT=Segoe UI, Arial]NVIDIA Windows Kernel Mode Driver, Version 361.75 [/FONT]
company: [FONT=Segoe UI, Arial]NVIDIA Corporation[/FONT]
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: [FONT=Segoe UI, Arial]NVIDIA Corporation DRIVER_IRQL_NOT_LESS_OR_EQUAL[/FONT]


[/FONT]
[FONT=Segoe UI, Arial]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: [FONT=Segoe UI, Arial]dxgmms1.sys[/FONT] (0xFFFFF800F747D2CE)
Bugcheck code: 0xD1 (0x0, 0x2, 0x0, 0xFFFFF800F747D2CE)
Error: [FONT=Segoe UI, Arial]DRIVER_IRQL_NOT_LESS_OR_EQUAL[/FONT]
file path: C:\Windows\system32\drivers\dxgmms1.sys
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
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.


[/FONT]

[FONT=Segoe UI, Arial]
Conclusion
[/FONT]
[FONT=Segoe UI, Arial]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:

[FONT=Segoe UI, Arial]nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 361.75 , NVIDIA Corporation)[/FONT]

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. [/FONT]
 

My Computer

System One

  • OS
    Windows 8.1
    Computer type
    PC/Desktop
    System Manufacturer/Model
    Custom Build / Mostly AMD Parts
    CPU
    AMD FX(tm)-8320 Eight-Core Processor
    Motherboard
    ASUSTeK COMPUTER INC. M5A97 R2.0
    Memory
    10,00 GB
    Graphics Card(s)
    NVIDIA GeForce GTX 960
    Sound Card
    (1) XMOS USB Audio (2) NVIDIA Miracast Audio (3) High Definition Audio Device (4) NVIDIA Virtu
    Monitor(s) Displays
    BenQ GL2250 Dual Monitors
    Screen Resolution
    1920 x 1080 x 32 bits (4294967296 colors) @ 60 Hz
    Hard Drives
    SAMSUNG HD321HJ 298,09 GB
    PSU
    Corsair HX850i with red sleeved cables
    Case
    Fractal Design Core 3000 USB 3.0
    Internet Speed
    http://www.speedtest.net/my-result/5042126498

My Computer

System One

  • OS
    Windows 10 Pro
    Computer type
    PC/Desktop
    System Manufacturer/Model
    Custom build
    CPU
    i5-6500 @3.20GHz
    Motherboard
    Gigabyte B150-HD3P-CF
    Memory
    16GB DDR4 2133 Crucial Ballistix Sport LT
    Graphics Card(s)
    MSI GeForce GTX 1060 GAMING X 6G
    Sound Card
    Built-in
    Monitor(s) Displays
    Liyama ProLite XB2483HSU-B2
    Screen Resolution
    1920 x 1080
    Hard Drives
    Crucial MX200 500GB & Toshiba DT01ACA300 3TB
    PSU
    Corsair RM550x
    Case
    Fractal Design Define S
    Cooling
    Cooler Master TX3 i
    Keyboard
    Func KB-460 (MX Red)
    Mouse
    Corsair Gaming M65 RGB
    Browser
    Google Chrome
    Antivirus
    Bitdefender Total Security 2017 + MBAM Pro + MBAE Pro
    Other Info
    Creative Sound Blaster Tactic3D Rage V2 headset
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 Computer

System One

  • OS
    Windows 7
TheITGuru said:
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.
Click to expand...

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 Computer

System One

  • OS
    Windows 8.1
    Computer type
    PC/Desktop
    System Manufacturer/Model
    Custom Build / Mostly AMD Parts
    CPU
    AMD FX(tm)-8320 Eight-Core Processor
    Motherboard
    ASUSTeK COMPUTER INC. M5A97 R2.0
    Memory
    10,00 GB
    Graphics Card(s)
    NVIDIA GeForce GTX 960
    Sound Card
    (1) XMOS USB Audio (2) NVIDIA Miracast Audio (3) High Definition Audio Device (4) NVIDIA Virtu
    Monitor(s) Displays
    BenQ GL2250 Dual Monitors
    Screen Resolution
    1920 x 1080 x 32 bits (4294967296 colors) @ 60 Hz
    Hard Drives
    SAMSUNG HD321HJ 298,09 GB
    PSU
    Corsair HX850i with red sleeved cables
    Case
    Fractal Design Core 3000 USB 3.0
    Internet Speed
    http://www.speedtest.net/my-result/5042126498
TheITGuru said:
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.
Click to expand...

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 Computer

System One

  • OS
    Windows 10 Pro
    Computer type
    PC/Desktop
    System Manufacturer/Model
    Custom build
    CPU
    i5-6500 @3.20GHz
    Motherboard
    Gigabyte B150-HD3P-CF
    Memory
    16GB DDR4 2133 Crucial Ballistix Sport LT
    Graphics Card(s)
    MSI GeForce GTX 1060 GAMING X 6G
    Sound Card
    Built-in
    Monitor(s) Displays
    Liyama ProLite XB2483HSU-B2
    Screen Resolution
    1920 x 1080
    Hard Drives
    Crucial MX200 500GB & Toshiba DT01ACA300 3TB
    PSU
    Corsair RM550x
    Case
    Fractal Design Define S
    Cooling
    Cooler Master TX3 i
    Keyboard
    Func KB-460 (MX Red)
    Mouse
    Corsair Gaming M65 RGB
    Browser
    Google Chrome
    Antivirus
    Bitdefender Total Security 2017 + MBAM Pro + MBAE Pro
    Other Info
    Creative Sound Blaster Tactic3D Rage V2 headset
You must log in or register to reply here.
Back
Top