|21 Sep 2012||#2|
| || |
Lets enable driver verifier to rule out buggy drivers.
I'd suggest that you first backup your data 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 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.
Driver Verifier - Enable and Disable
Verifier puts extreme stress on the drivers, bad ones will cause BSOD. If we change all those drivers we hope for no more BSODs, If you get no BSODs, then its not a driver and we look to hardware. With verifier on your computer may be a little laggy, but actually..its just doing its work.
Driver Verifier runs in the background, "testing" drivers for bugs. If it finds one, a Blue Screen of Death (BSOD) will result; the corresponding dump file will hopefully show the faulty driver.
Driver Verifier monitors kernel-mode drivers and graphics drivers to detect illegal function calls or actions that might corrupt the system. It can subject the drivers to a variety of stresses and tests to find improper behavior.
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.
|My System Specs|
|Similar help and support threads for2: Random BSOD tcpip.sys|
|Random BSOD, ntoskrnl.exe tcpip.sys||BSOD Help and Support|
|Random BSOD Browsing Internet, tcpip.sys||BSOD Help and Support|
|Random BSODs about once a day or so with ntoskrnl.exe and tcpip.sys.||BSOD Help and Support|
|Random BSOD: ntoskrnl.exe, afd.sys, tcpip.sys, atikmdag.sys & win32k.s||BSOD Help and Support|
|BSOD's after adding RAM [ tcpip.sys ] [ error:tcpip+7a6cc ]||BSOD Help and Support|
|Random BSOD tcpip.sys Driver_IRQ_NOT_LESS_OR_EQUAL_TOO most recent||BSOD Help and Support|
|Random BSOD's (Tcpip.sys)||BSOD Help and Support|