New System, Having Issues

CaptainK24 · Dec 5, 2010

I recently upgraded my entire system and I am having some trouble with it.

When playing PC games it randomly crashes to the desktop. This happens with a few different games, and sometimes after a few minutes, other times after an hour or two. I own a GeForce GT 430. I have also tried with a GeForce 8800GT (my original graphics card).

I attempted to download the nTune application to test it out, but when I run the Nvidia Monitor application I get a blue screen error: System_Service_Exception. Another blue screen error I have gotten recently is PFN_List_Corrupt.

I have attached my DxDiag file with all the information on my system to help, as I am not sure if it is a graphics card, motherboard, operating system, or memory problem, or simply a driver issue of some sort. Any support you can provide will be greatly appreciated.

Hopalong X · Dec 5, 2010

Create this report and post per instructions.
http://www.sevenforums.com/crashes-debugging/96879-blue-screen-death-bsod-posting-instructions.html

We have a very good BSOD team of specialists but they will need the BSOD report to help.
When the report is posted you will have assistance as soon as possible.

Mike

CaptainK24 · Dec 5, 2010

Zip file attached based on the instructions. Hope this helps! Please let me know if any other information is needed

CaptainK24 · Dec 5, 2010

Here is the event viewer log file, shows all the errors I have had. Not sure if that is included with any of the files in that zip

CaptainK24 · Dec 5, 2010

Not sure if there might actually be a sound driver issue, between the Nvidia drivers and the built in Realtex on my motherboard? If so, which do I go with??

Hopalong X · Dec 5, 2010

Nvidia sound works off the GPU/graphics card. Usually it only uses this if your running HDMI or similar to TV and such. The Realtek is the mother board sound for your front and rear audio connections.

Someone should get to you. Not too many of the BSOD crew on line today. This is all volunteer.

Hang in there. If it gets too late check back tomorrow we have people come and go 24/7. Once they look it over they will post what to check, update etc.
Mike

CaptainK24 · Dec 5, 2010

Sounds good, thanks for all your help so far!

CarlTR6 · Dec 5, 2010

Hi CaptainK and welcome to the forum. I looked at your four most recent dumps. Three of the four directly blame the driver, nvoclk64.sys, nVidia System Utility Driver, which is very outdated. It is dated 2007. This utility is either nTune or NVIDIA System Tools. It is an XP utility. Uninstall the utility. If you cannot uninstall the utility, first create a restore point; then navigate to C:\Windows\, find nvoclk64.sys and rename it from .sys to .old. Reboot and the driver will not load. This will break the utility. Run your system and see if this fixes the problem.

If you are overclocking anything, please return to default values.

Code:

Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02c0b000 PsLoadedModuleList = 0xfffff800`02e48e50
Debug session time: Sun Dec  5 00:18:47.864 2010 (GMT-5)
System Uptime: 0 days 2:01:01.926
Loading Kernel Symbols
...............................................................
................................................................
............
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffff8a1a9406f60, 1, fffff88003f56421, 5}


Could not read faulting driver name
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_DEVICE::RemoveCommitment+31 )

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

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

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced.  This cannot be protected by try-except,
it must be protected by a Probe.  Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: fffff8a1a9406f60, memory referenced.
Arg2: 0000000000000001, value 0 = read operation, 1 = write operation.
Arg3: fffff88003f56421, If non-zero, the instruction address which referenced the bad memory
    address.
Arg4: 0000000000000005, (reserved)

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


Could not read faulting driver name

WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002eb30e0
 fffff8a1a9406f60 

FAULTING_IP: 
dxgmms1!VIDMM_DEVICE::RemoveCommitment+31
fffff880`03f56421 ff0b            dec     dword ptr [rbx]

MM_INTERNAL_CODE:  5

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x50

PROCESS_NAME:  System

CURRENT_IRQL:  0

TRAP_FRAME:  fffff88002ec46d0 -- (.trap 0xfffff88002ec46d0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000008aa5738 rbx=0000000000000000 rcx=fffff8a00767a7a0
rdx=fffffa800682d1c0 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88003f56421 rsp=fffff88002ec4868 rbp=0000000000000000
 r8=fffffa800682d170  r9=fffff8a00767a7a0 r10=fffff8a0089c4dd0
r11=fffff8a009e4f630 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
dxgmms1!VIDMM_DEVICE::RemoveCommitment+0x31:
fffff880`03f56421 ff0b            dec     dword ptr [rbx] ds:00000000`00000000=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002cfa8c1 to fffff80002c7b740

STACK_TEXT:  
fffff880`02ec4568 fffff800`02cfa8c1 : 00000000`00000050 fffff8a1`a9406f60 00000000`00000001 fffff880`02ec46d0 : nt!KeBugCheckEx
fffff880`02ec4570 fffff800`02c7982e : 00000000`00000001 fffff8a1`a9406f60 00000000`000cb100 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x40e8b
fffff880`02ec46d0 fffff880`03f56421 : fffff880`03f4f5c0 fffffa80`08a76000 fffff8a0`089c4dd0 fffffa80`08894770 : nt!KiPageFault+0x16e
fffff880`02ec4868 fffff880`03f4f5c0 : fffffa80`08a76000 fffff8a0`089c4dd0 fffffa80`08894770 fffffa80`088948f0 : dxgmms1!VIDMM_DEVICE::RemoveCommitment+0x31
fffff880`02ec4870 fffff880`03f51ff3 : fffff8a0`098aaad8 fffff8a0`089c4ed8 fffff8a0`098aaad8 fffff8a0`089c4ed8 : dxgmms1!VIDMM_GLOBAL::NotifyAllocationEviction+0x38
fffff880`02ec48a0 fffff880`03f4eee4 : fffff8a0`089c4dd0 fffffa80`07250020 fffffa80`08a76000 fffffa80`08a66820 : dxgmms1!VIDMM_GLOBAL::EvictAllocation+0x67
fffff880`02ec48e0 fffff880`03f4bed3 : 00000000`00000000 fffffa80`072f9008 00000000`00000104 00000000`00000000 : dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+0x218
fffff880`02ec4910 fffff880`03f6665d : 00000000`00000000 fffff8a0`0767a7a0 fffffa80`00000000 fffffa80`077182f0 : dxgmms1!VIDMM_GLOBAL::PrepareDmaBuffer+0x43f
fffff880`02ec4ae0 fffff880`03f66398 : fffff800`00b96080 fffff880`03f65d00 fffffa80`00000000 fffffa80`00000000 : dxgmms1!VidSchiSubmitRenderCommand+0x241
fffff880`02ec4cd0 fffff880`03f65e96 : 00000000`00000000 fffffa80`077c2640 00000000`00000080 fffffa80`08821010 : dxgmms1!VidSchiSubmitQueueCommand+0x50
fffff880`02ec4d00 fffff800`02f1fc06 : 00000000`030a0b26 fffffa80`08894770 fffffa80`066df9e0 fffffa80`08894770 : dxgmms1!VidSchiWorkerThread+0xd6
fffff880`02ec4d40 fffff800`02c59c26 : fffff800`02df5e80 fffffa80`08894770 fffff800`02e03c40 fffff880`0122da90 : nt!PspSystemThreadStartup+0x5a
fffff880`02ec4d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_IP: 
dxgmms1!VIDMM_DEVICE::RemoveCommitment+31
fffff880`03f56421 ff0b            dec     dword ptr [rbx]

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  dxgmms1!VIDMM_DEVICE::RemoveCommitment+31

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: dxgmms1

IMAGE_NAME:  dxgmms1.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc578

FAILURE_BUCKET_ID:  X64_0x50_dxgmms1!VIDMM_DEVICE::RemoveCommitment+31

BUCKET_ID:  X64_0x50_dxgmms1!VIDMM_DEVICE::RemoveCommitment+31

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

Debug session time: Sun Dec  5 15:27:13.805 2010 (GMT-5)
System Uptime: 0 days 0:28:16.257
Loading Kernel Symbols
...............................................................
................................................................
..............
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000096, fffff880074050dc, fffff88007fbef50, 0}

Probably caused by : nvoclk64.sys ( nvoclk64+50dc )

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

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

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000096, Exception code that caused the bugcheck
Arg2: fffff880074050dc, Address of the exception record for the exception that caused the bugcheck
Arg3: fffff88007fbef50, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000096 - {EXCEPTION}  Privileged instruction.

FAULTING_IP: 
nvoclk64+50dc
fffff880`074050dc 0f32            rdmsr

CONTEXT:  fffff88007fbef50 -- (.cxr 0xfffff88007fbef50)
rax=fffff880074050d7 rbx=0000000000000000 rcx=000000000000002c
rdx=fffffa8006b4e320 rsi=fffffa8008d78b20 rdi=fffffa8006b4e320
rip=fffff880074050dc rsp=fffff88007fbf920 rbp=fffff88007fbfca0
 r8=fffffa8006b4e3f0  r9=000000009c40a484 r10=0000000000000060
r11=fffffa8006b19840 r12=fffffa8006b19840 r13=fffffa8006b4e320
r14=0000000000000001 r15=fffffa8006a56060
iopl=0         nv up ei ng nz ac po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010296
nvoclk64+0x50dc:
fffff880`074050dc 0f32            rdmsr
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x3B

PROCESS_NAME:  NVMonitor.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff880074050dc

STACK_TEXT:  
fffff880`07fbf920 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nvoclk64+0x50dc


FOLLOWUP_IP: 
nvoclk64+50dc
fffff880`074050dc 0f32            rdmsr

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nvoclk64+50dc

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvoclk64

IMAGE_NAME:  nvoclk64.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  468aa46f

STACK_COMMAND:  .cxr 0xfffff88007fbef50 ; kb

FAILURE_BUCKET_ID:  X64_0x3B_nvoclk64+50dc

BUCKET_ID:  X64_0x3B_nvoclk64+50dc

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

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

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000096, Exception code that caused the bugcheck
Arg2: fffff880074050dc, Address of the exception record for the exception that caused the bugcheck
Arg3: fffff88007fbef50, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000096 - {EXCEPTION}  Privileged instruction.

FAULTING_IP: 
nvoclk64+50dc
fffff880`074050dc 0f32            rdmsr

CONTEXT:  fffff88007fbef50 -- (.cxr 0xfffff88007fbef50)
rax=fffff880074050d7 rbx=0000000000000000 rcx=000000000000002c
rdx=fffffa8006b4e320 rsi=fffffa8008d78b20 rdi=fffffa8006b4e320
rip=fffff880074050dc rsp=fffff88007fbf920 rbp=fffff88007fbfca0
 r8=fffffa8006b4e3f0  r9=000000009c40a484 r10=0000000000000060
r11=fffffa8006b19840 r12=fffffa8006b19840 r13=fffffa8006b4e320
r14=0000000000000001 r15=fffffa8006a56060
iopl=0         nv up ei ng nz ac po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010296
nvoclk64+0x50dc:
fffff880`074050dc 0f32            rdmsr
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x3B

PROCESS_NAME:  NVMonitor.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff880074050dc

STACK_TEXT:  
fffff880`07fbf920 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nvoclk64+0x50dc


FOLLOWUP_IP: 
nvoclk64+50dc
fffff880`074050dc 0f32            rdmsr

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nvoclk64+50dc

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvoclk64

IMAGE_NAME:  nvoclk64.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  468aa46f

STACK_COMMAND:  .cxr 0xfffff88007fbef50 ; kb

FAILURE_BUCKET_ID:  X64_0x3B_nvoclk64+50dc

BUCKET_ID:  X64_0x3B_nvoclk64+50dc

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

0: kd> lmtsmn
start             end                 module name
fffff880`04352000 fffff880`04390000   1394ohci 1394ohci.sys Mon Jul 13 20:07:12 2009 (4A5BCC30)
fffff880`00f86000 fffff880`00fdd000   ACPI     ACPI.sys     Mon Jul 13 19:19:34 2009 (4A5BC106)
fffff880`02c8e000 fffff880`02d18000   afd      afd.sys      Mon Jul 13 19:21:40 2009 (4A5BC184)
fffff880`043ac000 fffff880`043c2000   AgileVpn AgileVpn.sys Mon Jul 13 20:10:24 2009 (4A5BCCF0)
fffff880`00dda000 fffff880`00de5000   amdxata  amdxata.sys  Tue May 19 13:56:59 2009 (4A12F2EB)
fffff880`02de7000 fffff880`02def000   AppleCharger AppleCharger.sys Mon Apr 26 23:54:05 2010 (4BD65FDD)
fffff880`00cda000 fffff880`00ce3000   atapi    atapi.sys    Mon Jul 13 19:19:47 2009 (4A5BC113)
fffff880`00db0000 fffff880`00dda000   ataport  ataport.SYS  Mon Jul 13 19:19:52 2009 (4A5BC118)
fffff880`019f2000 fffff880`019f9000   Beep     Beep.SYS     Mon Jul 13 20:00:13 2009 (4A5BCA8D)
fffff880`02c77000 fffff880`02c88000   blbdrive blbdrive.sys Mon Jul 13 19:35:59 2009 (4A5BC4DF)
fffff880`08f5e000 fffff880`08f7c000   bowser   bowser.sys   Mon Jul 13 19:23:50 2009 (4A5BC206)
fffff960`006d0000 fffff960`006f7000   cdd      cdd.dll      Wed May 19 15:48:26 2010 (4BF4408A)
fffff880`01992000 fffff880`019bc000   cdrom    cdrom.sys    Mon Jul 13 19:19:54 2009 (4A5BC11A)
fffff880`00c00000 fffff880`00cc0000   CI       CI.dll       Mon Jul 13 21:32:13 2009 (4A5BE01D)
fffff880`0192c000 fffff880`0195c000   CLASSPNP CLASSPNP.SYS Mon Jul 13 19:19:58 2009 (4A5BC11E)
fffff880`00d52000 fffff880`00db0000   CLFS     CLFS.SYS     Mon Jul 13 19:19:57 2009 (4A5BC11D)
fffff880`010e7000 fffff880`0115a000   cng      cng.sys      Mon Jul 13 19:49:40 2009 (4A5BC814)
fffff880`0439c000 fffff880`043ac000   CompositeBus CompositeBus.sys Mon Jul 13 20:00:33 2009 (4A5BCAA1)
fffff880`08e71000 fffff880`08e7a000   cpuz134_x64 cpuz134_x64.sys Fri Jul 09 07:16:58 2010 (4C37052A)
fffff880`08e7a000 fffff880`08e83000   cpuz135_x64 cpuz135_x64.sys Tue Nov 09 08:33:36 2010 (4CD94DB0)
fffff880`07489000 fffff880`07497000   crashdmp crashdmp.sys Mon Jul 13 20:01:01 2009 (4A5BCABD)
fffff880`018a5000 fffff880`018c3000   dfsc     dfsc.sys     Mon Jul 13 19:23:44 2009 (4A5BC200)
fffff880`02c68000 fffff880`02c77000   discache discache.sys Mon Jul 13 19:37:18 2009 (4A5BC52E)
fffff880`01916000 fffff880`0192c000   disk     disk.sys     Mon Jul 13 19:19:57 2009 (4A5BC11D)
fffff880`05b98000 fffff880`05bba000   drmk     drmk.sys     Mon Jul 13 21:01:25 2009 (4A5BD8E5)
fffff880`074c0000 fffff880`074c9000   dump_atapi dump_atapi.sys Mon Jul 13 19:19:47 2009 (4A5BC113)
fffff880`074b4000 fffff880`074c0000   dump_dumpata dump_dumpata.sys Mon Jul 13 19:19:47 2009 (4A5BC113)
fffff880`074c9000 fffff880`074dc000   dump_dumpfve dump_dumpfve.sys Mon Jul 13 19:21:51 2009 (4A5BC18F)
fffff880`0747d000 fffff880`07489000   Dxapi    Dxapi.sys    Mon Jul 13 19:38:28 2009 (4A5BC574)
fffff880`040f3000 fffff880`041e7000   dxgkrnl  dxgkrnl.sys  Thu Oct 01 21:00:14 2009 (4AC5509E)
fffff880`04000000 fffff880`04046000   dxgmms1  dxgmms1.sys  Mon Jul 13 19:38:32 2009 (4A5BC578)
fffff880`01075000 fffff880`01089000   fileinfo fileinfo.sys Mon Jul 13 19:34:25 2009 (4A5BC481)
fffff880`01029000 fffff880`01075000   fltmgr   fltmgr.sys   Mon Jul 13 19:19:59 2009 (4A5BC11F)
fffff880`013d0000 fffff880`013da000   Fs_Rec   Fs_Rec.sys   Mon Jul 13 19:19:45 2009 (4A5BC111)
fffff880`018dc000 fffff880`01916000   fvevol   fvevol.sys   Fri Sep 25 22:34:26 2009 (4ABD7DB2)
fffff880`0142b000 fffff880`01475000   fwpkclnt fwpkclnt.sys Mon Jul 13 19:21:08 2009 (4A5BC164)
fffff800`031ef000 fffff800`03238000   hal      hal.dll      Mon Jul 13 21:27:36 2009 (4A5BDF08)
fffff880`04046000 fffff880`0406a000   HDAudBus HDAudBus.sys Mon Jul 13 20:06:13 2009 (4A5BCBF5)
fffff880`0406a000 fffff880`0407b000   HECIx64  HECIx64.sys  Thu Sep 17 15:54:16 2009 (4AB293E8)
fffff880`074ea000 fffff880`07503000   HIDCLASS HIDCLASS.SYS Mon Jul 13 20:06:21 2009 (4A5BCBFD)
fffff880`07503000 fffff880`0750b080   HIDPARSE HIDPARSE.SYS Mon Jul 13 20:06:17 2009 (4A5BCBF9)
fffff880`074dc000 fffff880`074ea000   hidusb   hidusb.sys   Mon Jul 13 20:06:22 2009 (4A5BCBFE)
fffff880`08e96000 fffff880`08f5e000   HTTP     HTTP.sys     Mon Jul 13 19:22:16 2009 (4A5BC1A8)
fffff880`0148f000 fffff880`01498000   hwpolicy hwpolicy.sys Mon Jul 13 19:19:22 2009 (4A5BC0FA)
fffff880`018c3000 fffff880`018d9000   intelppm intelppm.sys Mon Jul 13 19:19:25 2009 (4A5BC0FD)
fffff880`04285000 fffff880`04294000   kbdclass kbdclass.sys Mon Jul 13 19:19:50 2009 (4A5BC116)
fffff880`0750c000 fffff880`0751a000   kbdhid   kbdhid.sys   Mon Jul 13 20:00:20 2009 (4A5BCA94)
fffff800`00bb7000 fffff800`00bc1000   kdcom    kdcom.dll    Mon Jul 13 21:31:07 2009 (4A5BDFDB)
fffff880`042a5000 fffff880`042e8000   ks       ks.sys       Wed Mar 03 23:32:25 2010 (4B8F37D9)
fffff880`013a5000 fffff880`013bf000   ksecdd   ksecdd.sys   Mon Jul 13 19:20:54 2009 (4A5BC156)
fffff880`01400000 fffff880`0142b000   ksecpkg  ksecpkg.sys  Fri Dec 11 01:03:32 2009 (4B21E0B4)
fffff880`05bba000 fffff880`05bbf200   ksthunk  ksthunk.sys  Mon Jul 13 20:00:19 2009 (4A5BCA93)
fffff880`07558000 fffff880`0756d000   lltdio   lltdio.sys   Mon Jul 13 20:08:50 2009 (4A5BCC92)
fffff880`07535000 fffff880`07558000   luafv    luafv.sys    Mon Jul 13 19:26:13 2009 (4A5BC295)
fffff880`00cfa000 fffff880`00d3e000   mcupdate_GenuineIntel mcupdate_GenuineIntel.dll Mon Jul 13 21:29:10 2009 (4A5BDF66)
fffff880`07527000 fffff880`07535000   monitor  monitor.sys  Mon Jul 13 19:38:52 2009 (4A5BC58C)
fffff880`04294000 fffff880`042a3000   mouclass mouclass.sys Mon Jul 13 19:19:50 2009 (4A5BC116)
fffff880`0751a000 fffff880`07527000   mouhid   mouhid.sys   Mon Jul 13 20:00:20 2009 (4A5BCA94)
fffff880`00cc0000 fffff880`00cda000   mountmgr mountmgr.sys Mon Jul 13 19:19:54 2009 (4A5BC11A)
fffff880`019bc000 fffff880`019e9000   MpFilter MpFilter.sys Sat Mar 20 01:58:08 2010 (4BA463F0)
fffff880`09319000 fffff880`09329000   MpNWMon  MpNWMon.sys  Sat Mar 20 01:58:00 2010 (4BA463E8)
fffff880`08f7c000 fffff880`08f94000   mpsdrv   mpsdrv.sys   Mon Jul 13 20:08:25 2009 (4A5BCC79)
fffff880`08f94000 fffff880`08fc1000   mrxsmb   mrxsmb.sys   Sat Feb 27 02:52:19 2010 (4B88CF33)
fffff880`08e00000 fffff880`08e4e000   mrxsmb10 mrxsmb10.sys Sat Feb 27 02:52:28 2010 (4B88CF3C)
fffff880`08e4e000 fffff880`08e71000   mrxsmb20 mrxsmb20.sys Sat Feb 27 02:52:26 2010 (4B88CF3A)
fffff880`0185e000 fffff880`01869000   Msfs     Msfs.SYS     Mon Jul 13 19:19:47 2009 (4A5BC113)
fffff880`00fe6000 fffff880`00ff0000   msisadrv msisadrv.sys Mon Jul 13 19:19:26 2009 (4A5BC0FE)
fffff880`01089000 fffff880`010e7000   msrpc    msrpc.sys    Mon Jul 13 19:21:32 2009 (4A5BC17C)
fffff880`02c5d000 fffff880`02c68000   mssmbios mssmbios.sys Mon Jul 13 19:31:10 2009 (4A5BC3BE)
fffff880`0147d000 fffff880`0148f000   mup      mup.sys      Mon Jul 13 19:23:45 2009 (4A5BC201)
fffff880`014a0000 fffff880`01592000   ndis     ndis.sys     Mon Jul 13 19:21:40 2009 (4A5BC184)
fffff880`043e6000 fffff880`043f2000   ndistapi ndistapi.sys Mon Jul 13 20:10:00 2009 (4A5BCCD8)
fffff880`04200000 fffff880`0422f000   ndiswan  ndiswan.sys  Mon Jul 13 20:10:11 2009 (4A5BCCE3)
fffff880`05b1d000 fffff880`05b32000   NDProxy  NDProxy.SYS  Mon Jul 13 20:10:05 2009 (4A5BCCDD)
fffff880`02d8c000 fffff880`02d9b000   netbios  netbios.sys  Mon Jul 13 20:09:26 2009 (4A5BCCB6)
fffff880`02d18000 fffff880`02d5d000   netbt    netbt.sys    Mon Jul 13 19:21:28 2009 (4A5BC178)
fffff880`01592000 fffff880`015f2000   NETIO    NETIO.SYS    Mon Jul 13 19:21:46 2009 (4A5BC18A)
fffff880`01869000 fffff880`0187a000   Npfs     Npfs.SYS     Mon Jul 13 19:19:48 2009 (4A5BC114)
fffff880`02c51000 fffff880`02c5d000   nsiproxy nsiproxy.sys Mon Jul 13 19:21:02 2009 (4A5BC15E)
fffff800`02c13000 fffff800`031ef000   nt       ntkrnlmp.exe Sat Jun 19 00:16:41 2010 (4C1C44A9)
fffff880`01202000 fffff880`013a5000   Ntfs     Ntfs.sys     Mon Jul 13 19:20:47 2009 (4A5BC14F)
fffff880`019e9000 fffff880`019f2000   Null     Null.SYS     Mon Jul 13 19:19:37 2009 (4A5BC109)
fffff880`053e8000 fffff880`053e9180   nvBridge nvBridge.kmd Sat Oct 16 13:06:16 2010 (4CB9DB88)
fffff880`05b32000 fffff880`05b5b000   nvhda64v nvhda64v.sys Tue Sep 07 16:08:40 2010 (4C869BC8)
fffff880`0480e000 fffff880`053e7a80   nvlddmkm nvlddmkm.sys Sat Oct 16 13:12:46 2010 (4CB9DD0E)
fffff880`09310000 fffff880`09319000   nvoclk64 nvoclk64.sys Tue Jul 03 15:33:03 2007 (468AA46F)
fffff880`02d66000 fffff880`02d8c000   pacer    pacer.sys    Mon Jul 13 20:09:41 2009 (4A5BCCC5)
fffff880`00e40000 fffff880`00e55000   partmgr  partmgr.sys  Mon Jul 13 19:19:58 2009 (4A5BC11E)
fffff880`00e00000 fffff880`00e33000   pci      pci.sys      Mon Jul 13 19:19:51 2009 (4A5BC117)
fffff880`00ec6000 fffff880`00ecd000   pciide   pciide.sys   Mon Jul 13 19:19:49 2009 (4A5BC115)
fffff880`00ff0000 fffff880`01000000   PCIIDEX  PCIIDEX.SYS  Mon Jul 13 19:19:48 2009 (4A5BC114)
fffff880`013bf000 fffff880`013d0000   pcw      pcw.sys      Mon Jul 13 19:19:27 2009 (4A5BC0FF)
fffff880`05a00000 fffff880`05aa6000   peauth   peauth.sys   Mon Jul 13 21:01:19 2009 (4A5BD8DF)
fffff880`05b5b000 fffff880`05b98000   portcls  portcls.sys  Mon Jul 13 20:06:27 2009 (4A5BCC03)
fffff880`00d3e000 fffff880`00d52000   PSHED    PSHED.dll    Mon Jul 13 21:32:23 2009 (4A5BE027)
fffff880`043c2000 fffff880`043e6000   rasl2tp  rasl2tp.sys  Mon Jul 13 20:10:11 2009 (4A5BCCE3)
fffff880`0422f000 fffff880`0424a000   raspppoe raspppoe.sys Mon Jul 13 20:10:17 2009 (4A5BCCE9)
fffff880`0424a000 fffff880`0426b000   raspptp  raspptp.sys  Mon Jul 13 20:10:18 2009 (4A5BCCEA)
fffff880`0426b000 fffff880`04285000   rassstp  rassstp.sys  Mon Jul 13 20:10:25 2009 (4A5BCCF1)
fffff880`02c00000 fffff880`02c51000   rdbss    rdbss.sys    Mon Jul 13 19:24:09 2009 (4A5BC219)
fffff880`01843000 fffff880`0184c000   RDPCDD   RDPCDD.sys   Mon Jul 13 20:16:34 2009 (4A5BCE62)
fffff880`0184c000 fffff880`01855000   rdpencdd rdpencdd.sys Mon Jul 13 20:16:34 2009 (4A5BCE62)
fffff880`01855000 fffff880`0185e000   rdprefmp rdprefmp.sys Mon Jul 13 20:16:35 2009 (4A5BCE63)
fffff880`011a6000 fffff880`011e0000   rdyboost rdyboost.sys Mon Jul 13 19:34:34 2009 (4A5BC48A)
fffff880`0756d000 fffff880`07585000   rspndr   rspndr.sys   Mon Jul 13 20:08:50 2009 (4A5BCC92)
fffff880`042fb000 fffff880`04352000   Rt64win7 Rt64win7.sys Thu Mar 04 08:42:52 2010 (4B8FB8DC)
fffff880`0724b000 fffff880`0747cc00   RTKVHD64 RTKVHD64.sys Fri Mar 26 06:30:50 2010 (4BAC8CDA)
fffff880`08e83000 fffff880`08e8e000   secdrv   secdrv.SYS   Wed Sep 13 09:18:38 2006 (4508052E)
fffff880`04390000 fffff880`0439c000   serenum  serenum.sys  Mon Jul 13 20:00:33 2009 (4A5BCAA1)
fffff880`02d9b000 fffff880`02db8000   serial   serial.sys   Mon Jul 13 20:00:40 2009 (4A5BCAA8)
fffff880`01475000 fffff880`0147d000   spldr    spldr.sys    Mon May 11 12:56:27 2009 (4A0858BB)
fffff880`09329000 fffff880`0939a000   spsys    spsys.sys    Mon May 11 13:20:58 2009 (4A085E7A)
fffff880`0927a000 fffff880`09310000   srv      srv.sys      Thu Aug 26 23:38:00 2010 (4C773318)
fffff880`07585000 fffff880`075ec000   srv2     srv2.sys     Thu Aug 26 23:37:46 2010 (4C77330A)
fffff880`08fc1000 fffff880`08fee000   srvnet   srvnet.sys   Thu Aug 26 23:37:24 2010 (4C7732F4)
fffff880`042a3000 fffff880`042a4480   swenum   swenum.sys   Mon Jul 13 20:00:18 2009 (4A5BCA92)
fffff880`01600000 fffff880`017fd000   tcpip    tcpip.sys    Sun Jun 13 23:39:04 2010 (4C15A458)
fffff880`08fee000 fffff880`09000000   tcpipreg tcpipreg.sys Mon Jul 13 20:09:49 2009 (4A5BCCCD)
fffff880`01898000 fffff880`018a5000   TDI      TDI.SYS      Mon Jul 13 19:21:18 2009 (4A5BC16E)
fffff880`0187a000 fffff880`01898000   tdx      tdx.sys      Mon Jul 13 19:21:15 2009 (4A5BC16B)
fffff880`02dd3000 fffff880`02de7000   termdd   termdd.sys   Mon Jul 13 20:16:36 2009 (4A5BCE64)
fffff960`00550000 fffff960`0055a000   TSDDD    TSDDD.dll    unavailable (00000000)
fffff880`013da000 fffff880`01400000   tunnel   tunnel.sys   Mon Jul 13 20:09:37 2009 (4A5BCCC1)
fffff880`042e8000 fffff880`042fa000   umbus    umbus.sys    Mon Jul 13 20:06:56 2009 (4A5BCC20)
fffff880`074b2000 fffff880`074b3f00   USBD     USBD.SYS     Mon Jul 13 20:06:23 2009 (4A5BCBFF)
fffff880`040de000 fffff880`040ef000   usbehci  usbehci.sys  Mon Jul 13 20:06:30 2009 (4A5BCC06)
fffff880`05ac3000 fffff880`05b1d000   usbhub   usbhub.sys   Mon Jul 13 20:07:09 2009 (4A5BCC2D)
fffff880`04088000 fffff880`040de000   USBPORT  USBPORT.SYS  Mon Jul 13 20:06:31 2009 (4A5BCC07)
fffff880`07497000 fffff880`074b2000   USBSTOR  USBSTOR.SYS  Mon Jul 13 20:06:34 2009 (4A5BCC0A)
fffff880`0407b000 fffff880`04088000   usbuhci  usbuhci.sys  Mon Jul 13 20:06:27 2009 (4A5BCC03)
fffff880`00e33000 fffff880`00e40000   vdrvroot vdrvroot.sys Mon Jul 13 20:01:31 2009 (4A5BCADB)
fffff880`01800000 fffff880`0180e000   vga      vga.sys      Mon Jul 13 19:38:47 2009 (4A5BC587)
fffff880`0180e000 fffff880`01833000   VIDEOPRT VIDEOPRT.SYS Mon Jul 13 19:38:51 2009 (4A5BC58B)
fffff880`00e55000 fffff880`00e6a000   volmgr   volmgr.sys   Mon Jul 13 19:19:57 2009 (4A5BC11D)
fffff880`00e6a000 fffff880`00ec6000   volmgrx  volmgrx.sys  Mon Jul 13 19:20:33 2009 (4A5BC141)
fffff880`0115a000 fffff880`011a6000   volsnap  volsnap.sys  Mon Jul 13 19:20:08 2009 (4A5BC128)
fffff880`02db8000 fffff880`02dd3000   wanarp   wanarp.sys   Mon Jul 13 20:10:21 2009 (4A5BCCED)
fffff880`01833000 fffff880`01843000   watchdog watchdog.sys Mon Jul 13 19:37:35 2009 (4A5BC53F)
fffff880`00ed3000 fffff880`00f77000   Wdf01000 Wdf01000.sys Mon Jul 13 19:22:07 2009 (4A5BC19F)
fffff880`00f77000 fffff880`00f86000   WDFLDR   WDFLDR.SYS   Mon Jul 13 19:19:54 2009 (4A5BC11A)
fffff880`02d5d000 fffff880`02d66000   wfplwf   wfplwf.sys   Mon Jul 13 20:09:26 2009 (4A5BCCB6)
fffff960`000c0000 fffff960`003cf000   win32k   win32k.sys   Tue Aug 31 22:58:04 2010 (4C7DC13C)
fffff880`00fdd000 fffff880`00fe6000   WMILIB   WMILIB.SYS   Mon Jul 13 19:19:51 2009 (4A5BC117)

Unloaded modules:
fffff880`0195c000 fffff880`0196a000   crashdmp.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
fffff880`0196a000 fffff880`01976000   dump_ataport
    Timestamp: unavailable (00000000)
    Checksum:  00000000
fffff880`01976000 fffff880`0197f000   dump_atapi.s
    Timestamp: unavailable (00000000)
    Checksum:  00000000
fffff880`0197f000 fffff880`01992000   dump_dumpfve
    Timestamp: unavailable (00000000)
    Checksum:  00000000

Here is an article on this driver: http://www.overclock.net/windows/643639-nvrodev-service-failed-start-solved.html

CaptainK24 · Dec 5, 2010

I am not overclocking anything

Yes I tried to download the nVidia system tools but got the wrong version (as you pointed out). I have just now completed uninstalling anything and everything NVIDIA and Realtek related, and reinstalled the latest video and sound card drivers, plus the proper graphics card utility tools.

No idea if it matters but when I uninstalled the NVIDIA HD Audio driver, and just installed the single Realtek Audio driver, Windows automatically installed 4 High Definition Audio Device files

Hopalong X · Dec 5, 2010

My Asus moboard did the same. It shows 4 drivers installed. Weird but it works.
Ahhh. HD is 4ch sound plus a subwoofer is driven somewhere along the way. It splits it up to four drivers.

I only have stereo so never thought about it until now.

I hope that got you all fixed up.

Mike

CaptainK24 · Dec 5, 2010

Just tried playing PC game again, still crashed

CarlTR6 · Dec 5, 2010

CaptainK24 said:
I am not overclocking anything

Yes I tried to download the nVidia system tools but got the wrong version (as you pointed out). I have just now completed uninstalling anything and everything NVIDIA and Realtek related, and reinstalled the latest video and sound card drivers, plus the proper graphics card utility tools.

No idea if it matters but when I uninstalled the NVIDIA HD Audio driver, and just installed the single Realtek Audio driver, Windows automatically installed 4 High Definition Audio Device files

Nuts; I hoped that would solve the problem.. Please upload your latest dump and we will take a look.

CaptainK24 · Dec 6, 2010

It wasn't a blue screen this time, just locked up. Was able to reboot and play for about an hour with no issues. Will try again tomorrow after work and see how it goes. Hopefully the driver deal fixed it. Did you see anything from my earlier crashes that might indicate anything?

CarlTR6 · Dec 6, 2010

Three of the earlier dumps blamed nvoclk64.sys. The other dump blamed a Windows system core file, which is very unlikely to be the true cause. That dump also indicated memory corruption, which can be caused by a bad or outdated driver. Your error log may give a clue regarding this latest crash. You can run the JC Griff tool again and upload the latest files it generates. We can then look at the error logs.

CaptainK24 · Dec 6, 2010

Here is the latest BSOD report ran approx one hour ago. Hope it helps!

CarlTR6 · Dec 7, 2010

Your latest dump is a Driver Verifier enabled dump and it blames a Windows system core driver, which is very unlikely to be the real cause. Turn Driver Verifier off. Run with Driver Verifier enabled and let's see how your system does. I suggest you run Memtest to test your RAM following the instructions in this tutorial: http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html. Run Memtest for at least 7 passes; this will take from 6-8 hours. Post your results.

CaptainK24 · Dec 7, 2010

How do I turn off Driver Verifier?

CaptainK24 · Dec 8, 2010

Just got done running the memtest and there were 31 errors in 7+ passes. Wonderful. However, I couldn't figure out how to save some sort of a log file from running it. Options were (Esc) to reboot, (c) to configure, and then two choices to scroll lock or something. I hit escape thinking it would give me an option to save on exit and it just rebooted. I don't mind running it again if I need to, just need to know how to save the results so I can share

CaptainK24 · Dec 8, 2010

Just tried to run the cd that came with my motherboard twice in a row (wanted to check drivers) and got back to back BSOD, both referring to the file gdvr.sys as the culprit

Tews · Dec 8, 2010

Errors of any type with memtest86 means you have a faulty module or a bad slot on the motherboard.. You will need to test each stick separately until you find one that passes... then you will need to test each slot to make sure that you dont have a faulty memory slot..

New System, Having Issues

New member

My Computer

R.I.P.

My Computer

New member

My Computer

New member

My Computer

New member

My Computer

R.I.P.

My Computer

New member

My Computer

Antique Senior Member

My Computer

New member

My Computer

R.I.P.

My Computer

New member

My Computer

Antique Senior Member

My Computer

New member

My Computer

Antique Senior Member

My Computer

New member

My Computer

Antique Senior Member

My Computer

New member

My Computer

New member

My Computer

New member

My Computer

Professional Lurker

My Computer

Similar threads