BSoD from nvdldmkm.sys

angelfreeze · 30 May 2010

Hi.
any help will be appreciated. somehow nvdldmkm.sys keeps poping up on my crashes along wif some win32k.sys on windows 7. So i thought maybe somehow i installed the 32bit vision of my nvidia driver(my gfx card is gtx 275). Then i uninstalled that and redownload and made sure it was the 64bit verison(197.45). With no luck it kept on crashing

. The crashes generally occur when i'm gaming but it does sometime crashes when i'm in idle just running a video file.

Thank you in advance

zigzag3143 · 30 May 2010

angelfreeze said:

Hi.
any help will be appreciated. somehow nvdldmkm.sys keeps poping up on my crashes along wif some win32k.sys on windows 7. So i thought maybe somehow i installed the 32bit vision of my nvidia driver(my gfx card is gtx 275). Then i uninstalled that and redownload and made sure it was the 64bit verison(197.45). With no luck it kept on crashing

. The crashes generally occur when i'm gaming but it does sometime crashes when i'm in idle just running a video file.

Thank you in advance

Nine dumps doing them now back in a bit

Jonathan_King · 30 May 2010

It may be bad RAM or other hardware. Several different bugchecks.

Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder. Boot from the CD, and leave it running for at least 5 passes.

Code:


BugCheck 50, {fffffa7ff67556c9, 1, fffff96000276e57, 7}
Probably caused by : win32k.sys ( win32k!SelectPaletteWorker+17 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
BugCheck 50, {fffff960185acd49, 1, fffff960000c4144, 2}
Probably caused by : win32k.sys ( win32k!SURFMEM::bCreateDIB+530 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
BugCheck D1, {1, 2, 1, fffff88010188b4d}
Probably caused by : nvlddmkm.sys ( nvlddmkm+380b4d )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
BugCheck 3B, {c0000005, fffff9600013aa3a, fffff88008fd21d0, 0}
Probably caused by : win32k.sys ( win32k!ValidateHwnd+7a )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
BugCheck D1, {ffffffffffffff83, 2, 1, fffff8801045b25e}
Probably caused by : nvlddmkm.sys ( nvlddmkm+5f025e )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
BugCheck 3B, {c0000005, fffff96000135847, fffff8800951fe40, 0}
Probably caused by : win32k.sys ( win32k!HMAssignmentLock+8b )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
BugCheck 1E, {ffffffffc000001d, fffff88005236c47, 2, 0}
Probably caused by : mouhid.sys ( mouhid!MouHid_ReadComplete+66b )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
BugCheck 3D, {fffff8800824d0b0, 0, 0, fffff88010065640}
Probably caused by : nvlddmkm.sys ( nvlddmkm+19c640 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
BugCheck D1, {0, 2, 0, fffff880100f90cd}
Probably caused by : nvlddmkm.sys ( nvlddmkm+2d50cd )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨

angelfreeze · 30 May 2010

thanks for the quick response.
i'm burning the disc now be back soon

angelfreeze · 30 May 2010

Currently on my 3rd pass and I already have 112 errors, first one had 80. I'll run to 5 but is there a report thing i need to save?

Jonathan_King · 30 May 2010

No, no report is created.

Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot. Test the sticks individually, and if you find a good one, test it in all slots.

angelfreeze · 31 May 2010

my errors sums up to around 280ish and thanks for the solution but just to clarify am i suppose to pull out my rams and test 2 of them each time ? i have 4x1gb rams on a p5k MB

Jonathan_King · 31 May 2010

Test them one at a time. Test stick #1 in slot #1. If it passes, you know both the slot and stick are good. Then test stick #2 in slot #1, stick #1 in slot #2, etc.

angelfreeze · 01 Jun 2010

tried pulling all the rams out and testing each ram on memtest. i did it by pulling all the rams out, tested everyone on slot 1 and use 1 passed ram to test all 4 slots. it all passed for some reason. so that means there no problem with my rams or mb ?

Jonathan_King · 02 Jun 2010

It probably means that your RAM is not compatible with each other. I will send a message to a couple of our RAM experts, but as they live in another time zone, please be patient.