Windows 10: Win10 Random BSOD

Hi,

This PC started crashing randomly about 3 weeks ago. No hardware changes have been made.
The following error keeps popping up in the event viewer:

Code: A corrected hardware error has occurred.Reported by component: Processor CoreError Source: Corrected Machine CheckError Type: Internal parity errorProcessor APIC ID: 0The details view of this entry contains further information[/quote] .

Logs, dumps are attached.
Help would be greatly appreciated.

Cheers,

NR.

:)

 

Legacy Geforce 6150se nforce 430 -- Random BSOD's with 1709

Same identical hardware and software issue here (6150SE GPU, NVidia 309.08 driver)

Found a better test than random BSOD, use Google earth. Runs perfect with Win10 1703, 1709 has rendering problem in main window (all black). Clearly something changed in graphics subsystem.

Left notes at link below. Entire thread BSOD with 6150SE GPU + 309.08 driver + Win10 1709 combination

Random blue screen after Windows 10 Fall Creators update - HP Support Forum

Also posted on Feedback app

 

Reinstalling Win10 on new HDD

I upgraded to Windows 10 for free. I'm happy with it, however my HDD is failing. Strange noises, random BSODs, sometimes fine. I am using the media creation tool now, whilst my rig is stable, to create a USB installer.

Question: When I'm installing Win10 it'll ask me for product key, which I've read in other threads I should skip. How will Win10 then determine my product key, version etc?

 

Hello netRAT and welcome to TenForums *Smile

I've had a look at the three crash dump files that were recorded over the last 2 days and while there is one possibly hardware related they could be caused by driver issues.

Two or more drivers were found as showing errors:

Code: BugCheck 1000007E, {ffffffffc0000005, fffff8032bcb0e02, ffffae84d9ffdb58, ffffae84d9ffd3a0} *** WARNING: Unable to verify timestamp for HPMoA407.sys *** ERROR: Module load completed but symbols could not be loaded for HPMoA407.sys *** WARNING: Unable to verify checksum for win32k.sys Probably caused by : HPMoA407.sys ( HPMoA407+1730 )[/quote] and

Code: *** WARNING: Unable to verify timestamp for TMUMH.sys *** ERROR: Module load completed but symbols could not be loaded for TMUMH.sys Unable to load image \SystemRoot\system32\DRIVERS\tmevtmgr.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for tmevtmgr.sys *** ERROR: Module load completed but symbols could not be loaded for tmevtmgr.sys[/quote] Try updating the Mouse Suite drivers for HPMoA407.sys and try updating or removing the Trend Micro Security software for the the other.