System experiencing crashes from multiple BSOD errors?
System experiencing crashes from multiple BSOD errors?
I would open the BIOS and verify the system date and time to determine if it was reset to defaults. (in case the battery failed and you lost the BIOS settings, leading to incorrect memory timings)
If the BIOS information appears normal, proceed with testing memory timings using memtest86. If the memory timings are acceptable, address the remaining issues below.
(Need to complete an errand; I'll review another dump once I return)
Reviewed the most recent bugcheck; system was running for about 20 minutes.
bugcheck 0x124 suggests a possible bad overclock from the overclock driver.
(removed overclock driver)
Attempting to inspect details reveals info is being paged out to pagefile.sys.
Debugger isn't able to locate the correct symbols for this build.
!errrec reported that the debug function disliked the returned data structures.
0: kd> !sysinfo cpuspeed
CPUID: "Intel® Core™ i5-8400 CPU @ 2.80GHz"
Rated Speed: 2800
Measured Speed: 2808
Indicates an overclock, possibly due to issues in IntelHaxm.sys.
third bugcheck, system ready for 31 minutes
heap corruption detected, in store.
unable to validate the page frame because symbols don't match.
possibilities: update bios, cpu chipset drivers, disable virtual memory and restore it to dump pagefile.sys, then create a new one.
run crystaldiskinfo.exe and analyze smart data from the drive to assess drive health.
consider reinstalling windows for a clean build without modified kernel files.
or try using dism.exe repair.
Removed Intel Hardware Execution Manager (intelhaxm.sys)
Verified the date and time along with BIOS/UEFI settings on my motherboard.
All details match the default configuration.
Performed
DISM.exe /online /cleanup-image /scanhealth
Result: No component store corruption found, process finished without issues.
The PC displayed a BSOD after executing the first
DISM.exe /online /cleanup-image /scanhealth command in CMD (I attached the minidump file).
I restarted the computer and rerun the command, which succeeded.
EDIT:
Checked WhoCrashed to see if different outcomes appeared during a BSOD, and it matched this result.
https://imgur.com/D8MJ8Xw
Also uploaded the memory dump file while making these changes.
Additionally, ALSysIO64.sys is included in the Core Temp tool, one of the systems I use to track temperatures.
Minidump Files (as of April 28, 2025)
These are the Minidump files recorded after BSOD occurrences.
Windows Minidump Files (stored in Google Drive folder)
to be more precise, the user mode service attempted to access data from the file system cache, prompting the cache manager to be invoked. subsequently, the Windows memory manager tried to prefetch pages, which ultimately triggered a bug check. it might simply indicate an issue with the storage, such as a corrupted pagefile or faulty drivers/malware.
i cannot rely on the symbols because the debugger does not accept your kernel version or crash dump.
you may search online for instructions on forcing Windows to remove pagefile.sys during a system reboot, then adjust the registry and restart. this process might help extract malware from the pagefile.sys.
the cpu executed a panic bug check, but the memory structure could not be read from the memory dump file. the symbols appear incorrect, yet the stack trace suggests windows cache management and memory management calls prior to the bug check.
i suspect the cpu performed a panic bug check and ended up saving a corrupted memory dump.
the system remained operational for about 10 minutes. i would be checking for abnormal voltage readings, an overheating CPU, or a stopped CPU fan—anything that could affect voltage accuracy.
alternatively, you might try using a keyboard to force a memory dump, adjust the registry settings, and perform a memory dump on the active system. this could confirm whether you obtain a clean dump.
you could also consider booting the system from a Windows installation image without installing it, just to observe if the CPU crashes.
if the CPU does not crash, ensure the BIOS is up to date and the CPU chipset drivers are current. due to the corrupted memory dump, you might need to disable Windows virtual memory and reboot. windows would then create an internal RAM pagefile. you can verify whether the system runs longer without a memory dump; if it crashes, you won’t get a clean dump.
after that, inspect the CPU for bent motherboard pins, burnt traces on the back of the CPU, or degraded CPU paste.
i assume you have verified that the BIOS is reporting correct voltages from your power supply.
Apologies for revisiting this discussion. I'm still facing the same issues with BSODs. I'm trying to figure out what might be causing the problem. I've shared the newly created minidumps here.
(All were generated from day "0 42925" to "050125").
Because I can't upload the minidump files via Google Drive, here are the screenshots from WhoCrashed instead.
overall, looks like overheated cpu causing the cpu to crash.
if this is not a overheating/power issue then update the bios to version F14a
to pick up the microcode fixes to prevent cpu hacks. then run your dism.exe command or reinstall windows to get the system stable. (checksum errors in windows files) code running from kernel address but not from inside a known windows module or named driver.
--------
I looked at several more minidumps.
overall my first guess is overheated cpu.
(check fan)
second guess would be improper power to cpu.
(i did not see any overclock drivers installed, bios had a very slight overclock by 8Mhz.)
very old bios version installed. I suspect if you boot into bios and leave the machine on, it will still crash while in bios. check the fans and power, if the machine is stable you will eventually want to update the bios and motherboard drivers and apply cpu firmware updates.
then attempt to fix your windows install by deleting the pagefile.sys and making another one. then run cmd.exe as an admin and run
dism.exe /online /cleanup-image /restorehealth
note: bunch of the bugcheck showed kernel address that looked valid but were not. this can indicate that the memory timings are wrong and you should run memtest86 to test. I would check the bios system time and date to see if it is wrong (indicating that the motherboard cr2032 battery has failed and the bios went back to defaults)
------------
most current minidump looked like a driver bug,
(will take a look at the kernel dump to see if i can figure out the driver)
kernel dump was a bugcheck 0x124.
looks like a usermode program made a call, and the there was some problem in cache management and the window memory manager before the bugcheck.
debugger does not like your memory dump, can not find proper symbols/ check sum errors.
since the machine is old, I would boot into bios, check the system date and time and make sure the motherboard battery did not die. (time will go to default)
then check the cpu fan and blow out dust and make sure the fan is spinning.
boot into bios and check voltages for 3.3v 5.0v and 12v to make sure they are within 10 %
make sure your fan in the psu is working.
the system up time was 10 minutes, it could indicate overheating of the cpu or the psu.
machine info:
BiosMajorRelease = 5
BiosMinorRelease = 12
BiosVendor = American Megatrends Inc.
BiosVersion = F2
BiosReleaseDate = 06/22/2018
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = H310M H 2.0
-------------------
the first bugchceck error code indicated an access violation.
the data at the memory location is incorrect, you do not know why.
the second bugcheck looks like it has valid kernel address but they are not.
Normally, you would first update the bios to get the best default memory timings, set your memory profile then test your memory by booting memtest86 and running the test.
I would also update the cpu chipset drivers, delete the pagefile.sys by turning off windows virtual memory and turning it back on again.
(just for the case where the problem is in virtual memory (pagefile.sys))
you might even download a utility like crystaldiskinfo.exe and read the smart data from the drive to see if it is having errors.
turn off any overclocking, make sure you do not have two overclocking drivers installed.
will take a quick look at some dumps in a minute.
I'm also encountering hardware errors while reviewing reliability history in Windows. I've included the two watchdog dump files produced, along with one minidump file created between them.