Games Crashing and BSODs

[Ngexp]

I'm not sure if these 2 issues have the same cause or not. They started at about the same time so I've been treating them as the same.

I built a new desktop about about 2 months ago, and everything worked perfectly for a few weeks. Then Windows Blue Screened. This was the initial crash report:

Spoiler

On Thu 2013-05-30 3:43:09 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\052913-3640-01.dmp
This was probably caused by the following module: nvlddmkm.sys (nvlddmkm+0x1156CD)
Bugcheck code: 0x1E (0xFFFFFFFFC000001D, 0xFFFFF88003A77F98, 0xFFFFF880009D2F00, 0x2)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\nvlddmkm.sys
product: NVIDIA Windows Kernel Mode Driver, Version 320.49
company: NVIDIA Corporation
description: NVIDIA Windows Kernel Mode Driver, Version 320.49
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
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 320.49 , NVIDIA Corporation).
Google query: NVIDIA Corporation KMODE_EXCEPTION_NOT_HANDLED

The first thing I did, obviously, was update my graphics drivers. Turns out 320.49 is already up to date, so I completely uninstalled and reinstalled them. No more issues for a month until it happened again. Crash dump almost exactly the same as the first but here it is anyways.

Spoiler

On Sat 2013-06-29 5:17:28 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\062913-3578-01.dmp
This was probably caused by the following module: nvlddmkm.sys (nvlddmkm+0x1156CD)
Bugcheck code: 0x1E (0xFFFFFFFFC000001D, 0xFFFFF88003A27F82, 0xFFFFF802C33D8800, 0x2)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\nvlddmkm.sys
product: NVIDIA Windows Kernel Mode Driver, Version 320.49
company: NVIDIA Corporation
description: NVIDIA Windows Kernel Mode Driver, Version 320.49
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
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 320.49 , NVIDIA Corporation).
Google query: NVIDIA Corporation KMODE_EXCEPTION_NOT_HANDLED

I was busy so I didn't have time to fix it right then. I went to bed and it was fine the next day, until it BSOD'd again with a new error message but referencing the same file.

Spoiler

On Sun 2013-06-30 4:02:14 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\063013-3671-01.dmp
This was probably caused by the following module: nvlddmkm.sys (nvlddmkm+0x1DA97B)
Bugcheck code: 0xD1 (0x40, 0xB, 0x8, 0x40)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\nvlddmkm.sys
product: NVIDIA Windows Kernel Mode Driver, Version 320.49
company: NVIDIA Corporation
description: NVIDIA Windows Kernel Mode Driver, Version 320.49
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 320.49 , NVIDIA Corporation).
Google query: NVIDIA Corporation DRIVER_IRQL_NOT_LESS_OR_EQUAL

I completely wipe anything and everything having to do with Nvidia clean and install 320.49 drivers over again. No more BSODs for 3 days, until I BSOD (I believe it was IRQL_NOT_LESS_OR_EQUAL) and Windows will no longer boot. I tried repeatedly to refresh but it wouldn't recognize my install media. I ended up getting it to boot by doing a system restore to an earlier date but consequently I lost the crash dump for this BSOD. However, the next day I got 2 more BSODs; a IRQL_NOT_LESS_NOR_EQUAL crash as well as a SYSTEM_SERVICE_EXCEPTION only a few hours apart, referencing different files.

Spoiler

On Thu 2013-07-11 10:37:33 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\071113-5187-01.dmp
This was probably caused by the following module: hal.dll (0xFFFFF8020BC33F23)
Bugcheck code: 0xA (0xFFFFFFF9335E81D5, 0x2, 0x0, 0xFFFFF8020BC33F23)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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 Thu 2013-07-11 6:51:25 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\071113-3984-01.dmp
This was probably caused by the following module: fltmgr.sys (fltmgr+0x513D)
Bugcheck code: 0x3B (0xC000001D, 0xFFFFF88000B1313D, 0xFFFFF8800F1E8490, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\drivers\fltmgr.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Microsoft Filesystem Filter Manager
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.

It's still referencing driver issues but am not sure what else to do at that point, so I again uninstall every instance of Nvidia drivers and install the previous driver for my GPU, 320.18. Another BSOD, but with a different error message.

Spoiler

On Fri 2013-07-12 2:16:27 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\071113-3703-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x5A440)
Bugcheck code: 0x133 (0x0, 0x501, 0x500, 0x0)
Error: DPC_WATCHDOG_VIOLATION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

I immediately uninstall all drivers again and re-update, and over the course of the past 15 hours have had 5 more BSODs all similar to the initial one (KMODE_EXCEPTION_NOT_HANDLED referencing nvlddmkm.sys). Since this started, I have also experienced constant crashing while playing video games. The programs stop responding and I have to close them, which can be critical in a multiplayer environment. I have experienced only one BSOD while not playing a game of any kind and it was while watching a video. As I said in the beginning, I am assuming these two issues have the same cause and if they do not I will reevaluate the crashing after I fix the BSODs.

Relevent hardware:

GIGABYTE GeForce GTX 660 Ti WINDFORCE 2X OC Edition
Intel Core i7-3770K Ivy Bridge 3.5GHz (3.9GHz Turbo) LGA 1155 77W Quad-Core
G.SKILL Ripjaws X Series 2 x 8GB 240-Pin DDR3 SDRAM DDR3

Running on Windows 8 64-Bit Full OEM.

Any help would be GREATLY GREATLY appreciated.

 

[mauller07]

when you uninstalled the driver did you use a driver cleaner such as driver fusion?

try downloading driver fusion and installing it, uninstall nvidia driver but do not restart.
run driver fusion and clean nvidia drivers.
restart and only install the nvidia display driver as a custom install and any hdmi audio drivers.

see if the problem happens again, hopefully not.

 

[Ngexp]

Thanks for the response.

I followed your instructions. After doing so I received another BSOD with a new error.

Spoiler

On Sat 2013-07-13 3:12:21 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\071213-3593-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x5A440)
Bugcheck code: 0xFC (0xFFFFF880009DB850, 0x8000000000E29963, 0xFFFFF880009DB420, 0x0)
Error: ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY
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 attempt was made to execute non-executable memory.
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. There is a possibility this problem was caused by a virus or other malware.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

This is obviously a driver issue but no matter what I do with the drivers nothing seems to work. About an hour after the BSOD above my computer shut down again with no error message. All temperatures were fine.

 

[Ngexp]

BSOD occurs even with GPU removed and HDMI cable plugged directly into the motherboard. ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY error almost identical to the one in the previous post.

 

[mauller07]

try the pc with 1 stick of ram at a time and see if the problem persists regardless of the error message it could be a ram issue.

also close any background programs you may have installed until you find one thats running that could be causing the problem.