BSOD During Gaming - BSOD's include dxgmms.sys, win32k.sys

EvilPengy · 23 Dec 2012

After all this I decided to re-install Windows. Got everything back up to scratch but then BSoD's have started to show again.

I've only had one atm, but there could be more. This time is was Bccode d1, something related to nvlddmkm.sys

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.256.1
Locale ID: 2057

Additional information about the problem:
BCCode: d1
BCP1: FFFFFFFFFFFFFFB0
BCP2: 0000000000000002
BCP3: 0000000000000000
BCP4: FFFFF880057EA74E
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1

Also using WhoCrashed program to analyse the mini dumps says that nvlddmkm.sys was responsible for the last two BSoD's. Any way to fix this? Could you rename it to nvlddmkm.old and then it would replace it with a new version of the file, if it's corrupted (I've done the same with win32k.sys in the past and it's worked)

EvilPengy · 24 Dec 2012

I also ran MemTest 86 too after re-installation of Windows, I ran it with both sticks in.

No errors, 9 Passes, left it going for 10 hours overnight

I will eventually get round to testing each stick on it's own but I don't think RAM is the cause of the current BSoD's. I'll update my BIOS and re-install the graphics driver in safe mode for the time being. I'm using the latest WHQL drivers from Nvidia btw (310.70) I had another BSoD earlier which relates to dxgmms1.sys too

All these BSoD's seem to happen only when I'm playing games too.

Arc · 24 Dec 2012

Download and install Driver Fusion.
Reboot the computer in Advanced Boot Options, safe mode. Search Driver Fusion in your start menu, and remove all components of your nVidia display driver.
Boot normally now. Apply the latest version of nVidia display driver.
You may download it directly, from our forum link Latest NVIDIA ForceWare Video Drivers Windows 7; or you may opt for the Option 2 of Drivers- Download NVIDIA Drivers for “Automatically find drivers for my NVIDIA products” (it requires java installed).

May be it is caused by the beta driver you are using right now.

EvilPengy · 24 Dec 2012

I've done all that, thats my usual routine for installing new drivers. These aren't BETA drivers neither, 310.70 is a WHQL driver so it's non-BETA. It's supposed to be the most recent and stable one

Just got another BSoD in Team Fortress 2, related to dxgmms1.sys, maybe DirectX has been corrupted? Seems to be a common sight does 'dxgmms1.sys', same goes for the nvidia one, although the BSoD's I've had since re-installing the Nvidia Drivers have all been dxgmms1.sys

I'll get the dump files up in a min

Maybe I should go back to the most recent WHQL drivers other than 310.70, I think that's 306.XX series

Arc · 24 Dec 2012

Good decision.

Download and install Driver Fusion.
Reboot the computer in Advanced Boot Options, safe mode. Search Driver Fusion in your start menu, and remove all components of your nVidia display driver.
Boot normally now. Go to Drivers - Download NVIDIA Drivers, Drivers > Beta and Legacy; search there with your cards particulars for GeForce 306.23 Driver, dated 13.9.2012 and install it.

This one is the most stable one as I have experienced.

EvilPengy · 24 Dec 2012

Still getting BSoD's even after rolling back to 306.XX drivers

This time win32k.sys is the problem.

Getting really frustrated with this issue now!

Arc · 24 Dec 2012

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffff1e00929b9ef, 1, fffff9600026f4e0, 7}


Could not read faulting driver name
Probably caused by : dxgkrnl.sys ( dxgkrnl!DxgkGetPresentHistory+f6 )

Followup: MachineOwner
---------

Graphics related crash, but not the nvidia display driver. Stress test the Graphics Card using Furmark.
Video Card - Stress Test with Furmark

Report the temperatures .... post a screenshot of Speccy summery tab.

EvilPengy · 24 Dec 2012

Ok I'm talking on here from my laptop as I've decided to run MemTest on one stick at a time.

On this current stick I've got 2 errors, so immediately the RAM is an issue, don't know if it's causing the recent BSoD's tho. I'm on Pass 2 and now I've got 26 errors on this current stick.

How long should I leave each stick in for and when I put the second stick in shall I try the same slot or another 1?

(Also in response to your last post, my GPU temps aren't bad. I have EVGA Precison X running when playing games and it displays temp on my Logitech G15. I average between 50-70c in-game, typically lingers around the 60-65c mark, so it's not that bad)

EvilPengy · 24 Dec 2012

Ok I left MemTest at 5 passes, it'd ran for 2 and half hours with 42 errors, so that stick is faulty

I'll try the other stick shortly

Arc · 25 Dec 2012

Run memtest for both the modules, in both the slots.

No code has to be inserted here. In such a format. Where S1 an S2 are the DIMM slots and M1 and M2 are the memory modules.

In this way you will be able to discriminate between a RAM issue or a motherboard issue. If the test reports are wrong for either module in a particular slot, then it is the slot of the motherboard that is faulty.
In the reverse situation, if a stick givs errors i either slot, it is just that stick.