[motokokusanagi]

Hey,

I am a first time poster here. For the BSOD it normally occurs when alot is going on, but can happen randomly at any time. I also get black screens from the game for no reason at all that force me to ctrl+alt+delete then log out because the task manager will not pop up in front of the game. Iv been scanning with SuperAntiSpyware & MSE. I also ran memtest86 and cleared all the tests, so my very limited computer knowledge is telling me its a driver issue. Browsing the forums, I found that I should run WhoCrashed. Im not sure how to turn the data into a file to attach... so ill copy & paste the text.
Thank you for your help in advance.

---------
System Information (local)
--------------------------------------------------------------------------------

computer name: ANDREW-PC
windows version: Windows 7 , 6.1, build: 7600
windows dir: C:\Windows
CPU: GenuineIntel Intel® Core™ i7 CPU 920 @ 2.67GHz Intel586, level: 6
8 logical processors, active mask: 255
RAM: 9654403072 total
VM: 2147352576, free: 1928937472

Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.


On Mon 10/15/2012 12:08:28 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\101512-18673-01.dmp
This was probably caused by the following module: nvlddmkm.sys (nvlddmkm+0xBD497) 
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\nvlddmkm.sys
product: NVIDIA Windows Kernel Mode Driver, Version 306.23 
company: NVIDIA Corporation
description: NVIDIA Windows Kernel Mode Driver, Version 306.23 
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 306.23 , NVIDIA Corporation). 
Google query: nvlddmkm.sys NVIDIA Corporation KMODE_EXCEPTION_NOT_HANDLED




On Mon 10/15/2012 12:08:28 PM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: danew.sys (danew+0x6DA) 
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\danew.sys
product: Razer DeathAdder USB Optical Mouse
company: Razer (Asia-Pacific) Pte Ltd
description: Razer DeathAdder USB Optical Mouse Driver
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: danew.sys (Razer DeathAdder USB Optical Mouse Driver, Razer (Asia-Pacific) Pte Ltd). 
Google query: danew.sys Razer (Asia-Pacific) Pte Ltd KMODE_EXCEPTION_NOT_HANDLED




On Fri 10/12/2012 8:47:33 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\101212-96159-01.dmp
This was probably caused by the following module: dxgkrnl.sys (dxgkrnl+0x313F) 
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\dxgkrnl.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics Kernel
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. 
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 which cannot be identified at this time. 


On Wed 10/10/2012 6:05:26 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\101012-101681-01.dmp
This was probably caused by the following module: dxgmms1.sys (dxgmms1+0x7F76) 
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
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 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. 
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 which cannot be identified at this time. 


On Sun 10/7/2012 1:36:37 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\100712-90932-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70010) 
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
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 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. 
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time. 


On Sun 10/7/2012 1:56:10 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\100612-95051-01.dmp
This was probably caused by the following module: dxgmms1.sys (dxgmms1+0x7F76) 
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
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 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. 
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 which cannot be identified at this time. 


On Sun 9/30/2012 5:54:43 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\093012-47689-01.dmp
This was probably caused by the following module: dxgmms1.sys (dxgmms1+0x7F76) 
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
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 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. 
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 which cannot be identified at this time. 


On Fri 9/28/2012 2:02:34 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\092712-48017-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70010) 
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
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 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. 
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time. 


On Sat 9/8/2012 7:47:55 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\090812-92820-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70010) 
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
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 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. 
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time. 


On Sat 9/8/2012 6:51:43 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\090812-46441-01.dmp
This was probably caused by the following module: dxgmms1.sys (dxgmms1+0xC095) 
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
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 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. 
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 which cannot be identified at this time. 


On Thu 8/30/2012 5:09:39 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\083012-50949-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70040) 
Bugcheck code: 0x1E (0xFFFFFFFFC0000047, 0xFFFFF80002EAB37C, 0xFFFFF880031FD500, 0xFFFFFA800CAB4000)
Error: KMODE_EXCEPTION_NOT_HANDLED
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 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. 
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time. 


On Tue 8/28/2012 2:29:40 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\082812-50325-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70010) 
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
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 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. 
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time. 


On Mon 8/13/2012 7:23:31 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\081312-52899-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70040) 
Bugcheck code: 0x9F (0x3, 0xFFFFFA8007681060, 0xFFFFF80000B9C518, 0xFFFFFA800A8A1550)
Error: DRIVER_POWER_STATE_FAILURE
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 driver is in an inconsistent or invalid power state.
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 which cannot be identified at this time. 

13 crash dumps have been found and analyzed. 2 third party drivers have 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 306.23 , NVIDIA Corporation)

danew.sys (Razer DeathAdder USB Optical Mouse Driver, Razer (Asia-Pacific) Pte Ltd)

Edited by motokokusanagi, 17 October 2012 - 09:32 AM.