Windows 11 22H2 reboot issue with SIV

Thank you for the quick reply!  I've been using this since early 2019, I'm just not one to do forum posting much anymore so I typically only register when there is a need =)

1.) I'm using 5.67.
2.) It does, however it goes to a different state than before it was run.


3.) I got that saved while running normally, added attachment to original post due to attachment limit per post.

4.) Yes, it reboots without issue with -NODRIVER though I saw this also kills the functionality I use it for.
Doing a bit further looking, I think this may have to do with the exit codes for the driver, it is different from the starting exit code to after closed when run normally but not when the -NODRIVER is used.  Does the driver do this on your other Win11 installs?


5.) It does, this is taken at Goverlay running at LCD plugged in / GOverlay not running and LCD plugged in / GOverlay not running and LCD unplugged


6.) For GOverlay, I've also done a fresh OS install without even having that installed and ran into the same issue.  I had two fresh installs of win11 to narrow down what was causing this weirdness.  After located I restored my full drive backup and verified that simply not autorunning or running SIV fixed the reboot issue, verifying that no other additional application on my current setup should cause an issue.

7.) The M715Q (two of them) are new to replace very old daily driver PCs so we aren't constantly on our higher powered gaming PCs for non gaming tasks, these are also my first step into Win11 testing so far.  I did not test Win10 on them and have not used Win11 prior to latest version so the only ISO I have for installation is the 22H2 at current. I can likely find the 21H2 and try Win10 as well, however I'll need to find a day where I have the time to take a fresh OS backup of Win11 and do the clean reinstalls and be able to reload my backup afterwards.

I wonder if there is a way to force unload the driver through command line at log off, so it could be used as normal and on log off it would clear the issue.
I tried using taskkill to force close the program and the driver/service is still running, so even stopping that with the sc cmd doesn't change anything in this end result.


I found devcon, but don't know enough about the driver to find the full path to see if that might even work.  I figured worse comes to worse that would just require a reinstall of SIV to fix if it completely removed the driver.

1.)  Starting and stopping the driver from cmd works and reboots as intended.  You are likely on the nose for the issue being another driver that is getting called, though it would have to be something that the system normally wouldn't load in order for it to only show up when pulled through SIV.

2.) I disabled core isolation in Win11 and rebooted.  Then tried SIV again and got the same hang on the reboot.  It is so weird, it drops power to my lighted keyboard and mouse, but not to my USB3/card reader hub.  There is no change in hardware I'm using between when it works and when it doesn't.

3.) Just to clarify, shutdown works as intended, even in my OS installed.  The issue only happens on reboots.  If it wasn't for some things forcing reboots or requiring a reboot over a shutdown and power back on, I wou;dn't have bothered with digging into it =)


I'm not sure what in BIOS the ITE IT8738 chip would be referring to or working off of.  I took 9 pics of the various BIOS screens, however the Lenovo BIOS for this is old school and ultra minimalistic....there is no sensor or status type screens to show health or what not.  I've attached as two separate zips to get under the 1 MB limit and not flood the post with 9 attachments.

I also just tried to disable a few extra bits in the flags for SIV on start, no change there either unfortunately:
siv64x -NOWIZARD -TRAY -SINGLE -LOCAL -NOBALLOON -DELAY=2 -NOLINK -NOLCD

The M715Q as a model was made from 06-2017 to 07-2018, I believe it was likely stopped when their 2nd gen of it came out (Ryzen APUs). Based on this, I grabbed and tested the oldest versions of SIV I could find, 5.46 & 5.38 to see if maybe somewhere additional calls were added for newer hardware that cause issues on this specific system. Unfortunately the same result.

Thank you for the screen shots and it looks like the BIOS does not report any of the ITE IT8738 Temperatures, Fan Speeds or Voltages, I will try and improve things for SIV 5.68 Beta-04 and later.

Shutdown being OK and Reboot having the issue is very strange. What happens if you boot the W11 22H2 installation device, select recovery then run SIV64X from the command window, do Menu->Machine->Shutdown then press [ Reboot ]?

None of the things you disabled will affect which other drivers SIVDriver will call and looking at the save file I think the only driver that SIVDriver will call on your system is AmdPPM, the AMD PRO A10-8770E R7, 10 COMPUTE CORES 4C+6G driver, which if the same as I use on my AMD Ryzen 9 5950X 16-Core Processor system.

Do/can you have DBG View? We could use it to get a trace of all the devices SIVDriver accesses by enabling the SIVDriver open tracing. Would you like to try this?

-NOASUS-WMI - should not be needed as you don't have a ACPI\PNP0C14\ASUSWMI device.
-NODIMMS - should not be needed as SIV directly reads the SMBus
-NOECR - I don't think this is needed.
-NORAID - should not be needed as you don't have a RAID disk drive.

I'll try that, just checked the flags I used and the only additional one needed to reboot successfully was -NODIMMS

I booted from the install disk and got to cmd line and was able to launch SIV.  I used the reboot option from inside SIV as directed, same issue as before.

I got to leave for work in like 30 minutes, if you want me to still do the debugger just let me know what to look for from it and I'll get that done tonight or tomorrow.  Thanks for all the help =)

Here is that log file.  I went in and did the SIV SMBus Setup exclusions as well.

Does that save to a local config file or does that change make the -NODIMMS flag no longer needed?  I mean for what I monitor I won't likely need it, but hopefully it will help someone else not run into a similar issue later.  I only went with Win11 on the daily driver systems so I can get used to the changes and find fixes for things like this that might come up before upgrading my wife's and my gaming rigs in the next month or so.

I really do appreciate the time and effort you put into assisting and supporting this program.  It has allowed me to go with one program (that doesn't have cost involved like AIDA64) rather than having to use separate programs to monitor different aspects.

I have just uploaded SIV64X 5.68 Beta-04 which should correctly report the ITE IT8738 Temperatures, Fan Speeds and Voltages, does it please?

It will also by default exclude the 0_18 to 0_1B SMBus slave addresses so with luck when -NODIMMS is not specified reboot will be OK, is it? This should work even if no exclusions have been added, do reg delete HKLM\Software\SIV /f /v "SMBus Skip" to delete all the exclusions you manually added.

Thank you for checking out the sensors and the numbers look OK to me, do they to you?

-NODIMMS still being needed when SIV 5.68 Beta-04 is used does not make sense, I wonder what does Menu->Tools->Configure->SIV SMBus Setup report? Did you do reg delete HKLM\Software\SIV /f /v "SMBus Skip"?

Please post the two log files generated doing as below.

SIV64X -DBGSMB          -EXIT=10 > SIV_DBGOUT_ONE.log | more
SIV64X -DBGSMB -NODIMMS -EXIT=10 > SIV_DBGOUT_TWO.log | more

The first one will access 0_50 + 0_36 to read the SPD, but I can't imagine this triggering the issue as I expect the BIOS will do much the same when the system posts given it sets up Samsung M471A1K43CB1-CRC #9257-11A9 in the SMBIOS, see [ Machine ].

Thank you for checking things out. Both .LOG files are as I expected they would be so something is very strange with the SMBus DIMM SPD access on this system, I have not come across any other system with a similar issue.

For now I guess just use -NODIMMS while I ponder what the root cause of the issue could be.

If you run CPUZ does it also trigger the reboot issue? If not what happens if you run SIV (without -NODIMMS), exit SIV, run CPUZ and finally reboot?

Given what is happening I expect any version of Windows will suffer the same reboot issue.

Thank you for doing the tests with CPUZ which gave me an idea as to what might be happening. As SIV64X.exe is too big to attach I have emailed you SIV64X.exe 5.68 Test-05 that may make the reboot issue go away, did it get through?

To test replace the Beta-04 with Test-05, run SIV64X (without -NODIMMS), confirm [ SPD ] reports the SPD then reboot. If it reboots OK then I can/will explain what the issue with reboot was if you would like to know.

With Test-05 the trace should be similar to:DIMM SPD    Slave 0_50  CMD 00  Numb 256
    SPD    Slave 0_50  CMD 00  Numb 256  Flag 00000D00  DDR4 Page 6
    SPD    Slave 0_50  CMD 00  Numb 256  Flag 00000F00  DDR4 Page 7
    TMP~   Slave 0_18  CMD 05  Numb 0    Flag 40000000  Status 0044  Time 8    Size 32   word 0000 0000 0000
    SPZ    Slave 0_50  CMD 00  Numb 0    Flag 00000D00  DDR4 Page 6
The SPZ at the end is new and resets the SPD page

Good, but it's Test-05 rather than Beta 5, I will release Beta-05 in a while

I expect the reboot issue was down to a getting stuck doing the BIOS post. When you did the reboot I think Windows shutdown OK and then got stuck in the BIOS when SPD page 1 was left selected before the reboot. The change to SIV was to select page 0 and the reason CPUZ made the issue go away is that it selected page 0. Given I have never seen this issue before I feel the Lenovo BIOS could/should allow for page 1 being selected.