Frequent BSODs everytime I install Win 10

Hi guys,

Just wanna ask for advice on a new build that i built 2 days ago.

I have a ryzen 2600 paired with an x370 taichi from Asrock and am running a r9 290.

Everytime when I install windows off the iso thats on my usb stick the system will bsod when microsoft is updating the drivers.
Its a different bsod every time, and the most recent one being kmode_exception_nothandled

Any ideas what the problem might be? This is the 5th time im trying to mount the OS, memtest and chkdsk are both showing memory and ssd are okay

Comments

  • When you say iso was it created from the official media creation tool.

    Is it using the internet to update and if so, can you disable internet (ie router) so it won't get the latest.

    Have you updated mobo bios?

    • Yup official media tool, and yep it is using the internet to update itself. During the install I dont connect it to the internet, i try to get the drivers off the disk.

      The bios is updated to the latest version.

  • Corrupt ISO? Very unlikely to be a hardware problem

    • I dont really know at this point, ive already tried a whole range of things. Fresh installed it more than 5 times now, and getting a bsod around 20 mins into the OS running

  • +1

    Its a different bsod every time,

    Run memtest86 (not windows memory test), run for several hours.

    when microsoft is updating the drivers

    Try installing OS, don't connect it to the network so it doesn't try and update drivers. Is it stable when running for several hours? (isolating it to windows update/driver issue).

    windows off the iso thats on my usb stick

    Redownload iso, recreate on a different USB disk using media creation tool.

    • I agree with running memtest. I had a recent machine I was building with Win10 and it kept failing or getting a BSOD, with different errors. The weird thing is, all of the parts were brand new except for the RAM stick - which had been running in another PC 24/7 for the last 6 months. I ran memtest86, and it detected hundreds of thousands of errors almost instantly. Replaced the memory, and it built without issue

    • Additionally, you can analyse your dump files to see what file is causing the blue screen. Have a read on windbg. You might find it's always video card drivers (eg atikmdag.sys). You might be able to isolate what's causing it / manually install drivers and see if that resolves issue.

      If you have onboard video on your mainboard, remove video card and reattempt driver update.

    • If i dont update the drivers, can i install a stress tester like aida to see if its stable? And if its not it would crash?

  • Sounds like an outdated mobo issue. Take everything out including the gpu and ram and any aftermarket cooler, so you just have a basic build with one stick of ram. Then install and update and add the rest of the ram (check boards ram capacity and ram speed too) , update and then add the gpu, and update with geforce. If still working, add any other accessory parts. I have had trouble installing win 10 from a boot usb on older hdd drives too, so try a fresh ssd drive (it doesnt have to be big, it just for the OS, you can chuck your other drives in as slaves).

    • The x370 doesnt have any display outputs haha. I will probably try to clear the cmos

      • oh damn, probably wont clear the cmos, but you will have to do a blind post and have a beep chart handy. Not for the fainthearted.

  • I’ve had something similar happen in the past. Kept having the OS crash and corrupt itself. It turned out to be the SSD.

  • Clear Cmos, Update Bios if possible and recreate the USB using this tool https://www.microsoft.com/en-au/software-download/windows10

  • Might also want to try without any internet just get windows installed, then when you update the drivers do it slowly. I have no idea how to do that in 10? But in 7 I had a similar issue, turned out I had to choose the oldest maybe 5 updates, update those, then restart, then updated another 5 or 10 and restarted again, then did another 10.

    I'm unsure why staggering it fixed the issue, maybe was a corrupted win driver that later got fixed or a newer update needing something older? Anyways good luck.

Login or Join to leave a comment