cancel
Showing results for 
Search instead for 
Did you mean: 

Processors

Jordi_Jodurson
Journeyman III

Another reboots on system with Ryzen 5 3600

Hi!

After 2.5 years start getting random Win 10 reboots.

My specs:

 

Spoiler

CPU: Ryzen 5 3600

RAM: Ballistix Sport LT Grau (BLS8G4D32AESBK)

GPU: GIGABYTE GeForce RTX 3070 Ti GAMING OC (GV-N307TGAMING OC-8GD)

MB: MSI Tomahawk Max B450

PSU: bequiet! Pure Power 11 (L11-CM-700W)

Fans: 4 x 120 mm

CPU fan: DEEPCOOL GAMMAXX GTE (DP-MCH4-GMX-GTE)

Display: HUAWEI MateView 34" GT ZQE-CAA 

 

Reboots occur (so far, as I noticed) only when working outside of games: in the browser when working and switching to new tabs, when switching from the browser to explorer.

Stress tests in the OCCT, AIDA64 - showed stability, nothing falls. In games - does not fall, everything is stable. Win 10 mem test - clear, system check - clear. Dunno...

At first I thought that I'm out of power, but OCCT Power Test without any errors, 5 PSU calculators show me that power supply is +/- fine for this specs.

Temps are always fine, I've do monitoring always.

Reboots starts after some time I get new monitor HUAWEI MateView 34" GT ZQE-CAA instead old FHD 22", week or two. But I don't see any dependency here, because specs allow the use of such a display...

Windows logs show almost always error "WHEA-Logger 18" with this:

 

Spoiler

- Machine Check Exception
- Cache Hierarchy Error
- ID APIC: 0

ErrorSource 3
ApicId 0
MCABank 5
MciStat 0xbea0000000000108
MciAddr 0x101f8074a559c69
MciMisc 0xd01a0ffe00000000
ErrorType 9
TransactionType 2
Participation 256
RequestType 0
MemorIO 256
MemHierarchyLvl 0
Timeout 256
OperationType 256
Channel 256
Length 936
RawData 435045521002FFFFFFFF03000100000002000000A803000027260A00070A16140000000000000000000000000000000000000000000000000000000000000000BDC407CF89B7184EB3C41F732CB57131FE6FF5E89C91C54CBA8865ABE14913BBEE99FBF538DAD80102000000000000000000000000000000000000000000000058010000C00000000003000001000000ADCC7698B447DB4BB65E16F193C4F3DB0000000000000000000000000000000001000000000000000000000000000000000000000000000018020000800000000003000000000000B0A03EDC44A19747B95B53FA242B6E1D0000000000000000000000000000000001000000000000000000000000000000000000000000000098020000100100000003000000000000011D1E8AF94257459C33565E5CC3F7E8000000000000000000000000000000000100000000000000000000000000000000000000000000007F010000000000000002010000000000100F87000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000007000000000000000000000000000000100F870000080C000B32F87EFFFB8B170000000000000000000000000000000000000000000000000000000000000000F50157A5EFE3DE43AC72249B573FAD2C03000000000000009F00020600000000699C554A07F801010000000000000000000000000000000000000000000000000200000002000000C990B6F638DAD801000000000000000000000000000000000000000005000000080100000000A0BE699C554A07F8010100000000FE0F1AD0000000000000000000000000B00005000000004D0000000079000000230000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000001B00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000

For 2.5 years I've use manual RAM OC to 3600 - without problems. For now I've drop RAM OC to stock XMP with 3200, with BIOS reset.

And before I've do a BIOS / Chipset / All potential drivers update. Nothing help.

I've also collect 5 memory.dmp files:

https://disk.yandex.ru/d/c6vk4XP4bs3RdA

My lay knowledge and reading logs points to the nvlddmkm.sys file, which is confusing: why does the system crash only during idle and basic work, but not in heavy games?

What can be done in this situation? Where to look? What to test or is it time to replace? I hope for your help.

0 Likes
0 Replies