Frequent BSODs on a number of different error codes

Alhazred · 28 Dec 2011

Hello,

I've been suffering more or less frequent BSODs for a while. They usually come when I'm playing something, ranging from Orcs Must Die to Fallout 3. Most often they appear when I'm on Skype, chatting with people while playing Magicka or League of Legends.

These BSODs are often accompanied with loud, "buzzing" sound which disappears only after the computer reboots itself. There have been many kinds of files which seem to be the cause behind the crash such as win32k.sys, dxgmms1.sys, nvlddmkm.sys, usbohci.sys and so on, but I don't know what to do about them.

I've updated my GFX, chipset and soundboard (I think, it's integrated) drivers and flashed the BIOS. I've also reinstalled the OS once, few months ago I guess. I've checked RAM with memtest, turned out fine, same with hard drives. I haven't monitored computer temps very closely, but I have removed the side of the case so the air should be flowing freely. The crashes are also quite random (sometimes I get a full day of BSOD-free LoL-goodness, sometimes I can't even start one match), so I guess temp shouldn't be the main issue, although I wouldn't be asking if I knew for myself. Ïn any case, I also have RivaTuner installed,

I have Windows 7 64-bit. My computer is kind of old, Nvidia GTX260, 4gb RAM, AMD Phenom II 2x no OC.

Dump files follow.

Please, "fix" my computer, I've just bought tons of holiday-sale games from Steam!

Alhazred · 29 Dec 2011

Shameless self-bump.

Alhazred · 31 Dec 2011

Bumping once again, I'm just hoping a solution for this most annoying problem.

wish · 31 Dec 2011

Hi Alhazred,
By looking at your 4 most recent dump files, several things caught my attention.
For troubleshooting purpose, please follow my suggestion:
1. Uninstall RivaTuner although you not OC
2. Uninstall Daemon Tools for a while (you may use Magicdisc for alternative)
3. Don't use any registry cleaner if it isn't necessary. Junk registry never harm your Windows. (another ref = https://www.sevenforums.com/1058589-post5.html)
4. Reinstall your Graphic Drivers (use Driver Sweeper to remove completely your current driver then download and install fresh display driver)
Phyxion.net - Driver Sweeper
5. Another dump indicated 0x124 bugcheck usually related to hardware issues. So it better to follow this step:
Stop 0x124 - what it means and what to try
Good luck :)

LOG

Code:

Symbol search path is: srv*C:\Symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Machine Name:
Kernel base = 0xfffff800`02e5c000 PsLoadedModuleList = 0xfffff800`03099e70
Debug session time: Wed Dec 28 10:03:40.627 2011 (GMT-8)
System Uptime: 0 days 3:49:43.282
Loading Kernel Symbols
...............................................................
................................................................
........................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff960000bafb3, fffff88008a116b0, 0}

Probably caused by : memory_corruption

Followup: memory_corruption
---------

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff960000bafb3, Address of the exception record for the exception that caused the bugcheck
Arg3: fffff88008a116b0, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP: 
win32k!RGNOBJAPI::bDeleteRGNOBJAPI+23
fffff960`000bafb3 210f            and     dword ptr [rdi],ecx

CONTEXT:  fffff88008a116b0 -- (.cxr 0xfffff88008a116b0)
rax=fffff88008a120a0 rbx=fffff960000baf50 rcx=fffff88008a120a0
rdx=0000000000003312 rsi=fffff96000087008 rdi=0000000000000000
rip=fffff960000bafb3 rsp=fffff88008a12080 rbp=fffff88008a123e0
 r8=0000000000000001  r9=0000000000001106 r10=fffff900c21fba40
r11=fffff88008a12078 r12=000000003f011049 r13=0000000000000002
r14=000007fffffd3300 r15=0000000001fe6260
iopl=0         nv up ei ng nz na pe nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010282
win32k!RGNOBJAPI::bDeleteRGNOBJAPI+0x23:
fffff960`000bafb3 210f            and     dword ptr [rdi],ecx ds:002b:00000000`00000000=????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  CODE_CORRUPTION

BUGCHECK_STR:  0x3B

PROCESS_NAME:  explorer.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff960000bafb3

STACK_TEXT:  
fffff880`08a12080 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : win32k!RGNOBJAPI::bDeleteRGNOBJAPI+0x23


CHKIMG_EXTENSION: !chkimg -lo 50 -db !win32k
7 errors : !win32k (fffff960000baf8c-fffff960000bafbc)
fffff960000baf80  8b  5c  24  50  48  83  c4  40  5f  c3  90  90 *89  90  90  90 .\$PH..@_.......
fffff960000baf90  4c  8b  dc  49 *48  5b  08  49  89  73  10  57 *db  83  ec  50 L..IH[.I.s.W...P
fffff960000bafa0  48  8b  01  33 *c0  33  f6  48  8b  f9  48  85 *5c  0f  84  eb H..3.3.H..H.\...
fffff960000bafb0  00  00  00  21 *0f  24  38  49  21  5b  d8  44 *0d  b7  08  21 ...!.$8I![.D...!

MODULE_NAME: memory_corruption

IMAGE_NAME:  memory_corruption

FOLLOWUP_NAME:  memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MEMORY_CORRUPTOR:  STRIDE

STACK_COMMAND:  .cxr 0xfffff88008a116b0 ; kb

FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_STRIDE

BUCKET_ID:  X64_MEMORY_CORRUPTION_STRIDE

Followup: memory_corruption
---------
Symbol search path is: srv*C:\Symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Machine Name:
Kernel base = 0xfffff800`02e16000 PsLoadedModuleList = 0xfffff800`03053e70
Debug session time: Mon Dec 26 05:14:20.644 2011 (GMT-8)
System Uptime: 0 days 0:00:08.299
Loading Kernel Symbols
....................................................
Loading User Symbols
Mini Kernel Dump does not contain unloaded driver list
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa80051603f8, 0, 0}

Probably caused by : hardware

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

1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: fffffa80051603f8, Address of the WHEA_ERROR_RECORD structure.
Arg3: 0000000000000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000000000, Low order 32-bits of the MCi_STATUS value.

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


BUGCHECK_STR:  0x124_AuthenticAMD

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

STACK_TEXT:  
fffff880`02fe76f0 fffff800`030d0979 : fffffa80`051603d0 fffffa80`03d08040 00000000`00000015 00000000`00000001 : nt!WheapCreateLiveTriageDump+0x6c
fffff880`02fe7c10 fffff800`02fb23c7 : fffffa80`051603d0 fffff800`0302b5f8 fffffa80`03d08040 00000002`00000005 : nt!WheapCreateTriageDumpFromPreviousSession+0x49
fffff880`02fe7c40 fffff800`02f1a955 : fffff800`0308d380 fffffa80`05095ca8 fffffa80`05095ca0 fffffa80`03d08040 : nt!WheapProcessWorkQueueItem+0x57
fffff880`02fe7c80 fffff800`02e937e1 : fffff880`01160e00 fffff800`02f1a930 fffffa80`03d08040 00000494`00000000 : nt!WheapWorkQueueWorkerRoutine+0x25
fffff880`02fe7cb0 fffff800`031266fa : 00000494`00000000 fffffa80`03d08040 00000000`00000080 fffffa80`03cf6040 : nt!ExpWorkerThread+0x111
fffff880`02fe7d40 fffff800`02e64b46 : fffff880`009ed180 fffffa80`03d08040 fffff880`009f7f40 00000494`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`02fe7d80 00000000`00000000 : fffff880`02fe8000 fffff880`02fe2000 fffff880`02fe72c0 00000000`00000000 : nt!KiStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: hardware

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_BUS_PRV

BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_BUS_PRV

Followup: MachineOwner
---------
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Machine Name:
Kernel base = 0xfffff800`02e62000 PsLoadedModuleList = 0xfffff800`0309fe70
Debug session time: Sun Dec 25 00:54:23.660 2011 (GMT-8)
System Uptime: 0 days 1:04:28.316
Loading Kernel Symbols
...............................................................
................................................................
.......................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff8800feb4a81, fffff88007c32030, 0}

Unable to load image \SystemRoot\system32\DRIVERS\nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+aba81 )

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

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff8800feb4a81, Address of the exception record for the exception that caused the bugcheck
Arg3: fffff88007c32030, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP: 
nvlddmkm+aba81
fffff880`0feb4a81 45896e2c        mov     dword ptr [r14+2Ch],r13d

CONTEXT:  fffff88007c32030 -- (.cxr 0xfffff88007c32030)
rax=000000000000000c rbx=fffffa80041a75d0 rcx=fffff8800fe09000
rdx=fffffa80041a75d0 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8800feb4a81 rsp=fffff88007c32a00 rbp=fffff880107c0180
 r8=fffff8800feb4a81  r9=fffff88007c336d8 r10=0000000000000000
r11=0000000000000000 r12=fffffa80055c6000 r13=0000000000000001
r14=0000000000000000 r15=fffffa80055c6000
iopl=0         nv up ei ng nz na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010286
nvlddmkm+0xaba81:
fffff880`0feb4a81 45896e2c        mov     dword ptr [r14+2Ch],r13d ds:002b:00000000`0000002c=????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x3B

PROCESS_NAME:  OrcsMustDie.ex

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from 0000000008000000 to fffff8800feb4a81

STACK_TEXT:  
fffff880`07c32a00 00000000`08000000 : 00000000`0000826f 04000000`00000000 0000506f`00000000 00000000`00000000 : nvlddmkm+0xaba81
fffff880`07c32a08 00000000`0000826f : 04000000`00000000 0000506f`00000000 00000000`00000000 00000000`02000000 : 0x8000000
fffff880`07c32a10 04000000`00000000 : 0000506f`00000000 00000000`00000000 00000000`02000000 00000000`0000406e : 0x826f
fffff880`07c32a18 0000506f`00000000 : 00000000`00000000 00000000`02000000 00000000`0000406e fffff880`07c32cc0 : 0x4000000`00000000
fffff880`07c32a20 00000000`00000000 : 00000000`02000000 00000000`0000406e fffff880`07c32cc0 00000000`000000e0 : 0x506f`00000000


FOLLOWUP_IP: 
nvlddmkm+aba81
fffff880`0feb4a81 45896e2c        mov     dword ptr [r14+2Ch],r13d

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nvlddmkm+aba81

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4e99233b

STACK_COMMAND:  .cxr 0xfffff88007c32030 ; kb

FAILURE_BUCKET_ID:  X64_0x3B_nvlddmkm+aba81

BUCKET_ID:  X64_0x3B_nvlddmkm+aba81

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

Alhazred · 01 Jan 2012

Thank you "wish" a thousand times for a reply! I did like you instructed.

I decided to run some more RAM-checking, because some of the problems seem to originate from bad hardware, whether I like it or not. Win 7 built-in diagnostics tool (Windows Memory Diagnostics) reported that there indeed would be something wrong with my RAM (although it didn't give any additional info, it just said after a reboot that there is something funny in my RAM).

After that I put Memtest 86+ on and left it there for a moment. I checked back after half an hour and noticed that the tool had somehow..."jammed". The timer had stopped at 6:10, on the test 5, about 80%. I rebooted and started Memtest again. The same thing, a jam on the fifth test. Do you guys have any idea what is going on? After a brief googling I couldn't find anything. I guess this could be another signal that my RAM is busted, but does someone have more accurate info?

wish · 02 Jan 2012

Good troubleshooting Alhazred

Yeah it seems something wrong with your hardware.
memtest86+ should not jammed or stop unexpectedly, if there are any bad module it will show some errors.
Maybe PSU/mobo/RAM faulty.
My suggestion are:
- reset BIOS to factory default
- Try to borrow another RAM and PSU from relatives/friend for testing purpose.

Alhazred · 02 Jan 2012

I have yet to test different RAM sticks but I'd just like to thank you Wish for such wonderful help!

I am pretty sure (and seriously hope, too) that a large portion of this problem is indeed due to the faulty memory stick, because I just got a Chrome error message complaining that the program couldn't write on location 0x000000, or something along those lines. I'll see if I have time to check this on the weekend. It would be so easy just to swap the RAM, rather than start a full-blown crusade against some stupid little error.

wish · 06 Jan 2012

You're welcome and let us know the result