[SOLVED] BSOD "System Service Exception" ?

[thebishop8]

I got myself a new computer last month, but in the last week or two I've been getting BSOD, usually with the "System Service Exception" error, but at least once it was
"IRQL Not Less Or Equal" ?

My specs are:

Windows 10 Home
Ryzen 7 5800x
RTX 3080
MSI MPG X570 Gaming Plus Motherboard
Patriot Viper Steel DDR4-3600 CL18
EVGA Supernova GA 850W Gold
Samsung 970 Evo Plus
TP-Link Archer T5E PCIe WiFi card.

Here's a link to the mini-dumps: https://1drv.ms/u/s!AnRvwG0Gz2Ejiww_3a5RgieY7qmc?e=NkAaLf

 

[Lutfij]

Welcome to the forums, newcomer!

Could you state what your BIOS version is for your motherboard? OS version(not edition) for Windows 10? Did you install the NVMe driver for your Samsung SSD after you installed all relevant drivers for your platform in an elevated command, i.e, Right click installer>Run as Administrator?

 

[thebishop8]

Thanks for the welcome.

The BIOS version is E7c37ams.ae0. The OS version is 21H1. I didn't install the NVMe drivers, and I didn't install any drivers as an Administrator.

 

[Drew125]

Spoiler

Latest Dump: 110721-6796-01.dmp
SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff80153e69661, Address of the instruction which caused the bugcheck
Arg3: ffff998d73dbee10, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

PROCESS_NAME: GameOverlayUI.exe

2nd dump: 110721-6625-01.dmp
PROCESS_NAME: svchost.exe

3rd: 110621-8156-01.dmp
PROCESS_NAME: svchost.exe
IMAGE_NAME: memory_corruption

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 0000000000000048, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff8044d206aa9, address which referenced memory

I have checked the dump files. It appears you may have 2 issues. Os corruption and bad RAM.
I would do the following

1. Run a Windows memory diagnostic / Memtest (Preferred, Linux boot stick)
2. Run the following in a powershell "Check System command: dism /online /cleanup-image /restorehealth;sfc /scannow"

Post the results of the these.

 

[thebishop8]

Windows Memory Diagnostics Results:

Spoiler

Log Name: System
Source: Microsoft-Windows-MemoryDiagnostics-Results
Date: 11/8/2021 10:47:18 AM
Event ID: 1102
Task Category: None
Level: Error
Keywords:
User: SYSTEM
Computer: DESKTOP-UIJ7545
Description:
The Windows Memory Diagnostic tested the computer's memory and detected hardware errors. To identify and repair these problems, contact the computer manufacturer
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-MemoryDiagnostics-Results" Guid="{5f92bc59-248f-4111-86a9-e393e12c6139}" />
<EventID>1102</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x8000000000000000</Keywords>
<TimeCreated SystemTime="2021-11-08T18:47:18.0308741Z" />
<EventRecordID>7148</EventRecordID>
<Correlation />
<Execution ProcessID="8844" ThreadID="8848" />
<Channel>System</Channel>
<Computer>DESKTOP-UIJ7545</Computer>
<Security UserID="S-1-5-18" />
</System>
<UserData>
<Results xmlns="http://manifests.microsoft.com/win/2005/08/windows/Reliability/Postboot/Events">
<LaunchType>Manual</LaunchType>
<CompletionType>Fail</CompletionType>
<MemorySize>65457</MemorySize>
<TestType>10</TestType>
<TestDuration>4803</TestDuration>
<TestCount>12</TestCount>
<NumPagesTested>16730651</NumPagesTested>
<NumPagesUnTested>1763</NumPagesUnTested>
<NumBadPages>26</NumBadPages>
<T1NumBadPages>0</T1NumBadPages>
<T2NumBadPages>0</T2NumBadPages>
<T3NumBadPages>9</T3NumBadPages>
<T4NumBadPages>0</T4NumBadPages>
<T5NumBadPages>0</T5NumBadPages>
<T6NumBadPages>0</T6NumBadPages>
<T7NumBadPages>0</T7NumBadPages>
<T8NumBadPages>0</T8NumBadPages>
<T9NumBadPages>17</T9NumBadPages>
<T10NumBadPages>0</T10NumBadPages>
<T11NumBadPages>0</T11NumBadPages>
<T12NumBadPages>0</T12NumBadPages>
<T13NumBadPages>0</T13NumBadPages>
<T14NumBadPages>0</T14NumBadPages>
<T15NumBadPages>0</T15NumBadPages>
<T16NumBadPages>0</T16NumBadPages>
</Results>
</UserData>
</Event>

Looks like it detected hardware problems and it's advising me to contact the manufacturer.

The powershell command did detect corrupt files, and it said it replaced them. Should I assume that problem is fixed?

 

[Drew125]

Looks like it detected hardware problems and it's advising me to contact the manufacturer.

The PowerShell command did detect corrupt files, and it said it replaced them. Should I assume that problem is fixed?

I would say since the memory diagnostic found issues your RAM is most likely going to be bad. Run MemTest to confirm. Follow the link below for instructions. Im guessing it will find some faults in your ram.

How To - How to Test your RAM

How to Test Your RAM Before testing your RAM, you need to know what type of firmware is on your PC. Either Legacy BIOS which is usually on pre-2012 PCs or UEFI which is usually on newer PCs. You can find this information in your motherboard manual. Or, run msinfo32.exe and look for BIOS...

forums.tomshardware.com

 

[thebishop8]

I would say since the memory diagnostic found issues your RAM is most likely going to be bad. Run MemTest to confirm. Follow the link below for instructions. Im guessing it will find some faults in your ram.

How To - How to Test your RAM

How to Test Your RAM Before testing your RAM, you need to know what type of firmware is on your PC. Either Legacy BIOS which is usually on pre-2012 PCs or UEFI which is usually on newer PCs. You can find this information in your motherboard manual. Or, run msinfo32.exe and look for BIOS...

forums.tomshardware.com

I've run 6 tests now. I could do more if needed, and I'm inclined to, but here are the results so far.

Both sticks, 3600 speed, 741 errors
Both sticks, 2666 speed, 0 errors
Stick one, 3600 speed, 3246 errors
Stick one, 2666 speed, 0 errors
Stick two, 3600 speed, 66 errors
Stick two, 2666 speed, 0 errors

Basically, every test at 3600 speed has failed, and every test at 2666 speed has passed. 3600 MHz is what the RAM is supposed to be rated for, 2666 MHz is what its default is.

 

[Drew125]

I've run 6 tests now. I could do more if needed, and I'm inclined to, but here are the results so far.

Both sticks, 3600 speed, 741 errors
Both sticks, 2666 speed, 0 errors
Stick one, 3600 speed, 3246 errors
Stick one, 2666 speed, 0 errors
Stick two, 3600 speed, 66 errors
Stick two, 2666 speed, 0 errors

Basically, every test at 3600 speed has failed, and every test at 2666 speed has passed. 3600 MHz is what the RAM is supposed to be rated for, 2666 MHz is what its default is.

Its not your speeds that worry me. Its those error counts. You need new RAM. Memtest should return 0 errors. Memory errors will cause BSODS all over the place from A to Z. If its rated for 3600 and failing at that speed id return them.

 

[thebishop8]

Small update. I RMA'd the RAM and got a new pair back. Except this new pair seems somehow worse than what I had before. Once it was set to 3600 MHz, it wouldn't even boot normally at first. I tested it with PassMark. The old RAM would fail 2/13 tests and got 3200 errors over 4 passes. This new RAM failed 8/13 tests and 10,000 errors were found in the middle of the second pass. Apparently once you get that many errors, PassMark is designed to stop testing because 10,000 errors is just too many. So, I guess I have no choice but RMA this set of RAM too.

 

[Drew125]

Small update. I RMA'd the RAM and got a new pair back. Except this new pair seems somehow worse than what I had before. Once it was set to 3600 MHz, it wouldn't even boot normally at first. I tested it with PassMark. The old RAM would fail 2/13 tests and got 3200 errors over 4 passes. This new RAM failed 8/13 tests and 10,000 errors were found in the middle of the second pass. Apparently once you get that many errors, PassMark is designed to stop testing because 10,000 errors is just too many. So, I guess I have no choice but RMA this set of RAM too.

The reviews on that ram is questionable. Ive had a similar experience. I bought Corsair ram 16 GB ddr4 3600. Ran great for a year then i found out it was running at 2667, not the advertised rates. On top of that the ram began failing after a year. I bought new and RMA'ed the old sticks. They are still in the box. The review for them said failed very quickly.