Windows 10: Need help in figuring out information on Why I got BSOD issue all of a sudden?

Hello Team,Today on Nov 25 2023, I encountered a BSOD Issue and collected minidump.The crash occurred at time : 12:37 PM IST @Nov 25, 2023Win ver: Windows 11 23H2PC Specs:core i7 11700K not overclockedRTX 3080 Vision OC Gigabyte undervolted Graphics Version: 545.92 DCHZ590-F Strix Gaming MotherboardRAM: Gskill 16x2 32GB 3200MhzAttaching the minidump file.112523-7187-01.dmp # Child-SP RetAddr Call Site 00 fffff806`2fa7f178 fffff806`2aa2bfa9 nt!KeBugCheckEx 01 fffff806`2fa7f180 fffff806`2aa27634 nt!KiBugCheckDispatch+0x69 02 fffff806`2fa7f2c0 fffff806`54188b82

:)

 

Help figuring out BSOD error nlem64nt.sys

Original thread here. Redirecting

Unfortunately, it is locked. nlem64nt.sys is used by NetLib encryptonizer. We had a similar issue with this causing a PFN File List Corrupt BSOD and their support confirmed we needed to upgrade. Hopefully this will help someone out in the future.

 

Various BSOD Errors Help

Hey all,

I've received multiple BSOD errors the past 2 days after rebuilding my PC. I've been trying to figure out the issue.

These are the few BSOD messages I remember seeing:

• DPC_WATCHDOG_VIOLATION (multiple times)
• CRITICAL_PROCESS_DIED (one time)
• IRQL_NOT_LESS_OR_EQUAL (one time)
• WHEA_UNCORRECTABLE_ERROR (multiple times)

Here's a link to the dmp files and system information: OneDrive

Steps I've taken:

• fully updated drivers
• applied all Windows updates
• Removed unnecessary hardware
• Monitored CPU/GPU temps (log file on temps during last crash in share)

Any help would be appreciated.

 

Getting BSOD 0x124 error

Ignore what everone said here.

0x124 BSOD is usually related to VCCIO (VTT), run Prime95 version 26.6 with custom sizes of 512K to 640K with 50% of your memory for at least 8 hours.

If you get a 0x124 BSOD, increase VCCIO voltage by small steps, run Prime95 again until your stable.

If you pass Prime95 512K to 640K without a BSOD, then its Vcore too low. I'd suggest running IntelBurnTest with 80% of your memory to verify stability (8 to 12 hours).

Oh, and yeah, if this problem appeared all of the sudden, the reason is CPU degradation, you can prevent it by enabling C-States or adjust your overclock to use lower voltages.