[SOLVED] BSOD loop at startup with error: IRQL_NOT_LESS_OR_EQUAL, but can boot into safe mode ?

[cocosoy29]

[SOLVED] Issue caused by mixing RAM kits, I was mixing two RAM kits (exact model, 2 sets of 2x16GB). But for that specific RAM kit, my mobo only supports 2x16 or 2x32 set up, not 4x16. After getting new RAM kits, no BSOD so far.

Non stop BSOD loop at start up showing error: IRQL_NOT_LESS_OR_EQUAL. This happened this all of a sudden, the PC was fine two nights ago when I shut it down. Suddenly BSOD after I tried to turn it on yesterday.

However, I can boot into Safe mode from the blue restore screen and everything seems fine in safe mode.

I have the dump files and can upload them if anyone wants to take a look.

Here are the steps I've tried:

- Update BIOS
- Run sfc /scannow; chkdsk etc.
- Tried disable GPU in safe mode.
- Tried analyzing the dump files with WinDBG, the results point to different sys file such as ITEUCMCXCLIENT.SYS or ACPI.sys
- Wanted to run intel processor diagnostic tool but it won't let me in safe mode.
- Overnight memtest86 for RAMs, passed
- unplugged all other devices (mic, exHD, mouse etc.)

Also, safe mode with networking doesn't really give me internet 🙁

System spec:

CPU: 13900K
MOBO: ROG STRIX Z790F LGA1700
GPU: MSI 4090
RAM: GSkillz Trident Z5 (16GB x 4) 6400MT/s CL32-39-39-102 1.40V
Cooler: Lian Li Galahad 240
PSU: MSI MPG A1000G PCIE 5.0 Gold (1000W)
SK Hynix Platinum P41 2TB M2 (system drive)

If it can reliably boot into safe mode, does that mean it's probably a driver issue? At this point, what should I do?

 

[Satan-IR]

If it can reliably boot into safe mode, does that mean it's probably a driver issue?

Yes that makes it more likely.

Wouldn't hurt to look at the dumps.

Did you run MemTest with one RAM stick at a time?

Is the chipset driver installed? Latest version?

 

[cocosoy29]

Here are the dump files:

https://drive.google.com/drive/folders/1yj82tBPC--_siwOLwmEfrKixR-b2UWIg?usp=sharing

I didn't MemTest with one RAM stick at a time, I had 4 sticks and the test was done when all of them were plugged.

Chipset driver is the latest version.

Also a quick update, i was able to boot into Windows11 after performing an image recovery. But this isn't the first time BSOD happened, so I really want to find the root of the issue.

Btw, Intel Processor diagnostic tool passed.

Thank you again!

 

[Satan-IR]

Here are the dump files:

https://drive.google.com/drive/folders/1yj82tBPC--_siwOLwmEfrKixR-b2UWIg?usp=sharing

I didn't MemTest with one RAM stick at a time, I had 4 sticks and the test was done when all of them were plugged.

Thank you again!

No problem, glad to help. Will take a look at dumps see if I can find anything.

No, one stick at time as in shut down, turn off PSU, take RAM sticks out, put 1 stick in the slot the motherboard manual instructs to use with single module (most probably slot A2, second slot from CPU), boot with booatable MemTest86, run at least 4 passes, note if RAM is bad, turn off, take module out. Rinse and repeat with all other 3 sticks.

Chipset driver is the latest version.

Also a quick update, i was able to boot into Windows11 after performing an image recovery. But this isn't the first time BSOD happened, so I really want to find the root of the issue.

Good move BIOS and chipset are the latest.

If image recovery fixed it that might mean some system files were corrupted and recovery fixed them. This might also point to RAM porblem, data corruption in general, when something messes the files up (if that was indeed the case) one of the culprits can be RAM.

 

[cocosoy29]

No problem, glad to help. Will take a look at dumps see if I can find anything.

No, one stick at time as in shut down, turn off PSU, take RAM sticks out, put 1 stick in the slot the motherboard manual instructs to use with single module (most probably slot A2, second slot from CPU), boot with booatable MemTest86, run at least 4 passes, note if RAM is bad, turn off, take module out. Rinse and repeat with all other 3 sticks.


Good move BIOS and chipset are the latest.

If image recovery fixed it that might mean some system files were corrupted and recovery fixed them. This might also point to RAM porblem, data corruption in general, when something messes the files up (if that was indeed the case) one of the culprits can be RAM.

Just wondering, why test the ram stick 1 by 1 if all of them were already tested together? Are you suggesting although they passed the test together, but they could fail individually? It sounds a bit counter-intuitive to me. I'm new to all those hardware stuff, so I might be asking dumb question.

Also, is there a tool to test all the harddrives similar to memtest86? I've only done chkdsk command and it shows no issue at all for all drive. However, I've seen the PC perform disk scan/repair before booting into windows a few times over the years when I boot up. So I'm a little bit concerned about that.

 

[Satan-IR]

Just wondering, why test the ram stick 1 by 1 if all of them were already tested together? Are you suggesting although they passed the test together, but they could fail individually? It sounds a bit counter-intuitive to me. I'm new to all those hardware stuff, so I might be asking dumb question.

No question is 'dumb' we all started learning about this stuff at some time. Yes exactly, that can happen. They pass together when tested individually one or more comes out as bad RAM with errors. Then again testing RAM with tools like Windows Memort Diagnositc or MemTest86 and so on that is not 100% fail-safe method. Sometimes bad RAM slips through those too.

Also, is there a tool to test all the harddrives similar to memtest86? I've only done chkdsk command and it shows no issue at all for all drive. However, I've seen the PC perform disk scan/repair before booting into windows a few times over the years when I boot up. So I'm a little bit concerned about that.

You can use tools like CrystalDiskInfo. HDTune or HDSentinel and check a drives health by looking at the SMART information. If there's anything wrong with the drive in terms of bad sectors and reallocated ones (drives have spare/reserve sectors, in case of SSDs cells and they move data from bad sectors to them if they can read it and mark sector as bad) therefore, reallocated sector.

Usually drive manufacturers (HDD or SSD) also provide their own utilities which shows the health status of storage drives and can test them.

I will look at the dumps again and see if anyting comes up. It's a hassle but no harm in checking the RAM.

 

[cocosoy29]

No question is 'dumb' we all started learning about this stuff at some time. Yes exactly, that can happen. They pass together when tested individually one or more comes out as bad RAM with errors. Then again testing RAM with tools like Windows Memort Diagnositc or MemTest86 and so on that is not 100% fail-safe method. Sometimes bad RAM slips through those too.


You can use tools like CrystalDiskInfo. HDTune or HDSentinel and check a drives health by looking at the SMART information. If there's anything wrong with the drive in terms of bad sectors and reallocated ones (drives have spare/reserve sectors, in case of SSDs cells and they move data from bad sectors to them if they can read it and mark sector as bad) therefore, reallocated sector.

Usually drive manufacturers (HDD or SSD) also provide their own utilities which shows the health status of storage drives and can test them.

I will look at the dumps again and see if anyting comes up. It's a hassle but no harm in checking the RAM.

Thank you for explaining this to me. I will re-test the RAM as you suggested over the weekend. My Chrome sometimes crashes for no reason, which might also indicate there is a RAM issue right? Either way, I will test and report back.

For the RAM, this is the model I'm using: GSkillz Trident Z5 (16GB x 4) 6400MT/s CL32-39-39-102 1.40V

However, I am not running it at full speed since the system isn't stable when I enable the XMP profile in Bios. I'm only running it at 6000 at this point.

I will look at the tools you suggested for SSD as well! I don't mind spending the money to replace all faulty parts, but it's very frustrating and scary when I don't know what's at fault 🙁

 

[cocosoy29]

Just want to report another BSOD that happened when I was using excel, and then the PC entered a disk repair mode before booting into windows (see screenshot and dump file in the folder):

https://drive.google.com/drive/folders/1tD1ohSZAF7N4aqviv7fO8XJbYg7IGvun?usp=sharing

Both Chrome and Excel have been acting weird after the image recovery I performed (Crash and restart without reason) 🙁

---

WinDBG result on the latest minidump:

PROCESS_NAME: System

READ_ADDRESS: fffff80555f1d470: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
unable to get nt!MmSpecialPagesInUse
000000000000fffe

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s.

EXCEPTION_CODE_STR: c0000005

EXCEPTION_PARAMETER1: 0000000000000000

EXCEPTION_PARAMETER2: 000000000000fffe

EXCEPTION_STR: 0xc0000005

STACK_TEXT:
ffffcc05`56dd51b0 fffff805`582589e0 : 00000000`0000000c ffffcc05`56dd7fff 00000000`aa46c4b4 ffff988d`3afdc268 : Ntfs!NtfsGetCachedLengthInsertionPoint+0xbcfc1
ffffcc05`56dd5220 fffff805`58149600 : ffffe00a`12198348 ffffcc05`56dd0000 00000000`aa46c4b4 00000000`0000000c : Ntfs!NtfsInsertCachedLcnAtIndex+0x40
ffffcc05`56dd52b0 fffff805`581492e0 : ffffe00a`12198348 00000000`0dd0ed08 ffffe00a`2553d8a0 ffffe00a`12198300 : Ntfs!NtfsInsertCachedLcn+0x2fc
ffffcc05`56dd5360 fffff805`582c379f : ffffe00a`12198348 ffffcc05`56dd55d0 00000000`0dd0ed08 00000000`00000000 : Ntfs!NtfsInsertCachedRunInTier+0x5c
ffffcc05`56dd5400 fffff805`582c3267 : 00000000`00000000 ffffe00a`255271b0 fffff805`00000010 ffffe00a`00000007 : Ntfs!NtfsScanEntireBitmap+0x52b
ffffcc05`56dd5820 fffff805`582d8533 : ffffe00a`12198348 ffffcc05`56dd5a40 00000000`00000020 ffffe00a`01d181c6 : Ntfs!NtfsBackgroundBitmapScanWorker+0x17
ffffcc05`56dd5850 fffff805`55434f85 : ffffe00a`01d1ebb0 ffffe00a`01d18040 ffffe00a`01d1ebb0 ffffe00a`00000000 : Ntfs!NtfsSpecialDispatch+0x1a3
ffffcc05`56dd5940 fffff805`55507167 : ffffe00a`01d18040 00000000`00000176 ffffe00a`01d18040 fffff805`55434e30 : nt!ExpWorkerThread+0x155
ffffcc05`56dd5b30 fffff805`5561bb94 : ffffcf80`5eddc180 ffffe00a`01d18040 fffff805`55507110 00000000`00000000 : nt!PspSystemThreadStartup+0x57
ffffcc05`56dd5b80 00000000`00000000 : ffffcc05`56dd6000 ffffcc05`56dcf000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x34


SYMBOL_NAME: Ntfs!NtfsGetCachedLengthInsertionPoint+bcfc1

MODULE_NAME: Ntfs

IMAGE_NAME: Ntfs.sys

IMAGE_VERSION: 10.0.22621.1252

STACK_COMMAND: .cxr 0xffffcc0556dd4790 ; kb

BUCKET_ID_FUNC_OFFSET: bcfc1

FAILURE_BUCKET_ID: AV_Ntfs!NtfsGetCachedLengthInsertionPoint

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {049c7458-bf3b-66af-d2c0-e64af285b076}

Followup: MachineOwner

 

[Satan-IR]

Just want to report another BSOD that happened when I was using excel, and then the PC entered a disk repair mode before booting into windows (see screenshot and dump file in the folder):

https://drive.google.com/drive/folders/1tD1ohSZAF7N4aqviv7fO8XJbYg7IGvun?usp=sharing

Both Chrome and Excel have been acting weird after the image recovery I performed (Crash and restart without reason) 🙁

---

WinDBG result on the latest minidump:

PROCESS_NAME: System

READ_ADDRESS: fffff80555f1d470: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
unable to get nt!MmSpecialPagesInUse
000000000000fffe

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s.

EXCEPTION_CODE_STR: c0000005

EXCEPTION_PARAMETER1: 0000000000000000

EXCEPTION_PARAMETER2: 000000000000fffe

EXCEPTION_STR: 0xc0000005

STACK_TEXT:
ffffcc05`56dd51b0 fffff805`582589e0 : 00000000`0000000c ffffcc05`56dd7fff 00000000`aa46c4b4 ffff988d`3afdc268 : Ntfs!NtfsGetCachedLengthInsertionPoint+0xbcfc1
ffffcc05`56dd5220 fffff805`58149600 : ffffe00a`12198348 ffffcc05`56dd0000 00000000`aa46c4b4 00000000`0000000c : Ntfs!NtfsInsertCachedLcnAtIndex+0x40
ffffcc05`56dd52b0 fffff805`581492e0 : ffffe00a`12198348 00000000`0dd0ed08 ffffe00a`2553d8a0 ffffe00a`12198300 : Ntfs!NtfsInsertCachedLcn+0x2fc
ffffcc05`56dd5360 fffff805`582c379f : ffffe00a`12198348 ffffcc05`56dd55d0 00000000`0dd0ed08 00000000`00000000 : Ntfs!NtfsInsertCachedRunInTier+0x5c
ffffcc05`56dd5400 fffff805`582c3267 : 00000000`00000000 ffffe00a`255271b0 fffff805`00000010 ffffe00a`00000007 : Ntfs!NtfsScanEntireBitmap+0x52b
ffffcc05`56dd5820 fffff805`582d8533 : ffffe00a`12198348 ffffcc05`56dd5a40 00000000`00000020 ffffe00a`01d181c6 : Ntfs!NtfsBackgroundBitmapScanWorker+0x17
ffffcc05`56dd5850 fffff805`55434f85 : ffffe00a`01d1ebb0 ffffe00a`01d18040 ffffe00a`01d1ebb0 ffffe00a`00000000 : Ntfs!NtfsSpecialDispatch+0x1a3
ffffcc05`56dd5940 fffff805`55507167 : ffffe00a`01d18040 00000000`00000176 ffffe00a`01d18040 fffff805`55434e30 : nt!ExpWorkerThread+0x155
ffffcc05`56dd5b30 fffff805`5561bb94 : ffffcf80`5eddc180 ffffe00a`01d18040 fffff805`55507110 00000000`00000000 : nt!PspSystemThreadStartup+0x57
ffffcc05`56dd5b80 00000000`00000000 : ffffcc05`56dd6000 ffffcc05`56dcf000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x34


SYMBOL_NAME: Ntfs!NtfsGetCachedLengthInsertionPoint+bcfc1

MODULE_NAME: Ntfs

IMAGE_NAME: Ntfs.sys

IMAGE_VERSION: 10.0.22621.1252

STACK_COMMAND: .cxr 0xffffcc0556dd4790 ; kb

BUCKET_ID_FUNC_OFFSET: bcfc1

FAILURE_BUCKET_ID: AV_Ntfs!NtfsGetCachedLengthInsertionPoint

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {049c7458-bf3b-66af-d2c0-e64af285b076}

Followup: MachineOwner

The disk checking might be due to the fact that Windows did not shut down properly.

I would test RAM with MemTest86 maximum number of passes for each module plugged in individually. You might need to do this overnight as it will take a few hours to finish.

I would also check storage health just in case.

Debugger says:
Error code: (NTSTATUS) 0xc0000005 (3221225477) - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

The PC has crashed because the instruction was trying to read from an invalid memory address. This is usually caused by driver issues or hardware like RAM.

Also as soon as you open the dump in debugger it says "Probably caused by : hardware_ram ( PAGE_NOT_ZERO )".

I would run SFC /scannow from an elevated Command Prompt. That is type CMD in Windows menus earch and when the CMD icon shows up right click it and then click Run as administrator. then type SFC /scannow and hit enter.
System file checker utility checks the integrity of Windows system files and repairs them if required. After the process is complete, reboot the PC.

Also inspite of the MemTest throws error or not if possible I'd run the system with other RAM to check if BSODs happen again or not.

 

[cocosoy29]

The disk checking might be due to the fact that Windows did not shut down properly.

I would test RAM with MemTest86 maximum number of passes for each module plugged in individually. You might need to do this overnight as it will take a few hours to finish.

I would also check storage health just in case.

Debugger says:
Error code: (NTSTATUS) 0xc0000005 (3221225477) - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

The PC has crashed because the instruction was trying to read from an invalid memory address. This is usually caused by driver issues or hardware like RAM.

Also as soon as you open the dump in debugger it says "Probably caused by : hardware_ram ( PAGE_NOT_ZERO )".

I would run SFC /scannow from an elevated Command Prompt. That is type CMD in Windows menus earch and when the CMD icon shows up right click it and then click Run as administrator. then type SFC /scannow and hit enter.
System file checker utility checks the integrity of Windows system files and repairs them if required. After the process is complete, reboot the PC.

Also inspite of the MemTest throws error or not if possible I'd run the system with other RAM to check if BSODs happen again or not.

Thank you again for helping! I will start testing the RAM individually tonight and should have all 4 sticks tested by Sunday night. I am almost hoping they fail the test so I can blame BSOD on something lol (For RAM, I can at least get a RMA from Gskillz). Fingers crossed!

Meanwhile, I'm using HDsentinel to run test on HD. So far it all shows 100% Health and performance, but I'm running extended test on all sectors just to be safe.

Hopefully, it's one of the above, not my CPU/GPU/Cooler/MOBO

 

[ubuysa]

In addition to the above, one of your dumps references a third-party driver; ITEUcmCxClient.sys. This is a USB driver and is part of the chipset package. The version of this driver that you have looks quite old, dating from Aug 2021...

8: kd> lmvm ITEUcmCxClient
Browse full module list
start             end                 module name
fffff804`98ba0000 fffff804`98bb5000   ITEUcmCxClient T (no symbols)          
    Loaded symbol image file: ITEUcmCxClient.sys
    Image path: ITEUcmCxClient.sys
    Image name: ITEUcmCxClient.sys
    Browse all global symbols  functions  data
    Timestamp:        Wed Aug 25 06:21:31 2021 (6125B73B)
    CheckSum:         00015389
    ImageSize:        00015000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    Information from resource tables:

There is an updated chipset driver on the download site for your ROG STRIX Z790-F GAMING board dated 8th Dec 2023, it might be worth installing that. There look to be several updated drivers on there, it would be worth updating them all.

There's no indication in the other dumps of this driver being involved but outdated chipset drivers could cause all manner of strange issues.

There is also a very recent BIOS update available. I wouldn't suggest updating the BIOS as a matter of course, but if everything else fails to stop these BSODs then updating the BIOS would be wise.

 

[Satan-IR]

A good catch by @ubuysa. I did check that driver but didn't notice the date.

I went through the dumps again and in one of the dumps (030624-13281-01.dmp) an executable files comes up named VaM.exe . I don't think that is a system/Windows files and it's likely a third party application.

THREAD ffff950c42dec080  Cid 3620.09c0  Teb: 000000e455273000 Win32Thread: ffff950c34515cd0 RUNNING on processor 8
Impersonation token:  ffffdc075bc6e940 (Level Delegation)
GetUlongFromAddress: unable to read from fffff8051280be4c
Owning Process            ffff950c43b790c0       Image:         <Unknown>
Attached Process          ffff950c3fd75080       Image:         VaM.exe
fffff78000000000: Unable to get shared data
Wait Start TickCount      1380730     
Context Switch Count      72             
ReadMemory error: Cannot get nt!KeMaximumIncrement value.
UserTime                  00:00:00.000
KernelTime                00:00:00.000
Win32 Start Address 0x00007ff6b63db540
Stack Init fffff20ae152fbb0 Current fffff20ae152e4b0
Base fffff20ae1530000 Limit fffff20ae1529000 Call 0
Priority 8 BasePriority 8 UnusualBoost 0 ForegroundBoost 0 IoPriority 2 PagePriority 5
Child-SP          RetAddr           : Args to Child                                                           : Call Site
fffff20a`e152e4d8 fffff805`1202c5e9 : 00000000`0000000a 00000000`00000107 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff20a`e152e4e0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69

You can work with the PC after updating that driver @ubuysa mentioned and see if BSODs happen again or not.

If PC did another BSOD and if that's some 3rd party application which is not absolutely needed you can uninstall the relevant application and see if that stops the BSODs. Or if that application has, installs and uses it's own drivers and so on you can check if there's any update to the app or said (possible) driver.

 

[cocosoy29]

Thank you guys so much! I am going to check and update all the drivers. I did update BIOS last week to the latest for my Mobi.

VaM.exe is a video game I play regularly, I’ve been playing that for couple years. So from the dump file, does it say this application is the cause of the BSOD? I’m not aware of any driver associated with this game. But it is a very demanding game in terms of CPU/GPU. Can a game cause BSOD by just sitting in the hard drive? This is kind of concerning since I do want to keep playing that game.

A quick update on the RAM issue, I tested each stick individually at the max pass (at least for the free version). They all passed with 0 error. However, I was checking my mobo and ram QVL. I found out my mobo doesn’t support 16gbx4 setup for my specific RAM! I bought 2 kits of 16x2 and mixed them together. Could that be the issue? I always thought you could mix RAM kits as long as they are the exact model. Either way, I have ordered some new RAM from the QVL (this time I made sure it’s supported on both the Mobo and RAMs QVL) and will test it out tomorrow when it arrives as you suggested.

p.s. while waiting for the new RAM, I did some Prime95 tests. With XMP enabled, it gives almost instant failure and BSOD. So the system is definitely not stable at this point.

 

[Satan-IR]

Can a game cause BSOD by just sitting in the hard drive? This is kind of concerning since I do want to keep playing that game.

No, more likely scenario is the BSOD occured while you were running the game or maybe game was running and you switched to desktop or some other like streaming apps perhaps or Discord or something of that sort?

I bought 2 kits of 16x2 and mixed them together. Could that be the issue? I always thought you could mix RAM kits as long as they are the exact model.

This is basically a bad idea since it's always a gamble. Even if they're the same model number which is metioned in the motherboard QVL for RAM. Sometimes they work OK, sometimes there are issues (likely in your case) and sometimes they outright refuse to play nice and won't even boot etc.

Check part numbers and run system with either pair that came as a pack/sold together and that might be it! There's a reason RAM come in packs. They make sure they run together. Yes same model number same specs and everything. There's no guarantee mixed RAM would work as user would like them to.

 

[ubuysa]

I truly have lost count of the number of BSODs I've seen that were caused by mixing RAM. That your manual doesn't support the RAM config you had is also very concerning. I think you've been wise to order fully supported RAM.

BTW. When it failed Prime95 which test did it fail? (Large FFts, small FFTs, or Blend)

 

[cocosoy29]

No, more likely scenario is the BSOD occured while you were running the game or maybe game was running and you switched to desktop or some other like streaming apps perhaps or Discord or something of that sort?


This is basically a bad idea since it's always a gamble. Even if they're the same model number which is metioned in the motherboard QVL for RAM. Sometimes they work OK, sometimes there are issues (likely in your case) and sometimes they outright refuse to play nice and won't even boot etc.

Check part numbers and run system with either pair that came as a pack/sold together and that might be it! There's a reason RAM come in packs. They make sure they run together. Yes same model number same specs and everything. There's no guarantee mixed RAM would work as user would like them to.

Can't believe I overlooked something this basic! It even says on the RAM box "DO NOT MIX KITS".... Not sure where I got the misconception that RAM kits can be mixed. I believed in that as long as I've been building PC.

Hopefully this is indeed the issue, I'm going to test with the new kit today and see if it still BSOD. Will report back. Thanks again for all your help and paitently explaining everything tot me. Really appreciate it!

 

[cocosoy29]

I truly have lost count of the number of BSODs I've seen that were caused by mixing RAM. That your manual doesn't support the RAM config you had is also very concerning. I think you've been wise to order fully supported RAM.

BTW. When it failed Prime95 which test did it fail? (Large FFts, small FFTs, or Blend)

Hmm, I'm not sure which test it failed. I just ran the default test, and it goes Beep then BSOD.

Also, I haven't got a BSOD all day today after switching to the new RAM kit!

 

[cocosoy29]

No BSOD so far!

How do I mark this thread as solved, and pick the best answer? I don't see the option anywhere.

 

[Satan-IR]

Glad your system is stable. Chech this thread here on how to mark a post as best solution and thread as 'solved'.

 

[cocosoy29]

Glad your system is stable. Chech this thread here on how to mark a post as best solution and thread as 'solved'.

I actually had 3 BSOD today again... while I was away from PC 🙁 3 of them happened very close together while I was taking a shower, another one happened later during dinner.

I've added the new dump files to that folder: https://drive.google.com/drive/folders/1tD1ohSZAF7N4aqviv7fO8XJbYg7IGvun?usp=drive_link

Not sure if I can reopen this thread.

p.s. PC just failed to boot like before, took a couple tries to boot into windows, added dump into folder.

 

[ubuysa]

Why was a disk check and repair happening?

Three of those BSOD happened during storage drive operation - the Windows ntfs.sys driver is on the call stack leading up to the BSOD. If these BSODs ONLY happen at boot, then coupled with that disk repair and the ntfs.sys driver being referenced in some of these dumps, I would look at that NVMe system drive.

I have seen several issues in the recent past that seem to have been caused by badly seated M.2 drives, so initially I would remove the drive, make sure the drive and M.2 port contacts are clean (don't blow on them with your mouth!) and then firmly re-seat the drive.

SK Hynix has a Drive Manager download, if that includes and diagnostic tests then run them. It may also display the SMART data, that would be worth looking at too. They also have a 5-year warranty on those drives so you might try an RMA on it?

 

[Satan-IR]

I actually had 3 BSOD today again... while I was away from PC 🙁 3 of them happened very close together while I was taking a shower, another one happened later during dinner.

I've added the new dump files to that folder: https://drive.google.com/drive/folders/1tD1ohSZAF7N4aqviv7fO8XJbYg7IGvun?usp=drive_link

Not sure if I can reopen this thread.

p.s. PC just failed to boot like before, took a couple tries to boot into windows, added dump into folder.

Well I said above you can check storage health with those tools and you didn't come back to us with any issues regarding storage and I thought drive is healthy and everything is OK.

I agree with @ubuysa I had noticed the ntfs driver mentioned in 1-2 other dumps before but since you didn't report anything wrong with the SSD health I though it's not an issue.

You also didn't come back to us regarding running SFC /scannow I mentioned in post#9 either.

Using the app made by the drive manufacturer or one of the tools I said above check the SMART data on the drive and post the link to a screenshot here so we can take a look. You can upload the screenshot to imgur.com. No sign up required. just click the green +New Post button on top left corner, upload the file and post link here.

I will look at the dumps later.

 

[cocosoy29]

Why was a disk check and repair happening?

Three of those BSOD happened during storage drive operation - the Windows ntfs.sys driver is on the call stack leading up to the BSOD. If these BSODs ONLY happen at boot, then coupled with that disk repair and the ntfs.sys driver being referenced in some of these dumps, I would look at that NVMe system drive.

I have seen several issues in the recent past that seem to have been caused by badly seated M.2 drives, so initially I would remove the drive, make sure the drive and M.2 port contacts are clean (don't blow on them with your mouth!) and then firmly re-seat the drive.

SK Hynix has a Drive Manager download, if that includes and diagnostic tests then run them. It may also display the SMART data, that would be worth looking at too. They also have a 5-year warranty on those drives so you might try an RMA on it?

The disk check and repair happen randomly after a BSOD, I haven't figured out a pattern yet. But I've seen it close to a dozen times over the year 🙁

I'm going to try that Drive Manager you mentioned and run the test.

I will also try to reseat the drive on the weekend. Btw, what's the best way to clean port contacts without blowing on them with my mouth lol. Is it better to use a wipe or an electric blower?

 

[cocosoy29]

Well I said above you can check storage health with those tools and you didn't come back to us with any issues regarding storage and I thought drive is healthy and everything is OK.

I agree with @ubuysa I had noticed the ntfs driver mentioned in 1-2 other dumps before but since you didn't report anything wrong with the SSD health I though it's not an issue.

You also didn't come back to us regarding running SFC /scannow I mentioned in post#9 either.

Using the app made by the drive manufacturer or one of the tools I said above check the SMART data on the drive and post the link to a screenshot here so we can take a look. You can upload the screenshot to imgur.com. No sign up required. just click the green +New Post button on top left corner, upload the file and post link here.

I will look at the dumps later.

I did run extended tests with HDsentiel, all drives show 100% healthy with 0 bad sectors. So I thought the drives are good too!

Now, the SFC scan thing is interesting. The first time I ran it, it says ”windows resource protection could not perform the requested operation.“ I did some research online and did a DISM restore health thing. After that, I was able to run SFC /scannow. It shows there is one corrupted file "BTHMODEM.sys" and it was repaired.

I will run test with the manufacture tool again on the SSD and report back.

Thank you guys!!

 

[cocosoy29]

Here are some of the report screenshots after running test with HD Sentinel and SK Hynix tool:

https://imgur.com/a/FI7U2Mx

View: https://imgur.com/a/FI7U2Mx


Let me know if there is any specific detail you guys may need to know.

p.s. imgur is great!!