Many different BSOD's. Memory management, bad pool header, chkdsk etc.

[RugerBaby]

Hi all i will try and type this as fast as i can before it crashes. lol

Ive ran memtest and chkdsk with 0 errors found. I also did a malwarebytes scan and have a clean bill of health.

Ive been getting them for the past week with different errors. Hope fully someone can help me with this as its driving me crazy!!

Sorry for being short just need to post before it crashes, it happened once already.

Thanks in advance

ooops forgot i attached the zip too.
Thank you!

 

[Arc]

Hi RugerBaby.

The zip is incomplete. Please try SF Diag Tool and upload the resulting zip with your reply post.

 

[RugerBaby]

sorry about that heres an updated one

 

[Arc]

Hi. The versatility of the bugchecks are giving a hint of memory issue.

Test your RAM modules for possible errors.

How to Test and Diagnose RAM Issues with Memtest86+
​

Run memtest86+ for at least 8 consecutive passes.

If it start showing errors/red lines, stop testing. A single error is enough to determine that something is going bad there.

If it does not show any error, 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.

 

[RugerBaby]

ok, so i ran memtest for 8 passes with zero errors found. I enabled driver verifier and it would crash before getting to the desktop. I had to do a system repair and restore to an earlier point to get to my desktop. Hopefully the crashes were logged. I've attached the zip. Thank you for your help Arc.

 

[Arc]

That BSOD was caused by ZCL OHCI compatible Driver.

BugCheck C9, {21f, fffff8800f0596fc, fffff98006616e10, 0}

Unable to load image \SystemRoot\system32\DRIVERS\ZclDrv64.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ZclDrv64.sys
*** ERROR: Module load completed but symbols could not be loaded for ZclDrv64.sys
[COLOR=Red]Probably caused by : ZclDrv64.sys[/COLOR] ( ZclDrv64+136fc )

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

    Image name: ZclDrv64.sys
    Timestamp:        Thu Jun 27 09:38:40 2013

Driver Reference Table - ZclDrv64.sys

Either update the driver or uninstall it. Report us how it goes after that.

 

[RugerBaby]

Ok, so I unistalled the zcl driver. But now im getting a different bsod, portcls.sys, and doesnt boot to the desktop. I hope its not my firewire soundcard thats making it crash. Its been stable for years. Here are the the files.

 

[RugerBaby]

BTW i added a pci express firewire card to connect my firewire soundcard. Ive never had any issues and i hope its not that. Ive also updated the driver for the soundcard just in case. Like i said, its been stable for 3-4 yrs.

*edit
I added the card 3-4 yrs ago, just to be clear.

 

[Arc]

Now I am thinking that you know about the issue.

BugCheck D6, {fffff98007815018, 0, fffff8800f002b15, 0}

[COLOR=Red]*** WARNING: Unable to verify timestamp for vrtaucbl.sys
*** ERROR: Module load completed but symbols could not be loaded for vrtaucbl.sys[/COLOR]

Could not read faulting driver name
Probably caused by : portcls.sys ( portcls!GetMaxMapRegisters+5 )

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

It is, as your system says ....

• Name: Virtual Audio Cable
• Manufacturer: EuMus Design
• PNP Device ID: ROOT\MEDIA\0000
• Driver: c:\windows\system32\drivers\vrtaucbl.sys (4.10.0.2964, 65.16 KB (66,728 bytes), 6/17/2013 11:09 PM)

    Image name: vrtaucbl.sys
[COLOR=Red]    Timestamp:        Mon Feb 15 22:37:10 2010 [/COLOR](4B797F3E)

I think you know the required action, too. Either update it or if there is no feasible update abandon it.