BSOD while doing nothing in particular

**axe0** · 30 Nov 2016

FYI 32gb of ram is entirely too much if you ever want to check it for errors.

We're aware of that, 8GB takes about a single night to finish (8-10h). 16GB could take up to 1 or 2 days, 32GB takes at least a few days.

ba12348 · 01 Dec 2016

Good(ish) news, I've managed to produce another BSOD. Rather interestingly it did NOT produce a dump file despite saying it was. I was sitting there when it happened and the check string was "driver IRQL not less or equal" New log collection file attached, not that I think it's any different from the last.

**axe0** · 02 Dec 2016

Please remove some files to increase the free space to at least 10-15%.
Every partition needs at least 10-15% free space so Windows can do its thing in the background.

Warning

Less free space could cause BSOD's

ba12348 · 02 Dec 2016

You mean on the C: drive? I've been kicking myself for doing that ever since I built this computer, next one will be a full size SSD, who knows maybe by then they won't cost your first born child. I'll clean it up when I get home tonight and report back if there are more issues.

ba12348 · 15 Dec 2016

Solution found: Old network driver. My particular motherboard requires a 3rd party network driver, without it installed there is no connection at all. So, I installed the driver that came on the disk with the board. After it crashed yet again I dug a little deeper and found that netio.exe was causing the BSOD, according to the dump file. Updating to the most recent network driver, from Gigabyte's website, seems to have fixed the issue. Thank you for your help Axe!