PC freezing and random BSODs

[thafuchs]

Hi,
I’ve been getting these BSODs since last September, when I had to change my hard drive, and my PC has also been freezing a lot and I have to restart it every time. It’s always random, I can’t really see a pattern…

I’ve run Memtest86 and found nothing, and had all the drivers updated with SlimDrivers.
Also, I don't know if it could be related, but my PC had been overheating for a long time. I've just cleaned all the dust last week and it seems it solved the heat problem, but it still crashes every few hours, either freezing or getting the BSOD.
I’ve attached the SF diagnostics here, really hope you can help me.

 

[Arc]

thafuchs. there is Realtek Wireless LAN 802.11n PCI-E NIC NT Driver.

BugCheck A, {fffff68000001000, 2, 0, fffff80003071c76}

*** WARNING: Unable to verify timestamp for rtl8192se.sys
*** ERROR: Module load completed but symbols could not be loaded for rtl8192se.sys
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : [B][URL="http://www.carrona.org/drivers/driver.php?id=rtl8192se.sys"]rtl8192se.sys[/URL][/B] ( rtl8192se+30ef7 )

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

And which is very old.

fffff880`0585d000 fffff880`0598c000   rtl8192se T (no symbols)           
    Loaded symbol image file: rtl8192se.sys
    Image path: \SystemRoot\system32\DRIVERS\rtl8192se.sys
 [COLOR=Red]   Image name: rtl8192se.sys
    Timestamp:        Fri Jul 30 15:01:31 2010[/COLOR] (4C529BF3)
    CheckSum:         0011F44B
    ImageSize:        0012F000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Update it from Realtek

Also you need to follow it: http://www.sevenforums.com/crash-lo...0x101-clock_watchdog_timeout-troubleshtg.html

[COLOR=Red][B]BugCheck 101[/B][/COLOR], {31, 0, fffff88003163180, 2}

Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )

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

http://www.sevenforums.com/crash-lockup-debug-how/35349-stop-0x124-what-means-what-try.html follow it, too.

[B][COLOR=Red]BugCheck 124[/COLOR][/B], {0, fffffa8005000028, b2000000, 80000106}

Probably caused by : GenuineIntel

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

Daemon Tools, Alcohol 120% and Power Archiver Pro uses SCSI Pass Through Direct (SPTD), which is a well known BSOD causer. Uninstall Alcohol 120% at first. Then download SPTD standalone installer from Disk-Tools.com, and execute the downloaded file as guided below :

• Double click to open it.
• Click this button only:
• 
• If it is grayed out, as in the picture, there is no more SPTD in your system, and you just close the window.

Free up the startup.

1. Click on the Start button
2. Type “msconfig (without quotes), click the resulting link. It will open the System Configuration window.
3. Select the “Startup” tab.
4. Deselect all items other than the antivirus.
5. Apply > OK
6. Accept the restart.

If possible, plan to update your BIOS, too.

BIOS Version/Date    INSYDE Q3H32, [COLOR=Red]12/07/2010[/COLOR]

 

[thafuchs]

Thanks for the answer, Arc!

I updated the Realtek driver, uninstalled Alcohol 120% and SPTD, and only the antivirus is opening at startup. Also did the drivers check until I got a BSOD (got it twice while trying to uninstall Alcohol). I've attached the new diagnostics.

This is the analysis I got from WhoCrashed:

crash dump file: C:\Windows\Minidump\021313-78281-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]pxhlpa64.sys[/FONT] (PxHlpa64+0x8938)
Bugcheck code: 0xC9 (0x224, 0xFFFFF88000E6C938, 0xFFFFF9801BBD4D80, 0x2)
Error: [FONT=Segoe UI, Arial]DRIVER_VERIFIER_IOMANAGER_VIOLATION [/FONT]
file path: C:\Windows\system32\drivers\pxhlpa64.sys
product: [FONT=Segoe UI, Arial]PxHelp64[/FONT]
company: [FONT=Segoe UI, Arial]Sonic Solutions[/FONT]
description: Px Engine Device Driver for 64-bit Windows
Bug check description: This is the bug check code for all Driver Verifier
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: pxhlpa64.sys (Px Engine Device Driver for 64-bit Windows, Sonic Solutions).

 

[Arc]

That driver is very old, so there is no doubt that it will be unstable. And, it is a very common cause of BSOD; it monitors your ODD for some possible autoplay etc.

start             end                 module name
fffff880`00e64000 fffff880`00e6fae0   PxHlpa64 T (no symbols)           
    Loaded symbol image file: PxHlpa64.sys
    Image path: PxHlpa64.sys
[COLOR=Red]    Image name: PxHlpa64.sys
    Timestamp:        Tue Dec 11 05:19:01 2007[/COLOR] (475DD06D)
    CheckSum:         0000FD49
    ImageSize:        0000BAE0
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Here is a list of programs that uses this driver: pxHelp20.sys programs. If you have any of these programs installed, better you uninstall it.

If you dont have, go to C:\Windows\system32\drivers and C:\Windows\SysWoW64\driver, and then delete pxhlpa64.sys manually.

 

[thafuchs]

Ok, I didn't had any of these programs installed, so I just deleted it from C:\Windows\system32\drivers, but couldn't find it anywhere in C:\Windows\SysWoW64\driver

 

[Arc]

It's ok.

Now observe the situation.

 

[thafuchs]

Just got another BSOD right now... this time I noticed something: my firefox has been crashing a lot too, and usually Windows manager stops working and I get a BSOD right after that.
I think you may be getting close to the problem. I've been using my computer all day, this is the first BSOD I got so far. Thanks for helping!

I've attached the new diagnostics...

 

[Arc]

In the zip, there is no new dump after yesterday.

For firefox, you may try http://www.sevenforums.com/tutorials/271263-firefox-gpu-hardware-acceleration-turn-off.html

 

[thafuchs]

That's strange.. I'll attach a new zip for you. After that crash, the computer froze 3 times.

This is the analysis from the last BSOD:
[FONT=Segoe UI, Arial]On Thu 14/02/2013 18:25:53 GMT your computer crashed
crash dump file: C:\Windows\Minidump\021413-21933-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x7F1C0)
Bugcheck code: 0xA (0x8500, 0x2, 0x0, 0xFFFFF800030E1911)
Error: [FONT=Segoe UI, Arial]IRQL_NOT_LESS_OR_EQUAL[/FONT]
file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

[/FONT]

 

[Arc]

Your crash dumps are not showing any finite probable cause. In such a situation, it is better to enable Driver Verifier to monitor the drivers.
Driver Verifier - Enable and Disable
Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

   Information

Why Driver Verifier:
It puts a stress on the drivers, ans so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.

How Can we know that DV is enabled:
It will make the system bit of slow, laggy.

   Warning

Before enabling DV, make it sure that you have earlier System restore points made in your computer. You can check it easily by using CCleaner looking at Tools > System Restore.

If there is no points, make a System Restore Point manually before enabling DV.

   Tip

• If you fail to get on the Desktop because of DV, Boot into Advanced Boot Options > Safe mode. Disable DV there. Now boot normally again, and try following the instruction of enabling DV again.
• If you cannot boot in Safe mode too, do a System Restore to a point you made earlier.

Test your RAM modules for possible errors.
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 passes, preferably overnight.

Let us know the results, with the subsequent crash dumps, if any.

 

[thafuchs]

Ok, here it is.. this time got these two:
[FONT=Segoe UI, Arial]CLOCK_WATCHDOG_TIMEOUT[/FONT]
[FONT=Segoe UI, Arial]PAGE_FAULT_IN_NONPAGED_AREA[/FONT]

I tested the RAM yesterday, each stick separately for 4 passes, but I will do it again and let the test run for 8 passes.

 

[Arc]

So you haven't enabled driver verifier yet.

I guess you haven't taken the memtest too?

And have you followed the other links suggested?

• STOP 0x101: CLOCK_WATCHDOG_TIMEOUT troubleshtg
• Stop 0x124 - what it means and what to try

For any further proceeding, let us know the results of the suggested steps accordingly.

 

[thafuchs]

Yes, I enabled it and let it run until I got these BSOD... I'll try these other steps you suggested

 

[thafuchs]

I did the memtest for 11 passes, but it found no errors. Also run the stress test (Prime95 - recommended in the stop 0x101 thread) for about 9 hours until my pc froze, but until then it hadn't found any errors either, the results are in the zip.
I enabled drive verifier and got one more BSOD. These last BSOD I got seemed to freeze while "Initializing disk for crash dump..." and it just stops responding. Maybe that's the reason there's no dump?

 

[Arc]

The latest crash is a special pool detected memory corruption.

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

SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION (c1)
Special pool has detected memory corruption.  Typically the current thread's
stack backtrace will reveal the guilty party.
Arguments:
Arg1: fffff98034c3eee0, address trying to free
Arg2: fffff98034c3e755, address where bits are corrupted
Arg3: 0000000000530118, (reserved)
Arg4: 0000000000000023, caller is freeing an address where nearby bytes within the same page have been corrupted

But current threads stack is not showing anything.

As the memtest came clear, we can say that it is a problem caused by a device driver. It is the situation that the dumps are coming silent about it. Here, as I can say, the best feasible solution will be a http://www.sevenforums.com/tutorials/219487-clean-reinstall-factory-oem-windows-7-a.html. Have a look here: http://www.sevenforums.com/crash-lo...0x101-clock_watchdog_timeout-troubleshtg.html

Recently it was found (here: http://www.sevenforums.com/crashes-d...ml#post1869800 ) that a wipe and reinstall of Windows fixed a STOP 0x101 problem.