issue with rebooting while playing games..

[imported_Malken]

its rather random.. but while playing everquest 2.. my system randomly just reboots. it gets a blue screen that goes away real quick so i cant read it.. then reboots itself. This just started happening in the last couple weeks, it only happens while playing everquest 2. I tried formatting and starting fresh last night, but it still does it.

It's not al the time tho, usually once per night or 2.. about once every 8-10 hours of playing. What could cause that to be happening?

system specs:

winxp os
Gigabyte M1689d motherboard
Amd Athlon 64 3400+
2gb DDR ram, made by Mushkin, forgot model number er anything
radeon x850 agp vid card
WD 74gb raptor HD
Antec 430w power supply
Lite-on LTR cd-rom

siw is showing my cpu temp at 42 cel and HDD temp at 32 cel.. not sure if thats high or lower if its overheating er anything.. thats also with nothing running but ie and siw..

 

[robisbell]

Power Issue.

 

[imported_Malken]

power issue... like.. i need a new power supply perhaps?

 

[robisbell]

yes.

 

[jackschmittusa]

Heat! It could be a number of components: vid card, NB, ram, cpu, hd, and even the psu, but it sure sounds like a thermal problem with one of the aforementioned getting too hot after an exrended period of heavy use.

 

[Old Hippie]

siw is showing my cpu temp at 42 cel and HDD temp at 32 cel.. not sure if thats high or lower if its overheating er anything.. thats also with nothing running but ie and siw..

Looks like the max temp for that chip is 60C. If you're idling at 42, I'll bet your hitting 60 while gaming.
How long has it been since you cleaned that thing?

Then again, it could be that PS............

 

[dclive]

Originally posted by: Malken
its rather random.. but while playing everquest 2.. my system randomly just reboots. it gets a blue screen that goes away real quick so i cant read it.. then reboots itself. This just started happening in the last couple weeks, it only happens while playing everquest 2. I tried formatting and starting fresh last night, but it still does it.

It's not al the time tho, usually once per night or 2.. about once every 8-10 hours of playing. What could cause that to be happening?

system specs:

winxp os
Gigabyte M1689d motherboard
Amd Athlon 64 3400+
2gb DDR ram, made by Mushkin, forgot model number er anything
radeon x850 agp vid card
WD 74gb raptor HD
Antec 430w power supply
Lite-on LTR cd-rom

siw is showing my cpu temp at 42 cel and HDD temp at 32 cel.. not sure if thats high or lower if its overheating er anything.. thats also with nothing running but ie and siw..

Don't guess. Read my web page, download the MS debugger, debug your dumps, post the results of '!analyze -v' from a few of them here, and I'll look at them.

 

[oynaz]

Originally posted by: robisbell
Power Issue.

Yes it might be a power issue. But it could also be a mobo issue, a RAM issue, a failing HDD, a driver issue, a botched game upgrade, malware problems or a CPU issue.

I would suggest following dclive's suggestion instead of taking a shot in the dark and possibly wasting money on a new PSU which could or could not solve the problem.

 

[imported_Malken]

I read your site some... but uh. i'm kindof computer illiterate for the most part.. but i got the program d/l'ed.. I just formatted so i only had one file in the minidump folder so far.. only 1 crash.. this is what i got from it.. is this what you needed posted? i'll prolly get another one durin the week sometime and i can post more 'n stuff

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


Loading Dump File [C:\WINDOWS\Minidump\Mini011108-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: *** Invalid ***
****************************************************************************
* Symbol loading may be unreliable without a symbol search path. *
* Use .symfix to have the debugger choose a symbol path. *
* After setting your symbol path, use .reload to refresh symbol locations. *
****************************************************************************
Executable search path is:
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805531a0
Debug session time: Fri Jan 11 16:24:04.312 2008 (GMT-8)
System Uptime: 0 days 3:58:43.903
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Loading Kernel Symbols
........................................................................................................................
Loading User Symbols
Loading unloaded module list
...............
Unable to load image ati3duag.dll, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ati3duag.dll
*** ERROR: Module load completed but symbols could not be loaded for ati3duag.dll
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000008E, {c0000005, bf251a1e, aa528938, 0}

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Probably caused by : ati3duag.dll ( ati3duag+e1a1e )

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

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: bf251a1e, The address that the exception occurred at
Arg3: aa528938, Trap Frame
Arg4: 00000000

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

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************

FAULTING_MODULE: 804d7000 nt

DEBUG_FLR_IMAGE_TIMESTAMP: 475610a4

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

FAULTING_IP:
ati3duag+e1a1e
bf251a1e 8b44242c mov eax,dword ptr [esp+2Ch]

TRAP_FRAME: aa528938 -- (.trap 0xffffffffaa528938)
ErrCode = 00000000
eax=00000001 ebx=00000800 ecx=00000001 edx=e29a9a78 esi=e3b85548 edi=00000000
eip=bf251a1e esp=aa5289ac ebp=00000080 iopl=0 nv up ei pl zr na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246
ati3duag+0xe1a1e:
bf251a1e 8b44242c mov eax,dword ptr [esp+2Ch] ss:0010:aa5289d8=00000000
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WRONG_SYMBOLS

BUGCHECK_STR: 0x8E

LAST_CONTROL_TRANSFER: from e3b85548 to bf251a1e

STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
aa5289a8 e3b85548 e29a9a78 e11dc010 00002199 ati3duag+0xe1a1e
aa5289ac e29a9a78 e11dc010 00002199 e14a6010 0xe3b85548
aa5289b0 e11dc010 00002199 e14a6010 00000001 0xe29a9a78
aa5289b4 00000000 e14a6010 00000001 00000000 0xe11dc010


STACK_COMMAND: kb

FOLLOWUP_IP:
ati3duag+e1a1e
bf251a1e 8b44242c mov eax,dword ptr [esp+2Ch]

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: ati3duag+e1a1e

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: ati3duag

IMAGE_NAME: ati3duag.dll

BUCKET_ID: WRONG_SYMBOLS

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

kd> lmvm ati3duag
start end module name
bf170000 bf4774a0 ati3duag T (no symbols)
Loaded symbol image file: ati3duag.dll
Image path: ati3duag.dll
Image name: ati3duag.dll
Timestamp: Tue Dec 04 18:44:52 2007 (475610A4)
CheckSum: 0030C754
ImageSize: 003074A0
Translations: 0000.04b0 0000.04e0 0409.04b0 0409.04e0

 

[dclive]

Well, you didn't follow the directions and key in the symbol file path correctly (please re-read the directions) but assuming nothing else changes, your ATI drivers are to blame. I see they're from Dec 4 2007, so they're recent. If you can update them, do so. If you cannot, roll back to a prior release, and see if that fixes your problem. If not, replace your ATI card with an nVidia card, or send the dumps to ATI so they can figure out what's wrong.

I'd now like everyone that said this was a power issue to explain why.

 

[imported_Malken]

ok.. i think i got it right now.. doesnt seem like it changed tho.. came up as this... cant afford a new vid card.. so I'll probably try to roll back the drivers.. i believe this started about 4 er 5 months ago.. would it make any difference if i used CCC? I've never installed it, i've just installed the drivers and WDM thingies and thats it


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


Loading Dump File [C:\WINDOWS\Minidump\Mini011108-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\debug*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp2_rtm.040803-2158
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805531a0
Debug session time: Fri Jan 11 16:24:04.312 2008 (GMT-8)
System Uptime: 0 days 3:58:43.903
Loading Kernel Symbols
........................................................................................................................
Loading User Symbols
Loading unloaded module list
...............
Unable to load image ati3duag.dll, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ati3duag.dll
*** ERROR: Module load completed but symbols could not be loaded for ati3duag.dll
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000008E, {c0000005, bf251a1e, aa528938, 0}



Probably caused by : ati3duag.dll ( ati3duag+e1a1e )

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

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: bf251a1e, The address that the exception occurred at
Arg3: aa528938, 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:
ati3duag+e1a1e
bf251a1e 8b44242c mov eax,dword ptr [esp+2Ch]

TRAP_FRAME: aa528938 -- (.trap 0xffffffffaa528938)
ErrCode = 00000000
eax=00000001 ebx=00000800 ecx=00000001 edx=e29a9a78 esi=e3b85548 edi=00000000
eip=bf251a1e esp=aa5289ac ebp=00000080 iopl=0 nv up ei pl zr na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246
ati3duag+0xe1a1e:
bf251a1e 8b44242c mov eax,dword ptr [esp+2Ch] ss:0010:aa5289d8=00000000
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0x8E

PROCESS_NAME: EverQuest2.exe

LAST_CONTROL_TRANSFER: from e3b85548 to bf251a1e

STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
aa5289a8 e3b85548 e29a9a78 e11dc010 00002199 ati3duag+0xe1a1e
aa5289ac e29a9a78 e11dc010 00002199 e14a6010 0xe3b85548
aa5289b0 e11dc010 00002199 e14a6010 00000001 0xe29a9a78
aa5289b4 00000000 e14a6010 00000001 00000000 0xe11dc010


STACK_COMMAND: kb

FOLLOWUP_IP:
ati3duag+e1a1e
bf251a1e 8b44242c mov eax,dword ptr [esp+2Ch]

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: ati3duag+e1a1e

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: ati3duag

IMAGE_NAME: ati3duag.dll

DEBUG_FLR_IMAGE_TIMESTAMP: 475610a4

FAILURE_BUCKET_ID: 0x8E_ati3duag+e1a1e

BUCKET_ID: 0x8E_ati3duag+e1a1e

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

 

[imported_Malken]

also.. would it really matter how far i rolled them back? what exactly do newer drivers do? would it affect performance er anything?

Catalyst 7.11 8.432 November 21, 2007
Catalyst 7.10 8.421 October 11, 2007
Catalyst 7.9 8.411 September 10, 2007
Catalyst 7.8 8.401 August 13, 2007
Catalyst 7.7 8.391 July 19, 2007
Catalyst 7.6 8.383 June 25, 2007
Catalyst 7.5 8.38 May 31, 2007
Catalyst 7.4 8.36 April 18, 2007
Catalyst 7.3 8.351 March 28, 2007
Catalyst 7.2 8.342 February 21, 2007
Catalyst 7.1 8.33 January 10, 2007
Catalyst 6.12 8.321 December 13, 2006


those are the ones i can choose from it seems on ati's site.. i know this was not happening from september back.. so should i just use the september ones, or go back even further? or does it even matter

 

[dclive]

Use whatever works.... if it happens again, just analyze the dump, confirm the problem, then jump to another driver.


CCC isn't needed; I suggest you avoid it.

 

[imported_Malken]

alrighty then.. thank you for the help


... raspberry cheesecake is awesome !!!!!!!!!!!!!

 

[fachmannn]

The problem is most deffinatly heat or power problems, had the same thing happen with Guild Wars and it was an over-heating GPU, reseated it and it ran fine ever since.

 

[dclive]

Originally posted by: fachmannn
The problem is most deffinatly heat or power problems, had the same thing happen with Guild Wars and it was an over-heating GPU, reseated it and it ran fine ever since.

In that case, that may have been true. In this case, the problem is with the ATI driver (or a related ATI subsystem - the ATI card itself could be bad), as the debugger has proven. How in the world can you say the problem is "most deffinatly (sic) heat or power problems" when you don't know anything about what's happening with the OP's machine?

 

[robisbell]

dc, sounds like you need to listen to your own advice, still stuck in the rut I see.

 

[oynaz]

It might be a RAM problem as well. I have seen what seemed like a driver problem actually being defective RAM. I guess a memtest 86+ run won't hurt.

BTW, ATI cards have been prone to overheating due to some inadequate cooling systems. This might cause your symptoms as well IIRC.

 

[dclive]

Originally posted by: robisbell
dc, sounds like you need to listen to your own advice, still stuck in the rut I see.

You apparently didn't read his dumpfile. It's an ATI driver issue.

Please detail how and why you think this is a power issue.

 

[dclive]

Originally posted by: oynaz
It might be a RAM problem as well. I have seen what seemed like a driver problem actually being defective RAM. I guess a memtest 86+ run won't hurt.

BTW, ATI cards have been prone to overheating due to some inadequate cooling systems. This might cause your symptoms as well IIRC.

Guys, we got the memory dump that Windows generates when the system went down. It pointed to the ATI driver. It's either literally the ATI driver, or something in the ATI driver's chain - like the ATI hardware.

If it were power (or hardware in general) we'd see all kinds of (different) random errors. We don't. We see one consistent error.

That's it. Case closed.

 

[oynaz]

That's it. Case closed.

So Malkens's problem has been solved? We can close the thread?

 

[robisbell]

ask the OP.

 

[imported_Malken]

seems to be solved... I stuck in some old drivers... had almost 20 hours of playtime so far.. really tryin to test it... hasent crashed once... think this is the longest its lasted since the crashes started happenin

 

[dclive]

Malken, you IM'd me with a new issue, but here you wrote it was fixed, so I'm not sure what is wrong. Please post (in here or in another posting) if there is a new problem rather than IM. That way everyone can see and learn how to resolve those kinds of issues.

 

[phaedrus73]

I used to have a very similar issue. It mostly would happen when playing World of Warcraft. Sometimes with other games, but I didnt play them to much. the problem turned out to be the CPU overheating. When I turned off the computer and looked at the Cooling unit on my CPU it was COVERED in cat hair and dust bunnies. I sprayed out my computer with compressed air, and everything was fine. I'd check to see if yours is covered in dust as well.