[gtmodder]

Whenever I run a game on my laptop it freezes after about 20 minutes of gameplay.
Single-player and Multi-player.
The error only occurs when I play games, full-screen video players work just fine.
When I play in window mode I can see the following error message pop-up:
http://img193.imageshack.us/img193/804/atierror1.jpg

Original OS was vista and the error message said "atikmdag" instead of "ATI Family Radeon"
I have already updated my display driver.
I have a cooling fan.
Usually the game unfreezes after about 3 minutes, but if the error occurs too many times it crashes the system.

Specs: http://img689.imageshack.us/img689/8891/50467270.png

Any help would be appreciated. Thanks!

[joeten]

Hi and welcome to TSG test your card you can use something like occt,furmark,prime95

[gtmodder]

hey, I tested my card using Furmark, the screen goes black, then the furmark thing appears for like 2 minutes or so, and then it just goes black again and nothing happens....I had to end the program via task manager.
what does that mean?

[gtmodder]

I got a BSOD
Can someone have a look at it?

this is what I got for yesterdays BSOD:
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\021610-20342-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 \SystemRoot\system32\ntkrnlpa.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Windows 7 Kernel Version 7600 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16481.x86fre.win7_gdr.091207-1941
Machine Name:
Kernel base = 0x82c4c000 PsLoadedModuleList = 0x82d94810
Debug session time: Tue Feb 16 18:49:01.020 2010 (GMT-5)
System Uptime: 0 days 0:00:09.798
*********************************************************************
* 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 \SystemRoot\system32\ntkrnlpa.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Loading Kernel Symbols
...............................................................
......................
Loading User Symbols
*************************************************************************** ****
* *
* Bugcheck Analysis *
* *
*************************************************************************** ****

Use !analyze -v to get detailed debugging information.

BugCheck A, {5434, 2, 0, 82c7f538}

*** WARNING: Unable to verify timestamp for mssmbios.sys
*** ERROR: Module load completed but symbols could not be loaded for mssmbios.sys
***** 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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 : ntkrnlpa.exe ( nt+33538 )

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



This is for todays BSOD:



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


Loading Dump File [C:\Windows\Minidump\021710-21886-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 \SystemRoot\system32\ntkrnlpa.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Windows 7 Kernel Version 7600 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16481.x86fre.win7_gdr.091207-1941
Machine Name:
Kernel base = 0x82c4e000 PsLoadedModuleList = 0x82d96810
Debug session time: Wed Feb 17 22:39:44.016 2010 (GMT-5)
System Uptime: 0 days 0:00:11.918
*********************************************************************
* 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 \SystemRoot\system32\ntkrnlpa.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Loading Kernel Symbols
...............................................................
......................
Loading User Symbols
*************************************************************************** ****
* *
* Bugcheck Analysis *
* *
*************************************************************************** ****

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {c0000005, 82e7008f, 80786890, 80786470}

*** WARNING: Unable to verify timestamp for mssmbios.sys
*** ERROR: Module load completed but symbols could not be loaded for mssmbios.sys
***** 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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 : ntkrnlpa.exe ( nt+22208f )

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

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

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
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: 82e7008f, The address that the exception occurred at
Arg3: 80786890, Exception Record Address
Arg4: 80786470, Context Record Address

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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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+ *
*********************************************************************

ADDITIONAL_DEBUG_TEXT:
Use '!findthebuild' command to search for the target build information.
If the build information is available, run '!findthebuild -s ; .reload' to set symbol path and load symbols.

MODULE_NAME: nt

FAULTING_MODULE: 82c4e000 nt

DEBUG_FLR_IMAGE_TIMESTAMP: 4b1e090a

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

FAULTING_IP:
nt+22208f
82e7008f 0fb702 movzx eax,word ptr [edx]

EXCEPTION_RECORD: 80786890 -- (.exr 0xffffffff80786890)
ExceptionAddress: 82e7008f (nt+0x0022208f)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 00000000
Parameter[1]: 00000858
Attempt to read from address 00000858

CONTEXT: 80786470 -- (.cxr 0xffffffff80786470)
eax=80786900 ebx=00000000 ecx=85dff4fc edx=00000858 esi=80786990 edi=00000007
eip=82e7008f esp=80786958 ebp=80786968 iopl=0 nv up ei pl nz ac po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010212
nt+0x22208f:
82e7008f 0fb702 movzx eax,word ptr [edx] ds:0023:00000858=????
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0x7E

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from 82e6ff6d to 82e7008f

STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
80786968 82e6ff6d 89a64d60 85dff4fc 00000000 nt+0x22208f
807869a4 82e56fec 85dff510 85e00000 85dff520 nt+0x221f6d
807869bc 82df185c 85dff520 00000000 85c7bff0 nt+0x208fec
80786b9c 82fff853 00000001 00000000 80786bd4 nt+0x1a385c
80786be8 82ffb87b 80810ed0 8080a560 00000000 nt+0x3b1853
80786c6c 83000e6f 0080a560 84c39a40 84c396d0 nt+0x3ad87b
80786d48 82dd947c 80786d90 82e5c66d 8080a560 nt+0x3b2e6f
80786d50 82e5c66d 8080a560 aae0e5c1 00000000 nt+0x18b47c
80786d90 82d0e1d9 82dd946f 8080a560 00000000 nt+0x20e66d
00000000 00000000 00000000 00000000 00000000 nt+0xc01d9


FOLLOWUP_IP:
nt+22208f
82e7008f 0fb702 movzx eax,word ptr [edx]

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: nt+22208f

FOLLOWUP_NAME: MachineOwner

IMAGE_NAME: ntkrnlpa.exe

STACK_COMMAND: .cxr 0xffffffff80786470 ; kb

BUCKET_ID: WRONG_SYMBOLS

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

0: kd> lmvm nt
start end module name
82c4e000 8305e000 nt T (no symbols)
Loaded symbol image file: ntkrnlpa.exe
Image path: \SystemRoot\system32\ntkrnlpa.exe
Image name: ntkrnlpa.exe
Timestamp: Tue Dec 08 03:06:34 2009 (4B1E090A)
CheckSum: 003C665C
ImageSize: 00410000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4

[joeten]

Hi this is some info on your error
0x0000007E: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
(Click to consult the online MSDN article.)
A system thread generated an exception which the error handler did not catch. There are numerous individual causes for this problem, including hardware incompatibility, a faulty device driver or system service, or some software issues. Check Event Viewer (EventVwr.msc) for additional information
info found here http://aumha.org/a/stop.htm
Have you updated the driver,your issue with testing is possibly idicative of failing hardware but you might try occt to stress test it again and try to confirm http://www.ocbase.com/perestroika_en/

[gtmodder]

ran memtest - no errors

ran cpu : occt - cpu too hot!
http://img685.imageshack.us/img685/8...819h49cpu2.png
http://img514.imageshack.us/img514/4...819h49gpu1.png

ran cpu : linpack - cpu too hot!
http://img194.imageshack.us/img194/6...819h59cpu2.png
http://img62.imageshack.us/img62/612...819h59gpu1.png

ran gpu : occt - no errors
http://img62.imageshack.us/img62/844...819h57cpu2.png
http://img186.imageshack.us/img186/2...819h57gpu1.png

I was planning on uninstalling all my drivers and downloading them from only the hp website.
should I skip that? looks like I need to clean my fan?

[joeten]

Hi a good clean will help so would a new application of heatsink paste,also updating the drivers is not a bad idea

[gtmodder]

well I cleaned out the laptop (wasn't that dirty anyways)
updated all the drivers I could from the hp website.
one thing I noticed after trying out some games was that Left 4 Dead 2 ran perfectly for about an hour, then I switched to Modern Warfare 2 and not even 2 minutes in and it started freezing up on me...confusing...
ran OCCT (it still says the cpu overheated?)

[joeten]

Hi then you may need to try a new coat of heatsink paste as I suggested before

[gtmodder]

ok I'll try that but it doesn't quite make sense to me.
I mean the problem has been occurring ever since I got this laptop last year...so you're suggesting the manufacturers didn't apply the heatsink paste properly in the first place?

[gtmodder]

once I get the paste, where would I apply it?
http://img203.imageshack.us/img203/6682/img1870r.jpg
I didn't take a picture of the other side...=\

[joeten]

Hi this may give you some idea http://www.insidemylaptop.com/apply-...top-processor/

[Triple6]

Reopening thread as requested.

[Triple6]

What is the exact model of your laptop? The full model should be on a sticker on the bottom of the laptop.

Have you checked for a BIOS update? A lot of HP's have BIOS updates that improve cooling and stability.

Also try the latest drivers from ATI rather then HP: http://www2.ati.com/relnotes/Catalys...ease_notes.pdf

[gtmodder]

building on Joeten's reply
I finally got a chance to apply the thermal paste after a good number of setbacks, anyhow, that didn't work =\

Model: HP Pavilion dv5z-1000 CTO Entertainment Notebook PC

BIOS update, do you mean this?: http://h10025.www1.hp.com/ewfrf/wc/s...roduct=3759541

will try to update drivers again and let you know