Help! BSOD - I Think RAM related?

[Hamdotca]

Hi all,

 

Been running my system for almost exactly a year now, experienced almost no Blue screens since building it. Within the last week, I have suddenly been getting LOTS of blue screens.

I have been getting many different types of errors including "Memory Management", "IRQL_NOT_LESS_OR_EQUAL", "System service exception", "System Thread exception not handled", "pfn list corrupt" and a couple more.

 

My first thought after looking into these is that it is some type of RAM error, Currently in my system are 2x16GB DDR5 5200 Corsair Vengance, Currently with xmp off as a troubleshooting step. I have also reinstalled windows twice to no success. I have also tried SFC/scannow in cmd which did find some corrupted/damaged files and repaired them. I have also found that running only 1 DIMM at a time has seemed to stop the crashes, Attached I have an image of some line (crack?) next to B2 (slot 4) wondering if that might have something to do with it or it may just be me being paranoid about a cracked mobo (line underneath the what I think is a cap?)

 

I am currently running the system for a few days with each stick individually to try and rule out a bad DIMM but again, been almost a year with no issues

 

Link to Sysnative Files (BSOD reports)

https://drive.google.com/file/d/12SeO4GQrDgkPvQ_-4jwQl9wGQvKzmwZQ/view?usp=sharing

 

 

[ChaoticChaosx]

Have you ran memtest86 on one stick and a time?

 

"memory management" It ensures that blocks of memory space are properly managed and allocated so the OS, applications and other running processes have the memory they need to carry out their operations.

 

"IRQL_NOT_LESS_OR_EQUAL" probably memory as other causes are antivirus and device driver which is doubtful as well.

 

"System service exception" since you ran SFC then this should not happen again unless installation of OS (windows) is corrupt also checking by CHKDSK command or in file explorer error check for a quick one.

 

"System Thread exception not handled" calls for memory check as mostly a driver or hardware faulty BSOD.

 

"pfn list corrupt" more or less same and service exception and thread exception.

 

I'm gonna say memory I suggest running memtest86 one stick at a time. I've had a DOA ram stick out of a kit once before.

 

They are in slot 2 and 4 right?

 

I'm just basing off what the BSOD mean. If you can try other ram from a friend or something. Do so. If issue still persists and not on friends (whom ever) system. Report.

[Hamdotca]

21 minutes ago, ChaoticChaosx said:

Have you ran memtest86 on one stick and a time?

 

"memory management" It ensures that blocks of memory space are properly managed and allocated so the OS, applications and other running processes have the memory they need to carry out their operations.

 

"IRQL_NOT_LESS_OR_EQUAL" probably memory as other causes are antivirus and device driver which is doubtful as well.

 

"System service exception" since you ran SFC then this should not happen again unless installation of OS (windows) is corrupt also checking by CHKDSK command or in file explorer error check for a quick one.

 

"System Thread exception not handled" calls for memory check as mostly a driver or hardware faulty BSOD.

 

"pfn list corrupt" more or less same and service exception and thread exception.

 

I'm gonna say memory I suggest running memtest86 one stick at a time. I've had a DOA ram stick out of a kit once before.

 

They are in slot 2 and 4 right?

 

I'm just basing off what the BSOD mean. If you can try other ram from a friend or something. Do so. If issue still persists and not on friends (whom ever) system. Report.

Yes slots 2 and 4

 

I haven't run memtest but that's a good idea, especially on each one individually, But again I have been using this system and these RAM sticks for about a year with no issues, not that I suppose It couldn't happen but it just seems weird to me that they would randomly just die

[Hamdotca]

After Running Memtest86 Ive narrowed it down, I have a bad RAM module, Going to RMA 

 

Thanks for the help!

[ChaoticChaosx]

1 hour ago, Hamdotca said:

After Running Memtest86 Ive narrowed it down, I have a bad RAM module, Going to RMA 

 

Thanks for the help!

Glad we found the issue.

 

Not a problem. For all PC enthusiasts! Hah.