BSOD while idle, and when keyboard crashes (?) and during WoW

[subtletuna]

Hi,

I have kind of a weird issue. My computer will crash at random times when playing WoW. When it happens, my computer will kind of hang there, and everything will freeze except i can use my mouse, but about 1 min later i'll BSOD. When I BSOD, my POST hangs at a black screen before the MSI screen, where it says A2 in the bottom right corner, which changes to A3 eventually, then it loads.

When it crashes via my keyboard crashing, i'll randomly be typing (pretend the last key I hit was 'n') it will spam the 'n' button and nothing else, kind of like the drivers crashed. The only thing I can do is log out of windows, and as soon as I hit log out it crashes.

And the most obvious one, when I come back from work and my computer is on i'll sometimes come back to a BSOD, or a black screen that says an error has occurred.

I've attached the SF diagnostic results.

Thanks a lot

 

[koolkat77]

Welcome

1. Get rid of Daemon tools, this software is a known cause of blue screens.
2. If you are overclocking any hardware, please restore back to default clocks and uninstall MSI Afterburner.
3. Uninstall McAfee and replace with MSE Microsoft Security Essentials - Free Antivirus for Windows while we troubleshoot problems with your computer.
4. Get all updates from windows updates including Service Pack 1
5. Run memtest86+ on each stick for 8 passes preferably overnight http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html
6. Look for and update to the latest BIOS version for your computer.

STOP 0x0000001E: KMODE_EXCEPTION_NOT_HANDLED BSOD Index
Usual causes: Device driver, hardware, System service, compatibility, Remote control programs, memory, BIOS.

Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Yusra\Downloads\subtletuna\SF_11-09-2012\081112-70325-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Unable to load image Unknown_Module_00000000`6a17302d, Win32 error 0n2
*** WARNING: Unable to verify timestamp for Unknown_Module_00000000`6a17302d
*** ERROR: Module load completed but symbols could not be loaded for Unknown_Module_00000000`6a17302d
Debugger can not determine kernel base address
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.17017.amd64fre.win7_gdr.120503-2030
Machine Name:
Kernel base = 0xfffff800`0325c000 PsLoadedModuleList = 0xfffff800`03498e70
Debug session time: Sun Aug 12 10:07:33.983 2012 (UTC + 6:00)
System Uptime: 1 days 2:03:45.263
Unable to load image Unknown_Module_00000000`6a17302d, Win32 error 0n2
*** WARNING: Unable to verify timestamp for Unknown_Module_00000000`6a17302d
*** ERROR: Module load completed but symbols could not be loaded for Unknown_Module_00000000`6a17302d
Debugger can not determine kernel base address
Loading Kernel Symbols
.
Loading User Symbols
Loading unloaded module list
.............
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

[COLOR=Red]BugCheck 1E,[/COLOR] {0, 0, 0, 0}

***** Debugger could not find nt in module list, module list might be corrupt, error 0x80070057.

Probably caused by : [COLOR=Red]Unknown_Image ( ANALYSIS_INCONCLUSIVE )[/COLOR]

Followup: MachineOwner
---------

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
[COLOR=Red]
KMODE_EXCEPTION_NOT_HANDLED (1e[/COLOR])
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: 0000000000000000, The exception code that was not handled
Arg2: 0000000000000000, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception

Debugging Details:
------------------

***** Debugger could not find nt in module list, module list might be corrupt, error 0x80070057.


EXCEPTION_CODE: (Win32) 0 (0) - The operation completed successfully.

FAULTING_IP: 
+5a7a2faf0289da40
00000000`00000000 ??              ???

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  0000000000000000

ERROR_CODE: (NTSTATUS) 0 - STATUS_WAIT_0

BUGCHECK_STR:  0x1E_0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff800032c3d6e to fffff800032cc010

STACK_TEXT:  
fffff800`00ba1dc8 fffff800`032c3d6e : 0000e7d8`00000010 00000020`00000006 fffff800`00ba25d0 fffff800`032f89a8 : 0xfffff800`032cc010
fffff800`00ba1dd0 0000e7d8`00000010 : 00000020`00000006 fffff800`00ba25d0 fffff800`032f89a8 00000000`00000001 : 0xfffff800`032c3d6e
fffff800`00ba1dd8 00000020`00000006 : fffff800`00ba25d0 fffff800`032f89a8 00000000`00000001 fffff800`032f175d : 0xe7d8`00000010
fffff800`00ba1de0 fffff800`00ba25d0 : fffff800`032f89a8 00000000`00000001 fffff800`032f175d fffff800`034d9b1c : 0x20`00000006
fffff800`00ba1de8 fffff800`032f89a8 : 00000000`00000001 fffff800`032f175d fffff800`034d9b1c fffff800`03412ac4 : 0xfffff800`00ba25d0
fffff800`00ba1df0 00000000`00000001 : fffff800`032f175d fffff800`034d9b1c fffff800`03412ac4 fffff800`0325c000 : 0xfffff800`032f89a8
fffff800`00ba1df8 fffff800`032f175d : fffff800`034d9b1c fffff800`03412ac4 fffff800`0325c000 fffff800`00ba2530 : 0x1
fffff800`00ba1e00 fffff800`034d9b1c : fffff800`03412ac4 fffff800`0325c000 fffff800`00ba2530 fffff800`00ba1ec0 : 0xfffff800`032f175d
fffff800`00ba1e08 fffff800`03412ac4 : fffff800`0325c000 fffff800`00ba2530 fffff800`00ba1ec0 fffff800`032f8dd0 : 0xfffff800`034d9b1c
fffff800`00ba1e10 fffff800`0325c000 : fffff800`00ba2530 fffff800`00ba1ec0 fffff800`032f8dd0 fffff800`0341a990 : 0xfffff800`03412ac4
fffff800`00ba1e18 fffff800`00ba2530 : fffff800`00ba1ec0 fffff800`032f8dd0 fffff800`0341a990 fffff800`00ba1e78 : 0xfffff800`0325c000
fffff800`00ba1e20 fffff800`00ba1ec0 : fffff800`032f8dd0 fffff800`0341a990 fffff800`00ba1e78 fffff800`00ba2530 : 0xfffff800`00ba2530
fffff800`00ba1e28 fffff800`032f8dd0 : fffff800`0341a990 fffff800`00ba1e78 fffff800`00ba2530 fffff800`0325c000 : 0xfffff800`00ba1ec0
fffff800`00ba1e30 fffff800`0341a990 : fffff800`00ba1e78 fffff800`00ba2530 fffff800`0325c000 00000000`00000000 : 0xfffff800`032f8dd0
fffff800`00ba1e38 fffff800`00ba1e78 : fffff800`00ba2530 fffff800`0325c000 00000000`00000000 00000000`00000000 : 0xfffff800`0341a990
fffff800`00ba1e40 fffff800`00ba2530 : fffff800`0325c000 00000000`00000000 00000000`00000000 00000000`00000000 : 0xfffff800`00ba1e78
fffff800`00ba1e48 fffff800`0325c000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0xfffff800`00ba2530
fffff800`00ba1e50 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 fffff800`00ba2fb0 : 0xfffff800`0325c000


STACK_COMMAND:  kb

SYMBOL_NAME:  ANALYSIS_INCONCLUSIVE

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: Unknown_Module

IMAGE_NAME:  Unknown_Image

DEBUG_FLR_IMAGE_TIMESTAMP:  0

BUCKET_ID:  CORRUPT_MODULELIST

Followup: MachineOwner
---------

Keep us posted

 

[subtletuna]

Thank you, I will do the above things and report back when/if i BSOD again (sometimes takes a few days)

 

[koolkat77]

Take your time. No problemo.

 

[subtletuna]

Finally got around to doing all this. What is the next step if I crash again?

 

[koolkat77]

We can say only after we see your next crash

 

[subtletuna]

Hi again,
My computer crashed last night while typing in WoW. (Keyboard style crash I mentioned in the original post). I've uploaded the new SF diagnostic results if it helps.

Thanks a lot

 

[koolkat77]

The dump does not provide any information so lets enable driver verifier to rule out buggy drivers.

Verifier puts extreme stress on the drivers, bad ones will cause BSOD. If we change all those drivers we hope for no more BSODs, If you get no BSODs, then its not a driver and we look to hardware. With verifier on your computer may be a little laggy, but actually..its just doing its work.

• http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html

Information
Driver Verifier runs in the background, "testing" drivers for bugs. If it finds one, a Blue Screen of Death (BSOD) will result; the corresponding dump file will hopefully show the faulty driver.

Driver Verifier monitors kernel-mode drivers and graphics drivers to detect illegal function calls or actions that might corrupt the system. It can subject the drivers to a variety of stresses and tests to find improper behavior.

Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation.

 

[subtletuna]

I did the above thing, and rebooted my computer.
My computer doesnt currently load up windows before it BSODs now. The BSOD happens right before the windows log in screen.
Im currently on my other hard drive on another copy of windows 7. How do i disable those changes from this HDD, and what's my next step?

Thanks again (you're super kind in helping me with this),

 

[koolkat77]

Whats the stop code? If its C4, thats normal. Just restart the computer manually.

If its something else, boot into safe mode, disable verifier, boot normally and upload the dump.

 

[subtletuna]

Hi, there was no C4 error (I think, i dont actually know where to look), but regardless my computer wouldnt start unless i reverted the verifier changes.

Here's the updated SF diagnostic.

Cheers

 

[subtletuna]

Also, it said IRQL_NOT_EQUAL_OR_LESS on the blue screen. Not sure if that means anything useful.

 

[koolkat77]

There's only one dump of 08-11-12
What happened to the rest?

 

[subtletuna]

I dont know. I just use that program and upload whatever it spits out. I will wait for another crash and reupload the new one

 

[koolkat77]

No hurries.
Take your time

 

[subtletuna]

Hi,
An update: Something happened last night while I was sleeping that caused my computer to reboot itself. Now everytime I log into windows, my NVIDIA drivers keep crashing over and over again. I tried rerolling my drivers and doing a system restore, but neither of these helped. Also, my computer isnt saving any of the minidump files so I cant run the SF diagnostic tool. (I'm writing this from safemode right now and I cant even find the tool on my computer).

I was thinking about reformatting my computer. Would this help at all or is it just a giant waste of time?

Thanks

 

[koolkat77]

Go to safe mode with networking via advanced boot options, and then sue driver sweeper to remove all nvidia elements.

Then download and install again.