BSODs, random restarts, lock-ups

cowvun · Mar 19, 2011

I've been having a ton of problems with BSODS, random restarts and lockups while gaming.
This only happens with graphical intensive games, so i kind of narrowed down what the issue is. Either it's my memory or my CPU is overheating. I had the same issues before using XP and decided to just reformat and run Windows 7 to see if the problem gets fixed.

Here is my .DMP File. Any help would be appreciated. Thanks.

Code:

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


Loading Dump File [C:\Users\Calvin\Desktop\031911-25615-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\Symbols*[URL]http://msdl.microsoft.com/download/symbols[/URL]
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17514.x86fre.win7sp1_rtm.101119-1850
Machine Name:
Kernel base = 0x82e19000 PsLoadedModuleList = 0x82f63850
Debug session time: Sat Mar 19 21:40:26.218 2011 (UTC - 4:00)
System Uptime: 0 days 3:17:07.138
Loading Kernel Symbols
...............................................................
................................................................
.................................
Loading User Symbols
Loading unloaded module list
.........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000008E, {c0000005, 9d8d76a8, 921f4b24, 0}

Probably caused by : win32k.sys ( win32k!HMChangeOwnerThread+25 )

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

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

KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
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.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: 9d8d76a8, The address that the exception occurred at
Arg3: 921f4b24, Trap Frame
Arg4: 00000000

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!HMChangeOwnerThread+25
9d8d76a8 8b89b8000000    mov     ecx,dword ptr [ecx+0B8h]

TRAP_FRAME:  921f4b24 -- (.trap 0xffffffff921f4b24)
ErrCode = 00000000
eax=ff91576c ebx=fdf9b800 ecx=00000000 edx=fdad0f20 esi=fea5c318 edi=ff9159a0
eip=9d8d76a8 esp=921f4b98 ebp=921f4ba4 iopl=0         nv up ei ng nz na pe nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010286
win32k!HMChangeOwnerThread+0x25:
9d8d76a8 8b89b8000000    mov     ecx,dword ptr [ecx+0B8h] ds:0023:000000b8=????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x8E

PROCESS_NAME:  APB.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from 9d91cdff to 9d8d76a8

STACK_TEXT:  
921f4ba4 9d91cdff fea5c318 ffa96dd8 00000000 win32k!HMChangeOwnerThread+0x25
921f4bbc 9d91d743 fdf9b8e8 0fbacbc5 00000000 win32k!MarkThreadsObjects+0x46
921f4c08 9d91ad58 8566dd48 8566dd48 00000000 win32k!xxxDestroyThreadInfo+0x715
921f4c1c 9d91aea5 8566dd48 00000001 8566dd48 win32k!UserThreadCallout+0x77
921f4c38 830834e2 8566dd48 00000001 a3fa44db win32k!W32pThreadCallout+0x3a
921f4cb4 83097051 00000001 88509560 00000001 nt!PspExitThread+0x457
921f4ccc 82eca8c0 88509560 921f4cf8 921f4d04 nt!PsExitSpecialApc+0x22
921f4d1c 82e572a4 00000001 00000000 921f4d34 nt!KiDeliverApc+0x28b
921f4d1c 775770b4 00000001 00000000 921f4d34 nt!KiServiceExit+0x64
WARNING: Frame IP not in any known module. Following frames may be wrong.
0304fbcc 00000000 00000000 00000000 00000000 0x775770b4


STACK_COMMAND:  kb

FOLLOWUP_IP: 
win32k!HMChangeOwnerThread+25
9d8d76a8 8b89b8000000    mov     ecx,dword ptr [ecx+0B8h]

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  win32k!HMChangeOwnerThread+25

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: win32k

IMAGE_NAME:  win32k.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4d23ea90

FAILURE_BUCKET_ID:  0x8E_win32k!HMChangeOwnerThread+25

BUCKET_ID:  0x8E_win32k!HMChangeOwnerThread+25

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

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

KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
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.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: 9d8d76a8, The address that the exception occurred at
Arg3: 921f4b24, Trap Frame
Arg4: 00000000

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!HMChangeOwnerThread+25
9d8d76a8 8b89b8000000    mov     ecx,dword ptr [ecx+0B8h]

TRAP_FRAME:  921f4b24 -- (.trap 0xffffffff921f4b24)
ErrCode = 00000000
eax=ff91576c ebx=fdf9b800 ecx=00000000 edx=fdad0f20 esi=fea5c318 edi=ff9159a0
eip=9d8d76a8 esp=921f4b98 ebp=921f4ba4 iopl=0         nv up ei ng nz na pe nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010286
win32k!HMChangeOwnerThread+0x25:
9d8d76a8 8b89b8000000    mov     ecx,dword ptr [ecx+0B8h] ds:0023:000000b8=????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x8E

PROCESS_NAME:  APB.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from 9d91cdff to 9d8d76a8

STACK_TEXT:  
921f4ba4 9d91cdff fea5c318 ffa96dd8 00000000 win32k!HMChangeOwnerThread+0x25
921f4bbc 9d91d743 fdf9b8e8 0fbacbc5 00000000 win32k!MarkThreadsObjects+0x46
921f4c08 9d91ad58 8566dd48 8566dd48 00000000 win32k!xxxDestroyThreadInfo+0x715
921f4c1c 9d91aea5 8566dd48 00000001 8566dd48 win32k!UserThreadCallout+0x77
921f4c38 830834e2 8566dd48 00000001 a3fa44db win32k!W32pThreadCallout+0x3a
921f4cb4 83097051 00000001 88509560 00000001 nt!PspExitThread+0x457
921f4ccc 82eca8c0 88509560 921f4cf8 921f4d04 nt!PsExitSpecialApc+0x22
921f4d1c 82e572a4 00000001 00000000 921f4d34 nt!KiDeliverApc+0x28b
921f4d1c 775770b4 00000001 00000000 921f4d34 nt!KiServiceExit+0x64
WARNING: Frame IP not in any known module. Following frames may be wrong.
0304fbcc 00000000 00000000 00000000 00000000 0x775770b4


STACK_COMMAND:  kb

FOLLOWUP_IP: 
win32k!HMChangeOwnerThread+25
9d8d76a8 8b89b8000000    mov     ecx,dword ptr [ecx+0B8h]

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  win32k!HMChangeOwnerThread+25

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: win32k

IMAGE_NAME:  win32k.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4d23ea90

FAILURE_BUCKET_ID:  0x8E_win32k!HMChangeOwnerThread+25

BUCKET_ID:  0x8E_win32k!HMChangeOwnerThread+25

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

sordid · Mar 19, 2011

How many RAM modules do you have in your box?

cowvun · Mar 19, 2011

I got four.

sordid · Mar 19, 2011

I'd try to test them in pairs.
Remove two and wait what happens - if the crashes occur again, replace those two and try again.
Damaged RAMs are the most common reason for your problem.

Oh, and try different banks on your mainboard.

cowvun · Mar 19, 2011

sordid said:
I'd try to test them in pairs.
Remove two and wait what happens - if the crashes occur again, replace those two and try again.
Damaged RAMs are the most common reason for your problem.

Oh, and try different banks on your mainboard.

If both pairs continue to have problems, should i start trying them individually?

sordid · Mar 19, 2011

Sure, good idea. But most of the time only one RAM module dies.
I had this a bunch of times - to be honest, the main reasons for BSODs are either a CPU overheating or a damaged RAM.

cowvun · Mar 19, 2011

sordid said:
Sure, good idea. But most of the time only one RAM module dies.
I had this a bunch of times - to be honest, the main reasons for BSODs are either a CPU overheating or a damaged RAM.

I also thought my CPU was overheating, but i monitored the temperatures. While playing games, my CPU was at 51c max, and that's when it BSOD on me, so i doubt overheating was the problem.

sordid · Mar 19, 2011

That's good - because replacing a single damaged RAM is way cheaper than a stir fried CPU.

cowvun · Mar 20, 2011

Alright, i just tested it out and i think it is a damaged ram causing the problem.
I want to see though if its the ram or the actual PCI slot, so i'm going to test out the slots since i got 4 and only have 2 2GB ram modules.

sordid · Mar 20, 2011

Good idea. Just try it all out.
Finding hardware errors can be a tedious task.

DeanP · Mar 20, 2011

http://www.sevenforums.com/crashes-debugging/96879-blue-screen-death-bsod-posting-instructions.html

BSODs, random restarts, lock-ups

cowvun

New member

My Computer

sordid

New member

My Computer

cowvun

New member

My Computer

sordid

New member

My Computer

cowvun

New member

My Computer

sordid

New member

My Computer

cowvun

New member

My Computer

sordid

New member

My Computer

cowvun

New member

My Computer

sordid

New member

My Computer

DeanP

Banned

My Computer