Here you go.
The crashes present haven't been caused by driver verifier, keep it running.
If you are using a program like Ccleaner please stop using it while troubleshooting.
This because programs like Ccleaner remove dump files that are needed to troubleshoot.
Or configure Ccleaner to not remove dump files:
Will do. What do I do next? Wait for driver verifier to crash?
Just keep driver verifier running for a few crashes, then upload a new zip.
2 more crashes since then, though I haven't used my computer intensively, just left it on. CLOCK WATCHDOG TIMEOUT (hal.dll) and CLOCK WATCHDOG TIMEOUT (ntoskrnl.exe). Again, I'm assuming this has nothing to do with driver verifier. Since DV hasn't crashed yet, does this rule out a driver issue?
NotePlease run HDTune first, in the order posted!
Run HDTune to
- check the health,
- scan for errors, no quick scan but full scan
- run a benchmark.
It may take some time, but please take the time you need to perform it properly.
When above is done please make screenshots of the following
- the health,
- the error scan,
- the benchmark incl. following
- transfer rate,
- access time,
- burst rate,
- cpu usage.
Run SeaTools DOS to check the integrity of your HDD. SeaTools for DOS and Windows - How to Use - Windows 7 Help Forums
Run the long test.
NoteDo not run SeaTools on an SSD as the results will be invalid.
Make a photo of the result and post it.
Disk Check - Windows 7 Help Forums
Use option TWO with parameter /r
Upload the chkdsk log Check Disk (chkdsk) - Read Event Viewer Log - Windows 7 Help Forums
Run MemTest86+ to analyse your RAM. MemTest86+ - Test RAM - Windows 10 Forums
MemTest86+ needs to be run for at least 8 complete passes for conclusive results. Set it running before you go to bed and leave it overnight. We're looking for zero errors here. Even a single error will indicate RAM failure.
Make a photo of the result and post it.
If errors show up you can stop the test, remove all sticks but 1 and test this single stick in each slot for 8 passes or until errors show, switch sticks and repeat.
If errors show up and you see them a lot later, no problem, the errors don't affect the test.
Memtest came back with 0 errors after 8 passes.
Running SeaTools later today.
EDIT: The SeaTools DOS will not work. When I boot the drive, I just get a black screen with a blinking line in the top left. Changing my SATA configuration to IDE not only produced the same result, but made it so that I could not boot regularly.
Latest crashes: CUSTOM ERROR, CLOCK WATCHDOG TIMEOUT, KMODE EXCEPTION NOT HANDLED (ntoskrnl.exe) and (ntkrnlmp.exe). Another one I saw earlier (which the minidump now has disappeared?) was PAGED FAULT IN NON PAGED AREA.
Last edited by usermx; 2 Weeks Ago at 16:15.
Please continue the tests, change the SATA configuration back and continue.
After the rest of the tests are done we can focus on SeaTools
Continue the tests? I did the 3 that were mentioned in your earlier post.
Also, when I tried to boot my computer today it said "Overclocking Failed!" and I had to go to BIOS setup. The thing is, I'm not overclocking. People have said this may be a RAM problem? I'm at a loss at this point.
And another SYSTEM THREAD EXCEPTION NOT HANDLED, seconds after loading windows today.
What are the results? Without the requested results I cannot tell if you did them.Continue the tests? I did the 3 that were mentioned in your earlier post.
I add a line after every test to make a photo or screenshot or to upload a log after the test is done. Those results are necessary so I can verify that the tests have been performed properly.
I want to verify them, because many do not perform the tests properly, 2 examples:
- With MemTest86+, many run MemTest86 which often does not show proper results
- With chkdsk, many run them from Windows Explorer or run only 'chkdsk', this results in several things being left unchecked/repaired, like the Master File Table or used space marked as free space (or the opposite). By leaving them unrepaired the file system may still be in a critical condition.