Question Blue screens / strange behavior / freezes

Jan 1, 2020
7
0
10
0
Hi. First, my components:

  • AMD Ryzen 7 2700x with stock cooler (Wraith Prism)
  • Gigabyte Aorus Elite x570 (F10 bios - compatible with AMD 2000 series)
  • Gigabyte RTX 2060 SUPER WINDFORCE OC
  • Kingston HyperX Fury RGB 16GB (2x8GB), DDR4, 3200MHz, CL16, 1.35V
  • Seasonic Focus GX, 80+ Gold, 650W
  • SSD Samsung 970 EVO Plus 250GB BOOT (first M2 slot)
  • SSD Samsung 970 EVO Plus 500GB (second M2 slot)
  • HDD Seagate BarraCuda 2TB
  • (all in a well ventilated case)
  • (all parts under warranty)
Now I'm going to tell you a short story.

I built this computer with the components mentioned above. Everything was fine, the computer started, post, I installed windows 10, I ran a few benchmarks, I checked the temperatures, everything seemed fine.

After 2 weeks, it won't start (sometimes it started at first, other times I had to turn off / on the power switch to start, "strange behavior"), I didn't take it seriously.

After 3 weeks the serious problems started, while I was in a game, I received BSOD with the following code: DPC_WATCHDOG_VIOLATION (first BSOD). After going through "Your PC ran into a problem and needs to restart. We're just ..." it got stuck in the screen with the AORUS logo (I could enter the bios, but the computer doesm't boot in windows). As I had no other solution and I needed a desktop, I reinstalled windows, all the drivers (everything went well, I was confident that I solved the problems (I know, stupid)).

After reinstalling windows, another BSOD came while I was on Google (IRQL_NOT_LESS_OR_EQUAL). It pass from "Your PC ran into a problem ...", the computer restarted, but with major problems:

  • Freezes - are constant, to help you better understand how it behaves, I will give an example, in League of Legends, with 144 FPS capped, goes down to 130 and goes up, very quickly, with a "BZZZ" in the background and a short delay (sound "BZZZ" always appears whenever a drop occurs). It happens to me in any application, on Youtube, on Spotify. Sometimes, it seems that something stabilizes and does not appear, but most of the time it is always present. Sometimes, during these drops, I also receive a BSOD. The most common errors in a week were "MEMORY_MANAGEMENT".
  • The computer doesn't turn off when I press "shut down" (the monitor turns off, the RGB LEDs on the motherboard turn off, but the fans and the processor fan don't, full RPM).
  • If I activate the XMP function in the bios, to change the RAM to 3200MHz, after saving the bios settings, the computer doesn't post anymore (black monitor, full fan speed).
  • To turn it on, I have to turn off the power switch, and hold the power button for a few seconds.
  • The second M2 slot doesn't work (it didn't work when I tried to format it in the windows installation process, not even after).
What have I tried so far?

  • I looked for this error (MEMORY_MANAGEMENT) and found that it may be caused by a faulty RAM. A friend gave me 16 GB RAM (2x8) Corsair Vengeance LPX, 3200MHz, CL16. I replaced my RAM with my friend's RAM and solved the situation partially. I got rid of the BSODs (no BSOD in two weeks), but not the freezes (which behave the same), the "shut down" or the "method of start".
  • I did stress tests (FurMark, OCCT), I never received BSOD during these tests (whether I was using my or my friend's RAM).
  • I reassembled the entire system.
  • Windows, updated to the last available version at this time.
  • Temps are fine.
What haven't I tried?

  • Many have recommended me to update the bios (I have F10 version now), but because of this strange behavior I'm a little scared, I don't want something to go wrong.
  • I reinstalled windows once, I was thinking of reinstalling it again, but with the RAM from Corsair, maybe is a bad driver or something.
Thank you if you have read so far, I know I have written a lot, but I have tried to describe it in as much detail as possible, maybe someone can identify the problem exactly or give me some advice.
Below I left a WhoCrashed log and all the BSODs errors I encountered after reinstalling windows.
If you need results from other test / software, just tell me and I will post here.
I'm not an expert, if I don't find a solution here I'll probably try to RMA the motherboard, I think maybe this is the problem.
 
Last edited:
Jan 1, 2020
7
0
10
0
Crash Dump Analysis

Crash dumps are enabled on your computer.

Crash dump directories:
C:\Windows
C:\Windows\Minidump

On Mon 27-Apr-20 00:13:43 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\042720-78000-01.dmp
This was probably caused by the following module: acpi.sys (ACPI+0x81802)
Bugcheck code: 0x1000009F (0x4, 0x12C, 0xFFFFDF0260E6B040, 0xFFFFDD08F926F8E0)
Error: CUSTOM_ERROR
file path: C:\Windows\system32\drivers\acpi.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: ACPI Driver for NT

The crash took place in a Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Mon 27-Apr-20 00:13:43 your computer crashed or a problem was reported
crash dump file: C:\Windows\MEMORY.DMP
This was probably caused by the following module: ntkrnlmp.exe (nt!IoTranslateBusAddress+0x956)
Bugcheck code: 0x9F (0x4, 0x12C, 0xFFFFDF0260E6B040, 0xFFFFDD08F926F8E0)
Error: DRIVER_POWER_STATE_FAILURE
Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state. The power state transition timed out waiting to synchronize with the PnP subsystem.
This is likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Wed 22-Apr-20 21:28:35 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\042220-71046-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C90D6)
Bugcheck code: 0x1000009F (0x4, 0x12C, 0xFFFFB3819ED20040, 0xFFFFF585EF67D8E0)
Error: CUSTOM_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System

The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Wed 22-Apr-20 11:30:53 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\042220-77953-01.dmp
This was probably caused by the following module: storport.sys (storport+0x59B58)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF8056DBCA277, 0xFFFFAE80389D3E58, 0xFFFFAE80389D36A0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\storport.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Microsoft Storage Port Driver
Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a storage driver or controller 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.



On Mon 20-Apr-20 22:28:12 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\042120-77859-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C2390)
Bugcheck code: 0xA (0x10, 0x2, 0x0, 0xFFFFF80114EB2EDF)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above. This is a software bug.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Fri 17-Apr-20 20:54:41 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\041720-77921-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C2390)
Bugcheck code: 0x1A (0x41201, 0xFFFF80810567CB88, 0x81000003F389C025, 0xFFFFA003218F5A10)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. This may be because of a hardware issue such as faulty RAM, overheating (thermal issue) or because of a buggy driver. This problem might also be caused because of overheating (thermal issue).
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.





Conclusion



6 crash dumps have been found and analyzed. No offending third party drivers have been found. Connsider 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 topic general suggestions for troubleshooting system crashes for more information.

Note that it's not always possible to state with certainty whether a reported driver is responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.
 
May 12, 2020
9
1
15
0
Can you do some test with just 1 ram in you pc? and then exchange it and do the tests again. If you can reproduce the error send it in for warranty if possible.
 
Jan 1, 2020
7
0
10
0
Can you do some test with just 1 ram in you pc? and then exchange it and do the tests again. If you can reproduce the error send it in for warranty if possible.
Same thing with 1 module of RAM in any slot.
I will send in warranty, but I would like to know exactly what is broken, especially since I need a computer during this period.

I have already tried all the tools from microsoft (scan, RAM test)
 
May 12, 2020
9
1
15
0
I hope you didn't sent them yet, can you turn down the speed of you memory to 2933? Seems that the max supported memory speed for AMD Ryzen 7 2700x is 2933. It should work though with faster memory. But just to give it a try.
 
Jan 1, 2020
7
0
10
0
I hope you didn't sent them yet, can you turn down the speed of you memory to 2933? Seems that the max supported memory speed for AMD Ryzen 7 2700x is 2933. It should work though with faster memory. But just to give it a try.
There are only two settings for XMP memory: default (2133Mhz) and 3200Mhz . With 3200Mhz doesn't post and with default i have the above problems.
 

ASK THE COMMUNITY

TRENDING THREADS