As a test, may you uninstall Adobe Premier Elements, Cyberlink PowerDVD and Total Media Extreme? These programs also monitor the ODD forcefully.
And, Go to C:\ Windows\System32\drivers and\or C:\Windows\Syswow64\drivers, and delete the pxHelp20.sys.
I have no driver named pxhelp20.sys
Is pxhlpa64.sys related?
Also, I've uninstalled those three programs.
So you believe it is related to my Optical disk drive?
Model: HP BD CMB UJ160
Appears to be controlled by iaStorF.sts and cdrom.sys
Thanks for the help.
Edit: If it is the Disk Drive, would uninstalling the hardware fix the problem? I've used it once, outside of installing programs from CD's.
Last edited by wisecraker1; 06 Feb 2013 at 11:12. Reason: Added info.
Update: After uninstalling, I got another BSOD. The usual ntoskrnl.exe was blamed. However the memory dump(not the minidump) shows the blame on nvoclk64.sys.
I turned the verifier on for just this driver and it crashes before windows fully loads.
It is not the disk drive itself, but some software monitoring the disk drive. and that one I told and that you you mentioned are the same thing, so delete it.
EDIT: that is a part of the dispaly driver, nVidia System Utility Driver.Code:PxHlpa64 PxHlpa64 Kernel 10/20/2009 2:08:42 PM
- 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.
- If it says the the free version of Driver Fusion cannot remove all the elements, stop there and follow Drivers - Clean Left over Files after Uninstalling
- 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.
Alrighty, I deleted it as well! :)
Everything short of installing the older Nvidia driver, my internet is being wonky, has been done. I did experience another BSOD about an hour ago. However, it pointed to nvidia again. I went into the System32\drivers folder and manually deleted the nvoclk64.sys
Not the most permanent solution, but it driver verifier is no longer throwing BSODs and the display adapter still functions. The only lost functionality I seem to have is that Nvidia System Monitor no longer works.
No BSODs since then, though!
lol .... yours a nForce based computer, and nVidia system utility is assumed to be one of the bloated program here. Though the GUI is cool.
And, next time, if there is another issue, let us know.
If driver verifier is still running, stop.
Dumb question, what is a nForce based computer? Is it one that is just based off of Nvidia graphics?
I used Nvidia system utility to monitor temps and GPU/CPU usage in games.
Was manually removing the nvoclk64.sys bad?
And I disabled driver verifier.
Ah. I received a new BSOD, well two right in a row. Haven't seen this one before. The full memory dump places the blame on:
On Sat 2/9/2013 10:29:44 AM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: win32k.sys (win32k!memset+0x77BC)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002C9F24E, 0xFFFFF8800F3CCAB0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\win32k.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Multi-User Win32 Driver
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
The SF Tool Report is also attached.
-- And I thought we had this beat
EDIT:
Also, I ran SFC again, no violations were found.
I was skimming through the dumps with WhoCrashed, and noticed a few things.
I don't know how accurate the program is, or if this means anything about the recent win32k.sys BSOD, but there are 7 other incidences where the same bug check code 0x3B and Parameter 1: 0xC0000005 are the same. Are those also win32k.sys related crashes?
Quote