BSOD 7e, 3b, and a primarily while gaming

[zigzag3143]

Ran driver verifier and got this BSOD. I think this was the first time I've seen the BSOD message point specifically to a driver; it looked like an nvidia one, but my computer rebooted too quickly to get a good look at it.

Driver verified and Related to nvlddmkm.sys nVidia Display Driver.. Finally.

I would re-install the newest version of the driver using these instructions.


When upgrading your graphic driver you MUST remove all traces of the current driver. In order to do that we recommend using

Phyxion.net - Driver Sweeper

When it is removed then download and install the fresh copy.

 

[Crypt135]

Still getting BSOD's after the gfx card driver update. Should I try rolling back the driver to an earlier version (assuming the cause is still nvlddmkn.sys) or is there something else that you'd suggest?

 

[Crypt135]

So I rolled back my gfx card driver to an older (said to me more stable) version and it looked like that fixed the issue, but I got another BSOD today. However, I'm wondering if it is my headset causing issues again (I had to continue to use it since I could not replace it atm). Is this new dmp file conclusive?

 

[Crypt135]

Still getting the same 3b blue screen from the previous post

 

[GianniDPC]

Just to say but you have a driver dated from 2006: secdrv.SYS ( Macrovision SECURITY Driver) (This device driver is part of Macrovision's SafeDisc copy protection scheme)

I recommend to update that one

 

[zigzag3143]

Just to say but you have a driver dated from 2006: secdrv.SYS ( Macrovision SECURITY Driver) (This device driver is part of Macrovision's SafeDisc copy protection scheme)

I recommend to update that one

Just an FYI, that security driver is the newest version. There have been no newer versions.

 

[Crypt135]

Well after testing a couple different gfx card driver versions it looks like I'm getting a new BSOD (Bcc code 50, looked like it said win32k.sys is what caused it) with the latest beta one. Driver verifier was still pointing to the same nvidia driver earlier this week before the update, but I haven't tried it yet with this beta driver (I'm going to try and catch a BSOD with verifier running tomorrow).

Any new suggestions with this BSOD?


Edit: I should note that I was tabbed over to firefox at the time of this BSOD and was only sitting idle in the game I was playing, if that helps discern anything.

 

[Crypt135]

With verifier running I'm still getting the same BSOD from the above post.

I'm not really sure what to do at this point. The prior BSOD's pointed to the nvidia driver nvlddmkm.sys on two separate release drivers and the newest beta one I'm using is causing this new BSOD (pointing to win32k.sys on the message). I tested my gfx card with OCCT again just to see if it was failing but it passed the stress test and memory test with no errors.


Here are the three BSOD's that occurred while running verifier today (the two on start-up are the a's and the new one that's been happening is the 50).

 

[zigzag3143]

With verifier running I'm still getting the same BSOD from the above post.

I'm not really sure what to do at this point. The prior BSOD's pointed to the nvidia driver nvlddmkm.sys on two separate release drivers and the newest beta one I'm using is causing this new BSOD (pointing to win32k.sys on the message). I tested my gfx card with OCCT again just to see if it was failing but it passed the stress test and memory test with no errors.


Here are the three BSOD's that occurred while running verifier today (the two on start-up are the a's and the new one that's been happening is the 50).

Driver verified and Related to skfiltv.sys Audio Driver from Creative Technology Ltd.

I would remove to test and if necessary update to the newest possible driver.

 

[Crypt135]

I removed the audio driver but I'm still getting BSOD's.

 

[zigzag3143]

I removed the audio driver but I'm still getting BSOD's.

This one was Related to nvmf6264.sys MCP Networking Function Driver. from NVIDIA Corporation Yours from 2009. Update to newest available.

 

[Crypt135]

Another BSOD after updating the MCP Networking Function driver. I don't think I've seen 1e since before the clean install.

 

[zigzag3143]

Another BSOD after updating the MCP Networking Function driver. I don't think I've seen 1e since before the clean install.

Sorry but this one is inconclusive.


It is much easier to find patterns, etc, when there are more than one crash. We prefer you wait until you have at least two so that if one is corrupt the other probably wont be.

 

[Crypt135]

Just got another BSOD, same bug check code (1e).

 

[Crypt135]

Bump.

Is the above BSOD more conclusive?

 

[Crypt135]

I gave verifier another shot and despite getting a different BSOD while it's not enabled and after I tried updating my gfx card driver prior to this it's still blaming nvlddmkm.sys. The BSOD problems occur with each of the previous four release drivers from Nvidia and the two newest beta ones. I am clueless as to how all of these driver versions produce the same issue and yet my card isn't defective according to the OCCT stress and memory tests.

I don't really know what else I can do besides trying a different gfx card and seeing if the issue persists.

Maybe the dmp file points to something different than what the message indicated?

 

[zigzag3143]

I gave verifier another shot and despite getting a different BSOD while it's not enabled and after I tried updating my gfx card driver prior to this it's still blaming nvlddmkm.sys. The BSOD problems occur with each of the previous four release drivers from Nvidia and the two newest beta ones. I am clueless as to how all of these driver versions produce the same issue and yet my card isn't defective according to the OCCT stress and memory tests.

I don't really know what else I can do besides trying a different gfx card and seeing if the issue persists.

Maybe the dmp file points to something different than what the message indicated?

It is driver verified and related to your video driver. It can be heat, power, overclocking, etc.

At least you know where to concentrate your efforts

 

[Crypt135]

I was able to get a hold of another gfx card to test and see if that would have gotten rid of the problem but my computer still blue screened with it in. However, with verifier running it listed a different BSOD message and code. Blue Screen View says that hal.dll is what caused the crash, what should I try next?

 

[Crypt135]

Since changing out the card I've gotten three BSOD's so far and each one of them has been a different error message and code. The only thing I've changed for this test is the gfx card; it's another nvidia gtx480, same driver version and everything.

I've been trying to find a pattern but there doesn't seem to be one so far. Any suggestions?

 

[zigzag3143]

Since changing out the card I've gotten three BSOD's so far and each one of them has been a different error message and code. The only thing I've changed for this test is the gfx card; it's another nvidia gtx480, same driver version and everything.

I've been trying to find a pattern but there doesn't seem to be one so far. Any suggestions?

Driver verified and Related to nvlddmkm.sys nVidia Display Driver.


Are you by chance running a RAID, or overclocking? I noticed an nvraid.sys driver.