So after playing for 4 hours non stop i got BSOD

[ArchieTheGreat]

so i picked up a Weapon then my game suddenly BSOD is this a bug or what xD

[MagikarpMagi]

or what

[Tenebris]

Sounds like a PC problem. CTD are one thing, but BSOD sounds like a hardware/firmware issue

[✠ 尺Σplica ✠]

Download „BlueScreenView“, maybe you can find the error code and google it.

[z0mB1tCh2001]

prolly cuz you were playing 4 hours non stop

[Ryzilynt]

Check event viewer and find out what caused it.

Originally posted by TDW ✠ 尺Σplica ✠:

Download „BlueScreenView“, maybe you can find the error code and google it.

Don't do this.

[Dimwit Donald (very high IQ)]

The funny thing about BSOD these day is that windows (10) gathers information about the problem for 30 seconds or so, so that it can tell you vaguely what DLLs were last used before the crash with some helper tool. Incredibly helpful in finding the cause...

[Touch Me]

BSOD could be a software problem, so check your drivers, or a hardware issue like overheating due to overclocking your CPU. I would skip the drivers since you seem to have been playing for a good amount of time before blue screening. Next would be to know if your CPU is overclocked, and even if it isn't then you should try to have better air circulation on your rig or keep the area colder.

Edit: the guy above me has a point, so that can help if it happens again, but if not then try what I posted.

[Dimwit Donald (very high IQ)]

Originally posted by Exposed Entrepreneur:

BSOD could be a software problem, so check your drivers, or a hardware issue like overheating due to overclocking your CPU. I would skip the drivers since you seem to have been playing for a good amount of time before blue screening. Next would be to know if your CPU is overclocked, and even if it isn't then you should try to have better air circulation on your rig or keep the area colder.

Edit: the guy above me has a point, so that can help if it happens again, but if not then try what I posted.

The guy above you has been having recurring BSODs for months now and wasn't entirely serious about that gathered information being of any help. Knowing the name of some DLLs that may or may not have been related to the crashes didn't get him any further in finding the cause than googling the error code did. The guy is just wondering how this can be all that windows can tell you after 30 seconds of analysis.

[Ryzilynt]

Originally posted by Electronic Old Man:

Originally posted by Exposed Entrepreneur:

BSOD could be a software problem, so check your drivers, or a hardware issue like overheating due to overclocking your CPU. I would skip the drivers since you seem to have been playing for a good amount of time before blue screening. Next would be to know if your CPU is overclocked, and even if it isn't then you should try to have better air circulation on your rig or keep the area colder.

Edit: the guy above me has a point, so that can help if it happens again, but if not then try what I posted.

The guy above you has been having recurring BSODs for months now and wasn't entirely serious about that gathered information being of any help. Knowing the name of some DLLs that may or may not have been related to the crashes didn't get him any further in finding the cause than googling the error code did. The guy is just wondering how this can be all that windows can tell you after 10 seconds of analysis.

If you haven't already, re-seat your ram sticks, run SFC/scannow in elevated command prompt or power shell. Maybe run memory diagnostics if neither of those help.

[Dimwit Donald (very high IQ)]

Originally posted by Ryzilynt:

Originally posted by Electronic Old Man:

The guy above you has been having recurring BSODs for months now and wasn't entirely serious about that gathered information being of any help. Knowing the name of some DLLs that may or may not have been related to the crashes didn't get him any further in finding the cause than googling the error code did. The guy is just wondering how this can be all that windows can tell you after 10 seconds of analysis.

If you haven't already, re-seat your ram sticks, run SFC/scannow in elevated command prompt or power shell. Maybe run memory diagnostics if neither of those help.

Already did. From what I gathered, RAM issues seemed like the most likely cause. I have been removing, replacing, rearranging the sticks ever since. Sometimes it stops for weeks, but then it starts again sooner or later, once a day or so. Also running sfc /scannow on a regular basis now. Did chkdisk(?), too, just in case, and a couple of malware and virus scans...

[Ryzilynt]

Originally posted by Electronic Old Man:

Originally posted by Ryzilynt:

If you haven't already, re-seat your ram sticks, run SFC/scannow in elevated command prompt or power shell. Maybe run memory diagnostics if neither of those help.

Already did. From what I gathered, RAM issues seemed like the most likely cause. I have been removing, replacing, rearranging the sticks ever since. Sometimes it stops for weeks, but then it starts again sooner or later, once a day or so. Also running sfc /scannow on a regular basis now. Did chkdisk(?), too, just in case, and a couple of malware and virus scans...

Assuming you also did a clean install of windows.

Also , reset bios to defaults, consider flashing bios.

[Dimwit Donald (very high IQ)]

Originally posted by Ryzilynt:

Originally posted by Electronic Old Man:

Already did. From what I gathered, RAM issues seemed like the most likely cause. I have been removing, replacing, rearranging the sticks ever since. Sometimes it stops for weeks, but then it starts again sooner or later, once a day or so. Also running sfc /scannow on a regular basis now. Did chkdisk(?), too, just in case, and a couple of malware and virus scans...

Assuming you also did a clean install of windows.

Also , reset bios to defaults, consider flashing bios.

I can do without having my whole registry wiped again for nothing. If windows was the problem, there would hardly be long intervals without BSOD. My is guess is that there is some fawlty/unstable contact somewhere in the hardware and I wouldn't find it if I had a lifetime for it. It's always the same with PCs... A few years at most and they start randomy glitching and crashing for no apparent reason until they are ripe for the trashcan.

[CEPHY]

Originally posted by DORK !!!:

prolly cuz you were playing 4 hours non stop

Username checks out.

[Niliu]

Originally posted by Electronic Old Man:

Originally posted by Ryzilynt:

If you haven't already, re-seat your ram sticks, run SFC/scannow in elevated command prompt or power shell. Maybe run memory diagnostics if neither of those help.

Already did. From what I gathered, RAM issues seemed like the most likely cause. I have been removing, replacing, rearranging the sticks ever since. Sometimes it stops for weeks, but then it starts again sooner or later, once a day or so. Also running sfc /scannow on a regular basis now. Did chkdisk(?), too, just in case, and a couple of malware and virus scans...

Sounds like your RAM is incompatible with your board/proc

[Ishan451]

Originally posted by ArchieTheGreat:

so i picked up a Weapon then my game suddenly BSOD is this a bug or what xD

Ever since Windows 2000 applications can't crash your pc with a BSOD anymore. BSOD most likely means a hardware issue, possibly heat related but also could be PSU.Since the forums ain't filled with threads like this we can rule out a driver bug.