Question Random BSODs with different errors

Ishu Singh

Distinguished
Jan 29, 2015
9
0
18,510
0
Hi, my office PC was working fine like a month ago. I used to hibernate every day & leave. I noticed, sometimes it immediately resumes & many times was already on the next morning, maybe it stayed on for a few days. So I started turning off the power supply after hibernating.
But after a few days I started getting these random BSODs with different error codes like Stop memory management, driver IRQL not less equal. I realized crashes occur when I put more load, like opening multiple browser tabs or software, and browser tabs crash many times. I felt it may be RAM issue but memtest was fine & 32GB ram is enough for multitasking. Intel processor test was also fine. Even windows reinstall didn't work. So I think it's a hardware issue, maybe PSU as it's a Segotep 400w with Cabinet.

I'm giving the whocrashed report below. Can someone please check & help :(

System Information (local)
--------------------------------------------------------------------------------

Computer name: DESKTOP-NT2AE4M
Windows version: Windows 10, 10.0, version 2009, build: 19043 (x64)
Windows dir: C:\WINDOWS
Hardware: B460MPOWER, Gigabyte Technology Co., Ltd., B460M POWER
CPU: GenuineIntel Intel(R) Core(TM) i5-10400F CPU @ 2.90GHz 8664, level: 6
Processor count: 12 logical processors, active mask: 4095
RAM: 32696.1MB
GPU: Nvidia GeForce GTX 1050ti 4GB
PSU: Segotep 400W

--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dumps are enabled on your computer.

Crash dump directories:
C:\WINDOWS
C:\WINDOWS\Minidump

On Sun 02-10-2022 16:46:49 your computer crashed or a problem was reported

Crash dump file: C:\WINDOWS\Minidump\100222-11625-01.dmp (Minidump)
Bugcheck code: 0x1A(0x41792, 0xFFFFEB3FFE3360D0, 0x10000, 0x0)
Bugcheck name: MEMORY_MANAGEMENT
Bug check description: This indicates that a severe memory management error occurred.
Analysis: A corrupted PTE has been detected. This is possibly a software problem. This is a typical case of memory corruption.
This bugcheck is often associated with overheating problems. Read this article on memory corruption. Read this article on thermal issues


On Sun 02-10-2022 16:46:49 your computer crashed or a problem was reported

Crash dump file: C:\WINDOWS\MEMORY.DMP (Kernel memory dump)
Bugcheck code: 0x1A(0x41792, 0xFFFFEB3FFE3360D0, 0x10000, 0x0)
Bugcheck name: MEMORY_MANAGEMENT
Driver or module in which error occurred: ntkrnlmp.exe (nt!RtlAvlRemoveNode+0x643A)
This is the core Windows kernel module. No offending driver has been revealed.
Description: NT Kernel & System
Product: Microsoft® Windows® Operating System
Company: Microsoft Corporation
Bug check description: This indicates that a severe memory management error occurred.
Analysis: A corrupted PTE has been detected. This is possibly a software problem. This is a typical case of memory corruption.
This bugcheck is often associated with overheating problems. Read this article on memory corruption. Read this article on thermal issues



On Sun 02-10-2022 15:25:59 your computer crashed or a problem was reported

Crash dump file: C:\WINDOWS\Minidump\100222-13671-01.dmp (Minidump)
Bugcheck code: 0x1A(0x41792, 0xFFFFFD0107A6C100, 0x20000, 0x0)
Bugcheck name: MEMORY_MANAGEMENT
Bug check description: This indicates that a severe memory management error occurred.
Analysis: A corrupted PTE has been detected. This is possibly a software problem. This is a typical case of memory corruption.
This bugcheck is often associated with overheating problems. Read this article on memory corruption. Read this article on thermal issues



On Sun 02-10-2022 13:37:52 your computer crashed or a problem was reported

Crash dump file: C:\WINDOWS\Minidump\100222-13265-01.dmp (Minidump)
Bugcheck code: 0xD1(0xFFFFBF80532C015C, 0x2, 0x0, 0xFFFFF8050ADE31E6)
Bugcheck name: DRIVER_IRQL_NOT_LESS_OR_EQUAL
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
Analysis: This is a typical software problem. Most likely this is caused by a bug in a driver.



On Thu 29-09-2022 12:16:46 your computer crashed or a problem was reported

Crash dump file: C:\WINDOWS\Minidump\092922-9906-01.dmp (Minidump)
Bugcheck code: 0x1000007E(0xFFFFFFFFC0000005, 0xFFFFF80406B07BEC, 0xFFFFC201FE1FF0B8, 0xFFFFC201FE1FE8F0)
Bugcheck name: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
Analysis: This is likely a software problem which means that it was probably caused by a bug in a driver.
There is a possibility that this is caused by memory corruption. Memory corruption can be caused by a faulty driver, faulty RAM, overheating and more. Read this article on memory corruption. Read this article on thermal issues



On Thu 29-09-2022 09:45:19 your computer crashed or a problem was reported

Crash dump file: C:\WINDOWS\Minidump\092922-10953-01.dmp (Minidump)
Bugcheck code: 0x7A(0x1, 0xFFFFFFFFC0000005, 0xFFFF908FBA9FB080, 0xFFFFA580D90C0000)
Bugcheck name: KERNEL_DATA_INPAGE_ERROR
Bug check description: This bug check indicates that the requested page of kernel data from the paging file could not be read into memory.
Analysis: STATUS_ACCESS_VIOLATION was repoted. The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s. This bugcheck indicates that the error is file system or disk related. If no offending driver is found, it is suggested that you run CHKDSK to check your drive(s) for errors. This is possibly a software problem. This is likely a case of memory corruption.
Memory corruption can be caused by a faulty driver, faulty RAM, overheating and more. Read this article on memory corruption. Read this article on thermal issues



On Wed 21-09-2022 13:36:45 your computer crashed or a problem was reported

Crash dump file: C:\WINDOWS\LiveKernelReports\ResourceTimeout-20220921-1336.dmp (Kernel memory dump)
Bugcheck code: 0x1CC(0xFFFFE68CA5909250, 0xFFFFE68C92A2A080, 0x1, 0x96)
Bugcheck name: EXRESOURCE_TIMEOUT_LIVEDUMP
Driver or module in which error occurred: Ntfs.sys (Ntfs+0x133c55)
File path: C:\WINDOWS\System32\Drivers\Ntfs.sys
Description: NT File System Driver
Product: Microsoft® Windows® Operating System
Company: Microsoft Corporation
Bug check description: A kernel ERESOURCE has timed out. This can indicate a deadlock condition or heavy contention which can cause performance issues.
Analysis: This is likely caused by a hardware problem, but there is a possibility that this is caused by a misbehaving driver.
This bugcheck indicates that a timeout has occurred. This may be caused by a hardware failure such as a thermal issue or a bug in a driver for a hardware device.
Read this article on thermal issues
A full memory dump will likely provide more useful information on the cause of this particular bugcheck. The crash took place in a file system driver. Since there is no other responsible driver detected, this could be pointing to a malfunctioning drive or corrupted disk. It's suggested that you run CHKDSK to check your drive(s) for errors.



--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

7 crash dumps have been found and analyzed. No offending third party drivers have been found. Consider using WhoCrashed Professional which offers more detailed analysis using symbol resolution. Also configuring your system to produce a full memory dump may help you.

Read the suggestions displayed in the bugcheck analysis above.

The analysis process took 0:00:11 (h🇲🇲ss).
 

Colif

Win 11 Master
Moderator
Jun 12, 2015
60,225
5,038
166,290
10,413
  1. Open Windows File Explore
  2. Navigate to C:\Windows\Minidump
  3. Copy the mini-dump files out onto your Desktop
  4. Do not use Winzip, use the built in facility in Windows
  5. Select those files on your Desktop, right click them and choose 'Send to' - Compressed (zipped) folder
  6. Upload the zip file to the Cloud (OneDrive, DropBox . . . etc.)
  7. Then post a link here to the zip file, so we can take a look for you . . .
What are full specs of PC?
What make/model of SSD/hdd

I felt it may be RAM issue but memtest was fine & 32GB ram is enough for multitasking. Intel processor test was also fine.
i won't go looking for intel test
Could be ssd as that is where page file is.
I can't say I ever seen the last BSOD before, so looking at memory makes sense.. get weird errors with corruption
maybe PSU as it's a Segotep 400w with Cabinet.
could be

Do you have latest BIOS? https://www.gigabyte.com/Motherboard/B460M-POWER-rev-10/support#support-dl-bios

you might want to run this:
https://www.guru3d.com/files-details/prime95-download.html
Prime 95 Instructions - https://appuals.com/how-to-run-a-cpu-stress-test-using-prime95/
it checks CPU, ram & psu.
 
Last edited:

Ishu Singh

Distinguished
Jan 29, 2015
9
0
18,510
0
Hi @Colif - Thank you for your reply & suggestions :)

Here is the Minidump Zip file
https://www.dropbox.com/s/4kg9trh7ix5noqp/Dump.zip?dl=0

Full PC Specs -
CPU: Intel Core i5-10400F CPU @ 2.90GHz 8664
RAM: 32 GB (2 x 16GB sticks, Crucial)
Motherboard: Gigabyte B460M POWER (U3E1)
GPU: Nvidia GeForce GTX 1050ti 4GB
SSD: Colorful SL500 256GB (SATA)
HDD: WD WDC WD10EZEX-22MFCA0 1TB
PSU: Segotep 400W


I tried PRIME95 & pc crashes when I choose big FFT which stresses RAM
[Tue Oct 4 12:22:02 2022]
FATAL ERROR: Rounding was 0.4990270962, expected less than 0.4
Hardware failure detected running 384K FFT size, consult stress.txt file.
FATAL ERROR: Rounding was 0.5, expected less than 0.4
Hardware failure detected running 384K FFT size, consult stress.txt file.
FATAL ERROR: Rounding was 0.4997954446, expected less than 0.4
Hardware failure detected running 384K FFT size, consult stress.txt file.
FATAL ERROR: Rounding was 0.5, expected less than 0.4
Hardware failure detected running 384K FFT size, consult stress.txt file.

Then I tried MemTest64 & it also showed some errors (screenshot)
So is there a way to fix this or do I need to change RAM?

 

Colif

Win 11 Master
Moderator
Jun 12, 2015
60,225
5,038
166,290
10,413
Okay, you can't fix ram. All you can do is replace it.
If its new and you have proof of purchase you should get replacements from maker.
Your ram - CB16GU2666.C8ET - Crucial Basics
Seems you get 10 years - https://www.crucial.com/company/warranty

It probably reason for rounding errors in prime.

Prime rounding errors can cause BSOD. I assume bad ram can cause rounding errors too.
Only once PC passes Prime will you not get BSOD, from hardware anyway.

No point looking at dumps when ram is bad.
 
Last edited:

ASK THE COMMUNITY

TRENDING THREADS