Multiple BSODs

defour

defour

Member
Joined
Apr 13, 2025
Posts
14
Hey Everyone,

1744753570931.webp
Honestly its killing me.
  • A brief description of your problem (but you can also include the steps you tried) My Machine is having multiple different BSODs (Sometimes daily, sometimes multiple times a day),I tried many things, like Reinstall windows (without deleting data), Migrating windows to new SSD (M.2), Changing RAMs, Changing Power Supply, Reinstalling some drivers, tried 1 pc of ram in every RAM Slot, tried MEMTEST Tools (all good), tried sfc scannow and other commands like chkdsk and DISM..etc all succeeded.
  • System Manufacturer? N/A (PC I Built)
  • Laptop or Desktop? Desktop
  • Exact model number (if laptop, check label on bottom) N/A
  • OS ? (Windows 11, 10, 8.1, 8, 7, Vista) ? Windows 11 Pro
  • x86 (32bit) or x64 (64bit)? 64Bit
  • (Only for Vista, Windows 7) Service pack? N/A
  • What was original installed OS on system? Windows 11
  • Is the OS an OEM version (came pre-installed on system) or full retail version (YOU purchased it from retailer)? not sure how to answer, I installed W11 myself and activate it using key from ebay or sth.
  • Age of system? (hardware) Differs, some parts are new some are old. but most are new (2-3 years)
  • Age of OS installation? not sure when exactly. maybe 4 years.
  • Have you re-installed the OS? yes, but without deleting data/apps.
  • CPU : Intel i7-13700KF
  • RAM (brand, EXACT model, what slots are you using?) VENGEANCE® RGB PRO 64GB (4 x 16GB) DDR4 (CMW64GX4M4D3600C18) - using all slots
  • Video Card : Zotac RTX 4070 Ti
  • MotherBoard - (if NOT a laptop) : MSI Z790 EDGE WIFI DDR4
  • Power Supply - brand & wattage (if laptop, skip this one) : ASUS TUF Gaming 1000W Gold ‎90YE00S1-B0NA00
  • Is driver verifier enabled or disabled? disabled, I remember enabling it then I got endless BSODs
  • What security software are you using? (Firewall, antivirus, antimalware, antispyware, and so forth) Windows Defender.
  • Are you using proxy, vpn, ipfilters or similar software? Nope
  • Are you using Disk Image tools? (like daemon tools, alcohol 52% or 120%, virtual CloneDrive, roxio software) no
  • Are you currently under/overclocking? Are there overclocking software installed on your system? no

    Speecy Snapshot : http://speccy.piriform.com/results/5IErGk6ZjEn2XHotGga047j

    Please help! and hopefully we can solve it without freshly installing windows again, the PC have multiple passkeys for diff accounts and also my work apps..etc
    it'll be too hard for me to fresh install windows.
 

Attachments

System Information > Problem Devices > Intel(R) Wi-Fi 6E AX210 160MHz PCI\VEN_8086&DEV_2725&SUBSYS_00248086&REV_1A\4&BCC1B65&0&00E2 This device is disabled.

Bluescreens are directed towards your memory
You have hundreds of errors relating to bad block(s) of the SSD.
 
ET_Explorer said:
System Information > Problem Devices > Intel(R) Wi-Fi 6E AX210 160MHz PCI\VEN_8086&DEV_2725&SUBSYS_00248086&REV_1A\4&BCC1B65&0&00E2 This device is disabled.

Bluescreens are directed towards your memory
You have hundreds of errors relating to bad block(s) of the SSD.
Click to expand...
Yeah i've Wi-Fi Disabled on purpose
but I've re-enabled it now, and just turned it off instead of disabling it.

Regarding SSD Bad Block, I've changed my system drive (Migration/Cloning) but still have issues, how can I check which SSD is that ?
and will I get crashes if bad SSD wasn't the system Drive ?

List of my Data Drives :

Markdown (GitHub flavored): 
476GB P3-512 (SATA (SSD))
111GB ADATA SP550 (SATA (SSD))
465GB Samsung SSD 980 PRO 500GB
1863GB Netac NVMe SSD 2TB
931GB NVME SSD 1TB
1863GB Netac NVMe SSD 2TB
 
Intel i7-13700KF only supports Up to DDR4 3200 MT/s
and you have DDR4 3600 which isn't supported. Ram Info.html shows 2133 MHz
so you down clock the DDR4 3600 to 2133 MHz
 
ET_Explorer said:
Intel i7-13700KF only supports Up to DDR4 3200 MT/s
and you have DDR4 3600 which isn't supported. Ram Info.html shows 2133 MHz
so you down clock the DDR4 3600 to 2133 MHz
Click to expand...
i didnt down clock the ram, when I turn on XMP crashes happen more often.
so with XMP Turned off, its 2133 MHz

Also that's interesting, didn't know that max is 3200 on my CPU.. what do you suggest ?
 
You appear to be running unlicensed copies of EASEUS and Adobe products and your statement that...
...I installed W11 myself and activate it using key from ebay or sth.
Click to expand...
...suggests that you may not have a valid Windows license. Can you please enter the command slmgr /dlv, either in the Run command box or in a command prompt window. Please post a screenshot of the small window that opens.
 
ubuysa said:
You appear to be running unlicensed copies of EASEUS and Adobe products and your statement that...

...suggests that you may not have a valid Windows license. Can you please enter the command slmgr /dlv, either in the Run command box or in a command prompt window. Please post a screenshot of the small window that opens.
Click to expand...
1744880533748.webp
 
Thank you for doing that. That's fine.

There are no dumps in the upload, despite you having BSODs. Were these dumps deleting by a disk cleanup tool (I can see the dump file created messages in the log, so they were written)? Please disable any disk cleanup tools you have until the problem has been resolved.

From the different bugchecks that you have it may be that a hardware cause is more likely. The 0xEF bugcheck is almost always caused by bad hardware.

Your RAM is already clocked at the native 2133MHz and you have tried each stick in its own, so we can probably consider your RAM to be good.

I am interested that you "got endless BSODs" when you enabled Driver Verifier, that's not at all normal and it might indicate a driver cause for these BSODs.

The data we have then seems to point in two directions (hardware and driver) but that 0xEF bugcheck makes me think it's wise to stick to testing hardware first. I suggest that you stress test the CPU with Prime95. This WILL make your CPU run hot, so I'd first give the PC a good clean, especially all the fan blades, and ensure that your cooler is working properly. Then download and run Prime95 as described below...
  1. Download Prime95 and a CPU temperature monitor (CoreTemp will do).
  2. Keep the temperature monitor running all the time you run Prime95. Your CPU will get hot!
  3. Run each of the three Prime95 tests (smallFFTs, largeFFTs, and Blend) one after the other for a minimum of 1 hour per test, 2 hours per test would be better.
  4. If Prime95 generates error messages, if the system crashes/freezes/BSODs, or if your CPU temp approaches 100°C (Tmax for your CPU), then stop Prime95 and let us know what happened.
Note that a properly cooled and stable CPU should be able to run all Prime95 tests pretty much indefinitely.

FYI: The small FFT test stresses the CPU more than RAM. The large FFT test stresses RAM more than the CPU. The Blend test is a mixture of the two.
 
ubuysa said:
There are no dumps in the upload, despite you having BSODs. Were these dumps deleting by a disk cleanup tool (I can see the dump file created messages in the log, so they were written)? Please disable any disk cleanup tools you have until the problem has been resolved.
Click to expand...
They're exist, idk why its not collected by the software honestly
here you go
 

Attachments

ubuysa said:
The data we have then seems to point in two directions (hardware and driver) but that 0xEF bugcheck makes me think it's wise to stick to testing hardware first. I suggest that you stress test the CPU with Prime95. This WILL make your CPU run hot, so I'd first give the PC a good clean, especially all the fan blades, and ensure that your cooler is working properly. Then download and run Prime95 as described below...
  1. Download Prime95 and a CPU temperature monitor (CoreTemp will do).
  2. Keep the temperature monitor running all the time you run Prime95. Your CPU will get hot!
  3. Run each of the three Prime95 tests (smallFFTs, largeFFTs, and Blend) one after the other for a minimum of 1 hour per test, 2 hours per test would be better.
  4. If Prime95 generates error messages, if the system crashes/freezes/BSODs, or if your CPU temp approaches 100°C (Tmax for your CPU), then stop Prime95 and let us know what happened.
Note that a properly cooled and stable CPU should be able to run all Prime95 tests pretty much indefinitely.

FYI: The small FFT test stresses the CPU more than RAM. The large FFT test stresses RAM more than the CPU. The Blend test is a mixture of the two.
Click to expand...
i'll do it and let you know, Thanks!
 
ubuysa said:
If Prime95 generates error messages, if the system crashes/freezes/BSODs, or if your CPU temp approaches 100°C (Tmax for your CPU), then stop Prime95 and let us know what happened.
Click to expand...
I Started Smallest FFTs test, immediatley crashed and got BSOD

1744899275064.webp
I attached minidump and prime.txt from Prime95 folder

Upd : I re-ran the test after restart, but PC is unusable (mouse doesn't move) so how im supposed to stop it after 1 hour ? anyways, i've force restart the system and ran Prime95 again and got BSOD immediatley again
 

Attachments

Last edited:
Of the three dumps, two fail because of an attempt to execute an illegal instruction in a Windows function...
Code: 
CONTEXT:  ffffac01de6d88d0 -- (.cxr 0xffffac01de6d88d0)
rax=0000000000000006 rbx=ffff83098028ad70 rcx=000000008028ad70
rdx=ffff83098028ad70 rsi=ffff83098028ad70 rdi=ffff83098028a0c0
rip=fffff8008dde15b0 rsp=fffffb8aa974f510 rbp=ffff83098028ad80
 r8=ffff83098028adc4  r9=ffff8309917e6dd8 r10=ffff83098028ad80
r11=ffff83098084fef8 r12=0000000000000000 r13=0000000000000000
r14=fffffb8aa974f580 r15=0000000000000000
iopl=0         nv up ei ng nz na pe nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00050282
nt!KiAbEntryRemoveEntryFromTreeAndRelease+0x78:
fffff800`8dde15b0 488d7e09        lea     rdi,[rsi+9]
Resetting default scope
That LEA instruction, within the Windows nt!KiAbEntryRemoveEntryFromTreeAndRelease function, should load the effective address of the RSI register address plus 9 into the RDI register. This has failed with a 0xC000001D exception - an attempt to execute an illegal instruction. This could be caused by a corrupted image in memory, that might be a RAM issue (unlikely in your case) or a flaky system drive (where the image was corrupted at load time) but I see you've tried a different system drive also.

What makes this interesting is that the third dump contains an image checksum mismatch for ntkrnlmp.exe - the Windows multiprocessor kernel, which contains the nt!KiAbEntryRemoveEntryFromTreeAndRelease function. A checksum mismatch indicates that the checksum of the image of ntkrnlmp.exe in your dump does not match the checksum of the same module in the Microsoft libraries. That indicates potential image corruption, either due to bad RAM or a flaky system drive - both unlikely in your case.

The dumps do however suggest that something may be causing memory corruptions, or the issue is with the CPU itself. I'd like you to try starting Windows in Safe Mode. I'd also like you to unplug everything from the PC except mouse, keyboard, and one monitor. In Safe Mode a stripped-down Windows system is loaded, with only critical services and drivers loaded. Typically no third-party drivers are loaded. This does mean that you won't be able to do any useful work in Safe Mode, or play games, and many of your devices may not work properly (or at all) because their drivers have not been loaded. Your display will be low resolution for example, because you'll be using only the Windows basic display driver.

Then try running Prime95 small FFTs again whilst in Safe Mode. This will eliminate any conflicts/interference from third-party drivers and external devices.
 
ubuysa said:
Of the three dumps, two fail because of an attempt to execute an illegal instruction in a Windows function...
Code: 
CONTEXT:  ffffac01de6d88d0 -- (.cxr 0xffffac01de6d88d0)
rax=0000000000000006 rbx=ffff83098028ad70 rcx=000000008028ad70
rdx=ffff83098028ad70 rsi=ffff83098028ad70 rdi=ffff83098028a0c0
rip=fffff8008dde15b0 rsp=fffffb8aa974f510 rbp=ffff83098028ad80
 r8=ffff83098028adc4  r9=ffff8309917e6dd8 r10=ffff83098028ad80
r11=ffff83098084fef8 r12=0000000000000000 r13=0000000000000000
r14=fffffb8aa974f580 r15=0000000000000000
iopl=0         nv up ei ng nz na pe nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00050282
nt!KiAbEntryRemoveEntryFromTreeAndRelease+0x78:
fffff800`8dde15b0 488d7e09        lea     rdi,[rsi+9]
Resetting default scope
That LEA instruction, within the Windows nt!KiAbEntryRemoveEntryFromTreeAndRelease function, should load the effective address of the RSI register address plus 9 into the RDI register. This has failed with a 0xC000001D exception - an attempt to execute an illegal instruction. This could be caused by a corrupted image in memory, that might be a RAM issue (unlikely in your case) or a flaky system drive (where the image was corrupted at load time) but I see you've tried a different system drive also.

What makes this interesting is that the third dump contains an image checksum mismatch for ntkrnlmp.exe - the Windows multiprocessor kernel, which contains the nt!KiAbEntryRemoveEntryFromTreeAndRelease function. A checksum mismatch indicates that the checksum of the image of ntkrnlmp.exe in your dump does not match the checksum of the same module in the Microsoft libraries. That indicates potential image corruption, either due to bad RAM or a flaky system drive - both unlikely in your case.

The dumps do however suggest that something may be causing memory corruptions, or the issue is with the CPU itself. I'd like you to try starting Windows in Safe Mode. I'd also like you to unplug everything from the PC except mouse, keyboard, and one monitor. In Safe Mode a stripped-down Windows system is loaded, with only critical services and drivers loaded. Typically no third-party drivers are loaded. This does mean that you won't be able to do any useful work in Safe Mode, or play games, and many of your devices may not work properly (or at all) because their drivers have not been loaded. Your display will be low resolution for example, because you'll be using only the Windows basic display driver.

Then try running Prime95 small FFTs again whilst in Safe Mode. This will eliminate any conflicts/interference from third-party drivers and external devices.
Click to expand...
Well, i started windows in Safe Mode (without networking) and I unplugged all devices except 1 monitor, keyboard and mouse
I opened Prime95 and chose small FFTs, got BSOD immediatley.
 

Attachments

defour said:
Well, i started windows in Safe Mode (without networking) and I unplugged all devices except 1 monitor, keyboard and mouse
I opened Prime95 and chose small FFTs, got BSOD immediatley.
Click to expand...
@ubuysa on Safe mode, Large FFTs, Blend Tests didn't crash at all ~1hr each
only smallest,small FFTs crashes immediatley.
 
@ubuysa i think i might found the root cause, i believe it is the CPU
a friend suggested undervolting, that didn't help, but then I went to BIOS and turned off Intel Boost Technology (and Boost 3.0)
now I booted without any issue, ran Prime95 Small FFTs for more than 1 hr no crash
also Temp max was 60C

So I believe it was CPU BOOST issue
 
Personally I think that disabling the boost feature is a workaround and not a solution. I'm always wary of suggesting that a CPU has failed, that's why I've asked you to run Prime95 in Safe Mode to be sure. All the tests you've done, including achieving stability with the boost feature disabled, suggest a failing CPU. It may be fine for some time now, but I would consider planning for a new CPU.

BTW, I realise you have an i7-13700KF, but I wonder whether that CPU suffers from the same voltage issues that has plagued the i9-14900K and i9-13900K CPUs? I would suggest contacting Intel and see whether your CPU may have been affected by the same issue. You might get an RMA replacement? I'd certainly be sure that you have the latest BIOS installed to get the mitigations for these voltage issues.
 
ubuysa said:
workaround and not a solution
Click to expand...
yes i totally get it, even when Stress test was running for 5+ hours now without an issue.

ubuysa said:
RMA replacement
Click to expand...
I'm not sure about this, I've ordered the CPU on 11-Apr-2023 and Intel offers only 2 years limited warranty on 13700KF
Also I've lost the original box, so I'm not sure if its needed from an RMA.
 
It's worth asking. I'd not be surprised to find the same flaw in other versions of 13 and 14 series CPUs. They can only say no.
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top