Question BSODs - - - 0x101, 0x1AA, 0x7F etc?
Question BSODs - - - 0x101, 0x1AA, 0x7F etc?
PC Specifications
CPU: Intel Core i7 - 10700 OEM
GPU: NVIDIA GeForce RTX 3060 Ti Gigabyte 8Gb (GV-N306TXGAMING OC-8GD)
Motherboard: ASRock H510M-HVS R2.0
RAM: 32GB DDR4 3200MHz Kingston Fury Beast Black (KF432C16BB1K2/32) (2x16Gb KIT)
Power Supply: 750W DeepCool DQ750-M-V2L WH
BIOS/Update: 012526-9515-01.dmp is the latest; other versions available at provided links
Diagnostics: WhoCrashed indicates possible hardware or driver problems, though I’m unsure of the exact cause. The system shows no thermal warnings, and temperatures remain normal. I attempted reinstalling Intel and Nvidia drivers, but nothing resolved the issue. The SFC/SCAN and DISM commands found no errors. Memory tests passed with 100 to 97% integrity. The SSD appears older and slower compared to the main drive.
Would you like me to attempt uploading a complete memory dump? It will take some time and I’ll share once it’s ready.
Power Supply (PSU):
750W DeepCool DQ750-M-V2L WH
What is the age of the PSU in your setup?
You didn't specify the case and storage model; could you share how you manage processor cooling? What temperatures do you observe during BSoD occurrences? What BIOS version is installed on your motherboard right now?
I attempted to reinstall Intel drivers and Nvidia video drivers, but it didn't resolve the issue.
Can you provide more details?
PSU is 2-3 years old.
Be Quiet Pure Rock 2 is the cooler for the processor.. Also some 4 fans from same vendor- 3 in front and one in back. case is Zalman Z10 Black. Bios P1.50. temps are 30-50 ranges for the processor and 63-73 for the car, no overheating that i could find.
Nvidia video drivers i reinstalled using DDU. Intel ones i took from my MB's vendor site and just installed.
Final Fantasy 14 and decided to try ZZZ- tho unsucsessfuly(it doesnt tax my system but crashes do occur more often in it)/ There are many others but crashes did not occur in any of em (at least in last couple of years). Installer for ZZZ sourced from the correct site of the game that i double checked, FF14 same thing- legitimate vendor.
Edit:grammar
Three of those files are unavailable, unclear why. The remaining two include one with a CLOCK_WATCHDOG_TIMEOUT, often caused by a problematic CPU. The other is a general KMODE_EXCEPTION_NOT_HANDLED error, possibly due to a faulty driver, insufficient RAM, or a defective CPU.
If the most recent crash was the CLOCK_WATCHDOG_TIMEOUT, consider submitting the complete kernel dump (C:\Windows\Memory.dmp). However, if the latest crash had a different stop code, it may not be necessary.
It is recommended to download Prime95 and perform stress tests on your CPU. Ensure the cooling system functions correctly and maintain adequate airflow around the PC to prevent overheating. Execute each of the three tests—smallFFTs, largeFFTs, and Blend—for at least an hour. The small FFT test targets the CPU more than RAM, the large FFT test targets RAM more than the CPU, while the Blend test combines both.
Should Prime95 produce error messages, cause the system to crash or display a BSOD, or reach CPU temperatures near 100°C (the maximum for your processor), cease the testing and inform us of the outcome.
For the future, you should set the dump type to 'Automatic memory dump'. Setting it to 'Full memory dump', as you have, makes the dump the size of RAM. I'm sure you didn't enjoy uploading 32GB of data, I certainly didn't enjoy downloading it. The full memory dump includes all the privates address spaces and nobody can debug those because the third-party vendors don't make symbol files available. The only dump we need is the Windows kernel. The 'Automatic memory dump' takes a kernel dump but gives Windows some latitude in changing the pagefile size to accommodate the dump.
What makes the above worse is that the most recent BSOD was NOT for a CLOCK_WATCHDOG_EXCEPTION bugcheck at all, so we didn't need that dump anyway!
There are a few things I've noticed in that dump...
1. The MbamElam.sys driver unloaded immediately before the dump, sometimes that's significant. This is a Malwarebytes driver, yet I don't see any other Malwarebytes drivers loaded, and I would expect to. Have you uninstalled Malwarebytes? If so, it wasn't uninstalled fully, use the
Malwarebytes Support Tool
to fully uninstall it. I also see the same driver unload in the minidump for the CLOCK_WATCHDOG_TIMEOUT bugcheck and no other Malwarebytes drivers loaded. If Malwarebytes is installed then make sure it's fully up to date (this is particularly important for Malwarebytes)..
2. Whilst there is no indication that it was involved in the BSOD, your LAN driver (rt68cx21x64.sys) is old, dating from July 2021 - which pre-dates Windows 11. I would visit you motherboard vendor's website and look for an update to this driver.
3. I can see the HoYoKProtect.sys Genshin Impact anti-cheat driver loaded. Whilst there is no indication that this driver was in any way responsible for the BSODs we know from long experience that all anti-cheat drivers cause BSODs on many systems now and then. It might be wise to uninstall the game and anti-cheat driver and see whether the problem remains. Note that anti-cheat drivers stay loaded even when not playing the game and can cause issues at any time.
4. There is a call to UnityPlayer.dll in the lead-up to the bugcheck in the full memory dump. Whilst that doesn't mean it's at fault it is very suspicious. I know very little about Unity Player but it looks like a game creation platform(?). I would disable/uninstall this feature and see whether the problems remain. This is strongly recommended since we know it was involved in the bugcheck.
5. Related to the above regarding Unity Player, I can also see libraries for the Unity ZF Browser that appears to allows embedding browsers in games(?). There's no indication that these libraries were directly involved but these kinds of tools must be considered suspect. You need to do some extensive testing by disabling/uninstalling this tool and see whether the problem remains.
6. There are many calls in the lead-up to the bugcheck to iaStorAC.sys, the Intel Rapid Storage Technology driver. There are also calls to storport.sys, the Windows storage driver. The version of iaStorAC.sys that you have installed is old, also dating from July 2021 and thus pre-dating Windows 11. You should look for an updated version of this driver from your motherboard vendor's website.
Given the outdated drivers above I would also suggest you check your motherboard vendor's website and update all outdated drivers. Whilst you're there look for a BIOS update too, that can often contain important updates/fixes.
Well, I have Malwarebytes installed, but it has been crashing even before that. Is it a problem with having it?
3,4,5 – this is related to ZenlessZoneZero. It runs on Unity, includes an in-game browser feature and uses anticheat. I got it recently due to a promotion, but crashes kept happening before then, so it probably isn’t the main cause.
2 and 6 – I’ll check it out. The MB is outdated, and those driver versions are actually recommended for WIN 11 on the vendor’s site. I’m looking for good full-sized ones, but they’re not available. Selling second-hand or shelf options is an option, though I’m unsure. Upgrading to a newer chipset isn’t feasible because of the high prices, so the only choice left is another H510M, which seems unnecessary.
012626-15515-01.dmp
recently crashed again.
Edit: To be clear, I was playing the game when the BSOD occurred.
I was thinking about upgrading to lga1700. AMD isn't an option either because its mainly RAM is the problem—my system has 32 GB of DDR4, but all the new models currently on sale use DDR5, and I'm not willing to spend a monitor or nearly a GPU for a couple sticks, especially since I can't afford that.
I highly recommend updating the BIOS. A recent update (version 1.60 from 12th January 2026) is available on your motherboard vendor's site. Many of the drivers listed there are outdated, even though they were released alongside Windows 11. It’s important to install these updated drivers to ensure compatibility.
Additionally, the RAM you have (2 x Kingston 16GB KF3200C16D4/16GX) isn’t recognized by the system for that CPU and motherboard. This could cause issues, especially if you experience BSODs. Do you still have the original RAM installed?
Regarding the dump you provided, the specific bug (0x133 with argument 1 = 1) can only be resolved using a full kernel dump. Please upload the file C:\Windows\Memory.dmp before another BSOD occurs to prevent it from being overwritten. Malwarebytes is up to date, but always ensure it’s running properly.
Didn't manage to fix settings before BSOD, so I'll wait for the next one.
Definitely going to update the BIOS, even though it was already released before.
I thought I had everything installed, but now I'm confused.
Both versions are really problematic—I realize they're not on the list at all. RAM is also way too expensive right now... And I don't have any other options. It seems like I made a mistake when picking this motherboard.