[SOLVED] BSOD in Win 10

I eliminate any OC, log into windows, complete a session of Prepapr3d without crashing (a lot sluggish of course as the PC preforms slower), shut down the computer tried to get back in and emediately run into a BSOD during the windows "thinking"screen saying Stop code: inaccesible boot device. No code numbers or the like.
I tried the Driver Verifier deactivation but it doesn't come up in my register at all. I even perform a search to be sure it was not in where it is suggested should be neither in anywhere else.
I can try to recover the boot sector and things like that or any other advice course of action but I rather ask you first.
Sorry for the trouble.
Cheers
 
Update
I was having a look through the internet in case I'm missing something on my OC (it has been running stable for quite a long time but one never know...) I went to the BIOS for finer adjustment, and tried the AIDA64 test (it's the only thing I have installed after the fresh Win installation). Surprisingly it reported overheating very soon and consistently. Droped the voltage but same result.... So, open the case, and I couldn't believe it, the fins of the CPU radiator were compleately locked with a thick layer of dust, right between the fan and the fins... and not long I clean it up though... but we have moved house and country, so the new place may accumulate more dust than the old one...
Good clean up and problems gone emediately: Aida64 kept the test runing for a while with the normal OC without errors, the simulator didn't crashed as before... all looked a lot better... but this morning, running the sim, the computer just restarted, just like that no BSOD at all, in a split of a second, black-restart screen. The PC went back on, I run Aida64 test and emediately a hardware error came up. I have attached the zip again in the hope they can reveal something (DV it was suposed to be running as well).
I have also attached the Aiday pic
Cheers
 

Attachments

By the way, the reason I couldn't start windows was a wrong setting in the BIOS when I removed the OC. I guess you wonder how I did all of the above if I couldn't get into windows. It was just the wrong setting for storage (IDE instead of AHCI, sorry for the mistake)
 
The last crash is a power crash when reading from the hibernation file, the data in the hibernation file does not match with the previous state.
Code: 
INTERNAL_POWER_ERROR (a0)
The power policy manager experienced a fatal error.
Arguments:
Arg1: 000000000000010e, The disk subsystem returned corrupt data while reading from the
    hibernation file.
Arg2: 000000000000000a
Arg3: 0000000000000bd4, Incorrect checksum
Arg4: 0000000000001ecc, Previous disk read's checksum

And, no, driver verifier data does not appear to be available in the dump.
Code: 
0: kd> !verifier
fffff8064ce307a0: Unable to get verifier list.

What I would do if I were you, remove any OC and test the system for stability. If it is guaranteed the OC, then you can adjust it to the point where it's stable again.
 
Run the same program you used before the last crash.
 
Update
I removed the OC and run Aida64 stress test for about 2 hours with no probs at all.
Set the OC back and start with problems again. Review OC. I found two things that seem to be causing the problem.
  • RAM pushed slightly above of what the system seems to be able to cope with. Although it's rated to 2000MHz and was running at 1600 with enough voltage, seems that it is a bit too much for the system. Lowered a notch and seems to work.
  • The CPU overall speed was 4.4MHz achieved with a 22 multiplier and 200MHz FSB. I have now achieved the same with 25 multiplier and 176 FSB. That helps to reduce the RAM speed.
With those two adjustments, I have reduced the CPU voltage so far in 0.01875 volts which has an impact on heat (although it doesn't seem to be the primary problems, it is nevertheless a contributor).

Run the test and also the simulator, both without problems so far (attached a pic with, at the left, part of the stress test, and at the right only running the sim)

I'll keep testing and adjusting as needed (lowering when possible I mean). I would like your advice but it seems to me that the old OC was ok with Win7, on the limit of stability but ok, but win10 is a fraction more demanding hence causing all that ramdom trouble on a very subtle fashion, I mean not clearly showing bad OC and always with ramdom issues. Please let me know if my attemp of diagnosis is wrong or it may be something along those lines.

As I said, let me test a bit further and I'll report back.

Cheers

a
 
I do not have experience with overclocking and cannot help you with that. Maybe someone else can.

What I do know is that, because overclocking degrades hardware faster, after a few years it's inevitable that you may need to lower the overclock. This may not have anything to do with Windows 7 vs 10 but with time.
 
My be true, in any case thanks to your help the problem has been isolated and fixed. I while now running the PC and all seems to work fine. Planning for a new computer though. :-) is about time.

Thanks a lot
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top