- Thread Author
-
- #1
Hi
I might be unusual in that I already have a good idea whats causing my BSODs in my new Win7 installation.
I have old ASUS drivers which are for my P5N-E sli Motherboard I believe and one in particular ASACPI.sys
However when I try to update this driver Windows 7 says the software for the driver is up to date! Umm no its not as its dated 2004 and I have a later driver for it to use! Any idea how to get round that issue????
Anyway here are my specs and the CPU-Z shots etc you wanted.
Win 7 Home Premium 32Bit Version 6.17601 SP1
Intel Q6600 2.4Gig CPU
2 Gig of Ram
P5N-E Sli Motherboard
ASUS GTX560 Ti Video Card
Cheers
Baz
I might be unusual in that I already have a good idea whats causing my BSODs in my new Win7 installation.
I have old ASUS drivers which are for my P5N-E sli Motherboard I believe and one in particular ASACPI.sys
However when I try to update this driver Windows 7 says the software for the driver is up to date! Umm no its not as its dated 2004 and I have a later driver for it to use! Any idea how to get round that issue????
Anyway here are my specs and the CPU-Z shots etc you wanted.
Win 7 Home Premium 32Bit Version 6.17601 SP1
Intel Q6600 2.4Gig CPU
2 Gig of Ram
P5N-E Sli Motherboard
ASUS GTX560 Ti Video Card
Cheers
Baz
Solution
- Thread Author
-
- #2
Just had another one.:
Had another crash so have attached the screen captures of the Blue screenview errors and the Device manager.
So I thought I would try uninstalling the ATK0110 ACPI Utility and the graphics card and all its software. I then rebooted reinstalled the graphics card then tried to update the ATK0110 ACPI Utility driver (which had come back after the reboot(!) but this keeps on saying it has the latest driver (2004) even though I try and install a newer driver which I downloaded (ATKDrv_V1043231105_Win7_32) which has this file atkacpi.sys dated 2009 inside it. When you try and run this part PNPINST which is the exe file it comes up with the error which I have attached.
So for some reason it doesn't want to let go of the old driver. Bad bad Windows!
Had another crash so have attached the screen captures of the Blue screenview errors and the Device manager.
So I thought I would try uninstalling the ATK0110 ACPI Utility and the graphics card and all its software. I then rebooted reinstalled the graphics card then tried to update the ATK0110 ACPI Utility driver (which had come back after the reboot(!) but this keeps on saying it has the latest driver (2004) even though I try and install a newer driver which I downloaded (ATKDrv_V1043231105_Win7_32) which has this file atkacpi.sys dated 2009 inside it. When you try and run this part PNPINST which is the exe file it comes up with the error which I have attached.
So for some reason it doesn't want to let go of the old driver. Bad bad Windows!
Elmer
Extraordinary Member
- Joined
- Mar 5, 2010
- Messages
- 3,864
Hi baz62 and Welcome to The Forum.
Never rely on Windows Update or Device Manager to update your drivers until you've exhausted your PC Mfr., Motherboard Mfr. or the software/hardware Mfr. resources.
To stop Windows installing drivers Automatically
Go to Control Panel >> Devices and Printers, r-click your computer icon and select Device installation settings. Select Never install driver software from Windows Update >> Save Changes
Driver Install - Manual method
- Download the driver and extract it to a folder.
- Open the Device Manager.
- Right click the device you wish to change the drivers for. You can select Properties > Driver > Driver Details to check you have the right device.
- Choose Update Driver Software.
- Select Browse My Computer For Driver Software.
- Select Let me pick from a list of device drivers on my computer.
- Select Have disk...
- Select Browse..
- Navigate to the extracted folder and double click on the .inf file
- Hit OK, then Next and the driver(s) will then begin to install.
- After it has installed, GoTo C:\Windows\System32\Drivers. Locate the Asacpi.sys driver, right click it and check the dates under its properties. You're looking for a "Modified" date of 2009 or 2010. Occasionally it can be a bit stubborn to change.
Your RAM timings are set to 6-6-6-31 when it should be set to 6-6-6-18
HTH Will look at your dumpfile. Edit!! No I won't there isn't one. I NEED SLEEP!
Last edited:
- Thread Author
-
- #4
Ah Yeeeeeeees I know about not using Windows update or Device manager.
However I did go to the link you had to see if it was a different driver to the one i got off the net and surprise surprise it was! ASUS need shooting as it had nothing about this driver with my Motherboard support! I ran the installer and it seems to have worked with the date for the driver now being 2009. The other problem driver or bit of software was the ASUSTeK Display Lower Filter but this is dated 2009 and was created on the date I installed Windows 7. Wonder if there is an update for that?
The dump files you mention (from a couple of days ago) are attached.
Fingers crossed this update has magically fixed things......but I won't hold my breath!
However I did go to the link you had to see if it was a different driver to the one i got off the net and surprise surprise it was! ASUS need shooting as it had nothing about this driver with my Motherboard support! I ran the installer and it seems to have worked with the date for the driver now being 2009. The other problem driver or bit of software was the ASUSTeK Display Lower Filter but this is dated 2009 and was created on the date I installed Windows 7. Wonder if there is an update for that?
The dump files you mention (from a couple of days ago) are attached.
Fingers crossed this update has magically fixed things......but I won't hold my breath!
Elmer
Extraordinary Member
- Joined
- Mar 5, 2010
- Messages
- 3,864
Hi Baz. Those are just my canned speeches. Everybody gets them !
Most of your dump files list the following error:
STOP 0x00000116: VIDEO_TDR_ERROR
Usual causes: Video driver, overheating, bad video card, ?BIOS, ?Power to card
Old and incompatible drivers can and do cause issues with Windows 7, often giving false error codes.
Outdated Drivers. Update:
asusgsb.sys Thu Sep 27 14:14:15 2007 Link Removed
ATKDispLowFilter.sys Wed May 14 04:02:50 2008 Link Removed
Drivers with Updates:
nvlddmkm.sys Mon Dec 27 16:34:09 2010 nVidia Graphics Drivers.
Drivers:
Let us know how it goes. If you get further problems with blue screens, attach your new dump files and details and we'll move on from there.
HTH.
Most of your dump files list the following error:
STOP 0x00000116: VIDEO_TDR_ERROR
Usual causes: Video driver, overheating, bad video card, ?BIOS, ?Power to card
Old and incompatible drivers can and do cause issues with Windows 7, often giving false error codes.
Outdated Drivers. Update:
asusgsb.sys Thu Sep 27 14:14:15 2007 Link Removed
ATKDispLowFilter.sys Wed May 14 04:02:50 2008 Link Removed
Drivers with Updates:
nvlddmkm.sys Mon Dec 27 16:34:09 2010 nVidia Graphics Drivers.
- Download and install Driver Sweeper.
- Uninstall your current graphics setup through Programs and Features
- Boot to Safe Mode
- Run Driver Sweeper to clean up the remnants of your current Graphics Driver set up.
- Reboot to Normal Mode.
- Install your new Graphics Driver set up.
Code:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 116, {875c4308, 891f7c4e, 0, 2}
Unable to load image \SystemRoot\system32\drivers\ATKDispLowFilter.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ATKDispLowFilter.sys
*** ERROR: Module load completed but symbols could not be loaded for ATKDispLowFilter.sys
Probably caused by : ATKDispLowFilter.sys ( ATKDispLowFilter+1c4e )
Followup: MachineOwner
---------
2: kd> !Analyze
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 116, {875c4308, 891f7c4e, 0, 2}
Probably caused by : ATKDispLowFilter.sys ( ATKDispLowFilter+1c4e )
Followup: MachineOwnerDrivers:
Code:
8ffd0000 8fffd000 1394ohci 1394ohci.sys Sat Nov 20 10:01:11 2010 (4CE79C67)
88c8d000 88cd5000 ACPI ACPI.sys Sat Nov 20 08:37:52 2010 (4CE788E0)
8da33000 8da8d000 afd afd.sys Mon Apr 25 03:18:00 2011 (4DB4D9D8)
9186d000 9187f000 AgileVpn AgileVpn.sys Tue Jul 14 00:55:00 2009 (4A5BC954)
88e9d000 88ea6000 amdxata amdxata.sys Fri Mar 19 16:19:01 2010 (4BA3A3F5)
9185a000 9185b420 ASACPI ASACPI.sys Fri Aug 13 03:52:52 2004 (411C2D04)
91869000 9186cb80 asusgsb asusgsb.sys Thu Sep 27 14:14:15 2007 (46FBACA7)
967a9000 967abb00 aswFsBlk aswFsBlk.SYS Mon Jul 04 12:32:10 2011 (4E11A4BA)
96771000 967a9000 aswMonFlt aswMonFlt.sys Mon Jul 04 12:32:19 2011 (4E11A4C3)
8da8d000 8da91200 aswRdr aswRdr.SYS Mon Jul 04 12:32:30 2011 (4E11A4CE)
89519000 89589000 aswSnx aswSnx.SYS Mon Jul 04 12:36:42 2011 (4E11A5CA)
8dbb6000 8dbff900 aswSP aswSP.SYS Mon Jul 04 12:36:30 2011 (4E11A5BE)
895f4000 895fc900 aswTdi aswTdi.SYS Mon Jul 04 12:35:22 2011 (4E11A57A)
88db2000 88dbb000 atapi atapi.sys Tue Jul 14 00:11:15 2009 (4A5BBF13)
88dbb000 88dde000 ataport ataport.SYS Sat Nov 20 08:38:00 2010 (4CE788E8)
891f6000 891fd900 ATKDispLowFilter ATKDispLowFilter.sys Wed May 14 04:02:50 2008 (482A565A)
97790000 977dd000 ATMFD ATMFD.DLL unavailable (00000000)
89590000 89597000 Beep Beep.SYS Tue Jul 14 00:45:00 2009 (4A5BC6FC)
8dba8000 8dbb6000 blbdrive blbdrive.sys Tue Jul 14 00:23:04 2009 (4A5BC1D8)
88aa2000 88aaa000 BOOTVID BOOTVID.dll Tue Jul 14 02:04:34 2009 (4A5BD9A2)
9f8c3000 9f8dc000 bowser bowser.sys Wed Feb 23 04:47:32 2011 (4D649164)
97770000 9778e000 cdd cdd.dll unavailable (00000000)
894fa000 89519000 cdrom cdrom.sys Sat Nov 20 08:38:09 2010 (4CE788F1)
88aec000 88b97000 CI CI.dll Sat Nov 20 12:05:17 2010 (4CE7B97D)
89475000 8949a000 CLASSPNP CLASSPNP.SYS Tue Jul 14 00:11:20 2009 (4A5BBF18)
88aaa000 88aec000 CLFS CLFS.SYS Tue Jul 14 00:11:10 2009 (4A5BBF0E)
89182000 891df000 cng cng.sys Tue Jul 14 00:32:55 2009 (4A5BC427)
9185c000 91869000 CompositeBus CompositeBus.sys Sat Nov 20 09:50:21 2010 (4CE799DD)
9668a000 96697000 crashdmp crashdmp.sys Tue Jul 14 00:45:50 2009 (4A5BC72E)
8db90000 8dba8000 dfsc dfsc.sys Sat Nov 20 08:42:32 2010 (4CE789F8)
8db84000 8db90000 discache discache.sys Tue Jul 14 00:24:04 2009 (4A5BC214)
89464000 89475000 disk disk.sys Tue Jul 14 00:11:28 2009 (4A5BBF20)
8ffb7000 8ffd0000 drmk drmk.sys Tue Jul 14 01:36:05 2009 (4A5BD2F5)
96697000 966a1000 dump_diskdump dump_diskdump.sys Fri Apr 22 18:35:13 2011 (4DB1BC51)
966d9000 966ea000 dump_dumpfve dump_dumpfve.sys Tue Jul 14 00:12:47 2009 (4A5BBF6F)
966a1000 966d9000 dump_nvstor32 dump_nvstor32.sys Fri Apr 09 10:19:21 2010 (4BBEF119)
96680000 9668a000 Dxapi Dxapi.sys Tue Jul 14 00:25:25 2009 (4A5BC265)
8fe3d000 8fef4000 dxgkrnl dxgkrnl.sys Sat Nov 20 09:08:14 2010 (4CE78FFE)
8fef4000 8ff2d000 dxgmms1 dxgmms1.sys Thu Feb 03 03:45:05 2011 (4D4A24C1)
8db7b000 8db84000 EIO EIO.sys Wed Jul 22 03:34:52 2009 (4A667ACC)
8db71000 8db7b000 ElbyCDIO ElbyCDIO.sys Thu Dec 16 22:57:56 2010 (4D0A9974)
88eda000 88eeb000 fileinfo fileinfo.sys Tue Jul 14 00:21:51 2009 (4A5BC18F)
88ea6000 88eda000 fltmgr fltmgr.sys Tue Jul 14 00:11:13 2009 (4A5BBF11)
891ed000 891f6000 Fs_Rec Fs_Rec.sys Tue Jul 14 00:11:14 2009 (4A5BBF12)
89432000 89464000 fvevol fvevol.sys Sat Nov 20 08:40:22 2010 (4CE78976)
89382000 893b3000 fwpkclnt fwpkclnt.sys Sat Nov 20 08:39:08 2010 (4CE7892C)
83212000 83249000 hal halmacpi.dll Sat Nov 20 08:37:38 2010 (4CE788D2)
8ff2d000 8ff4c000 HDAudBus HDAudBus.sys Sat Nov 20 09:59:28 2010 (4CE79C00)
96630000 96680000 HdAudio HdAudio.sys Sat Nov 20 10:00:19 2010 (4CE79C33)
96730000 96743000 HIDCLASS HIDCLASS.SYS Sat Nov 20 09:59:37 2010 (4CE79C09)
96743000 96749480 HIDPARSE HIDPARSE.SYS Tue Jul 14 00:50:59 2009 (4A5BC863)
96725000 96730000 hidusb hidusb.sys Sat Nov 20 09:59:38 2010 (4CE79C0A)
9f83e000 9f8c3000 HTTP HTTP.sys Sat Nov 20 08:40:17 2010 (4CE78971)
8922d000 89235000 hwpolicy hwpolicy.sys Sat Nov 20 08:37:35 2010 (4CE788CF)
8ff88000 8ffa0000 i8042prt i8042prt.sys Tue Jul 14 00:11:23 2009 (4A5BBF1B)
8da21000 8da33000 intelppm intelppm.sys Tue Jul 14 00:11:03 2009 (4A5BBF07)
9190a000 91917000 kbdclass kbdclass.sys Tue Jul 14 00:11:15 2009 (4A5BBF13)
9674a000 96756000 kbdhid kbdhid.sys Sat Nov 20 09:50:10 2010 (4CE799D2)
80bb1000 80bb9000 kdcom kdcom.dll Tue Jul 14 02:08:58 2009 (4A5BDAAA)
8fe00000 8fe34000 ks ks.sys Sat Nov 20 09:50:17 2010 (4CE799D9)
8916f000 89182000 ksecdd ksecdd.sys Sat Nov 20 08:38:54 2010 (4CE7891E)
88bbc000 88be1000 ksecpkg ksecpkg.sys Tue Jul 14 00:34:00 2009 (4A5BC468)
967c6000 967d6000 lltdio lltdio.sys Tue Jul 14 00:53:18 2009 (4A5BC8EE)
96756000 96771000 luafv luafv.sys Tue Jul 14 00:15:44 2009 (4A5BC020)
88a0c000 88a91000 mcupdate_GenuineIntel mcupdate_GenuineIntel.dll Sat Nov 20 12:00:54 2010 (4CE7B876)
966ea000 966f5000 monitor monitor.sys Tue Jul 14 00:25:58 2009 (4A5BC286)
8ffa0000 8ffad000 mouclass mouclass.sys Tue Jul 14 00:11:15 2009 (4A5BBF13)
88d9c000 88db2000 mountmgr mountmgr.sys Sat Nov 20 08:38:09 2010 (4CE788F1)
9f8dc000 9f8ee000 mpsdrv mpsdrv.sys Tue Jul 14 00:52:52 2009 (4A5BC8D4)
9f8ee000 9f911000 mrxsmb mrxsmb.sys Wed Apr 27 03:17:20 2011 (4DB77CB0)
9f911000 9f94c000 mrxsmb10 mrxsmb10.sys Wed Apr 27 03:17:33 2011 (4DB77CBD)
9f94c000 9f967000 mrxsmb20 mrxsmb20.sys Wed Apr 27 03:17:26 2011 (4DB77CB6)
88e5b000 88e65000 msahci msahci.sys Sat Nov 20 09:50:48 2010 (4CE799F8)
895e9000 895f4000 Msfs Msfs.SYS Tue Jul 14 00:11:26 2009 (4A5BBF1E)
88cde000 88ce6000 msisadrv msisadrv.sys Tue Jul 14 00:11:09 2009 (4A5BBF0D)
89144000 8916f000 msrpc msrpc.sys Tue Jul 14 00:11:59 2009 (4A5BBF3F)
8db67000 8db71000 mssmbios mssmbios.sys Tue Jul 14 00:19:25 2009 (4A5BC0FD)
89000000 89010000 mup mup.sys Tue Jul 14 00:14:14 2009 (4A5BBFC6)
88eeb000 88fa2000 ndis ndis.sys Sat Nov 20 08:39:19 2010 (4CE78937)
91897000 918a2000 ndistapi ndistapi.sys Tue Jul 14 00:54:24 2009 (4A5BC930)
918a2000 918c4000 ndiswan ndiswan.sys Sat Nov 20 10:07:48 2010 (4CE79DF4)
9199d000 919ae000 NDProxy NDProxy.SYS Sat Nov 20 10:07:39 2010 (4CE79DEB)
8daea000 8daf8000 netbios netbios.sys Tue Jul 14 00:53:54 2009 (4A5BC912)
8da92000 8dac4000 netbt netbt.sys Sat Nov 20 08:39:22 2010 (4CE7893A)
88fa2000 88fe0000 NETIO NETIO.SYS Sat Nov 20 08:40:03 2010 (4CE78963)
89400000 8940e000 Npfs Npfs.SYS Tue Jul 14 00:11:31 2009 (4A5BBF23)
8db5d000 8db67000 nsiproxy nsiproxy.sys Tue Jul 14 00:12:08 2009 (4A5BBF48)
82e00000 83212000 nt ntkrpamp.exe Sat Apr 09 04:49:39 2011 (4D9FD753)
89015000 89144000 Ntfs Ntfs.sys Sat Nov 20 08:39:08 2010 (4CE7892C)
89589000 89590000 Null Null.SYS Tue Jul 14 00:11:12 2009 (4A5BBF10)
90bfb000 90bfc040 nvBridge nvBridge.kmd Mon Dec 27 16:29:46 2010 (4D18BEFA)
919ae000 919cf000 nvhda32v nvhda32v.sys Thu Nov 11 23:10:19 2010 (4CDC77DB)
90201000 90bfa940 nvlddmkm nvlddmkm.sys Mon Dec 27 16:34:09 2010 (4D18C001)
91813000 91859d80 nvmf6232 nvmf6232.sys Fri Mar 05 01:04:18 2010 (4B905892)
88b97000 88bbc000 nvstor nvstor.sys Fri Mar 19 20:51:52 2010 (4BA3E3E8)
88e65000 88e9d000 nvstor32 nvstor32.sys Fri Apr 09 10:19:21 2010 (4BBEF119)
91662000 917bf000 P17 P17.sys Fri Oct 16 03:11:53 2009 (4AD7D669)
8dacb000 8daea000 pacer pacer.sys Tue Jul 14 00:53:58 2009 (4A5BC916)
8ff70000 8ff88000 parport parport.sys Tue Jul 14 00:45:34 2009 (4A5BC71E)
88d1b000 88d2c000 partmgr partmgr.sys Sat Nov 20 08:38:14 2010 (4CE788F6)
9f967000 9f96e000 parvdm parvdm.sys Tue Jul 14 00:45:29 2009 (4A5BC719)
88ce6000 88d10000 pci pci.sys Sat Nov 20 08:37:57 2010 (4CE788E5)
88d87000 88d8e000 pciide pciide.sys Tue Jul 14 00:11:19 2009 (4A5BBF17)
88d8e000 88d9c000 PCIIDEX PCIIDEX.SYS Tue Jul 14 00:11:15 2009 (4A5BBF13)
891df000 891ed000 pcw pcw.sys Tue Jul 14 00:11:10 2009 (4A5BBF0E)
98838000 988cf000 peauth peauth.sys Tue Jul 14 01:35:44 2009 (4A5BD2E0)
917bf000 917ee000 portcls portcls.sys Tue Jul 14 00:51:00 2009 (4A5BC864)
88a91000 88aa2000 PSHED PSHED.dll Tue Jul 14 02:09:36 2009 (4A5BDAD0)
9187f000 91897000 rasl2tp rasl2tp.sys Tue Jul 14 00:54:33 2009 (4A5BC939)
918c4000 918dc000 raspppoe raspppoe.sys Tue Jul 14 00:54:53 2009 (4A5BC94D)
918dc000 918f3000 raspptp raspptp.sys Tue Jul 14 00:54:47 2009 (4A5BC947)
918f3000 9190a000 rassstp rassstp.sys Tue Jul 14 00:54:57 2009 (4A5BC951)
8db1c000 8db5d000 rdbss rdbss.sys Sat Nov 20 08:42:44 2010 (4CE78A04)
895d1000 895d9000 RDPCDD RDPCDD.sys Sat Nov 20 10:22:19 2010 (4CE7A15B)
895d9000 895e1000 rdpencdd rdpencdd.sys Tue Jul 14 01:01:39 2009 (4A5BCAE3)
895e1000 895e9000 rdprefmp rdprefmp.sys Tue Jul 14 01:01:41 2009 (4A5BCAE5)
89200000 8922d000 rdyboost rdyboost.sys Sat Nov 20 09:00:07 2010 (4CE78E17)
967d6000 967e9000 rspndr rspndr.sys Tue Jul 14 00:53:20 2009 (4A5BC8F0)
91923000 91949000 SCSIPORT SCSIPORT.SYS Sat Nov 20 09:50:55 2010 (4CE799FF)
988cf000 988d9000 secdrv secdrv.SYS Wed Sep 13 14:18:32 2006 (45080528)
8ff66000 8ff70000 serenum serenum.sys Tue Jul 14 00:45:27 2009 (4A5BC717)
8ff4c000 8ff66000 serial serial.sys Tue Jul 14 00:45:33 2009 (4A5BC71D)
893f2000 893fa000 spldr spldr.sys Mon May 11 17:13:47 2009 (4A084EBB)
98957000 989a9000 srv srv.sys Fri Apr 29 03:46:30 2011 (4DBA2686)
98907000 98957000 srv2 srv2.sys Fri Apr 29 03:46:13 2011 (4DBA2675)
988d9000 988fa000 srvnet srvnet.sys Fri Apr 29 03:46:08 2011 (4DBA2670)
88e13000 88e5b000 storport storport.sys Sat Nov 20 09:50:58 2010 (4CE79A02)
91949000 9194a380 swenum swenum.sys Tue Jul 14 00:45:08 2009 (4A5BC704)
89238000 89382000 tcpip tcpip.sys Mon Apr 25 03:18:36 2011 (4DB4D9FC)
988fa000 98907000 tcpipreg tcpipreg.sys Sat Nov 20 10:07:13 2010 (4CE79DD1)
89425000 89431000 TDI TDI.SYS Sat Nov 20 08:39:18 2010 (4CE78936)
8940e000 89425000 tdx tdx.sys Sat Nov 20 08:39:17 2010 (4CE78935)
8db0b000 8db1c000 termdd termdd.sys Sat Nov 20 10:21:10 2010 (4CE7A116)
97740000 97749000 TSDDD TSDDD.dll unavailable (00000000)
8da00000 8da21000 tunnel tunnel.sys Sat Nov 20 10:06:40 2010 (4CE79DB0)
9194b000 91959000 umbus umbus.sys Sat Nov 20 10:00:23 2010 (4CE79C37)
9670e000 96725000 usbccgp usbccgp.sys Sat Nov 20 10:00:08 2010 (4CE79C28)
9670c000 9670d700 USBD USBD.SYS Tue Jul 14 00:51:05 2009 (4A5BC869)
91653000 91662000 usbehci usbehci.sys Sat Nov 20 09:59:43 2010 (4CE79C0F)
91959000 9199d000 usbhub usbhub.sys Sat Nov 20 10:00:34 2010 (4CE79C42)
8ffad000 8ffb7000 usbohci usbohci.sys Tue Jul 14 00:51:14 2009 (4A5BC872)
91608000 91653000 USBPORT USBPORT.SYS Sat Nov 20 09:59:49 2010 (4CE79C15)
966f5000 9670c000 USBSTOR USBSTOR.SYS Sat Nov 20 09:59:48 2010 (4CE79C14)
91917000 91923000 VClone VClone.sys Sat Jan 15 16:20:14 2011 (4D31C93E)
88d10000 88d1b000 vdrvroot vdrvroot.sys Tue Jul 14 00:46:19 2009 (4A5BC74B)
89597000 895a3000 vga vga.sys Tue Jul 14 00:25:50 2009 (4A5BC27E)
895a3000 895c4000 VIDEOPRT VIDEOPRT.SYS Tue Jul 14 00:25:49 2009 (4A5BC27D)
88d2c000 88d3c000 volmgr volmgr.sys Sat Nov 20 08:38:06 2010 (4CE788EE)
88d3c000 88d87000 volmgrx volmgrx.sys Tue Jul 14 00:11:41 2009 (4A5BBF2D)
893b3000 893f2000 volsnap volsnap.sys Sat Nov 20 08:38:13 2010 (4CE788F5)
8daf8000 8db0b000 wanarp wanarp.sys Sat Nov 20 10:07:45 2010 (4CE79DF1)
895c4000 895d1000 watchdog watchdog.sys Tue Jul 14 00:24:10 2009 (4A5BC21A)
88c0e000 88c7f000 Wdf01000 Wdf01000.sys Tue Jul 14 00:11:36 2009 (4A5BBF28)
88c7f000 88c8d000 WDFLDR WDFLDR.SYS Tue Jul 14 00:11:25 2009 (4A5BBF1D)
8dac4000 8dacb000 wfplwf wfplwf.sys Tue Jul 14 00:53:51 2009 (4A5BC90F)
974e0000 9772e000 win32k win32k.sys unavailable (00000000)
88cd5000 88cde000 WMILIB WMILIB.SYS Tue Jul 14 00:11:22 2009 (4A5BBF1A)
967ac000 967c6000 WudfPf WudfPf.sys Sat Nov 20 09:58:55 2010 (4CE79BDF)
Unloaded modules:
8949a000 894a7000 crashdmp.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
ImageSize: 0000D000
894a7000 894b1000 dump_storpor
Timestamp: unavailable (00000000)
Checksum: 00000000
ImageSize: 0000A000
894b1000 894e9000 dump_nvstor3
Timestamp: unavailable (00000000)
Checksum: 00000000
ImageSize: 00038000
894e9000 894fa000 dump_dumpfve
Timestamp: unavailable (00000000)
Checksum: 00000000
ImageSize: 00011000Let us know how it goes. If you get further problems with blue screens, attach your new dump files and details and we'll move on from there.
HTH.
Last edited:
- Thread Author
-
- #6
Thanks for that I'll have a look at that tomorrow (bedtime for me here). I forgot to mention I have had this video card for a month or so but running on Windows XP (which I still have fully installed on a separate hard drive just in case the installation did not go well
Anyway I'll let you know how I get on.
Cheers
Anyway I'll let you know how I get on.
Cheers
- Thread Author
-
- #7
Had another crash (its always minutes straight after I boot into Windows 7 too) and followed your instructions.
The two drivers you mention ATKDispLowFilter.sys and asusgsb.sys seem to have dates saying they were created on 17/2/2009 so hope that's the latest
Heres the last dump before I redid the Graphics drivers. Interested to see if the dates for those drivers have changed!
Ignore the Bluescreen txt file thats a mistake
The two drivers you mention ATKDispLowFilter.sys and asusgsb.sys seem to have dates saying they were created on 17/2/2009 so hope that's the latest
Heres the last dump before I redid the Graphics drivers. Interested to see if the dates for those drivers have changed!
Ignore the Bluescreen txt file thats a mistake
- Joined
- Jun 2, 2009
- Messages
- 802
Still the same kind of crash (as Emler correctly said) BCC 116, but the file causing it now is different and may have been the problem all along. The crash was Related to ATKDispLowFilter.sys ATKDispLowFilter from ASUSTeK Computer..
Yours is dated
ATKDispLowFilter.sys 5/13/2008 11:02:50 PM ATKDispLowFilter.sys+1c4e 0x8e3f7000 0x8e3fe900 0x00007900 0x482a565a
That absolutely could be the cause of the could boot crash. I would go to Asus and get the newest available and install it.
Kudo's to Elmer for a great read.
Yours is dated
ATKDispLowFilter.sys 5/13/2008 11:02:50 PM ATKDispLowFilter.sys+1c4e 0x8e3f7000 0x8e3fe900 0x00007900 0x482a565a
That absolutely could be the cause of the could boot crash. I would go to Asus and get the newest available and install it.
Kudo's to Elmer for a great read.
Elmer
Extraordinary Member
- Joined
- Mar 5, 2010
- Messages
- 3,864
Why, Thank you Ken!
@Baz Just for reference the best date entry to check for the actual date is the modified one. This is because I could modify a 1970 file in 1980 for a program but you could create it on your PC in 2011, the same date you last accessed it to check its date! This doesn't always happen btw! (does that make sense??
- Thread Author
-
- #10
yes Elmer you are a legend! I don't want to jump the gun but I'm on my third boot and no issues so far....................The Modified date of ATKDispLowFilter.sys says 5/2/2009. I'll have a look and see if I can find a newer one though. I'll let you know how I get on.
Also Elmer you mentioned my RAM setting were not correct. Not sure why they have changed as I don't fiddle with them. How do about changing them?
- Thread Author
-
- #13
I have uninstalled Smart Doctor so will see how we go. I did have a crash last night as I left my PC paused on a game and about an hour or so later I went back and found I was looking at the log in screen. Yep it had rebooted after "unexpectedly shutting down".
I'll let you know how it goes with Smart Doctor uninstalled.
I'll let you know how it goes with Smart Doctor uninstalled.
- Thread Author
-
- #15
I booted up this morning after no problems last night and straight away after getting to the desktop it went to a black screen then back to desktop with a message that the Graphics display driver had been restarted etc etc etc. Smart Doctor is gone but both those pesky ASUS drivers are still there. Surely they are the up to date drivers now as I've run the update for the ASUS (Nvidia) chipset and the update for the ASUS drivers and the graphics card.
What would happen if I deleted them out of windows? Probably make things worse I'll bet.
Its been running now for about 10 minutes or so with none of the usual issues (like locking up then black screen then back to desktop then repeat) so we must have improved something. The hard drive is busy though so I'm wondering if its getting ready to make my day!
I suppose the other thing to try is a repair install or a complete one. Now I know what drivers I should be usingperhaps a fresh one would help?
What do you think?
I've attached the latest dump files for your viewing pleasure.
EDIT: Just a crazy thought would XP (even thought its installed on a seperate hard drive be causing this?
What would happen if I deleted them out of windows? Probably make things worse I'll bet.
Its been running now for about 10 minutes or so with none of the usual issues (like locking up then black screen then back to desktop then repeat) so we must have improved something. The hard drive is busy though so I'm wondering if its getting ready to make my day!
I suppose the other thing to try is a repair install or a complete one. Now I know what drivers I should be usingperhaps a fresh one would help?
What do you think?
I've attached the latest dump files for your viewing pleasure.
EDIT: Just a crazy thought would XP (even thought its installed on a seperate hard drive be causing this?
Elmer
Extraordinary Member
- Joined
- Mar 5, 2010
- Messages
- 3,864
Well baz,
Sorry to have led you up the wrong path re: those two drivers. Nearly joined the other forum to say they were wrong but noticed the thread was 18mths old so didn't bother! You could rename the drivers from .sys to .bak. This will stop them from loading but also "break" anything they are related to. If you tried that I'd suggest you make a restore point before going ahead.
Which graphics card do you have? (Actually, if you could fill in some of your specs under your user profile it would be a great help!!)
Might be worth re-setting / installing your graphics drivers.
Update:
RTKVHDA.sys Tue Jul 28 14:02:38 2009 Link Removed
As to XP affecting it? Seeing as I can't find my XP key (
Sorry to have led you up the wrong path re: those two drivers. Nearly joined the other forum to say they were wrong but noticed the thread was 18mths old so didn't bother! You could rename the drivers from .sys to .bak. This will stop them from loading but also "break" anything they are related to. If you tried that I'd suggest you make a restore point before going ahead.
Which graphics card do you have? (Actually, if you could fill in some of your specs under your user profile it would be a great help!!)
Might be worth re-setting / installing your graphics drivers.
- Download and install Driver Sweeper.
- Uninstall your current Graphics setup through Programs and Features
- Boot to Safe Mode
- Run Driver Sweeper to clean up the remnants of your current Graphics set up.
- Reboot to Normal Mode.
- Install your new Graphics set up.
Update:
RTKVHDA.sys Tue Jul 28 14:02:38 2009 Link Removed
As to XP affecting it? Seeing as I can't find my XP key (
Last edited:
- Thread Author
-
- #17
Hell sorry I thought I had posted them! Here you go:
Win 7 Home Premium 32Bit Version 6.17601 SP1
Intel Q6600 2.4Gig CPU
2 Gig of Ram
P5N-E Sli Motherboard
ASUS GTX560 Ti Video Card
And not long after I posted yesterday the PC did start behaving as before and I rebooted back to XP! And no problem about going up any garden paths we need to try these things after all.
One thing I am wondering is this Realtek driver. Its for the motherboard sound
I have a Creative Sound card installed but I'm not using it (long story) but have my sound cables plugged into the motherboard sockets.
Now the Video Card software installs its own HD audio software so I was wondering about a conflict? Plus Creative drivers keep on re appearing (even though I've got the auto detect function disabled (!))
So I might try two things.
First i'll plug in the sound into my sound card.
Second, I'll remove the card altogether.
Of course XP doesn't seem to have an issue with the sound but you never know. I'll try renaming those drivers first and re doing the graphics drivers and see what that does first.
Wish me luck!
Win 7 Home Premium 32Bit Version 6.17601 SP1
Intel Q6600 2.4Gig CPU
2 Gig of Ram
P5N-E Sli Motherboard
ASUS GTX560 Ti Video Card
And not long after I posted yesterday the PC did start behaving as before and I rebooted back to XP! And no problem about going up any garden paths we need to try these things after all.
One thing I am wondering is this Realtek driver. Its for the motherboard sound
I have a Creative Sound card installed but I'm not using it (long story) but have my sound cables plugged into the motherboard sockets.
Now the Video Card software installs its own HD audio software so I was wondering about a conflict? Plus Creative drivers keep on re appearing (even though I've got the auto detect function disabled (!))
So I might try two things.
First i'll plug in the sound into my sound card.
Second, I'll remove the card altogether.
Of course XP doesn't seem to have an issue with the sound but you never know. I'll try renaming those drivers first and re doing the graphics drivers and see what that does first.
Wish me luck!
Last edited:
- Thread Author
-
- #18
Ok I did what you suggested and now there are 3 files changed from .sys to .BAK they are Asacpi.sys, ATKDisplowfilter.sys and asusgsb.sys. The reason for the last one was I did the first 2 then re installed the Graphics driver and a minute after I got to the Desktop the Graphics Driver crashed and restarted. So as we had talked about that one I tried that one too but same result. Seems to me the PC boots happily into Windows 7 without any problems but as soon as you introduce the Graphics Driver whamo instant problem. I've attached another dump file load for you to look at, maybe with those drivers disabled it will show something else. Oh and I updated that RealTek audio driver too.
Elmer
Extraordinary Member
- Joined
- Mar 5, 2010
- Messages
- 3,864
STOP 0x00000116: VIDEO_TDR_ERROR
Usual causes: Video driver, overheating, bad video card, ?BIOS, ?Power to card.
Your latest dump file lists nvlddmkm.sys as the probable cause (graphics driver).
For now, while you are still getting BSOD's uninstall Avast! as it has been known to cause issues on some Win 7 systems.
Uninstall Avast then use the Avast Link Removed to clear up. Download BSOD friendly Link Removed due to 404 Error as its replacement. Make sure Windows firewall is enabled!
Once everything has settled feel free to re-install Avast.
Update:
AsUpIO.sys Mon Jul 06 03:21:27 2009 Link Removed hardware monitoring software related.
Run sfc /scannow to check your system files are in good order.
Physically re-seat your graphics card in your machine. Can you then stress test it.
Bugcheck Analysis:
There's an interesting (if old) thread regarding 116 errors on the nVidia Forum
Usual causes: Video driver, overheating, bad video card, ?BIOS, ?Power to card.
Your latest dump file lists nvlddmkm.sys as the probable cause (graphics driver).
For now, while you are still getting BSOD's uninstall Avast! as it has been known to cause issues on some Win 7 systems.
Uninstall Avast then use the Avast Link Removed to clear up. Download BSOD friendly Link Removed due to 404 Error as its replacement. Make sure Windows firewall is enabled!
Once everything has settled feel free to re-install Avast.
Update:
AsUpIO.sys Mon Jul 06 03:21:27 2009 Link Removed hardware monitoring software related.
Run sfc /scannow to check your system files are in good order.
Physically re-seat your graphics card in your machine. Can you then stress test it.
Bugcheck Analysis:
Code:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 116, {84dba510, 8f542b2c, 0, 2}
Unable to load image \SystemRoot\system32\DRIVERS\nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+11fb2c )
Followup: MachineOwner
---------
2: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: 84dba510, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: 8f542b2c, The pointer into responsible device driver module (e.g. owner tag).
Arg3: 00000000, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 00000002, Optional internal context dependent data.
Debugging Details:
------------------
FAULTING_IP:
nvlddmkm+11fb2c
8f542b2c 55 push ebp
DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_TDR_FAULT
CUSTOMER_CRASH_COUNT: 1
BUGCHECK_STR: 0x116
PROCESS_NAME: System
CURRENT_IRQL: 0
STACK_TEXT:
8a18db74 8fee107b 00000116 84dba510 8f542b2c nt!KeBugCheckEx+0x1e
8a18db98 8fed5937 8f542b2c 00000000 00000002 dxgkrnl!TdrBugcheckOnTimeout+0x8d
8a18dbbc 8ff1192c 00000000 00000102 8767a788 dxgkrnl!TdrIsRecoveryRequired+0xb8
8a18dc34 8ff3b944 fffffcfb 00004635 00000000 dxgmms1!VidSchiReportHwHang+0x3c0
8a18dc5c 8ff3c065 00000000 00000000 00000000 dxgmms1!VidSchiCheckHwProgress+0x68
8a18dc98 8ff188f0 8a18dc90 8512e9f8 86450270 dxgmms1!VidSchiWaitForSchedulerEvents+0x1b1
8a18dd28 8ff3d3c9 8767a788 82e4c50e 8767a788 dxgmms1!VidSchiScheduleCommandToRun+0xaa
8a18dd3c 8ff3d485 8767a788 00000000 87687d48 dxgmms1!VidSchiRun_PriorityTable+0xf
8a18dd50 8301df64 8767a788 a843fa6b 00000000 dxgmms1!VidSchiWorkerThread+0x7f
8a18dd90 82ec6219 8ff3d406 8767a788 00000000 nt!PspSystemThreadStartup+0x9e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19
STACK_COMMAND: .bugcheck ; kb
FOLLOWUP_IP:
nvlddmkm+11fb2c
8f542b2c 55 push ebp
SYMBOL_NAME: nvlddmkm+11fb2c
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nvlddmkm
IMAGE_NAME: nvlddmkm.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4dd73a6b
FAILURE_BUCKET_ID: 0x116_IMAGE_nvlddmkm.sys
BUCKET_ID: 0x116_IMAGE_nvlddmkm.sys
Followup: MachineOwnerThere's an interesting (if old) thread regarding 116 errors on the nVidia Forum
Last edited:
- Thread Author
-
- #20
Ok uninstalled Avast and have MSE running now. Is this a good bit of software? I usually use AVG (its on my XP installation) and onluy used Avast because my brother in law raved about it.
Ran the stress test, it got up to approx 63 degrees after a minute or so and then stayed there. i'll do another one and leave it longer to see if anything happens.
Interestingly when I was booting in and out of Windows it wanted to do an update. (Note the Nvidia drivers were uninstalled at the time)
When i got to my desktop my resolution was back up! So as part of the update it had re installed the drivers! DirectX says its now using version 8.17.12.7533 which I presume is the one I've been trying to use.
So far (I'm typing quietly in case the computer hears it...) no crash!
Ok let it run for 10 minutes and no issues. Temperature stable at 65/66 degrees C
Other specs:
14FPS
7900 frames
VDDC: 0.987V
Fan Speed: 48% (2550 RPM)
GPU Load: 99%
Mem Load: 16%
Ran the stress test, it got up to approx 63 degrees after a minute or so and then stayed there. i'll do another one and leave it longer to see if anything happens.
Interestingly when I was booting in and out of Windows it wanted to do an update. (Note the Nvidia drivers were uninstalled at the time)
When i got to my desktop my resolution was back up! So as part of the update it had re installed the drivers! DirectX says its now using version 8.17.12.7533 which I presume is the one I've been trying to use.
So far (I'm typing quietly in case the computer hears it...) no crash!
Ok let it run for 10 minutes and no issues. Temperature stable at 65/66 degrees C
Other specs:
14FPS
7900 frames
VDDC: 0.987V
Fan Speed: 48% (2550 RPM)
GPU Load: 99%
Mem Load: 16%
Last edited:
Similar threads
- Solved
- Solved
- Solved