Just uninstalling any software is unlikely to yield anything useful. The drivers would need to be uninstalled from the device manager anyway.
At this point, more narrowing would be necessary to point at drivers specifically. Safe mode loads a very limited set of them, so that would be where I would look to next. If safe mode does not crash, then we can begin trying to narrow the offending software. If it does crash, we should continue analyzing hardware issues.
In my case I also had no problems with performing the memory test after several runs. Only in my case there was clearly some problem with pci-e and a falling disk. All the communication between the disk would fail and it would end with various BSODs because W11 would suddenly lose the disk as if you had physically yanked it out.
The errors were different, some indicated the file system, others indirectly a problem with the disk, although I also remember that I had some error with WATCHDOG a few times.
Of course I am not saying that it is similar in your case because at the moment there is absolutely nothing to indicate it.
But in such situations, in order not to dig too big a hole, I always recommend myself and others to check the situation on another OS/disk, even some Linux live from USB. If the situation is similar here, the problem lies somewhere in the hardware.
Iâm ok w/safe mode, but that really messes up my display. Been through the ddu/gpu process a few times already since this began. Any way to do safe mode w/o losing graphics?
To test in linux, I downloaded MX-23.4_x64.iso from Download Links â MX Linux, rufus considered my mxlinux, to be a potential vector for bios malware because it has uefi loader. proceeding anyway.
So youâre saying safe mode works fine?
Ironically enough a coworker of mine just had this same BSOD error code after windows updates just now.
Iâm not sure what all got updated, but the timing seems suspect.
Full safe mode. Mouse wiggle to verify itâs alive. Donât touch. 28 minutes later, itâs frozen again.
Donât know if Iâm just imagining it, but I think that my using the mouse and keyboard stave off freezes, at least partially. Perhaps the interrupts postpone till later some admin that does something bad.
mouse: G703 lightspeed
Kb: ms ergnomic (natural, I think).
You could try disabling c states or just c6 as the manual shows. Tweaker > Advanced CPU > Global C-State Control.
The next step if windows is not stable in safe mode would be testing linux. You would probably want to find another computer to make a bootable USB for this.
Adubs
I ran the rufus created MX-23.4_x64.iso usb. Got to the point of some sort of âwhat do you want to do nextâ semi-graphical menu. could move up and down. Unsure of how to proceed, so went away for a while. When I came back, the screen was still visible but locked.
It was at this point that I did the full safe mode boot and let it idle. This froze after about 28 min.
I assumed that this meant it was not a configuration error, but hw.
In uefi I reset the bios to system defaults. I think previously I had altered an xmp setting for memory. Still crashes.
Opened up the case and vacuumed away dust. All fans spin easily. Nothing untoward about the mb. It holds 4 identical mem sticks, a cpu w/a big cooling fan, and the gpu. It also has my boot ssd flat against the mb. But in reality, w/only the cpu-cooler and gpu sticking out it looks relatively empty compared to previous builds Iâve seen.
As the gpu seems the most swap-testable item, I thought to do that. Unfortunately, the only other functional computers in the house both have gpuâs that require more connections than my power supply provides, so I canât readily swap those different GPUs in to rule it the 2070s
Having passed the mem test, I assumed that meant the memory couldnât be the issue. Also, just to reiterate, while the mem test lasted longer than an hour, It didnât freeze/crash at all. That alone initially made me think the problem was not hw.
At one pt, I thought that the time between crashes was longer when I was playing w/the mouse/keyboard. Now, I think that was just my imagination.
The only reference I found to C-states in the pdf you provide tells only this:
Global C-state Control (Note)
Allows you to determine whether to let the CPU enter C states. When enabled, the CPU core frequency will be reduced during system halt state to decrease power consumption. (Default: Enabled)
I could try that out, but I donât understand how reducing cpu core frequency during system halt states could possibly reduce the number of crashes.
It could be the ssd since your not booting from it to run memtest x86!
Do you have another ssd you can try in the system?
Have you booted from a linux live cd for more than an hour?
Memtest is specifically designed to be stable in an environment where stability is not a guarantee.
By disabling cstates youâre not reducing core frequency. In fact itâs the opposite. Reread what you posted from the manual.
There are many instances of system instability on AMD with certain cstates (c6 specifically). This is in line with your own experience of jiggling the mouse preventing the freeze.
At any rate if there are newer bios versions available you should be flashing latest. Disable cstates, and report back.
If the machine wonât run from a live Linux USB without locking up after disabling c6 then the options are to start swapping parts/reducing to a minimum and adding them back until you find your instability. Thereâs no reason why a Linux os shouldnât run if memtest passes short of a hardware issue.
Adub
I found an inspiron i3 laptop to use as I was trying to figure out how to fix my desktop w/o breaking the bank. Besides bloatware and being many iterations behind in windows updates, both of which seemed to leave me only 1/2 of a cycle/minute to try to run the browser, the stupid thing wouldnât let me do anything until the it had updated the antimalware and run it on the system. All of this is absolutely unrelated, but I really wanted to rant how horrible the last few days have been.
Nonetheless, I finally figured out that you were telling me that the c-states thing could help me. I didnât understand it, and Iâm really grateful that you provided the path w/in the bios controls to access it, but I made the change. So far, even though I have been using the keyboard and mouse heavily, Iâve been on for almost 3 hours. I donât want to jinx it, but it sure looks promising.
Thank you for that advice and being patient.
In the BIOS disable whatever power management settings you find. You may pay another 25¢ per week for electricity but that seems like a necessary tradeoff. Linux support for power management on AMD . . . sucks.
This topic was automatically closed 273 days after the last reply. New replies are no longer allowed.