Need some help, don't know what to do.

CarlTR6 · 15 Aug 2010

I certainly do not think you are rude or arrogant at all. You certainly should express your opinion. That is how we all learn - from one another. I wish you the best in getting your system running smoothly. Jonathan will give you sound and solid advice.

cwr89 · 15 Aug 2010

just a bump cause my last post was on the last page, not sure if it was seen.

restart after driver verifier resulted in unbootable PC. Dump is attached. I used safe mode to disable driver verifier.

thanks!
~Casey

CarlTR6 · 15 Aug 2010

The dump blames PxHlpa64.sys for the crash. It is a driver for Px Engine Device Driver for 64-bit Windows or PxHlpa belongs to the software PxHelp or PxHlpa by Sonic Solutions (www.sonic.com).

Code:

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


Loading Dump File [C:\Users\Owner\AppData\Local\Temp\Temp1_dump2.zip\dump\081510-29078-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*Symbol information
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`03057000 PsLoadedModuleList = 0xfffff800`03294e50
Debug session time: Sun Aug 15 21:32:06.666 2010 (GMT-4)
System Uptime: 0 days 0:00:15.352
Loading Kernel Symbols
...............................................................
...............................
Loading User Symbols
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck C9, {228, fffff88001177f74, fffff98002642d30, 0}

Unable to load image \SystemRoot\System32\Drivers\PxHlpa64.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for PxHlpa64.sys
*** ERROR: Module load completed but symbols could not be loaded for PxHlpa64.sys
Probably caused by : PxHlpa64.sys ( PxHlpa64+2f74 )

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

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

DRIVER_VERIFIER_IOMANAGER_VIOLATION (c9)
The IO manager has caught a misbehaving driver.
Arguments:
Arg1: 0000000000000228, A driver's completion routine has not marked the IRP pending if the
    PendingReturned field was set in the IRP passed to it. This may cause the OS
    to hang, especially if an error is returned by the stack.
Arg2: fffff88001177f74, The address in the driver's code where the error was detected.
Arg3: fffff98002642d30, IRP address.
Arg4: 0000000000000000

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


BUGCHECK_STR:  0xc9_228

DRIVER_VERIFIER_IO_VIOLATION_TYPE:  228

FAULTING_IP: 
PxHlpa64+2f74
fffff880`01177f74 49894818        mov     qword ptr [r8+18h],rcx

FOLLOWUP_IP: 
PxHlpa64+2f74
fffff880`01177f74 49894818        mov     qword ptr [r8+18h],rcx

IRP_ADDRESS:  fffff98002642d30

DEVICE_OBJECT: fffffa8009612030

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP

PROCESS_NAME:  System

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff800035513dc to fffff800030c7740

STACK_TEXT:  
fffff880`031a7208 fffff800`035513dc : 00000000`000000c9 00000000`00000228 fffff880`01177f74 fffff980`02642d30 : nt!KeBugCheckEx
fffff880`031a7210 fffff800`0355b47a : fffff800`0354f9f0 fffff880`01177f74 fffff980`02642d30 00000000`00000000 : nt!VerifierBugCheckIfAppropriate+0x3c
fffff880`031a7250 fffff800`0355c483 : 00000000`00000228 fffff880`01177f74 fffff980`02642d30 00000000`ffffffff : nt!ViErrorFinishReport+0xda
fffff880`031a72a0 fffff800`0355c654 : fffff880`01177f74 fffffa80`06d1ea80 fffff880`01177f74 fffff980`02642d30 : nt!VfErrorReport1+0x63
fffff880`031a7340 fffff800`0356f5f9 : fffff980`02642ed8 00000000`00000000 fffff880`031a7500 fffff980`02642d30 : nt!IovpCompleteRequest4+0x64
fffff880`031a7370 fffff800`030c9d26 : fffff980`02642edb fffff800`00000000 00000000`00000000 fffffa80`05201210 : nt!IovpLocalCompletionRoutine+0x189
fffff880`031a73d0 fffff800`0356719f : fffff980`02642d30 fffff880`031a7f01 fffffa80`06b71101 00000000`00000000 : nt!IopfCompleteRequest+0x3a6
fffff880`031a74b0 fffff880`010e941a : fffff880`031a7f20 00000000`00000000 00000000`00000000 fffffa80`06b711b0 : nt!IovCompleteRequest+0x19f
fffff880`031a7580 fffff880`010eb9ef : 00000000`00000000 fffff880`031a7f20 fffffa80`06b711b0 fffff880`00eeb787 : ataport!IdeCompleteScsiIrp+0x62
fffff880`031a75b0 fffff880`010e74ee : fffff980`02642d30 00000000`00000000 00000000`00000002 fffffa80`06b71060 : ataport!IdePortPdoDispatch+0xc3
fffff880`031a75e0 fffff800`0356dc16 : fffff980`02642d30 00000000`00000002 fffffa80`04ede3f0 fffff880`00ef1016 : ataport!IdePortDispatch+0x16
fffff880`031a7610 fffff880`00eeb787 : fffff980`02642d30 fffffa80`06b1ee40 fffff980`02642d30 fffffa80`06d06840 : nt!IovCallDriver+0x566
fffff880`031a7670 fffff880`00ef3751 : fffff880`00f11b50 fffff880`00eeb962 00000000`00000010 00000000`00000202 : ACPI!ACPIDispatchForwardIrp+0x37
fffff880`031a76a0 fffff880`00eeba1f : fffff880`00f11b50 fffffa80`04ede3f0 fffff980`02642d30 fffff980`02642d30 : ACPI!ACPIIrpDispatchDeviceControl+0x75
fffff880`031a76d0 fffff800`0356dc16 : fffff980`02642d30 00000000`00000002 fffff980`02642d30 00000000`00000002 : ACPI!ACPIDispatchIrp+0x12b
fffff880`031a7750 fffff800`0356cc42 : fffff980`02642e90 00000000`00000002 fffffa80`09611f50 fffffa80`06c85cc0 : nt!IovCallDriver+0x566
fffff880`031a77b0 fffff800`0356dc16 : fffff980`02642d30 00000000`00000002 fffffa80`09611e00 fffffa80`081c25e8 : nt!ViFilterDispatchGeneric+0x62
fffff880`031a77e0 fffff880`011784d5 : fffff980`02642ed8 fffffa80`09612180 fffff980`02642d30 fffffa80`06c84910 : nt!IovCallDriver+0x566
fffff880`031a7840 fffff980`02642ed8 : fffffa80`09612180 fffff980`02642d30 fffffa80`06c84910 fffffa80`00000000 : PxHlpa64+0x34d5
fffff880`031a7848 fffffa80`09612180 : fffff980`02642d30 fffffa80`06c84910 fffffa80`00000000 fffffa80`00000001 : 0xfffff980`02642ed8
fffff880`031a7850 fffff980`02642d30 : fffffa80`06c84910 fffffa80`00000000 fffffa80`00000001 fffffa80`00000000 : 0xfffffa80`09612180
fffff880`031a7858 fffffa80`06c84910 : fffffa80`00000000 fffffa80`00000001 fffffa80`00000000 00000000`00000000 : 0xfffff980`02642d30
fffff880`031a7860 fffffa80`00000000 : fffffa80`00000001 fffffa80`00000000 00000000`00000000 00000000`00000000 : 0xfffffa80`06c84910
fffff880`031a7868 fffffa80`00000001 : fffffa80`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0xfffffa80`00000000
fffff880`031a7870 fffffa80`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0xfffffa80`00000001
fffff880`031a7878 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 fffffa80`08c4db00 : 0xfffffa80`00000000


STACK_COMMAND:  .bugcheck ; kb

SYMBOL_NAME:  PxHlpa64+2f74

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: PxHlpa64

IMAGE_NAME:  PxHlpa64.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a416253

FAILURE_BUCKET_ID:  X64_0xc9_228_VRF_PxHlpa64+2f74

BUCKET_ID:  X64_0xc9_228_VRF_PxHlpa64+2f74

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

Generally speaking, Windows 7 does not like older drivers. Drivers dated prior to July 13, 2009 are considered old (there are exceptions).

PxHlpa64.sys Tue Jun 23 19:16:35 2009 - since this driver was blamed by driver verifier, see if you can update it or the software it is associated with. If not, consider uninstalling the software.

Turn off Driver Verifier while you are updating drivers.

I find two more out of date drivers on your system.

AnyDVD.sys Tue May 26 17:56:25 2009 - AnyDVD Filter Driver or Watch & copy any DVD! belongs to the software AnyDVD by SlySoft, Inc (www.slysoft.com). UPdate the driver/software or uninstall.

ElbyCDIO.sys Tue Feb 17 12:11:23 2009 - ElbyCD Windows NT/2000/XP I/O driver or ElbyCD Windows NT/2000 I/O driver belongs to the software CDRTools or ElbyCDIO Driver or DVD Region Killer or VirtualCloneDrive by Elaborate Bytes AG (www.elby.ch). Update the driver/software or uninstall.

Post back if we can help you and keep us updated. When you have updated these three drivers, reboot and run your system. Let's see if maybe these solve the problem. If yo have another BSOD, please upload it.

cwr89 · 15 Aug 2010

Ok, So, I have long since removed Roxio Media Creator from my system. I don't even know where to begin to look for the driver to update. how would I go about removing it? do I remove it in the registry?

CarlTR6 · 15 Aug 2010

If you have removed Roxio, do a search in Windows Explorer (Drive C) for the driver. Rename it from .sys to .bak. Reboot and and it will not load. No need to go to the registry.

cwr89 · 16 Aug 2010

I took care of all three drivers by uninstalling the software and then changing the .sys to .bak on the 2 that still remained in my system 32 folder. I restarted and then set the verifier back up and restarted again.

I am attaching the dmp
thanks!
~Casey

CarlTR6 · 16 Aug 2010

cwr89 said:

I took care of all three drivers by uninstalling the software and then changing the .sys to .bak on the 2 that still remained in my system 32 folder. I restarted and then set the verifier back up and restarted again.

I am attaching the dmp
thanks!
~Casey

Very good job on the drivers! :)

This Driver Verifier enabled dump specifically blames RTKVHD64.sys. This is your Realtek High Definition Audio Function Driver Realtek. It is up to date - Jan 19 2010.

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck D5, {fffff9800167ad60, 0, fffff880068e045a, 0}

Unable to load image \SystemRoot\system32\drivers\RTKVHD64.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for RTKVHD64.sys
*** ERROR: Module load completed but symbols could not be loaded for RTKVHD64.sys

Could not read faulting driver name
Probably caused by : RTKVHD64.sys ( RTKVHD64+cc45a )

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

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

DRIVER_PAGE_FAULT_IN_FREED_SPECIAL_POOL (d5)
Memory was referenced after it was freed.
This cannot be protected by try-except.
When possible, the guilty driver's name (Unicode string) is printed on
the bugcheck screen and saved in KiBugCheckDriver.
Arguments:
Arg1: fffff9800167ad60, memory referenced
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation
Arg3: fffff880068e045a, if non-zero, the address which referenced memory.
Arg4: 0000000000000000, (reserved)

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


Could not read faulting driver name

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800033030e0
 fffff9800167ad60 

FAULTING_IP: 
RTKVHD64+cc45a
fffff880`068e045a 8b4630          mov     eax,dword ptr [rsi+30h]

MM_INTERNAL_CODE:  0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP

BUGCHECK_STR:  0xD5

PROCESS_NAME:  svchost.exe

CURRENT_IRQL:  0

TRAP_FRAME:  fffff880029da2b0 -- (.trap 0xfffff880029da2b0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=fffff880029da4d8
rdx=fffff880029da440 rsi=0000000000000000 rdi=0000000000000000
rip=fffff880068e045a rsp=fffff880029da440 rbp=0000000000000002
 r8=0000000000000000  r9=fffff880068e045a r10=0000000000000000
r11=fffff88002f64180 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
RTKVHD64+0xcc45a:
fffff880`068e045a 8b4630          mov     eax,dword ptr [rsi+30h] ds:4180:00000000`00000030=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff8000314bf14 to fffff800030cb740

STACK_TEXT:  
fffff880`029da148 fffff800`0314bf14 : 00000000`00000050 fffff980`0167ad60 00000000`00000000 fffff880`029da2b0 : nt!KeBugCheckEx
fffff880`029da150 fffff800`030c982e : 00000000`00000000 fffff8a0`02766114 fffffa80`08425000 fffff800`030fe33f : nt! ?? ::FNODOBFM::`string'+0x42837
fffff880`029da2b0 fffff880`068e045a : fffff880`029da4d8 00000000`00000000 fffff8a0`02766114 fffffa80`091463d0 : nt!KiPageFault+0x16e
fffff880`029da440 fffff880`029da4d8 : 00000000`00000000 fffff8a0`02766114 fffffa80`091463d0 00000000`00000000 : RTKVHD64+0xcc45a
fffff880`029da448 00000000`00000000 : fffff8a0`02766114 fffffa80`091463d0 00000000`00000000 fffff800`00000000 : 0xfffff880`029da4d8


STACK_COMMAND:  kb

FOLLOWUP_IP: 
RTKVHD64+cc45a
fffff880`068e045a 8b4630          mov     eax,dword ptr [rsi+30h]

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  RTKVHD64+cc45a

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: RTKVHD64

IMAGE_NAME:  RTKVHD64.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4b558c81

FAILURE_BUCKET_ID:  X64_0xD5_VRF_RTKVHD64+cc45a

BUCKET_ID:  X64_0xD5_VRF_RTKVHD64+cc45a

Followup: MachineOwner

On the off chance that the driver is corrupted, I recommend you down load another copy of this driver to your desktop. Turn Driver Verifier off. Go to Device Manager and uninstall the present driver, then install the new driver. Reboot. Run your system. If you get another BSOD, please upload it and we will go from there.

You also might see if there is an update for this driver available:

Rt64win7.sys Thu Feb 26 04:04:13 2009 - This is your network adapter driver - Realtek 8101E/8168/8169 Network Driver Interface Specification 6.20 64-bit Driver. Realtek

I suggest you update this driver also:

VClone.sys Fri May 22 19:08:37 2009 - VirtualCloneCD Driver by Elaborate Bytes AGelby CloneDVD™ 2. Update this driver and update the software. If an updated driver is not available, you might consider uninstalling the software and replacing it with software certified to be compatible with Win 7.

Keep us updated.

cwr89 · 16 Aug 2010

Ok, Heres the new deal,
I have updated the Realtek NIC drivers, that was simple.
I have renamed and uninstalled the VClone driver, as I thought that I had actually uninstalled the Virtual DVD drive a while back. so thats no longer running.

I have not yet reinstalled the Audio Driver, I was going to redownload it from gigabyte's website so its specific for my motherboard.

the new problem is that my 3 physical DVD drives are missing. Device manager says that it cannot load the device driver for that hardware, driver may be missing or corrupt.

I have gone through in device manager and unistalled all and then did a scan to reinstall them 3 times now and it keeps coming back unable to be installed or working.

should I remove the driver manually in the system 32/drivers folder? I know they come from microsoft so a simple removal and reinstall should work right?

thanks!
~Casey

cwr89 · 16 Aug 2010

So scratch that previous post. I did some digging and found the Microsoft Automated Troubleshooting tool.
I assumed since it was on Microsoft's website, it was legit. I was able to repair the driver snaffoo with my DVD drives and get them working again.

I have updated my Realtek HD Audio drivers from version 4.8.2 to 5.2.8
I have updated my Realtek NIC drivers (for both NIC ports) to the most recent driver via microsoft update. (it was apparently one that I was neglecting to update because it was marked optional)
I have removed all the Virtual Clone Drive and Clone DVD Elby drivers and also all the Roxio/Sonic drivers.

I enabled Driver Verifier, restarted and have completed 2 successful restarts without BSODs.
I have dissabled verifier and restarted.

I think everything is going to work from here. BUT as I have not been seeing BSODs except for once ever 24-48 hours I don't want to mark it solved yet.

also I might be taking this a bit too fast by assuming that since it passed the verifier that it is fixed.

thanks for the help!!
~Casey

CarlTR6 · 16 Aug 2010

Wow, you have done some superb work. A very good job. Kudos for solving the DVD drive problem; you did very well. Thank you for reporting back with details of what you have done. I am really happy to hear that you are running smoothly at the present.

Run your system. If you do not get a BSOD, in a couple of days, maybe we can consider this one solved. Keep us updated. I hope your problems are behind you and that we can mark this thread as solved.

It is looking good.