Another crash today. Everything but antivirus is turned off in start-up section of msconfig except for Microsoft security essentials. Here is the error code and dump files. 0x0000007E (0xFFFFFFFFC0000005, 0xFFFFF80002F16F98, 0xFFFFF880031D2888, 0xFFFFF880031D20E0)
Are we to the point of doing a new windows install?
How about run Seatools for Dos first. Run the short and the long tests. SeaTools for DOS and Windows - How to Use
If you haven't done it already, open an elevated command prompt ( click start, type cmd in the search box, right click on the cmd entry and select run as administrator) in the black box that opens, copy/paste sfc /scannow. If you decide to type it, notice the space between the sfc and the /. It is a system file checker which will scan your system files and attempt to correct any missing or corrupt files. What we want are the results to say windows found no integrity violations. If it says files were found but could not be repaired, close the box, reboot and run it again, after opening the administrative command prompt. You may have to reboot and run it three times for it to repair all system files. If it can't repair them after 3 reboots, let us know.
Let me know how that goes and I would like to try one other thing, before a clean install. Also, keep track of your CPU temps.
What does sea tools look for in the drive? Will it be able to detect anything from a SSD? Just curious I am working on downloading and creating a bootable USB now. Currently the CPU temp is at 27C the motherboard is running the same.
Also I ran sfc /scannow two days ago with no errors. I will run again.
Probably not necessary for the sfc if you ran it 2 days ago. Seatools checks the drive for defects. I don't think it's necessary on an SSD. They write data different anyway. Just make sure you have the latest firmware for it.
Firmware is up to date. What is our one last thing to try?
Lets run Driver Verifier. Sort the drivers by provider, then select all drivers not provided by Microsoft. Your computer will seem a little slow and sluggish. That is normal, Run it for 24 hours of actual use, nit just idling. We are hoping it will BSOD and we can catch the bad driver in the dump file. This will tell you how. But, be sure to create a restore point first before doing anything.
WarningBe sure to create a System Restore point before proceeding further System Restore Point - Create
Driver Verifier - Enable and Disable
Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.
Information
What is Driver Verifier:
It puts stress on the drivers, and tries to make the faulty driver crash the computer. It is designed this way, to attempt to trap the offending driver.
What you will notice:
It will tend to make the computer rather slow and sluggish because the drivers are being stressed.
Warning
Before enabling DV, make sure you have created a system restore point before enabling Driver Verifier. make a System Restore Point manually before enabling DV.
Tip
- If you fail to get on the Desktop because of DV, Boot into Advanced Boot Options > Safe mode. Disable DV there. Now boot normally again, and try following the instruction of enabling DV again.
- If you cannot boot in Safe mode, do a System Restore to a point you made earlier.
Let us know the results, with the subsequent crash dumps, if any.
Quote