Random Blue Screen involving pacer.sys (out of ideas)

Hi Rick :)

Before the member that Dave (Northernsoul55) mentioned appears, I want to ask you a couple of questions.

Northernsoul55 said:

I will have to ask another member to assist with this who is far more knowledgeable
and experienced on these types of issues.

cheers

Dave

► First, do you know what is the source of the pxhlpa64.sys in your system?

Code:

Event[19299]:
  Log Name: System
  Source: Service Control Manager
  Date: 2013-09-17T04:35:22.757
  Event ID: 7026
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: CosmosII
  Description: 
The following boot-start or system-start driver(s) failed to load: 
PxHlpa64

If not, help us to know.
Upload the list of all the third party drivers Using NirSoft DriverView :

• Download and execute Driverview
• View > Hide Microsoft Drivers
• Edit > Select all
• File > Save Selected Items
• In the Save dialog, Set the path to desktop, Put "Driverview" in the name field, and save.
• Zip the .txt file and upload it.

Download and install CCleaner. Then run it.
Go to "Tools" .... by default it will open the "uninstall" tab.
Click on save as text file. Save it on your desktop.
Upload the text file for us.


► Second, is RAID a must for you there? It is failing there, you know

Code:

Description    Disk drive
Model    Intel Raid 0 Volume SCSI Disk Device
Size    5.46 TB (6,001,139,612,160 bytes)
-------------------------------------------------
Drive    D:
Size    5.46 TB (6,001,006,706,688 bytes)

A non-system drive is RAID there. Decide that if it is a must or not .......

Code:

 Event[3903]:
  Log Name: System
  Source: Service Control Manager
  Date: 2013-09-05T01:25:34.366
  Event ID: 7034
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: CosmosII
  Description: 
The Intel(R) Rapid Storage Technology service terminated unexpectedly.  It has done this 1 time(s).

Let us know.

First Off thank you for all the help so far. With all of life's complications I am only now attending to the matter. It wears me out just thinking about this. It makes me very sad...

I've uploaded both the "driverview" txt file and the ccleaner "uninistall" program list
as well as recent sevenforums "Grab all" with tonights's blue screen dump

Regarding pxhlpa64.sys:
I do not know what was using it when those errors were logged
on 9-30-13 I installed Panasonic HD writer (rips m2ts video off my camera) and that installed PxHlpa64 as well
after that the errors in Event viewer stopped
PxHlpa64.sys exists in locations (windows\system32\drivers and the Panasonc HD directory

Regarding the Raid
My C: (system) Drive is SSD. My D: (programs & storage) drive is raid.
I have the option of RST or RSTe drivers. I have Intel RSTe drivers installed. I originally tried RST and it was chronically unstable.
The Raid is not an absolute necessity if getting rid of it will solve my problems, although I have had a raid for as long as I can remember and I hate to loose it.
Why does it crash so infrequently (Once a week?). Wouldn't something in constant use like a storage system crash every session?

Thanks for the help. I've been building machines since the 90's, never had a problem like this. This was supposed to be my dream machine, top $$ x79 buld and it's turned into a nightmare.

-Rick

Some things I wonder about:

I've always run raid, why is this intel chipset so much trouble?
Do you think this can be fixed with drivers and/or setup or is it a hardware problem?
All the X79 boards use this intel raid chipset? Is it possible a board from a different manufacture would solve anything?

UPDATE: I updated my MB tonight and it also updated the Intel Raid Storage Rom from 3.5 to 3.7. Maybe this will help?

Hi Rick. Dont know how the computer ran during the last two weeks .... no information about it in your post :)

It is not any hardware issue, apparently. Lately only two things were problematic there, which are known and worldwide problems, PxHelpa64 and iaStor.

If issues continue to occur, you should keep away from those two, at least as a test.