|07 May 2011||#2|
| || |
Old drivers needing update
MarvinBus64.sys 9/23/2005 05:17:03 PM fffff880`04c87000 0x00044000 0x433470cf fffff880`04c43000 speedfan.sys 9/24/2006 09:26:48 AM fffff880`018fa000 0x00007000 0x45168798 fffff880`018f3000 AtiPcie.sys 11/6/2006 12:59:54 PM fffff880`019d7000 0x00008000 0x454f6a0a fffff880`019cf000 acedrv08.sys 11/23/2006 11:48:16 AM fffff880`03624000 0x00024000 0x4565c2c0 fffff880`03600000 amdide64.sys 10/11/2007 09:40:08 PM fffff880`00d8c000 0x00007000 0x470ed078 fffff880`00d85000 PxHlpa64.sys 3/12/2008 09:58:17 PM fffff880`010b0d00 0x0000bd00 0x47d88a39 fffff880`010a5000 VSTCNXT6.SYS 10/15/2008 08:52:22 PM fffff880`051c2000 0x000cb000 0x48f69046 fffff880`050f7000 VSTBS26.SYS 10/15/2008 08:54:06 PM fffff880`04de1000 0x00070000 0x48f690ae fffff880`04d71000 VSTDPV6.SYS 10/15/2008 08:57:45 PM fffff880`04ff0000 0x00174000 0x48f69189 fffff880`04e7c000
- 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.
- - Driver manufacturer links are on this page: Drivers and Downloads
Please run driver verifier to determine which driver is causing the page fault
I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Windows 7 Startup Repair feature).
In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .
Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.
Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).
If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.
|My System Specs|
|Similar help and support threads for2: BSOD problems...can't pinpoint...help!?|
|BSOD Unable to pinpoint cause||BSOD Help and Support|
|Multiple BSoD strings - Unable to pinpoint||BSOD Help and Support|
|BSOD can't pinpoint what is triggering it||BSOD Help and Support|
|BSOD on Win 7 startup- trying to pinpoint cause||BSOD Help and Support|
|BSOD- Persistent for months, cannot pinpoint problem. Different codes||BSOD Help and Support|
|Can't pinpoint these wipes Im getting||Software|
|Various Random BSOD - Can't Pinpoint the exact error!||BSOD Help and Support|
|Our Sites ||Site Links ||About Us ||Find Us |
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.
© Designer Media Ltd
All times are GMT -5. The time now is 07:12 AM.