Question BSOD on fresh install


Apr 7, 2014
Ok so ive been battling this issue for a while. Using blue screen view to see the crash dump all 4 have ntoskrnl.exe in common but i have no idea how to fix it , google search isn't very enlightening either.
Ive done the usual memtest86 , update windows and drivers but even with minimal things installed i still get BSOD. Also tried driver verifier but i get stuck in a boot loop with DRIVER MANAGER IO VIOLATION blue screen resulting in installing windows again.
Will post the results of blue screen view below

EDIT Actual dump files below
Thanks in advance!
Last edited:


Hi, I ran the dump files through the debugger and got the following information:

File information:031519-7718-01.dmp (Mar 15 2019 - 14:37:13)
Probably caused by:win32kfull.sys (Process: upc.exe)
Uptime:0 Day(s), 1 Hour(s), 22 Min(s), and 07 Sec(s)

File information:031519-6875-01.dmp (Mar 15 2019 - 12:12:45)
Probably caused by:memory_corruption (Process: dirtrally2.exe)
Uptime:0 Day(s), 0 Hour(s), 10 Min(s), and 46 Sec(s)

File information:031519-6718-01.dmp (Mar 15 2019 - 13:14:34)
Probably caused by:ntkrnlmp.exe (Process: chrome.exe)
Uptime:0 Day(s), 1 Hour(s), 01 Min(s), and 15 Sec(s)

File information:031519-6437-01.dmp (Mar 15 2019 - 11:34:42)
Driver warnings:*** WARNING: Unable to verify timestamp for atikmdag.sys
Probably caused by:memory_corruption (Process: System)
Uptime:0 Day(s), 4 Hour(s), 18 Min(s), and 48 Sec(s)

The last crash was likely caused by your graphics card. You may want to cleanly re-install the drivers. Download DDU and the latest driver, boot into safe mode and run DDU to fully remove the old driver, reboot back into normal mode and install the latest driver. Full instructions can be found [here].

Possible Motherboard page:
It appears you have the latest BIOS already installed, ver 4207.


he appears to have the latest ATI drivers

  1. Mar 12 2019 - atikmdag.sys - ATI Radeon Kernel Mode driver
  2. Mar 12 2019 - atikmpag.sys - ATI video card driver
the ram you have installed - TEAMGROUP-UD4-3200 - doesn't show on the motherboard QVL listing, there is only so many which have 3200 speed tested and none from team group. That could well be cause of errors.

win32kful errors can also just be GPU drivers, maybe latest aren't as stable as they could be.


Apr 7, 2014
Thanks for your help guys unfortunately im still none the wiser.

Im pretty sure my ram is ok despite not being on the qvl list , because i done 24 hours of memtest with no errors also done this at 3400mhz overclock just in case and again no errors.

As for GPU drivers yes ive already done the DDU process along with multiple fresh installs of windows.
Would installing windows to another fresh drive give me the same results ? I ask because i must have reinstalled windows 4 times already from bootable usb media tool , with full drive format in-between.



Or can you test card in another PC and see if it works there? (building on what Drivinfast suggested)

normally failing GPU won't let you install the drivers as card stops being recognised as a GPU. Its not in 100% of cases though.

tempted to get you to run driver verifer... I did see you tried it before and it did its usual Boot loop thing... I can hopefully get us past that

Before running this,

1) search for “Create a restore point” and create a restore point

2) second step is create a WIn 10 installer but you probably have one already.

Try running driver verifer, just read the instructions carefully. It is part of win 10 designed to find misbehaving drivers. It will cause BSOD, that is its job since it tests drivers.

Once it bsod, upload the minidump file and we see what it shows us.

Steps 1 & 2 are just precautions as sometimes driver verifer can put you in a boot loop. If this happen, follow these steps to get out of it
change boot order so USB is first, hdd second
boot from installer
on screen after languages, choose repair this pc, not install.
choose troubleshoot
choose advanced
choose system restore and roll system back to restore point created in step 1. PC should boot normally.

Similar threads