New
#11
I did try it from the motherboard's boot menu. It was after I selected the "u disk" entry that it booted to the desktop. How would I do it from the BIOS?
I did try it from the motherboard's boot menu. It was after I selected the "u disk" entry that it booted to the desktop. How would I do it from the BIOS?
Fill up your system specs.
See your system specs and fill it up here.
The process to access boot menu key and enter to BIOS key depends on make/model of the computer.
Connect the USB to the computer and restart.
Tap the F12 key on the keyboard during booting, and press it frequently. It will give you the boot menu key ... like this one.
Select the USB stick using the up/down arrow key and hit enter. It will boot from the USB stick.
Actually, that's the way that I tried. I'm sorry for getting it wrong. Is it worth changing the boot order in Windows?
You can change the boot order for the time being. But the boot menu key works all the times, and it is the easier option.
Ok, so I managed to get SeaTools for DOS to boot off a USB stick using this method: NowhereLAN » Boot SeaTools off of a USB Drive
I've updated my chipset drivers from the Gigabyte website as I've heard that can be a reason for the test not running. However, the test still won't run as it should do. The status bar just says "Testing" and the clock freezes.
I'm assuming that the SeaTools scan always looks like it does in the link below:
Seatools for DOS - YouTube
Do you have any ideas why it might not be working for me?
Last edited by Polygone; 15 Jul 2013 at 05:28. Reason: Various typos
Yes, the seatools scan should look like the video you pointed. It it is doing something different, that should mean that it is detecting some problem and so it cannot pass a particular point where the clock freezes.
Try long test. It has a mechanism to recover the bad sectors after the test is done. Though t takes a few hours to be completed.
If the long test also fails, better you replace the HDD.
Yeh, the long test freezes at start up as well. SeaTools for Windows' Long Generic Test ran fine and didn't find any problems. I know that you said that the Windows version wasn't very effective at finding faulty drives but as it managed to run, does that change your diagnosis?
It is not a good indicator that the Seatools for DOS is not working properly. But, as the Seatools for Windows passed, it is apparently good.
Have you had more BSODS after this post? SERVICE_EXCEPTION and MEMORY_MANAGEMENT BSODs after PC rebuild
If so, let us see the dumps.