red-ray Posted September 4, 2016 Share Posted September 4, 2016 Did you add the exclusion and reboot? If you reboot the system and then do SIV64X.exe -DBGSMB what is in SIV_DBGOUT.log? I have now asked 3 times, how many times will I have to ask you to do this? Link to comment Share on other sites More sharing options...
AM16 Posted September 4, 2016 Author Share Posted September 4, 2016 2016-09-04 00:19:42 ********** \\DESKTOP-KCFJEHT 0000000000000000 = GetStdHandle( STD_OUTPUT_HANDLE ) - error 10 - The environment is incorrect.SIV_DBGOUT.txt Link to comment Share on other sites More sharing options...
red-ray Posted September 4, 2016 Share Posted September 4, 2016 Did you add the exclusion and reboot? That is only the first line, what about the others? Link to comment Share on other sites More sharing options...
AM16 Posted September 4, 2016 Author Share Posted September 4, 2016 Pretty much the same thing, and yes, I did reboot. Let me remove the exlusion and reboot. Link to comment Share on other sites More sharing options...
AM16 Posted September 4, 2016 Author Share Posted September 4, 2016 Yep, same thing 016-09-04 00:25:32 ********** \\DESKTOP-KCFJEHT 0000000000000000 = GetStdHandle( STD_OUTPUT_HANDLE ) - error 10 - The environment is incorrect.SIV_DBGOUT.txt Link to comment Share on other sites More sharing options...
red-ray Posted September 4, 2016 Share Posted September 4, 2016 Pretty much the same thing, and yes, I did reboot. Let me remove the exlusion and reboot. NO, leave the exclusion there. Also add 0_20 + 0_41 + 0_45 + 0_70 to 0_78, reboot, delete SIV_DBGOUT.log and try again. Basically I suspect there is one or more strange SMBus slave devices and as soon as HWiNFO/SIV try to read it then the SMBus locks up (Time 999 shows it's locked up). We need to add these to the exclusion list and then all should be OK. Link to comment Share on other sites More sharing options...
AM16 Posted September 4, 2016 Author Share Posted September 4, 2016 NO, leave the exclusion there. Also add 0_20 + 0_41 + 0_45 + 0_70 to 0_78, reboot, delete SIV_DBGOUT.log and try again. 2016-09-04 00:19:42 ********** \\DESKTOP-KCFJEHT 0000000000000000 = GetStdHandle( STD_OUTPUT_HANDLE ) - error 10 - The environment is incorrect. PWMX PWM Slave 0_60 Regime 1 Model 0000 PWMI PWM Slave 0_70 Regime 1 Model 0000 CMD 9A Numb 0 Status 41 Time 999 Size 32 PWMI PWM Slave 0_41 Regime 1 Model 0000 CMD 9A Numb 0 Status 44 Time 499 Size 32 PWMI PWM Slave 0_45 Regime 1 Model 0000 CMD 9A Numb 0 Status 41 Time 999 Size 32 PWMI PWM Slave 0_20 Regime 1 Model 0000 CMD 9A Numb 0 Status 41 Time 999 Size 32 PWMI PWM Slave 0_78 Regime 1 Model 0000 CMD 9A Numb 0 Status 44 Time 531 Size 32 PWMI PWM Slave 0_71 Regime 2 Model 0000 CMD 9A Numb 0 Status 41 Time 999 Size 32 PWMI PWM Slave 0_72 Regime 2 Model 0000 CMD 9A Numb 0 Status 41 Time 999 Size 32 PWMI PWM Slave 0_73 Regime 2 Model 0000 CMD 9A Numb 0 Status 44 Time 524 Size 32 PWMI PWM Slave 0_74 Regime 2 Model 0000 CMD 9A Numb 0 Status 41 Time 999 Size 32 PWMI PWM Slave 0_75 Regime 2 Model 0000 CMD 9A Numb 0 Status 41 Time 999 Size 32 PWMI PWM Slave 0_76 Regime 2 Model 0000 CMD 9A Numb 0 Status 44 Time 559 Size 32 PWMI PWM Slave 0_77 Regime 2 Model 0000 CMD 9A Numb 0 Status 41 Time 999 Size 32 Whoa, ok so I added those you told me, shut down the system, came up with a memory error beep, hard powered back up, and now SPD is showing everywhere. Thanks a trillion. Is there any risk on adding all those exclusions to windows 10 itself?SIV_DBGOUT.txt Link to comment Share on other sites More sharing options...
red-ray Posted September 4, 2016 Share Posted September 4, 2016 Is there any risk on adding all those exclusions to windows 10 itself? None at all. They are stored in HKCU\Software\SIV\SMBus Skip and only SIV accesses this. HWiNFO has a similar regime. I should change SIV so that it excludes these by default, but suspect they don't all need to be excluded. I assume Menu->System->SMB Bus how reports the DIMMs, etc.. Please will you remove each exclusion in turn for the range 0_10 to 0_7F, check [sMB Bus] still reports the DIMMs and come up with which ones are actually needed. Once we know this I will update SIV so this happens automatically for Intel DZ77 motherboards. Link to comment Share on other sites More sharing options...
AM16 Posted September 4, 2016 Author Share Posted September 4, 2016 Yep, let me create the list/log Link to comment Share on other sites More sharing options...
red-ray Posted September 4, 2016 Share Posted September 4, 2016 Yep, let me create the list/log Great. Ideally just post the final [sMB Bus] + [sIV SMBus Setup] panel screen shots. Link to comment Share on other sites More sharing options...
AM16 Posted September 4, 2016 Author Share Posted September 4, 2016 Well... I unchecked everything from 0_10 to 0_7F, rebooted, made the list, excluded the ones on the list, rebooted but it still doesn't work after doing that.SIV_DBGOUT.txt Link to comment Share on other sites More sharing options...
AM16 Posted September 4, 2016 Author Share Posted September 4, 2016 I'm guessing maybe the 0_10 row needs to be exceptioned entirely? I'll give it a shot, that's the big change from earlier kind of? Link to comment Share on other sites More sharing options...
red-ray Posted September 4, 2016 Share Posted September 4, 2016 Well... I unchecked everything from 0_10 to 0_7F, rebooted, made the list, excluded the ones on the list, rebooted but it still doesn't work after doing that. You need to remove one at a time each time checking that [sMB Bus] still works and reports the DIMMs. Power cycle the system and start again. Looking at [sMB Bus] you have excluded 0_50 to 0_57. These are the DIMMs so should be ne excluded. Link to comment Share on other sites More sharing options...
AM16 Posted September 4, 2016 Author Share Posted September 4, 2016 It's going to take a while... the behaviour here is crazy. I hope the system doesn't fail either. It only likes full power cycles while waiting, otherwise it keeps the old stuff. Link to comment Share on other sites More sharing options...
red-ray Posted September 4, 2016 Share Posted September 4, 2016 OK. My guess is that 0_60 + 0_69 will have to be excluded. As for the others your guess is as good as mine! Link to comment Share on other sites More sharing options...
AM16 Posted September 4, 2016 Author Share Posted September 4, 2016 Yeah... I'm guessing the main problem is that this Mainboard doesn't like XMP, non SPD standard configurations and loses its normality when using XMP. It could be the BIOS going haywire... I'll try reflashing the latest one (the one it currently has 066) later. Here's the best I could do what the log says: 2016-09-04 03:17:17 ********** \\DESKTOP-KCFJEHT 0000000000000000 = GetStdHandle( STD_OUTPUT_HANDLE ) - error 10 - The environment is incorrect. PWMX PWM Slave 0_60 Regime 1 Model 0000 PWMX PWM Slave 0_70 Regime 1 Model 0000 PWMX PWM Slave 0_41 Regime 1 Model 0000 PWMX PWM Slave 0_45 Regime 1 Model 0000 PWMX PWM Slave 0_20 Regime 1 Model 0000 PWMX PWM Slave 0_78 Regime 1 Model 0000 PWMX PWM Slave 0_71 Regime 1 Model 0000 PWMX PWM Slave 0_72 Regime 1 Model 0000 PWMX PWM Slave 0_73 Regime 1 Model 0000 PWMX PWM Slave 0_74 Regime 1 Model 0000 PWMX PWM Slave 0_75 Regime 1 Model 0000 PWMX PWM Slave 0_76 Regime 1 Model 0000 PWMX PWM Slave 0_77 Regime 1 Model 0000 DIMM SPD Slave 0_50 CMD 0 Numb 256 BAD Slave 0_18 CMD 5 Numb 0 Flag 40000000 Status 0044 Time 11 Size 32 word 0000 0000 DIMM SPD Slave 0_51 CMD 0 Numb 256 BAD Slave 0_19 CMD 5 Numb 0 Flag 40000000 Status 0044 Time 11 Size 32 word 0000 0000 DIMM SPD Slave 0_52 CMD 0 Numb 256 BAD Slave 0_1A CMD 5 Numb 0 Flag 40000000 Status 0044 Time 10 Size 32 word 0000 0000 DIMM SPD Slave 0_53 CMD 0 Numb 256 BAD Slave 0_1B CMD 5 Numb 0 Flag 40000000 Status 0044 Time 11 Size 32 word 0000 0000 I even unchecked one by one from 0_18-0_1B and nothing either. The RTC Timer also shows an odd error which is why I think it's bad frequency... or at worst, the mainboard is somehow dying via RTC or the chipset. Link to comment Share on other sites More sharing options...
red-ray Posted September 4, 2016 Share Posted September 4, 2016 The SMBus locking and the XMP issues are two different issues. DIMM SPD Slave 0_50 CMD 0 Numb 256 BAD Slave 0_18 CMD 5 Numb 0 Flag 40000000 Status 0044 Time 11 Size 32 word 0000 0000 The BAD Slave 0_18 is fine as Time 11 is OK. These are SIV trying to detect the DIMM MTS (Module Thermal Sensors). I can't believe all of these need to be excluded. Post the [sMB Bus] panel. Uncheck both 0_41 and 0_45, press [sMB Bus] and post the panel. Uncheck all of 0_30 to 0_3B, press [sMB Bus] and post the panel. Uncheck all of 0_20 to 0_2F, press [sMB Bus] and post the panel. Uncheck all of 0_10 to 0_1F, press [sMB Bus] and post the panel. Link to comment Share on other sites More sharing options...
AM16 Posted September 4, 2016 Author Share Posted September 4, 2016 Anything in the 20s and 30s freezes the mainboard, and after rebooting it just gives errors/no spd readings. Anything in the 10 series well doesn't work with the exception of 18-1B which gives the same bad message as the memory. 41 and 45 give the error about the timeout 44 status. Link to comment Share on other sites More sharing options...
AM16 Posted September 4, 2016 Author Share Posted September 4, 2016 But If I don't leave them on as exceptions, then the weird nonexistent devices show up on the Link device list. Link to comment Share on other sites More sharing options...
red-ray Posted September 4, 2016 Share Posted September 4, 2016 As you have no posted any [sMB Bus] screen shots I can't sensibly comment. Link to comment Share on other sites More sharing options...
AM16 Posted September 4, 2016 Author Share Posted September 4, 2016 As you have no posted any [sMB Bus] screen shots I can't sensibly comment. This is like... LITERALLY the best I could get it to. Unchecking anything else stops the SPD display or freezes the system and requires a cold start. I had some data corruption on the hard drives so that's why it took a while to get this. As always, the Link is showing crap if I enable all that stuff. 2016-09-04 06:06:10 ********** \\DESKTOP-KCFJEHT 0000000000000000 = GetStdHandle( STD_OUTPUT_HANDLE ) - error 10 - The environment is incorrect. PWMX PWM Slave 0_60 Regime 1 Model 0000 PWMI PWM Slave 0_70 Regime 1 Model 0000 CMD 9A Numb 0 Status 44 Time 11 Size 32 PWMI PWM Slave 0_41 Regime 1 Model 0000 CMD 9A Numb 0 Status 44 Time 11 Size 32 PWMI PWM Slave 0_45 Regime 1 Model 0000 CMD 9A Numb 0 Status 44 Time 11 Size 32 PWMX PWM Slave 0_20 Regime 1 Model 0000 PWMI PWM Slave 0_78 Regime 1 Model 0000 CMD 9A Numb 0 Status 44 Time 11 Size 32 PWMI PWM Slave 0_71 Regime 2 Model 0000 CMD 9A Numb 0 Status 44 Time 11 Size 32 PWMI PWM Slave 0_72 Regime 2 Model 0000 CMD 9A Numb 0 Status 44 Time 11 Size 32 PWMI PWM Slave 0_73 Regime 2 Model 0000 CMD 9A Numb 0 Status 44 Time 10 Size 32 PWMI PWM Slave 0_74 Regime 4 Model 0D01 CMD 20 Numb 1 Status 42 Time 37 Size 33 PWMI PWM Slave 0_75 Regime 2 Model 0000 CMD 9A Numb 0 Status 44 Time 11 Size 32 PWMI PWM Slave 0_76 Regime 4 Model 0501 CMD 20 Numb 1 Status 42 Time 37 Size 33 PWMI PWM Slave 0_77 Regime 2 Model 0000 CMD 9A Numb 0 Status 44 Time 11 Size 32 DIMM SPD Slave 0_50 CMD 0 Numb 256 BAD Slave 0_18 CMD 5 Numb 0 Flag 40000000 Status 0044 Time 11 Size 32 word 0000 0000 DIMM SPD Slave 0_51 CMD 0 Numb 256 BAD Slave 0_19 CMD 5 Numb 0 Flag 40000000 Status 0044 Time 11 Size 32 word 0000 0000 DIMM SPD Slave 0_52 CMD 0 Numb 256 BAD Slave 0_1A CMD 5 Numb 0 Flag 40000000 Status 0044 Time 11 Size 32 word 0000 0000 DIMM SPD Slave 0_53 CMD 0 Numb 256 BAD Slave 0_1B CMD 5 Numb 0 Flag 40000000 Status 0044 Time 9 Size 32 word 0000 0000 PWMU PWM Slave 0_74 Regime 4 Model 0D01 PWMU PWM Slave 0_76 Regime 4 Model 0501 PWMU PWM Slave 0_74 Regime 4 Model 0D01 Link to comment Share on other sites More sharing options...
AM16 Posted September 4, 2016 Author Share Posted September 4, 2016 This might help as well... Link to comment Share on other sites More sharing options...
red-ray Posted September 4, 2016 Share Posted September 4, 2016 PWMI PWM Slave 0_74 Regime 4 Model 0D01 CMD 20 Numb 1 Status 42 Time 37 Size 33 PWMI PWM Slave 0_76 Regime 4 Model 0501 CMD 20 Numb 1 Status 42 Time 37 Size 33 Thank you for all the testing and things now seem to be stabilising. I can see there are PWM power controllers at 0_74 + 0_76. Please will you generate new save files so I can get SIV to report these? I suspect one will be the CPU power usage, but am unsure about the other. Please do Menu->File->Download->SIV Beta to get SIV 5.13 Beta-13 or later and use this to generate the save files. I suspect it will report System Power Usage on the initial screen and also sets the default exclusions. Once I have these I will adjust the PWM power controller information as needed. Link to comment Share on other sites More sharing options...
AM16 Posted September 4, 2016 Author Share Posted September 4, 2016 Got the Beta running... Is the save file the same one as before or is it a dump of something else? I attached the same command as before but on the beta. It didn't say anything different nor did it change the settings.SIV_DBGOUT.txt Link to comment Share on other sites More sharing options...
red-ray Posted September 4, 2016 Share Posted September 4, 2016 Is the save file the same one as before or is it a dump of something else? Yes, as before better still do Menu->File->Save Local ;): Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.