|18 Aug 2010||#3|
| || |
Please update this driver:
PxHlpa64 PxHlpa64.sys Sat Feb 03 04:24:22 2007 (45C3AC06)
This will break your CD/DVD program, but can easily be renamed after we've finished.
The results from the DMP files do not give a definitive answer. While we investigate further here are a few things that you can do.
1-Run a system file check to verify and repair you system files. You do this by typing cmd in search, then right click and run as admin. SFC /SCANNOW
2-Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Boot from the CD, and leave it running for at least 5 or 6 passes.
Go into event viewer (type eventvwr in search). Go to the windows log>application tab.
You want to look for critical errors (they have red in the left column ).
When you find them you want to look for critical errors that say app hang, app crash, or anything that relates to the problem.
When you find them please note the event ID, and the source codes and tell us what they are.
Please go to start>search>type device manager.
Are there any "unknown devices" with yellow triangles on them?
Is you driver there , listed, and working?
If your driver is missing, or there is a yellow triangle on it, you will need to update it.
please run Verifier with these settings:
Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.
So, I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Windows 7 Startup Repair feature).
Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
NOTE: You can use Low Resource Simulation if you'd like. From my limited experimentation it makes the BSOD's come faster.
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.
Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).
Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.
If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.
If that doesn't work, post back and we'll have to see about fixing the registry entry off-line:
Delete these registry keys (works in XP, Vista, Windows 7): HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDrivers HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDriverLevel
|My System Specs|
|18 Aug 2010||#4|
| || |
Hey, sorry for getting back so late, was playing a game to see if it would happen again and it didn't. The game(BFBC2) crashed a few times but that's it.
IntelKidA - I hope this is what you're after.
problem has been detected and Windows has been shut down to prevent damage
to your computer.
The problem seems to be caused by the following file: win32k.sys
If this is the first time you've seen this stop error screen,
restart your computer. If this screen appears again, follow
Check to make sure any new hardware or software is properly installed.
If this is a new installation, ask your hardware or software manufacturer
for any Windows updates you might need.
If problems continue, disable or remove any newly installed hardware
or software. Disable BIOS memory options such as caching or shadowing.
If you need to use safe mode to remove or disable components, restart
your computer, press F8 to select Advanced Startup Options, and then
select Safe Mode.
*** STOP: 0x00000050 (0xfffff9600095898d, 0x0000000000000008, 0xfffff9600095898d,
*** win32k.sys - Address 0xfffff9600012b72d base at 0xfffff960000a0000 DateStamp
ttran - Did memtest off a usb, ran furmark, ran seatools for my HDD and they all went well. I will try some of the other things that you mentioned now.
Thanks for the help fellas.
|My System Specs|
|18 Aug 2010||#5|
| || |
Event viewer info:
Number of events=177
Application errors=37 - Event ID 1000
Application hang=8 - Event ID 1002
SideBySide= 99 - Event ID 33
I don't know what sidebyside is but of the 99 events, 99 of them were either logitech/setpoint or nero.
What do I do after I've renamed PxHlpa64.sys to PxHlpa64.BAK
EDIT - I ran Nero after renaming the file and it said that it's 'sidebyside is incorrect'. So I guess that means that PxHlpa64,sys is used by Nero.
|My System Specs|
|Similar help and support threads for2: BSOD ntoskrnl.exe win32k.sys|
|BSOD BCCode 50 and 19 ntoskrnl.exe and win32k.sys||BSOD Help and Support|
|BSOD error caused by ntoskrnl.exe,win32k.sys etc||BSOD Help and Support|
|BSOD related with win32k.sys and ntoskrnl.exe(memory_management, IRQL)||BSOD Help and Support|
|Random BSOD: ntoskrnl.exe, afd.sys, tcpip.sys, atikmdag.sys & win32k.s||BSOD Help and Support|
|Windows 7 - win32k.sys+ntoskrnl.exe BSOD||BSOD Help and Support|
|Constant BSOD involving ntoskrnl.exe and win32k.sys||BSOD Help and Support|
|Our Sites ||Site Links ||About Us ||Find Us |
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.
© Designer Media Ltd
All times are GMT -5. The time now is 04:26 PM.