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.
"Display Driver ATI Family Radeon has stopped responding and has successfully recovered."

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: Windows 7 Professional 32-bit, HP Pavilion dv5 Notebook, AMD Turion(tm) X2 Dual-Core Mobile RM-70 (2 CPUs), ~2.0GHz, 2048MB RAM, ATI Mobility Radeon HD 3450,

Any help would be appreciated. Thanks!

Originally Posted by atikmdag

Usually the game unfreezes after about 3 minutes, but if the error occurs too many times it crashes the system.

Specs: Windows 7 Professional 32-bit, HP Pavilion dv5 Notebook, AMD Turion(tm) X2 Dual-Core Mobile RM-70 (2 CPUs), ~2.0GHz, 2048MB RAM, ATI Mobility Radeon HD 3450,

Any help would be appreciated. Thanks!

Hi atikmdag Welcome to D-A-L

When the system crashes do you get a BOSD (Blue Screen of Death)
If not could you disable Auto restart
Instructions on this here Automatic Restart Windows 7 - How To Disable the Automatic Restart on System Failure in Windows 7
Could you the post full details of the BSOD when the system crashes.
Could you also tell us what game your running when the system crashes?

Jim

hey,
when it crashes (as in from a game to a crash) what I usually see are white lines appearing on the screen until it covers the whole screen....or a completely black screen. in both cases laptop has to be restarted. (cold boot)

the following is the minidump of respective date(02.16.10):
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
---------



the following is another minidump of the respective date(02.17.10):

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


to name a few games: Killing Floor, Modern Warfare 2, Bioshock, Mass Effect

I ran memtest: no errors.

Hi atikmdag

I see the mini dump from the BSOD could you tell us full details of the BOSD as it first occurs
on your screen.

How long have you had this problem can you use System Restore to return to a position before the error occurred?

Could you also try a clean boot of Windows 7 to determine if something starting is causing your problem

Instructions on how to do this here How to troubleshoot a problem by performing a clean boot in Windows Vista or in Windows 7

Jim

I've had this problem since the first day. (last year)
clean boot didn't work, still got a BSOD

Hi atikmdag

We need the details of the BSOD.
So could you tell us the full details of the BSOD error?
Could go here Hardware Scan | D-A-L Computer Help
and do a hardware scan. When the scans completed could you
post the link for the scan at the top of the page here,
When you say "clean boot did not work."
Are you saying you could not do clean boot or when you try to do a clean boot you get a BSOD?
Did you try a System Restore?

Jim

umm what do you mean by 'the full details' of the BSOD? like the minidump details?

I attempted the scan but a 'fatal error' occurred
this is just the top paragraph of the notepad file:

#
# A fatal error has been detected by the Java Runtime Environment:
#
# Internal Error (0xe06d7363), pid=3464, tid=392
#
# JRE version: 6.0_17-b04
# Java VM: Java HotSpot(TM) Client VM (14.3-b01 mixed mode, sharing windows-x86 )
# Problematic frame:
# C [KERNELBASE.dll+0x9617]
#
# If you would like to submit a bug report, please visit:
# ["can't post links until I have 5 posts"]HotSpot Virtual Machine Error Reporting Page[/url]
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.
#

when I said clean boot did not work I meant to say a BSOD still occurs. sorry about the vagueness.

the earliest system restore is last week. so no point in doing that.
In one of the replies from hp's help and support emails they said I should revert back to the original OS (vista), but I told them that the error occurred right out of the box so doing that would make no difference.

Hi atikmdag

At the moment we have nothing tangible to go on to analyse your problem.
Did you follow the instructions here Automatic Restart Windows 7 - How To Disable the Automatic Restart on System Failure in Windows 7
To disable Automatic restart. Then if a BSOD does occur we will have something to go on.
The problem is that your minidump file is full of Symbols errors.
The problem in resolving this can be complicated as the Microsoft instruction here show
Use the Microsoft Symbol Server to obtain debug symbol files
There is a small freeware program from Resplendence which could give us the information we need.
It can be found here Resplendence Software - WhoCrashed, automatic crash dump analyzer
Download and install WhoCrashed
Then when you have the problem Start WhoCrashed and click on the Analyze Button
This will hopefully give you some information on what is causing your problem
Post that information here

Jim

Hello atikmdag,

Have you checked compatibility?
Just an FYI for you.

It is always best to check with the software manufacturer FIRST. They will tell you if they have tested the product and the version, as well as whether or not it will work with Windows 7.
Check out the Windows 7 Compatibility site (There you will find out about hardware and software compatibilty.)
There is a pulldown from which you can choose "hardware" and "software".

There are also some great articles, instructional videos and such to help with your Windows 7 at our Springboard site

In any event a lot of the times, Vista drivers will work in lieu of Windows 7 drivers, however, it's not 100%!

As stated previously, it's best to have the Windows 7 certified drivers installed.

Microsoft does have an official Windows 7 Support Forum. It is supported by product specialists as well as engineers and support teams. You may want to check the threads available there for additional assitance and support.

Thanks again,
John M.
Microsoft Windows Client Support