Hello,
I am a new member here that has noticed an "issue" when using the BSOD Collection App (SN BSOD CA going forward).
I have a PC that is experiencing a BSOD boot loop. I posted over on the Bleeping Computer forums because I have gotten excellent help before.
Their first step requests a dump of the SN BSOD CA from the computer requiring support. This is great and useful if the PC can boot into Windows normally. However, when in a boot loop that even safe mode can't break, things are more complicated.
As a person that tries to give the best info possible, I booted unto Hiren's Boot CD, downloaded and ran SN BSOD CA. This resulted in the Windows version being reported as Enterprise even though the real Windows 10 install was home version.
Since I couldn't boot to the problem OS I grabbed a spare laptop and tested on that. The results were as expected. When running SN BSOD CA within a functioning Windows install it reports the proper OS version and edition, but within Hiren's Boot CD recovery environment, the version and edition are reporting as Enterprise. Below are two pastebins of the DxDiagx86 files.
Sysnative run in Windows 10 DxDiag - ------------------System Information------------------ Time of this r - Pastebin.com
Sysnative run in Hirens Boot CD DxDiag - ------------------System Information------------------ Time of this r - Pastebin.com
I also attached the full zip's from each boot environment.
Overall, I do not think this is a serious issue (and it may be a known issue, I couldn't find anything) but it is one that could put a small subset of users into a place where they cannot get support due to the Edition reporting as Enterprise.
I am a new member here that has noticed an "issue" when using the BSOD Collection App (SN BSOD CA going forward).
I have a PC that is experiencing a BSOD boot loop. I posted over on the Bleeping Computer forums because I have gotten excellent help before.
Their first step requests a dump of the SN BSOD CA from the computer requiring support. This is great and useful if the PC can boot into Windows normally. However, when in a boot loop that even safe mode can't break, things are more complicated.
As a person that tries to give the best info possible, I booted unto Hiren's Boot CD, downloaded and ran SN BSOD CA. This resulted in the Windows version being reported as Enterprise even though the real Windows 10 install was home version.
Since I couldn't boot to the problem OS I grabbed a spare laptop and tested on that. The results were as expected. When running SN BSOD CA within a functioning Windows install it reports the proper OS version and edition, but within Hiren's Boot CD recovery environment, the version and edition are reporting as Enterprise. Below are two pastebins of the DxDiagx86 files.
Sysnative run in Windows 10 DxDiag - ------------------System Information------------------ Time of this r - Pastebin.com
Sysnative run in Hirens Boot CD DxDiag - ------------------System Information------------------ Time of this r - Pastebin.com
I also attached the full zip's from each boot environment.
Overall, I do not think this is a serious issue (and it may be a known issue, I couldn't find anything) but it is one that could put a small subset of users into a place where they cannot get support due to the Edition reporting as Enterprise.
