nvlddmkm bsod when overclocking (also has other causes)

So for a little while now I've been trying to overclock this machine and I know people have done it so I tried it to no avail. Thats when I came to these forums and started asking around. Ive been getting bsod's every time I oc. Vista will fall on its face faster than Windows 7 ie I can have a higher stable overclock in Windows 7 (7022 32bit) than in my Home Premium 64bit Vista.

The following is the latest dump that I got from Vista.

Microsoft (R) Windows Debugger Version 6.11.0001.402 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\Mini022609-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

WARNING: Whitespace at end of path element
Symbol search path is: SRV*c:\symbols* http://msdl.microsoft.com/download/symbols

Executable search path is:
Windows Server 2008/Windows Vista Kernel Version 6001 (Service Pack 1) MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 6001.18145.amd64fre.vistasp1_gdr.080917-1612
Machine Name:
Kernel base = 0xfffff800`02a02000 PsLoadedModuleList = 0xfffff800`02bc7db0
Debug session time: Thu Feb 26 18:40:16.607 2009 (GMT-5)
System Uptime: 0 days 9:11:37.695
Loading Kernel Symbols
...............................................................
................................................................
...................................................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {6b0, 9, 0, fffffa6003a30696}

Unable to load image \SystemRoot\system32\DRIVERS\nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+227696 )

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

0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: 00000000000006b0, memory referenced
Arg2: 0000000000000009, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffffa6003a30696, address which referenced memory

Debugging Details:
------------------


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002c2b080
00000000000006b0

CURRENT_IRQL: 9

FAULTING_IP:
nvlddmkm+227696
fffffa60`03a30696 ?? ???

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0xD1

PROCESS_NAME: setfsb.exe

TRAP_FRAME: fffffa600ac8b8b0 -- (.trap 0xfffffa600ac8b8b0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=fffffa80071e6000
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffffa6003a30696 rsp=fffffa600ac8ba40 rbp=fffffa80071e6000
r8=0000000000000000 r9=0000000000000000 r10=fffffa600ac8ba40
r11=0000000000000001 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na pe nc
nvlddmkm+0x227696:
fffffa60`03a30696 ?? ???
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff80002a570ee to fffff80002a57350

STACK_TEXT:
fffffa60`0ac8b768 fffff800`02a570ee : 00000000`0000000a 00000000`000006b0 00000000`00000009 00000000`00000000 : nt!KeBugCheckEx
fffffa60`0ac8b770 fffff800`02a55fcb : 00000000`00000000 00000000`00000000 fffffa60`0ac8b900 00000000`00000000 : nt!KiBugCheckDispatch+0x6e
fffffa60`0ac8b8b0 fffffa60`03a30696 : fffffa80`0b16f000 00000000`00000000 fffffa80`071e6000 fffffa80`07462380 : nt!KiPageFault+0x20b
fffffa60`0ac8ba40 fffffa80`0b16f000 : 00000000`00000000 fffffa80`071e6000 fffffa80`07462380 fffffa80`07462380 : nvlddmkm+0x227696
fffffa60`0ac8ba48 00000000`00000000 : fffffa80`071e6000 fffffa80`07462380 fffffa80`07462380 fffffa60`03978925 : 0xfffffa80`0b16f000


STACK_COMMAND: kb

FOLLOWUP_IP:
nvlddmkm+227696
fffffa60`03a30696 ?? ???

SYMBOL_STACK_INDEX: 3

SYMBOL_NAME: nvlddmkm+227696

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME: nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4983485b

FAILURE_BUCKET_ID: X64_0xD1_nvlddmkm+227696

BUCKET_ID: X64_0xD1_nvlddmkm+227696

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

I have updated the gfx driver to the newest one and updated my bios and directx. After updating all this i seem to be getting a more consistant cause of the bsod where before it was a variety of things.
Please refer to my other posts here

I have also gathered all the error logs for second to most recent bsod. I also have the majority if not all of the dump files.

Any help in sorting this out would be much appreciated.
Thank you.

 

Funny, I artifact 20-30 MHz earlier on my core in Windows 7 than I did in XP Pro.

 

what re the specs of lappy your overclocking?
i think i got this error message too when i up'ed my oc too much
i use hwmonitor to check temps but the thing is it doesnt check temps for the gpu's memory modules
true enough when i lowered the memory clocks without touching my gpu.shader settings , my system stabilized
try it out...



cheers

 

I have a first generation asus g50vm-x1
t5750 at 2.0ghz built in overclocking feature gets it to 2.2ghz
nvidia 9700m gt graphics card
1 seagate 200gb hard drive
1 hitatchi 320gb hard drive
both are 7200rpm sata 3.0gbps
4 gb of 667mhz ddr2

How would I go about lowering the memory clocks?
(I cant do it in the bios because my bios has nearly no options)

Thanks

 

Well, you're getting that error because you're overclocking too high and your display driver is crashing. This is generally referred to as instability while overclocking.

If you're having this problem, you probably should not be overclocking. There are a few things you can do though...

• See this overclocking guide and make sure you follow the instructions carefully! The trick is finding the highest stable overclock.
• Try updating your graphics driver. See this thread: http://forum.notebookreview.com/showthread.php?t=258626
• Monitor your temps while you're playing games (I'm assuming that is why you're overclocking.. to get better gaming performance). See this thread: http://forum.notebookreview.com/showthread.php?t=81852

 

Thanks Crash I'll read those over and give them a shot. Oh, and I have already updated the graphics driver so I don't think its that.