Constant Crashes/BSOD with different error messages.

[RugerBaby]

Hello, I've been trying to figure out what is wrong with my pc but Im throwing in the towel. I've ran memtest and no errors were found. Check disk was also ran and I think nothing was found. This has been happening for about a month or two now. I get constant freezes/crashes and also constant BSOD. The BSOD has giving many different errors. I've also read and followed the posting guide. Thanks for any help.

 

[Arc]

The BSOD dumps are not showing adequate information, but giving a hint of storage related failure. It may be either a failing HDD or a failing disc controller.

At first, you need to uninstall MagicISO and MagicDisc. They install a MagicISO SCSI Host Controller mcdbus.sys which is problematic in this case.

The NVIDIA nForce Serial ATA Controller needs to be updated.

fffff880`01023000 fffff880`01062000   nvstor64   (deferred)             
    Image path: \SystemRoot\system32\DRIVERS\nvstor64.sys
[COLOR=Red]    Image name: nvstor64.sys
    Timestamp:        Fri Apr 09 14:52:41 2010 [/COLOR](4BBEF1E1)
    CheckSum:         0003FFC4
    ImageSize:        0003F000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

No update is available in Acer | Download. You may search in Drivers - Download NVIDIA Drivers, search for nForce, as per your motherboard's chipset specifications.

Check the HDD using Western Digital Data Lifeguard.

Let us know the results. Will take the further steps depending on the situation.
________________________________________________________________________
BSOD ANALYSIS:

BugCheck A, {10, 2, 0, fffff800030e9a55}

Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+260 )

Followup: MachineOwner
-----------------------------------------------------------------------------
BugCheck 3B, {c0000005, fffff960000d797e, fffff8800cf1e470, 0}

Probably caused by : win32k.sys ( win32k!RGNOBJ::bMerge+aa )

Followup: MachineOwner
-----------------------------------------------------------------------------
BugCheck 1A, {41287, 8b, 0, 0}

Probably caused by : hardware ( nt! ?? ::FNODOBFM::`string'+454f5 )

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

 

[RugerBaby]

Ok, I updated the drivers from Nvidia, but during the 1st installation it restarted on its own. Ran the Data Lifeguard for 2-3 hrs and it froze. Not sure but I did the same as before with the SF diagnsotic tool, Ive attached the results. I'll try the Data Lifeguard again right now. Thanks a bunch. View attachment 271774

 

[RugerBaby]

Ran the quick test just too see the result and it passed. Now I'll try the extended test.

 

[RugerBaby]

Test Option: QUICK TEST
Model Number: WDC WD10EADS-00M2B0
Unit Serial Number:
Firmware Number: 01.00A01
Capacity: 1000.20 GB
SMART Status: Not Available
Test Result: PASS
Test Time: 20:31:08, June 08, 2013

Test Option: EXTENDED TEST
Model Number: WDC WD10EADS-00M2B0
Unit Serial Number:
Firmware Number: 01.00A01
Capacity: 1000.20 GB
SMART Status: Not Available
Test Result: PASS
Test Time: 00:17:45, June 09, 2013

 

[Arc]

Have you uninstalled MagicISO and MagicDisc? If not, do it. And then it is to wait and observe the situation.

 

[RugerBaby]

oh sorry, yes I have uninstalled magiciso/magicdisc. I'll post back if anything happens. Thanks

 

[RugerBaby]

ok, I got anotrher bsod with the message apc index mismatch

I checked but there was no dmp file created. I got the bsod then it froze and let out a loud ongoing beep until I had to power it off. Im beginning to think it might be my firewire soundcard.

 

[Arc]

ok, I got anotrher bsod with the message apc index mismatch

I checked but there was no dmp file created. I got the bsod then it froze and let out a loud ongoing beep until I had to power it off. Im beginning to think it might be my firewire soundcard.

You cannot host images in dropbox. And an image is useless in bsod analysis. Post it following the Blue Screen of Death (BSOD) Posting Instructions.

 

[RugerBaby]

ok, sorry. Here's the zip.

 

[Arc]

As per the zip you uploaded, the latest BSOD is of 08.06; which is a stop 0xA, and already checked earlier.

If you get a stop 0x1, I would suggest you 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.

Let us know the results, with the subsequent crash dumps, if any. Post it following the Blue Screen of Death (BSOD) Posting Instructions.

 

[RugerBaby]

ok, will do. Man this stuff is frustrating! Thanks again.

 

[RugerBaby]

Enabled verifier.exe and restarted but now its says my computer was unable to start, startup repair.

 

[Arc]

Boot into Safe mode. Disable DV. Boot into normal mode again .... (it will do) and enable DV again. Make it sure that you are not selecting any driver supplied by "microsoft" or "unknown" and run the computer with DV on ... hopefully it will go to desktop before crashing again.

 

[RugerBaby]

Ok, will make sure the unknown drivers arent checked, I might have checked them. Its crashed a couple times since then.

 

[RugerBaby]

Heres the zip. View attachment 272054

 

[Arc]

The bsod is caused by PxHlpa64.sys.

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

Use !analyze -v to get detailed debugging information.

BugCheck C9, {228, fffff880011eef74, fffff980016eed80, 0}

*** 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
---------

You need to uninstall it. A list of programs that includes the driver is here: pxHelp20.sys programs .. I will add quicktime with that list.

Uninstall any program contains that driver.

Do to C:\Windows\System32\drivers and C:\Windows\Syswow64\drivers, and delete PxHlpa64.sys manually.

BTW, MagicISO and MagicDisc, with their fake SCSI controller is present there, still.

 

[RugerBaby]

ok, uninstalled pxhlpa64.sys and also deleted magiciso from the registry. I also deleted the mcdbus.sys. Hopefully everything is under control now.

 

[Arc]

Let us wait and see

 

[RugerBaby]

son of a.. Woke up today and it has crashed a few times. No bsod this time, just freezes and locks up. My monitor starts flickering and then it freezes. Ive attached a zip but I dont believe any dmp files were created. Once again, thanks Arc.