Question Reboot from Bugcheck 0x0000000a (0xfffff30a9545e6f2, 0x0000000000000002, 0x0000000000000000, 0xfffff804152677fc).

Aug 22, 2023
12
0
10
Hey all,

Just wondering if anyone can give me a hand getting to the bottom of this, we're not having much luck and I need help from people with big brains.

'The computer has rebooted from a bugcheck. The bugcheck was: 0x0000000a (0xfffff30a9545e6f2, 0x0000000000000002, 0x0000000000000000, 0xfffff804152677fc). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 4e82bf6a-dc91-4a93-8549-32c6a184783e'

Mini Dump file - https://1drv.ms/u/s!Av4MKmCrfZNhaupShPD_I6QvEn8?e=aao0di
Memory Dump file - https://1drv.ms/u/s!Av4MKmCrfZNha402lO_MrBbPh1c?e=ALytPl

This is a new, custom build ( built by a computer shop for me), less than 1 year old. It was BSOD'ing, It's been in and had the mobo replaced, the ram cards replaced, the OS reinstalled repeatedly, the power cables replaced, peripherals replaced and I've just replaced the PSU today. I'm at a loss as to whats causing this. Any help would be MUCH appreciated. ( use small words, I'm a small brain. ) 😉
 
Crash was caused by an error, IRQL_NOT_LESS_OR_EQUAL.
From Microsoft, "An attempt was made to access a pageable (or completely invalid) address at an interrupt request level (IRQL) that is too high"

IRQ refers to interrupt levels.
Interrupt are handled by code in device drivers.

Normally this error is a device driver bug, or a hardware failure.
Hardware failure is typically more random. Device driver bug will be more consistent in giving the same error, IRQL_NOT_LESS_OR_EQUAL

Crash dump blamed this code, "MiMakeSystemCacheRangeValid" in ntkrnlmp.exe. i.e. Windows itself, which seems unlikely.

So I would start by collecting several crash dumps and see how random they are.

Very unlikely this was the PSU. You have pretty much swapped everything except the CPU.
 
Last edited:
  • Like
Reactions: CaloNord
Got ya,

Is it minidumps or memory dumps you're looking for? I have several other minidumps from other crashes it's had today.

It's doing a diskcheck at the moment, which should be done soon. After which I'll add some more dumps :)
 
You have Driver Verifier enabled with only the standard check. Has someone asked you to enable that?

The dumps seem to fall into two categories. One set (the 0x1000007E bugchecks) appear to fail because of a Driver Verifier assertion that seems to be related to farflt.sys - a Malwarebytes driver. The other set (the 0xA bugchecks) fail during a storage drive access (ntfs.sys is called) and then the cache manager gets control and that's where we see the bugcheck. This could also be Malwarebytes realted of course.

I would suggest in the first instance that you uninstall Malwarebytes and see whether the BSODs cease. Malwarebytes is usually pretty reliable, as long as it's keep updated, but the indications in the dumps can't be ignored.
 
  • Like
Reactions: CaloNord
Yea someone had mentioned it earlier today, it's now disabled again. Malware Bytes has now been uninstalled (it bluescreened halfway through but it appears to be gone now).

Is there anything wrong with the disk drive? Its a brand new SSD and passed a disk check earlier today.

I will upload further dump logs as or if they continue to occur.
 
Let's see how it goes with Malwarebytes removed. Though it's worrying that you had a BSOD during the uninstall.
Yes. It worries me a bit as well. This system has been a nightmare since day one. xD

With that uninstalled the BSODs seem to have subsided for now, programs are still not massively stable, games that are stable on my other systems crash regularly on this one, but I'm not sure if thats the games or the system.

Is upgrading to Windows 11 (something it keeps harassing me about) likely to improve anything? Or a clean install of Windows 10 for that matter?

( Thank you for taking the time to help, it's much appreciated. )
 
Last edited:
So that is a fairly diverse set of crashes.
I assume after you did a clean windows install you saw some crashes while the system was still clean, before loading up any 3rd party stuff.

Other things to try:

  • A live Linux boot and see if hardware is stable in Linux.
  • MemTest86 RAM testing
  • Check the "SMART" data on the SSD / HDD for CRC error and bad sectors.
  • Check the Window event log for any hardware related issues (e.g. PCIe bus errors). There is so much crap in this log however it can be hard to tell what is normal.
  • Check system temperatures / cooling
  • Turn off any RAM overclocking XMP setting you might have active
  • Swap out whatever has not already been swapped out. (GPU & CPU ?). Depending on your motherboard you might be able to buy a second low end CPU (Intel i3) for maybe $70 for testing.
 
  • Like
Reactions: CaloNord
Can you list specs of your hardware?
Or run userbenchmark test and show link to results page?

Indeed I can.

So that is a fairly diverse set of crashes.
I assume after you did a clean windows install you saw some crashes while the system was still clean, before loading up any 3rd party stuff.

Other things to try:

  • A live Linux boot and see if hardware is stable in Linux.
  • MemTest86 RAM testing
  • Check the "SMART" data on the SSD / HDD for CRC error and bad sectors.
  • Check the Window event log for any hardware related issues (e.g. PCIe bus errors). There is so much crap in this log however it can be hard to tell what is normal.
  • Check system temperatures / cooling
  • Turn off any RAM overclocking XMP setting you might have active
  • Swap out whatever has not already been swapped out. (GPU & CPU ?). Depending on your motherboard you might be able to buy a second low end CPU (Intel i3) for maybe $70 for testing.

The OS was installed by the local place that built it for me when it went in to have the RAM and Mobo replaced and I grabbed a new SSD while I was there. The only thing I did to it was install Steam, Chrome, Signal and BG3 and start downloading DCS World.

Why is there more crap in the log than normal? It shouldn't have much of anything on it should it?

Nothing is overclocked in anyway. Ill run the MemTest86 when I figure it out, it passed the built in windows tests with no problems and the RAM and Mobo are both brand new replacements for the previous near-new ones.

The Event Viewer log is here ( https://1drv.ms/u/s!Av4MKmCrfZNhgQNUouRVOVmoq4hm?e=YJiXoq )
 
Last edited:
Definitely run Memtest86, the latest dumps all appear to be memory related. You have two 0xC0000005 exception codes (memory access violation) and a 0xC0000096 (attempted execute of a privileged instruction) which was caused by a stack pointer error. RAM is the common denominator in these three dumps.
 
  • Like
Reactions: CaloNord
Definitely run Memtest86, the latest dumps all appear to be memory related. You have two 0xC0000005 exception codes (memory access violation) and a 0xC0000096 (attempted execute of a privileged instruction) which was caused by a stack pointer error. RAM is the common denominator in these three dumps.
What are the odds of a second set of RAM being dodgy? xD

I'll run it now, as soon as I get it figured out, then report back. :)
 
I would never upgrade a PC that was already having problems.

I've looked through the system log you uploaded and there are many error 41 messages (crash and restart) with nothing to indicate why. Some of these were BSODs but many weren't. That is strongly indicative of a hardware problem I think.

You've changed the motherboard and RAM, but what about the CPU? It might be worthwhile running Prime95 on it just to check. Run each of the three tests for about an hour each test. This will make your CPU run hot, so also have some temperature monitoring software (like CoreTemp) running to keep an eye on CPU temperatures. If Prime95 produces errors, if the system crashes or BSODs, or if the CPU gets too hot, then that would suggest a CPU issue. A good CPU should be abhle to run each of these tests pretty much continuously.
 
  • Like
Reactions: CaloNord
Hey all,

Just wondering if anyone can give me a hand getting to the bottom of this, we're not having much luck and I need help from people with big brains.

'The computer has rebooted from a bugcheck. The bugcheck was: 0x0000000a (0xfffff30a9545e6f2, 0x0000000000000002, 0x0000000000000000, 0xfffff804152677fc). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 4e82bf6a-dc91-4a93-8549-32c6a184783e'

Mini Dump file - https://1drv.ms/u/s!Av4MKmCrfZNhaupShPD_I6QvEn8?e=aao0di
Memory Dump file - https://1drv.ms/u/s!Av4MKmCrfZNha402lO_MrBbPh1c?e=ALytPl

This is a new, custom build ( built by a computer shop for me), less than 1 year old. It was BSOD'ing, It's been in and had the mobo replaced, the ram cards replaced, the OS reinstalled repeatedly, the power cables replaced, peripherals replaced and I've just replaced the PSU today. I'm at a loss as to whats causing this. Any help would be MUCH appreciated. ( use small words, I'm a small brain. ) 😉
What psu is in the machine now?
Make and model.
 
  • Like
Reactions: CaloNord
What psu is in the machine now?
Make and model.
A brand new corsair RM850e, replacing the 8 month old RM750e.

I would never upgrade a PC that was already having problems.

I've looked through the system log you uploaded and there are many error 41 messages (crash and restart) with nothing to indicate why. Some of these were BSODs but many weren't. That is strongly indicative of a hardware problem I think.

You've changed the motherboard and RAM, but what about the CPU? It might be worthwhile running Prime95 on it just to check. Run each of the three tests for about an hour each test. This will make your CPU run hot, so also have some temperature monitoring software (like CoreTemp) running to keep an eye on CPU temperatures. If Prime95 produces errors, if the system crashes or BSODs, or if the CPU gets too hot, then that would suggest a CPU issue. A good CPU should be abhle to run each of these tests pretty much continuously.
I will run Prime95 today and report back :)

Update - The first Small FFT attempt caused a BSOD in about 15 seconds.
Minidump - https://1drv.ms/u/s!Av4MKmCrfZNhgQUO09J4PwofefMC?e=mYUmKM

Second Small FFT test ran for about 25 minutes or so - heat maxes out at just under 100 degrees (Though it wasn't stressing all the cores evenly, not sure if thats intentional or not), then it seems the program crashed? Log for it below.
Log - https://1drv.ms/t/s!Av4MKmCrfZNhgQbR-Bnt0bWybuFg?e=2EIFsb
Stress - https://1drv.ms/t/s!Av4MKmCrfZNhgQm2f9YzUxPI4N70?e=H3CGE4
Heat maxes after test - https://1drv.ms/i/s!Av4MKmCrfZNhgQeHpG8pv07SoG7C?e=E4Pl1b

Update 2 - I ran one of the other tests, it too seems to have terminated itself early after about 20 or so minutes.
Log - https://1drv.ms/t/s!Av4MKmCrfZNhgQhRkDNFXHJ5U6kq?e=LyrgAD
Stress - https://1drv.ms/t/s!Av4MKmCrfZNhgQqV0IKBfFuwtDXS?e=gDFSda

While I was making this post and copy pasting stuff - it had TWO more BSODs. :/
Dumps below if they're useful.
Minidump - https://1drv.ms/u/s!Av4MKmCrfZNhgQt22hzBWXRnna0c?e=bb47D7
Minidump - https://1drv.ms/u/s!Av4MKmCrfZNhgQwZwTI91KtPiYrB?e=uoqlQl

Dodgy CPU?
 
Last edited:
This is too hot. As mentioned above, check the cooling.
These i9 CPUs can produce a huge amount of heat under load. Need a really solid cooling solution.
Fair, it has a Noctua NH-D15 in it. Normally it doesn't run that hot, the mobo has a fault code display that shows temps when running and I've never seen it above 75 or so except during that stress test.


Why are only half the cores hot? They're all at 100% usage, both fans on the Noctua are running.
 
Last edited:
That CPU has 8 performance cores, 8 efficient cores & 8 more hyper-threaded cores. So that explains why 8 are hotter.

That is a good cooler, but on the other hand it has 275W of power to dump. The i9-12900KF is not a practical CPU. Depending on what you read the Noctua NH-D15 is rated to 225W. But of course normal apps won't be the same load as Prime95.

Are fans running at max RPM when it gets to 100C? How good was the thermal paste application? Are the fans spinning the right direction?

I might be tempted to buy a low end i3-12100F CPU to test with. If that fixes the problem, you can be pretty sure it is a bad CPU.

 
  • Like
Reactions: CaloNord
Alright, I've taken it back to the shop today, it's still under warrenty so I don't see why I should be paying for it, it already cost 3 grand.

With your help and the test results and logs hopefully we'll get somewhere. :)

I'll letcha know how it goes.

Thank you all for the help, it's very appreciated. :)