BSOD's after performing BIOS update for Intel microcode fix

[Dankvampire]

I updated my BIOS last night since it was available with the Intel microcode fix for CPU voltage.

My system is as follows:

I7-13700k

32 gb 3200mhz ddr4 (g.skill tridentZ)

Gigabyte Z790 Aorus Elite AX DDR4

EVGA 3090ti

 

I upgraded to windows 11 late last year, but just to be safe, I reformatted my boot drive and performed a completely fresh install of windows 11.  I have never had a BSOD with this CPU/mobo combo until last night after I performed this BIOS update.

 

My old settings for the previous BIOS version had the GB perfdrive setting to default and I had XMP enabled.

 

I have tried disabling XMP, but to no avail.  I have no clue how to correct the BSOD's, but it's infuriating because the system won't even fully boot before getting a BSOD.

 

Any help or advice would be greatly appreciated.

[Dreckssackblase]

A BSOD should give you some a Stop Code, which gives some hint as to what the issue might be.

Have you seen your Stop Code ?

[DoctorNick]

14 minutes ago, Dankvampire said:

I updated my BIOS last night since it was available with the Intel microcode fix for CPU voltage.

My system is as follows:

I7-13700k

32 gb 3200mhz ddr4 (g.skill tridentZ)

Gigabyte Z790 Aorus Elite AX DDR4

EVGA 3090ti

 

I upgraded to windows 11 late last year, but just to be safe, I reformatted my boot drive and performed a completely fresh install of windows 11.  I have never had a BSOD with this CPU/mobo combo until last night after I performed this BIOS update.

 

My old settings for the previous BIOS version had the GB perfdrive setting to default and I had XMP enabled.

 

I have tried disabling XMP, but to no avail.  I have no clue how to correct the BSOD's, but it's infuriating because the system won't even fully boot before getting a BSOD.

 

Any help or advice would be greatly appreciated.

Looks like a great fix intel. I'll just limit vcore to 1.55v. If you haven't had any issues before, why not just roll back?

https://community.intel.com/t5/Processors/Microcode-0x129-Update-for-Intel-Core-13th-and-14th-Gen-Desktop/m-p/1622129

[Mark Kaine]

1 minute ago, DoctorNick said:

Looks like a great fix intel. I'll just limit vcore to 1.55v. If you haven't had any issues before, why not just roll back?

https://community.intel.com/t5/Processors/Microcode-0x129-Update-for-Intel-Core-13th-and-14th-Gen-Desktop/m-p/1622129

hey if it doesn't run it also cant break, intel, probably.  

[Dankvampire]

18 minutes ago, Dreckssackblase said:

A BSOD should give you some a Stop Code, which gives some hint as to what the issue might be.

Have you seen your Stop Code ?

I'll turn the PC on when I get home and get the BSOD code for you!  I do believe it was exactly the same as the code you show in the above screenshot.

[Dankvampire]

13 minutes ago, DoctorNick said:

Looks like a great fix intel. I'll just limit vcore to 1.55v. If you haven't had any issues before, why not just roll back?

https://community.intel.com/t5/Processors/Microcode-0x129-Update-for-Intel-Core-13th-and-14th-Gen-Desktop/m-p/1622129

How would I go about performing a rollback of the BIOS?  If that is possible, I will happily try that tonight!

[Haswellx86]

49 minutes ago, DoctorNick said:

I'll just limit vcore to 1.55v

Maybe a little lower. Depends on the temps as well. I saw a brilliant video where the guy told to sync all cores instead having a high single core turbo, which will spike the voltage the highest. But having an IA VR limit will be the best.

 

We still need the error code, as it could also be caused by other factors as well.

[Bjoolz]

Go to C:\Windows\Minidump and check if you have any minidump files. If you do, go back to the Windows folder and copy the Minidump folder itself to the Downloads folder (You can use the desktop if you don't have OneDrive syncing files). Zip the copied folder and attach it to a post. Please follow the instructions to the letter as Windows doesn't like you messing with files in this location.

[Dankvampire]

8 hours ago, Gat Pelsinger said:

Maybe a little lower. Depends on the temps as well. I saw a brilliant video where the guy told to sync all cores instead having a high single core turbo, which will spike the voltage the highest. But having an IA VR limit will be the best.

 

We still need the error code, as it could also be caused by other factors as well.

The stop code I repeatedly get with XMP enabled is "SYSTEM SERVICE EXCEPTION".

[Dankvampire]

9 hours ago, Dankvampire said:

I'll turn the PC on when I get home and get the BSOD code for you!  I do believe it was exactly the same as the code you show in the above screenshot.

The stop code that I am getting is "SYSTEM SERVICE EXCEPTION" 

[Dankvampire]

50 minutes ago, Bjoolz said:

Go to C:\Windows\Minidump and check if you have any minidump files. If you do, go back to the Windows folder and copy the Minidump folder itself to the Downloads folder (You can use the desktop if you don't have OneDrive syncing files). Zip the copied folder and attach it to a post. Please follow the instructions to the letter as Windows doesn't like you messing with files in this location.

Here is the minidump that was in that file location.  What would I be looking for in here?

Minidump.zip

[Bjoolz]

2 hours ago, Dankvampire said:

Here is the minidump that was in that file location.  What would I be looking for in here?

Minidump.zip 530.36 kB · 0 downloads

You need a debugger to read them. I would suggest WinDbg which is free on the Microsoft Store (Might be called WinDbg Preview).

And you might have to. The latest Windows didn't have symbols for the kernel. Symbols are created for each driver by the driver developer and they explain to the debugger what each command means. They put them on Microsoft's server where the debugger can download them. Without symbols, you just get a string of letters and numbers instead of the command which isn't readable to a human. And you just get "Wrong Symbols" all over the place in the debugger. You often have symbols for stuff on your own PC though, so you might be able to read these. If you could, open them in WinDbg, click the blue "Analyze -v" button and then copy paste the output to either a pastebin or text document and link/upload them here. 

 

If you get this after analyzing, you have the same issue everyone else is having: 

[DoctorNick]

15 hours ago, Dankvampire said:

How would I go about performing a rollback of the BIOS?  If that is possible, I will happily try that tonight!

Q-flash plus. See page 12: https://download.gigabyte.com/FileList/Manual/mb_manual_intel700-features_e.pdf?v=d6673418751249dec153085bd2189129

[DoctorNick]

15 hours ago, Gat Pelsinger said:

Maybe a little lower. Depends on the temps as well. I saw a brilliant video where the guy told to sync all cores instead having a high single core turbo, which will spike the voltage the highest. But having an IA VR limit will be the best.

 

We still need the error code, as it could also be caused by other factors as well.

It says 1.55v limit. Theres obviously a lot of other factors going on. Limiting current being the main goal.