Windows 10 1909 x32 english iso checksum

[Mazaki]

I'm always getting BSOD when I start the windows 10, I downloaded the iso in the website of microsoft . Can someone tell me your checksum of your windows 10 x32 1909 iso pls...

Windows 10 1909
English
x32

Sorry for my bad english...

[SOLVED]
File: Download/Win10_1909_English_x32.iso
MD5: 503917:c6:96:19:08:cf:21:63:f4:32:89:13
SHA1: 05:aa:e7:5b:98:43:be:90:45:e3:73:77:89:d7:10:df:ce:93:98:4b
SHA256: 07:04:47:d8:8b:b3:a7:12:60:b1:48:4f:d7:9d:ee:b6:f2:1b:c4:ec:af:45:76:8a:3f:90:2d:4e:6f:a6:48:6d

[scottgus1]

I don't have a W10 1909 32bit ISO to checksum. You can re-download the ISO and do a file compare.

You can zip and post a guest vbox.log for that BSODing guest, using the forum's Upload Attachment tab, there may be something amiss in the guest's settings.

If your guest's Virtualbox container window is still open while the guest BSODs, then Virtualbox is working and the Windows OS has problems. Troubleshoot the BSODs as if your Windows 10 was installed on a real PC.

[Mazaki]

I don't have a W10 1909 32bit ISO to checksum. You can re-download the ISO and do a file compare.

You can zip and post a guest vbox.log for that BSODing guest, using the forum's Upload Attachment tab, there may be something amiss in the guest's settings.

If your guest's Virtualbox container window is still open while the guest BSODs, then Virtualbox is working and the Windows OS has problems. Troubleshoot the BSODs as if your Windows 10 was installed on a real PC.

My first experience, my first error...

[scottgus1]

00:01:36.142179 Changing the VM state from 'RUNNING' to 'SUSPENDING'
00:01:37.834978 PDMR3Suspend: Driver 'VD'/1 on LUN#6 of device 'ahci'/0 took 1 692 728 678 ns to suspend
00:01:37.872806 PDMR3Suspend: 1 730 581 407 ns run time
00:01:37.872834 Changing the VM state from 'SUSPENDING' to 'SUSPENDED'
00:01:37.872856 Console: Machine state changed to 'Paused'
00:01:40.623311 GUI: Request for close-action to power VM off.
00:01:40.623357 GUI: Passing request to power VM off from machine-logic to UI session.
00:01:40.623368 GUI: Powering VM down on UI session power off request...
00:01:40.623834 Console: Machine state changed to 'Stopping'
00:01:40.624938 Console::powerDown(): A request to power off the VM has been issued (mMachineState=Stopping, InUninit=0)
00:01:40.626189 Changing the VM state from 'SUSPENDED' to 'POWERING_OFF

'

Looks like a normal minute & 40 seconds run to me.

00:00:09.779772 Display::i_handleDisplayResize: uScreenId=0 pvVRAM=000000000b490000 w=1024 h=768 bpp=24 cbLine=0xC00 flags=0x0 origin=0,0
00:01:33.161799 VMMDev: Guest Log: BIOS: KBD: int09h_handler(): unknown scancode read: 0x5d!
00:01:33.527027 VMMDev: Guest Log: BIOS: KBD: int09h_handler(): scancode & asciicode are zero?
00:01:33.541258 VMMDev: Guest Log: BIOS: KBD: int09h_handler(): scancode & asciicode are zero?

This part looks unusual, were you mashing an unusual keyboard sequence?

The attached zipped picture 'VirtualBox_Windows 10_30_12_2019_16_14_39.png' shows a clear in-the-guest BSOD. You will have to:

Troubleshoot the BSODs as if your Windows 10 was installed on a real PC.

[Mazaki]

Troubleshoot the BSODs as if your Windows 10 was installed on a real PC.

But I don't know how to troubleshoot I'm new to this BSOD and I can't go to recovery tool I'm always getting BSOD... Can I ask if the picture that I send you meaning that the iso I install is corrupted?

[scottgus1]

Can I ask if the picture that I send you meaning that the iso I install is corrupted?

If the BSOD happened while you're installing, then maybe.

Troubleshooting a BSOD is best Googled about. Plenty of info out there on the web.