Bios update caused weird issues after, looking for help

psyrex157b02d5

New member
Joined
Sep 5, 2020
Messages
6
I have a MSI MPG Z390 GAMING EDGE AC ATX w/ ARGB motherboard.. I was advised to update the bios/drivers so i did. When I came back to windows, after restart, I noticed in task manager my RAM (32GB (8GBx4) DDR4/3200MHz(GSKILL Trident Z RGB)) was set to 2133 (was 3200 before) and my cpu (9900k) was showing 4.7-4.8ghz (it was set at around 4.1 before). I know I asked for overclock option when i got computer (OVERCLOCK: Extreme OC (Extreme Overclock 20% or more)). I went into bios (dont know alot just enough to get by, barely) and changed memory to 3200 (it was now set to "auto"). There was a memory dump file created, 1.61gb in size. I googled "how to see why bsod happened".. I'm asking in here because this is my first bsod and it happened after the bios update and I dont want to adjust anything further that i probably shouldn't be. if there's any info needed please let me know.
 

citay

Active member
SERGEANT
Joined
Oct 12, 2016
Messages
813
The 9900K can go up to 5 GHz with single-core load, so the 4.7 to 4.8 GHz are not out of the ordinary. It will use different turbo frequencies, depending on the load (how many cores are doing something).

Enter the BIOS, switch to advanced mode (press F7). Under Settings - Save & Exit, select to Load optimal defaults.

Then go to "OC".

It looks like so:



First of all, set "OC Explore Mode" to Expert. Under "Misc Setting", set EIST to Enabled and "Enhanced Turbo" to Disabled.

For your RAM, set DRAM Frequency back to Auto, and set Extreme Memory Profile to "Enabled". This will set 3200 MHz and also raise the voltages accordingly, which i'm sure you neglected. Actually, myself, i like to avoid XMP and set everything manually, because sometimes XMP sets slightly too high of a voltage on two other settings (SA and IO voltage). But in your case, getting it stable is more important.

Next, find "CPU Features" (probably down at the bottom). Looks like so:



There, set "Intel C-State" to Enabled.
Set "C1E Support" to Enabled.
Set "Package C-State Limit" to C10 or the highest C-number there is.
Set "Intel Speed Shift" to Enabled.

Finally, go back (pressing ESC and using the arrow keys) to the "Settings" menu. Go Advanced - Power Management Setup and set "ErP Ready" to Enabled:



Then Save & Exit. Should be stable now. If not, report back.
 

psyrex157b02d5

New member
Joined
Sep 5, 2020
Messages
6
thank you for response.. i caught the code when this second bsod happened. Its said "IRQL_NOT_LESS_OR_EQUAL", so i'm stumped
 

citay

Active member
SERGEANT
Joined
Oct 12, 2016
Messages
813
That's a common code that can happen with any instability. Just do the settings i mentioned and hopefully it's stable then.
 

psyrex157b02d5

New member
Joined
Sep 5, 2020
Messages
6
happened again today, the bsod. Error that i see as critical in event viewer is: Kernel-Power - The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

-System

-Provider
[ Name]Microsoft-Windows-Kernel-Power
[ Guid]{331c3b3a-2005-44c2-ac5e-77220c37d6b4}

EventID41

Version8

Level1

Task63

Opcode0

Keywords0x8000400000000002

-TimeCreated
[ SystemTime]2020-09-07T23:18:05.1940075Z

EventRecordID2325

Correlation

-Execution
[ ProcessID]4
[ ThreadID]8

ChannelSystem

ComputerJims-Beast

-Security
[ UserID]S-1-5-18

-EventData

BugcheckCode126

BugcheckParameter10xffffffff80000003

BugcheckParameter20xfffff80160530c03

BugcheckParameter30xffffd888109261c8

BugcheckParameter40xffffd88810925a00

SleepInProgress0

PowerButtonTimestamp0

BootAppStatus0

Checkpoint0

ConnectedStandbyInProgressfalse

SystemSleepTransitionsToOn0

CsEntryScenarioInstanceId0

BugcheckInfoFromEFIfalse

CheckpointStatus0

CsEntryScenarioInstanceIdV20

LongPowerButtonPressDetectedfalse

-System

-Provider
[ Name]Microsoft-Windows-WER-SystemErrorReporting
[ Guid]{ABCE23E7-DE45-4366-8631-84FA6C525952}
[ EventSourceName]BugCheck

-EventID1001
[ Qualifiers]16384

Version0

Level2

Task0

Opcode0

Keywords0x80000000000000

-TimeCreated
[ SystemTime]2020-09-07T23:18:16.5871663Z

EventRecordID2350

Correlation

-Execution
[ ProcessID]0
[ ThreadID]0

ChannelSystem

ComputerJims-Beast

Security

-EventData

param10x0000007e (0xffffffff80000003, 0xfffff80160530c03, 0xffffd888109261c8, 0xffffd88810925a00)

param2C:\WINDOWS\MEMORY.DMP

param3c744a402-2785-4d5f-940b-cdefdc27b512

Sorry, that didnt come out how i thought it would
 

psyrex157b02d5

New member
Joined
Sep 5, 2020
Messages
6
there was some additional windows updates i applied after previous post:
Intel System 9/19/2017 - 11.7.0.1000
Intel Net - 12.18.9.20
Intel Net - 21.90.3.2
A-Volute - Software Component 1.8.4.0 (not sure if this ties in)
Intel - System - 7/18/1968 - 10.1.16.6 (weird date??)
Intel - System - 7/18/1968 - 10.1.14.7
Intel - Other Hardware - Intel(R) Xeon(R) E3 - 1200/1500 v5/6th Gen Intel(R) Core(TM) PCIe Controller (x16) - 1901
Intel - Other Hardware - Intel(R) Xeon(R) E3 - 1200/1500 v5/6th Gen Intel(R) Core(TM) Gaussian Mixture Model - 1911

I have done the mem chk and the 2 passes it did came back without any errors
 

laurence1211

Active member
PRIVATE E-2
Joined
Jun 28, 2020
Messages
389
Out of interest, why were you told to update the bios? Were you having trouble with the computer before hand? Have you considered rolling back to an older bios? Also I would check the power supply unit as well as the CPU.
 

psyrex157b02d5

New member
Joined
Sep 5, 2020
Messages
6
2 reasons really (trust me if I could go back to 4th Sept I would not have done any updates.) -- 1) I was experiencing an issue with Windows Explorer running constantly @ about 10% cpu and RAM was incrementally increasing upwards of 6GB's (sometimes more). And no matter what I did, I couldnt make it stop. Malware/virus checks, sfc /scannow's, etc. 2) I was running a game that was having issues (nothing computer breaking) and was advised that i may need to update all drivers & motherboard. So to tried to kill 2 birds with one stone - I flashed the bios since its date was last 2018 I believe, and I updated GPU, Windows and other drivers. All in one swoop.. When I got done, later that day my problems started.. I did a mem chk, I posted here, I followed those instructions, I even tried to do a system restore, which I thought I would have more options to choose from but only had 2, and they were both around the time this happened (I know I created a restore point sometime in last 30 days personally (forget why)) and I thought it created a restore point anytime I did a total shut down of computer / restart. So, that's the reasons and, again, I wish I hadn't.
 

citay

Active member
SERGEANT
Joined
Oct 12, 2016
Messages
813
So to be clear, you applied the BIOS settings i listed? After loading the standard settings under "Save & Exit" in the BIOS?


About the "CPU Lite Load", yes, i use it on 5. You have to find that out individually for each specific CPU.

BIOS_CPU_Features2.png


Here you can see where CPU Lite Load is.

How to find the right setting: Run https://www.techpowerup.com/download/linpack-xtreme/
(When running that, press 2, then press 5 for 10GB testing, then press 5 for five runs, then press Y and N and N)

Start with CPU Lite Load 5. If it's not enough, Linpack Xtreme will show FAIL. Raise CPU Lite Load by one, until Linpack Xtreme always shows PASS. Then raise it by one additional step for some headroom.

For me, CPU Lite Load 4 was already Linpack-stable (3 was not). I went to 5 to have a little headroom.
 

psyrex157b02d5

New member
Joined
Sep 5, 2020
Messages
6
After updating the drivers I mentioned above and also, just to be sure, I disconnected my phone from usb (usually just let it sit there to charge).. Again, I don't know nothing about anything with this stuff but when I was looking at event viewer around the times of bsod I saw a warning (each time), source Kernel-PnP, right before the crash concerning "The driver \Driver\WudfRd failed to load for the device USB\VID_04E8&PID_6860&MS_COMP_MTP&SAMSUNG_Android\6&36d12e5f&1&0000." -- so hey, why not.. lol.. but so far i've been crash free for almost 24 hours (knock on wood! Usually happens once in a 24hour period thus far) Will update or report another 24hr free of bsod.

- System
- Provider
[ Name] Microsoft-Windows-Kernel-PnP
[ Guid] {9c205a39-1250-487d-abd7-e831c6290539}
EventID 219
Version 0
Level 3
Task 212
Opcode 0
Keywords 0x8000000000000000
- TimeCreated
[ SystemTime] 2020-09-08T01:42:17.1572154Z
EventRecordID 2619
Correlation
- Execution
[ ProcessID] 4
[ ThreadID] 312
Channel System
Computer Jims-Beast
- Security

[ UserID] S-1-5-18

- EventData
DriverNameLength 67
DriverName USB\VID_04E8&PID_6860&MS_COMP_MTP&SAMSUNG_Android\6&36d12e5f&1&0000
Status 3221226341
FailureNameLength 14
FailureName \Driver\WudfRd
Version 0
 
Top