I've got a load of HD-DVDs which I'm backing up while my ageing LG HD-DVD/Blu-Ray combi drive still works.
I was using Handbrake, so x264 at the time. I am quite heavily overclocked at 4.6Ghz so I suspect I may need to increase the voltage slightly, but system was well and truly soak tested at the time the overclock was finalised last year. Both Prime95 and memtest ran overnight without errors, also tested with x264 before without error but this was with Windows 8.1.
Zip file attached as requested:
DESKTOP-05_09_2015_183057_37.zip
Hi SpecChum,
Welcome to the 10blog.
Remove the overclocking and see if that helps.
The error 0x124 WHEA_UNCORRECTABLE_ERROR (Windows Hardware Error Architecture)
This means that there are problems with your hardware, unfortunately this error rarely gives enough information for a specific cause. Fortunately, this error is mostly caused by overclocking or faulty drivers.
Thanks for the welcome
I think I know what it might be actually, I seem to remember I lowered the ring (cache) voltage quite a few months ago. I took it from auto which set it to a ridiculously high amount so I set it manually. I've not had 1 BSOD since, I don't think I've tried x264 since either.
I'll raise that and try the encode again
Keep us posted
Will do, nothing unusual in my zipped logs?
There is a fair chance that the issue is caused of RAID.In Sevenblog we have experienced it with a great frequency that RAID is problematic. So if RAID is not a must for you, dont go for RAID. Disable RAID in BIOS (which may claim a clean reinstallation of windows; usually changing the storage controller mode does not allow windows to boot up) and see how it goes.Code:BugCheck 124, {0, ffffe0014e9de028, ff800000, 124} *** WARNING: Unable to verify timestamp for iaStorA.sys *** ERROR: Module load completed but symbols could not be loaded for iaStorA.sysProbably caused by : GenuineIntel Followup: MachineOwner ---
If RAID is a must for you, search for any possible update to Intel Chipset SATA RAID Controller in MSI India - Computer, Laptop, Notebook, Desktop, Motherboard, Graphics and more
See how it goes. Let us know.
This was going to be my 2nd thing to check, but thank you for posting itThere is a fair chance that the issue is caused of RAID.In Sevenblog we have experienced it with a great frequency that RAID is problematic. So if RAID is not a must for you, dont go for RAID. Disable RAID in BIOS (which may claim a clean reinstallation of windows; usually changing the storage controller mode does not allow windows to boot up) and see how it goes.Code:BugCheck 124, {0, ffffe0014e9de028, ff800000, 124} *** WARNING: Unable to verify timestamp for iaStorA.sys *** ERROR: Module load completed but symbols could not be loaded for iaStorA.sysProbably caused by : GenuineIntel Followup: MachineOwner ---
If RAID is a must for you, search for any possible update to Intel Chipset SATA RAID Controller in MSI India - Computer, Laptop, Notebook, Desktop, Motherboard, Graphics and more
See how it goes. Let us know.
RAID certainly is not essential no, in fact if anyone is thinking of RAIDing 2 SSDs together, don't bother; it's unnoticeable outside of synthetic benchmarks.
I had every intention of installing back onto a single SSD next time a new install was needed.
Saying that though I dare say if RAID was the culprit I'd be seeing a BSOD of some sort more frequently. This is the only one I've had since I settled on this over clock almost 12 months ago. I game as well so PC is well used.
EDIT: I've increased the ring voltage and encoding again now, same setting. 2.5hrs left, so I'll let you know how it goes.
16 mins left on the encode and working fine so far, crashed well before this before, but I've just realised, I did an nvidia driver update just before the BSOD and did I reboot after the update? Nope. D'oh!
Maybe the voltage increase wasn't needed at all.
Only thing that I would call unusual is missing files.Will do, nothing unusual in my zipped logs?
Keep us posted in case of new bluescreens.
