Tech Support Forum banner
Status
Not open for further replies.
1 - 20 of 21 Posts

·
Registered
Joined
·
15 Posts
Discussion Starter · #1 ·
Odd BSOD / LiveKernelEvent errors every so often when trying to boot

I have recently bought a second hand laptop - The Medion Akoya s5610 - please see this link for review. Full specs are: Medion Akoya s5610 Laptop, s5610 Motherboard, Intel Mobile Core2Duo P7350 2Ghz, Intel PM45 Chipset, 3GB PC2-5300 333Mhz DDR2 RAM, ATI Mobility Radeon HD3470 256mb, 320 GB HD.

Initially it wasnt working properly and needed a clean install of Vista. So after doing that i downloaded and installed all the drivers from the Medion website (as I didnt have the original setup disc).

Everything seemed to be ok, however after turning it off and leaving it overnight, the screen would sometimes flicker with green and pink stripes randomly or not show anything at all when turning it on. Now im not sure if Windows is still booting ok when the screen is off, but the blue led's were still flashing and working as normal, as if it was booting. It will take a few times of turning off and back on - or plugging the hdmi lead into the tv before the screen comes back on - and boots fine with no problem.

Now, this only happens after the laptop has been left off for a good 10 hours, if I were to turn it off now and back on it would seem to be fine. It is very strange.

I checked the Problem Reports and Solutions centre in Vista and it seems whenever this happens there has been a "Video Hardware Error". Please see below for the 2 events that usually occur:


Description
A problem with your video hardware caused Windows to stop working correctly.

Problem signature
Problem Event Name: LiveKernelEvent
OS Version: 6.0.6002.2.2.0.768.3
Locale ID: 2057

Files that help describe the problem
WD-20100728-1722.dmp
sysdata.xml
Version.txt

View a temporary copy of these files
Warning: If a virus or other security threat caused the problem, opening a copy of the files could harm your computer.

Extra information about the problem
BCCode: 117
BCP1: 8937B008
BCP2: 89F0D5E6
BCP3: 00000000
BCP4: 00000000
OS Version: 6_0_6002
Service Pack: 2_0
Product: 768_1

OR

"Shut Down Unexpectedly"

Problem signature
Problem Event Name: BlueScreen
OS Version: 6.0.6002.2.2.0.768.3
Locale ID: 2057

Files that help describe the problem (some files may no longer be available)
Mini072610-02.dmp
sysdata.xml
Version.txt

View a temporary copy of these files
Warning: If a virus or other security threat caused the problem, opening a copy of the files could harm your computer.

Extra information about the problem
BCCode: 116
BCP1: 89361008
BCP2: 89F0D5E6
BCP3: 00000000
BCP4: 00000002
OS Version: 6_0_6002
Service Pack: 2_0
Product: 768_1
Server information: 0a24dca4-70c8-4a36-a8f8-15495d97d2f3

All I can put this down to is a problem with the video drivers. I have installed the ones from the Medion site, then tried the one from the ATI site and have recently tried modding the driver with "mobility modder". All using "driver sweeper" to make sure I am doing a clean install each time.

The funny thing is I have tried leaving the laptop without the ATI drivers installed, and left the standard vga graphics driver running. This seems to fix the problem, as it switches on with no errors and no problems. The only problem with that is that I have a crappy resolution that I cant change.

I have attached the latest dump files from the last time I got a "LiveKernelEvent" error.

Please could someone suggest something to try and fix this as I can not return the laptop and to be fair it is a great laptop. It must be a driver issue as the temperature of the GPU is running fine and it isnt caused by demanding programs.:4-dontkno
 

Attachments

·
Registered
Joined
·
15 Posts
Discussion Starter · #2 ·
I have recently bought a second hand laptop - The Medion Akoya s5610 - Full specs are: Medion Akoya s5610 Laptop, s5610 Motherboard, Intel Mobile Core2Duo P7350 2Ghz, Intel PM45 Chipset, 3GB PC2-5300 333Mhz DDR2 RAM, ATI Mobility Radeon HD3470 256mb, 320 GB HD.

Initially it wasnt working properly and needed a clean install of Vista. So after doing that i downloaded and installed all the drivers from the Medion website (as I didnt have the original setup disc).

Everything seemed to be ok, however after turning it off and leaving it overnight, the screen would sometimes flicker with green and pink stripes randomly or not show anything at all when turning it on. Now im not sure if Windows is still booting ok when the screen is off, but the blue led's were still flashing and working as normal, as if it was booting. It will take a few times of turning off and back on - or plugging the hdmi lead into the tv before the screen comes back on - and boots fine with no problem.

Now, this only happens after the laptop has been left off for a good 10 hours, if I were to turn it off now and back on it would seem to be fine. It is very strange.

I checked the Problem Reports and Solutions centre in Vista and it seems whenever this happens there has been a "Video Hardware Error". Please see below for the 2 events that usually occur:


Description
A problem with your video hardware caused Windows to stop working correctly.

Problem signature
Problem Event Name: LiveKernelEvent
OS Version: 6.0.6002.2.2.0.768.3
Locale ID: 2057

Files that help describe the problem
WD-20100728-1722.dmp
sysdata.xml
Version.txt

View a temporary copy of these files
Warning: If a virus or other security threat caused the problem, opening a copy of the files could harm your computer.

Extra information about the problem
BCCode: 117
BCP1: 8937B008
BCP2: 89F0D5E6
BCP3: 00000000
BCP4: 00000000
OS Version: 6_0_6002
Service Pack: 2_0
Product: 768_1

OR

"Shut Down Unexpectedly"

Problem signature
Problem Event Name: BlueScreen
OS Version: 6.0.6002.2.2.0.768.3
Locale ID: 2057

Files that help describe the problem (some files may no longer be available)
Mini072610-02.dmp
sysdata.xml
Version.txt

View a temporary copy of these files
Warning: If a virus or other security threat caused the problem, opening a copy of the files could harm your computer.

Extra information about the problem
BCCode: 116
BCP1: 89361008
BCP2: 89F0D5E6
BCP3: 00000000
BCP4: 00000002
OS Version: 6_0_6002
Service Pack: 2_0
Product: 768_1
Server information: 0a24dca4-70c8-4a36-a8f8-15495d97d2f3

All I can put this down to is a problem with the video drivers. I have installed the ones from the Medion site, then tried the one from the ATI site and have recently tried modding the driver with "mobility modder". All using "driver sweeper" to make sure I am doing a clean install each time.

The funny thing is I have tried leaving the laptop without the ATI drivers installed, and left the standard vga graphics driver running. This seems to fix the problem, as it switches on with no errors and no problems. The only problem with that is that I have a crappy resolution that I cant change.

I have attached the latest dump files from the last time I got a "LiveKernelEvent" error.

Please could someone suggest something to try and fix this as I can not return the laptop and to be fair it is a great laptop. It must be a driver issue as the temperature of the GPU is running fine and it isnt caused by demanding programs

Dumpfiles
 

·
Decessit
Joined
·
68,881 Posts
Hi both the error codes you posted point to a Video_TDR_timeout error please follow the instructions here http://www.techsupportforum.com/f217/blue-screen-of-death-bsod-posting-instructions-452654.html and attach the info to your next post,this will allow me to ask one of the analyst to run them through a debug and narrow down the issue,as a general rule of thumb it is often a driver error but not always,it could also be card failure hopefully the debug will help us find out
 

·
Decessit
Joined
·
68,881 Posts
Hi as I said it could be but never bank on things with a computer, I have asked a analyst to look over the files so please be patient and he will get to you as soon as he can
 

·
Administrator, Manager, Microsoft Support, MVP
Joined
·
34,396 Posts
Re: Odd BSOD / LiveKernelEvent errors every so often when trying to boot

Hi -

The dump included in the RAR file is a "Watch Dog" dump related to the Live Kernel Event - video.

Bugcheck on the WD dump = 0x117 = Video TDR timeout = video driver did not reset in the alloted time - 30000ms = 30 secs -- but did ultimately recover.

These Symantec/ Norton drivers are odd, given extreme range (4 years) of timestamps -
Code:
[font=lucida console]
SRTSP.SYS    Sat Nov 18 01:00:27 [color=red]2006[/color] (455EA17B)
SRTSPX.SYS   Sat Nov 18 01:00:27 [color=red]2006[/color] (455EA17B)
SYMEVENT.SYS Wed Oct 18 00:13:40 [color=red]2006[/color] (4535A9F4)
SYMTDI.SYS   Mon Oct 23 20:26:29 [color=red]2006[/color] (453D5DB5)
SPBBCDrv.sys Fri Oct 06 17:01:22 [COLOR=red]2006[/COLOR] (4526C422)


NAVENG.SYS   Thu Jul 01 14:05:22 2010 (4C2CD8E2)
NAVEX15.SYS  Thu Jul 01 14:13:10 2010 (4C2CDAB6)
eeCtrl.sys   Fri May 21 17:44:53 2010 (4BF6FED5)
EraserUtilRebootDrv.sys Fri May 21 17:44:53 2010 (4BF6FED5)  
[/font]
Run Norton Removal Tool --> http://jcgriff2.com/NRT_N360_Removal.html

Your ATI video drivers appear current -
Code:
[font=lucida console]
atikmdag.sys Thu May 27 12:44:23 2010 (4BFEA167)
atikmpag.sys Thu May 27 12:25:19 2010 (4BFE9CEF)  
[/font]
I would suggest that you download and install fresh ones from ATI

Update Synaptics Touchpad driver -
Code:
[font=lucida console]
SynTP.sys    Fri Jan 04 14:42:51 2008 (477E8C3B)
[/font]
Synaptics --> http://www.synaptics.com/support/drivers

Update Realtek driver -
Code:
[font=lucida console]
Rtlh86.sys   Thu Feb 14 01:56:01 2008 (47B3E601)  
[/font]
Realtek --> http://218.210.127.131/

Update Intel wifi driver -
Code:
[font=lucida console]
NETw5v32.sys Sun Jun 07 10:50:32 2009 (4A2BD3B8)
[/font]
Intel --> http://downloadcenter.intel.com/Default.aspx


If BSODs persist, run the Driver Verifier --> http://jcgriff2.com/driver_verifier.htm


Windbg Logs
--> http://jcgriff2.com/dbug_logs/_99-dbug_nmarshall0_VistaSP2x86_07-28-2010_jcgriff2_.txt
--> http://jcgriff2.com/dbug_logs/_99-dbug_nmarshall0_VistaSP2x86_07-28-2010_jcgriff2_.txt.zip

I also suggest that you lose "Driver Sweeper"!

Please let me know how you make out.

Regards. . .

jcgriff2

`

BSOD BUGCHECK SUMMARY
Code:
[font=lucida console]
Built by: 6002.18209.x86fre.vistasp2_gdr.100218-0019
Debug session time: Wed Jul 28 12:21:21.888 2010 (GMT-4)
System Uptime: 0 days 0:00:40.653
*** WARNING: Unable to verify timestamp for dxgkrnl.sys
*** ERROR: Module load completed but symbols could not be loaded for dxgkrnl.sys
BugCheck 117, {8936f008, 89f0d5e6, 0, 0}
*** WARNING: Unable to verify timestamp for atikmpag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmpag.sys
Probably caused by : atikmpag.sys ( atikmpag+55e6 )
BUGCHECK_STR:  0x117
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  [/font]
 

·
Registered
Joined
·
15 Posts
Discussion Starter · #9 ·
Re: Odd BSOD / LiveKernelEvent errors every so often when trying to boot

Thanks much appreciated - I will try these suggestions and get back to you!
 

·
TSF Team Emeritus, Microsoft MVP
Joined
·
7,483 Posts
A series of STOP 0x116 and 0x117 errors usually indicates video problems - either with the drivers or with the card itself. As the 0x117 errors are very similar to the 0x116 errors - Please follow these instructions for troubleshooting: http://www.sevenforums.com/crash-lo...op-0x116-video_tdr_error-troubleshooting.html

The standard VGA drivers only use a limited number of features of the video card - so if the problem is in an unused feature you won't see any problems. Also, the more features are used, the more the card is worked, so the more heat it generates.

Have you blown out the vents of this laptop with canned air? (Don't use an air compressor or a vacuum as they can damage the hardware components). Is the fan working? Can you feel it blowing air out of the case?

In short, if you try everything and there's still problems - then it's gotta be a problem with the video card. On most laptops the graphics chipset is soldered on - and most people won't be able to replace these components.

Your antivirus program is very out of date, please do the following:
Anti-Virus Removal:
Please do the following:
- download a free antivirus for testing purposes: http://www.carrona.org/freeav.html
- uninstall the Norton from your system (you can reinstall it, if so desired, when we're done troubleshooting)
- remove any remnants of Norton using this free tool: http://service1.symantec.com/Support/tsgeninfo.nsf/docid/2005033108162039
- IMMEDIATELY install and update the free antivirus
- check to see if this fixes the BSOD's
Also, please remove or update these older drivers that were loaded at the time of the crash. Don't use Windows Update or the Update drivers function of Device Manager.
Please use the following instructions to locate the most currently available drivers to replace the one's that you uninstall OR remove:
How To Find Drivers:
- I have listed links to most of the drivers in the code box below. Please use the links there to see what info I've found about those drivers.
- search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
- if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.
- - The most common drivers are listed on this page: http://www.carrona.org/dvrref.html
- - Driver manufacturer links are on this page: http://www.carrona.org/drvrdown.html

Here's the older drivers (You can look them up here: http://www.carrona.org/dvrref.html ).
Please pay particular attention to any dated 2008 or earlier:
Code:
SRTSP.SYS    Sat Nov 18 01:00:27 2006 - Norton/Symantec AutoProtect - http://www.carrona.org/dvrref.html#SRTSP.SYS
SRTSPX.SYS   Sat Nov 18 01:00:27 2006 - Norton/Symantec AutoProtect - http://www.carrona.org/dvrref.html#SRTSPX.SYS
SYMEVENT.SYS Wed Oct 18 00:13:40 2006 - Norton/Symantec Event Library - http://www.carrona.org/dvrref.html#SYMEVENT.SYS
SPBBCDrv.sys Fri Oct 06 17:01:22 2006 - Norton/Symantec Firewall driver - http://www.carrona.org/dvrref.html#SPBBCDrv.sys
SYMREDRV.SYS Mon Oct 23 20:29:54 2006 - Norton/Symantec Redirector Filter driver - http://www.carrona.org/dvrref.html#SYMREDRV.SYS
Rtlh86.sys   Thu Feb 14 01:56:01 2008 - Realtek 8101/8168/8169 Wired Network Driver - http://www.carrona.org/dvrref.html#Rtlh86.sys
SynTP.sys    Fri Jan 04 14:42:51 2008 - Synaptic Touch Pad Driver - http://www.carrona.org/dvrref.html#SynTP.sys
BSOD BUGCHECK SUMMARY
Code:
[font=lucida console]
Built by: 6002.18209.x86fre.vistasp2_gdr.100218-0019
Debug session time: Wed Jul 28 12:22:45.384 2010 (UTC - 4:00)
System Uptime: 0 days 0:00:43.165
*** WARNING: Unable to verify timestamp for dxgkrnl.sys
*** ERROR: Module load completed but symbols could not be loaded for dxgkrnl.sys
BugCheck 116, {8937b008, 89f0d5e6, 0, 2}
*** WARNING: Unable to verify timestamp for atikmpag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmpag.sys
Probably caused by : atikmpag.sys ( atikmpag+55e6 )
BUGCHECK_STR:  0x116
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 6002.18209.x86fre.vistasp2_gdr.100218-0019
Debug session time: Wed Jul 28 12:21:21.904 2010 (UTC - 4:00)
System Uptime: 0 days 0:00:40.669
*** WARNING: Unable to verify timestamp for dxgkrnl.sys
*** ERROR: Module load completed but symbols could not be loaded for dxgkrnl.sys
BugCheck 116, {8936f008, 89f0d5e6, 0, 2}
*** WARNING: Unable to verify timestamp for atikmpag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmpag.sys
Probably caused by : atikmpag.sys ( atikmpag+55e6 )
BUGCHECK_STR:  0x116
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 6002.18209.x86fre.vistasp2_gdr.100218-0019
Debug session time: Mon Jul 26 15:44:30.345 2010 (UTC - 4:00)
System Uptime: 0 days 0:00:49.001
*** WARNING: Unable to verify timestamp for dxgkrnl.sys
*** ERROR: Module load completed but symbols could not be loaded for dxgkrnl.sys
BugCheck 116, {89361008, 89f0d5e6, 0, 2}
*** WARNING: Unable to verify timestamp for atikmpag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmpag.sys
Probably caused by : atikmpag.sys ( atikmpag+55e6 )
BUGCHECK_STR:  0x116
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 6002.18209.x86fre.vistasp2_gdr.100218-0019
Debug session time: Mon Jul 26 15:41:28.952 2010 (UTC - 4:00)
System Uptime: 0 days 0:00:49.717
*** WARNING: Unable to verify timestamp for dxgkrnl.sys
*** ERROR: Module load completed but symbols could not be loaded for dxgkrnl.sys
BugCheck 116, {89334008, 89f125e6, 0, 2}
*** WARNING: Unable to verify timestamp for atikmpag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmpag.sys
Probably caused by : atikmpag.sys ( atikmpag+55e6 )
BUGCHECK_STR:  0x116
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 6002.18209.x86fre.vistasp2_gdr.100218-0019
Debug session time: Sat Jul 24 05:32:52.355 2010 (UTC - 4:00)
System Uptime: 0 days 0:00:42.135
*** WARNING: Unable to verify timestamp for dxgkrnl.sys
*** ERROR: Module load completed but symbols could not be loaded for dxgkrnl.sys
BugCheck 116, {891b2008, 89f195e6, 0, 2}
*** WARNING: Unable to verify timestamp for atikmpag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmpag.sys
Probably caused by : atikmpag.sys ( atikmpag+55e6 )
BUGCHECK_STR:  0x116
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 6002.18209.x86fre.vistasp2_gdr.100218-0019
Debug session time: Sat Jul 24 05:25:08.949 2010 (UTC - 4:00)
System Uptime: 0 days 0:00:41.714
*** WARNING: Unable to verify timestamp for dxgkrnl.sys
*** ERROR: Module load completed but symbols could not be loaded for dxgkrnl.sys
BugCheck 116, {89337008, 89f0d5e6, 0, 2}
*** WARNING: Unable to verify timestamp for atikmpag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmpag.sys
Probably caused by : atikmpag.sys ( atikmpag+55e6 )
BUGCHECK_STR:  0x116
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 6002.18209.x86fre.vistasp2_gdr.100218-0019
Debug session time: Fri Jul 23 10:44:05.652 2010 (UTC - 4:00)
System Uptime: 0 days 0:01:30.438
*** WARNING: Unable to verify timestamp for dxgkrnl.sys
*** ERROR: Module load completed but symbols could not be loaded for dxgkrnl.sys
BugCheck 116, {88dd3510, 8da15bb2, 0, 2}
*** WARNING: Unable to verify timestamp for atikmdag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
Probably caused by : atikmdag.sys ( atikmdag+fbb2 )
BUGCHECK_STR:  0x116
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 6002.18209.x86fre.vistasp2_gdr.100218-0019
Debug session time: Fri Jul 23 10:42:10.804 2010 (UTC - 4:00)
System Uptime: 0 days 0:03:20.605
*** WARNING: Unable to verify timestamp for dxgkrnl.sys
*** ERROR: Module load completed but symbols could not be loaded for dxgkrnl.sys
BugCheck 116, {84740008, 8d61abb2, 0, 2}
*** WARNING: Unable to verify timestamp for atikmdag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
Probably caused by : atikmdag.sys ( atikmdag+fbb2 )
BUGCHECK_STR:  0x116
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 6002.18209.x86fre.vistasp2_gdr.100218-0019
Debug session time: Thu Jul 22 03:36:59.554 2010 (UTC - 4:00)
System Uptime: 0 days 0:01:00.365
*** WARNING: Unable to verify timestamp for dxgkrnl.sys
*** ERROR: Module load completed but symbols could not be loaded for dxgkrnl.sys
BugCheck 116, {8973c510, 8d819bb2, 0, 2}
*** WARNING: Unable to verify timestamp for atikmdag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
Probably caused by : atikmdag.sys ( atikmdag+fbb2 )
BUGCHECK_STR:  0x116
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 6002.18209.x86fre.vistasp2_gdr.100218-0019
Debug session time: Wed Jul 21 13:29:50.945 2010 (UTC - 4:00)
System Uptime: 0 days 0:02:47.742
*** WARNING: Unable to verify timestamp for dxgkrnl.sys
*** ERROR: Module load completed but symbols could not be loaded for dxgkrnl.sys
BugCheck 116, {84aca008, 8d810bb2, 0, 2}
*** WARNING: Unable to verify timestamp for atikmdag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
Probably caused by : atikmdag.sys ( atikmdag+fbb2 )
BUGCHECK_STR:  0x116
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 6002.18209.x86fre.vistasp2_gdr.100218-0019
Debug session time: Sun Jul 18 05:34:42.804 2010 (UTC - 4:00)
System Uptime: 0 days 0:00:24.585
BugCheck 1000008E, {c0000005, 9aeb2fca, 8c14da68, 0}
Probably caused by : win32k.sys ( win32k!xxxCheckFullScreen+b2 )
BUGCHECK_STR:  0x8E
PROCESS_NAME:  wininit.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 6002.18209.x86fre.vistasp2_gdr.100218-0019
Debug session time: Sun Jul 18 05:28:01.862 2010 (UTC - 4:00)
System Uptime: 0 days 0:00:37.642
*** WARNING: Unable to verify timestamp for dxgkrnl.sys
*** ERROR: Module load completed but symbols could not be loaded for dxgkrnl.sys
BugCheck 116, {89329008, 8de14bb2, 0, 2}
*** WARNING: Unable to verify timestamp for atikmdag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
Probably caused by : atikmdag.sys ( atikmdag+fbb2 )
BUGCHECK_STR:  0x116
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
  
  
 
[/font]
 

·
Registered
Joined
·
15 Posts
Discussion Starter · #14 ·
OK Usasma - I have removed the casing and blew out any dust (although it looks brand new) It doesnt get as hot as other laptops I have had so i guess thats not the problem.

I have been through the steps on the link you provided. I will run a Video Memory Stress test today and see what happens.

Jcgriff2 - I decided to do a clean install of Vista to start fresh without the Symantec Antivirus. I have also updated everything else to the latest driver versions. I have let windows update install the old drivers for the ATI 3400 series WITHOUT catalyst control centre, to limit features. As this is a periodic fail unfortunately I have to wait about 24 hours before finding out if this has made a difference.

If this does not work I will try installing the latest drivers. What I did notice was that when I download the 10.7 version software from the ATI website, it seems to only install catalyst control centre and not the driver. 10.6 worked OK but im not sure if I was doing something wrong?

If I still have problems how long do I have to run the Driver Verifier for? 24 hours? Could you specify what this actually does?

Joeten - No problem friend, I will eagerly await the analysts verdicts.

Thank you all for your attention.
 

·
Registered
Joined
·
15 Posts
Discussion Starter · #16 ·
OK - so I tried almost everything and it still didnt work. So I randomly removed the 1gb of ram from the laptop, leaving just the 2gb stick, and after 24 hours it may have fixed the problem. I hope so anyway because i really dont want to be paying loads for a new mobo.

i will post again tomorrow if it is still working ok - then other people might see and try this if they have a similar issue.
 

·
TSF Team Emeritus, Microsoft MVP
Joined
·
7,483 Posts
Driver Verifier is supposed to cause BSOD's - particularly in the drivers that are selected to be tested (and that have problems with the tests that are selected).
Run Driver Verifier for up to 36 hours - or until you start getting BSOD's

In the event that you don't get BSOD's from Driver Verifier - then the problem is usually due to hardware problems - although Windows issues can also be a cause.

If the RAM thing works - then you'll have solved your problem without the need for further testing. Good luck!
 

·
Registered
Joined
·
15 Posts
Discussion Starter · #18 ·
OK so im devastated - thought it may have been defective RAM but after an initial OK period iv got the usual LiveKernelEvent errors again and it takes me a few tries to get the screen to come on...

Havent tried updating BIOS yet - could this make a difference?
 

·
Registered
Joined
·
15 Posts
Discussion Starter · #19 ·
OK - updated the BIOS sucessfully - still doesnt work though. I am nearly at breaking point, I am running out of thing to try.

I have got some DNA-Ati drivers that I am going to try out tonight, then I will do a driver verifier run for 36 hours.

After that im going to throw it in the bin...:sigh:
 

·
Registered
Joined
·
15 Posts
Discussion Starter · #20 ·
Could it be that the driver is failing to shut down correctly during windows shut down which causes the TDR? If I were to dual boot to say xp also, and try XP would this determine weather it is a driver problem or not? Thanks.
 
1 - 20 of 21 Posts
Status
Not open for further replies.
Top