BSOD every now and then

(Mescman) #1

I keep getting the blue screen of death every now and then because of Dirty Bomb. Never seen bsod on my current computer before this.

Happens in menus and sometimes after starting the game from desktop.

(Ardez1) #2

What is the BSOD error code?

(DanielFluffy) #3

It could definitely be due to you not having a good enough GPU (Graphics Card) for the game or not having the right drivers installed for your GPU. Try updating your drivers on your GPU. I doubt it’s due to Dirty Bomb alone.

(GeneralLee131) #4

BSOD is most often caused by a bad driver, hardware failure, improper overclocking or overheating. Knowing the error code it throws is paramount in diagnosing the problem. If it flashes the BSOD and resets the computer before you can jot down the 0x000 codes, you’ll need to disable Automatic Restart. To do this navigate to My Computer > System Properties > Advanced System Settings > Click the Advanced tab > Hit Settings button under Startup and Recovery > Untick Automatic Restart.

(Mescman) #5

igdkmd64.sys

I’m playing on a laptop. Might have something to do with integrated graphics? I have also the Geforce 765M but sometimes games prefer to use the integrated one, i’m not sure if this is the case to be honest… I get steady 100 fps. (could maybe get even more)

Again, only happens in menus, not even every day, but still regularly.

(GeneralLee131) #6

[quote=“Mescman;32695”]igdkmd64.sys

I’m playing on a laptop. Might have something to do with integrated graphics? I have also the Geforce 765M but sometimes games prefer to use the integrated one, i’m not sure if this is the case to be honest… I get steady 100 fps. (could maybe get even more)

Again, only happens in menus, not even every day, but still regularly.[/quote]

You’ve probably fixed the issue by now, but yeah thats definitely your Intergrated Intel graphics wreaking havoc. You can probably disable it or force it to use your Nvidia chip only in the BIOS. Its usually referred to as something like “iGPU”. Alternatively you can probably just remove its driver in Device Manager and be fine.

(Mescman) #7

Yeap the problem “fixed itself” over time, I don’t know what caused it, but it doesn’t happen anymore.