New
#11
Uninstalled and so far nothing, should I do another stress test without or just wait till there is another BSOD?
Uninstalled and so far nothing, should I do another stress test without or just wait till there is another BSOD?
Just give it a due time .... observe the situation for a few days in normal condition.
If the problem is not cured by the uninstall, it will recur very shortly. A couple of days will be enough.
And tadaa! 2 BSOD on login, 0x01a, setting up files, should I run the verifier?
Your crash dumps are not showing any finite probable cause.
Test your RAM modules for possible errors.
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 passes, preferably overnight.
First run it with all the existing/installed RAM modules. If errors are reported, stop then and there. Otherwise run upto 8 passes.
If memtest comes free from errors, enable Driver Verifier to monitor the drivers.
Driver Verifier - Enable and Disable
Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.
InformationWhy Driver Verifier:
It puts a stress on the drivers, ans so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.
How Can we know that DV is enabled:
It will make the system bit of slow, laggy.
WarningBefore enabling DV, make it sure that you have earlier System restore points made in your computer. You can check it easily by using CCleaner looking at Tools > System Restore.
If there is no points, make a System Restore Point manually before enabling DV.
Let us know the results, with the subsequent crash dumps, if any.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 too, do a System Restore to a point you made earlier.
I will do so tonight, however running seatools seems the C: drive is faililng the short test, which might mean the drive is going bad?
Chance is there, obviously. Seatool for dos: SeaTools | Seagate download
- Burn it in a blank cd. boot from the CD, click on "Accept", wait for it to finish detecting the drives, then in the upper left corner select "Basic Tests", then select "Long Test" and let it run.
- You can use Win32 DiscImager to create a bootable USB and run Seatools for DOS. Follow this post to know how to make a bootable Seatools USB.
Now, follow this post .... an option to repair the disc is there. If it is within repair, it will be done. Otherwise replace the HDD.
Yea at the moment seatools is failing short tests every time with the following:
System.IndexOutOfRangeException: Index was outside the bounds of the array.
at SeaToolsforWindows.frmSTXMain.ProcessTestCompleted(Int32 xd)
at SeaToolsforWindows.frmSTXMain.Timer_Tick(Object sender, EventArgs e)
at System.Windows.Forms.Timer.OnTick(EventArgs e)
at System.Windows.Forms.Timer.TimerNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
According to Tom's Hardware should just go and replace the drive :/
If you want, you can. But if you take the long test and attempt the repair, nothing will be a loss :)
But, back your data up first, preferably externally.
Thank you so much for your help, at this point backing up and RMing this HD :)