BAD_POOL_CALLER c2 BSOD - RAID card?

[ZeikHunter]

BACKSTORY: Tortuous process here, wanted to put a new RAID card in my main PC because i got a deal on a bunch of gently used 4Tb drives.

Got a PERC H310 card off ebay, working pull, re-arrange a couple things, and away we go.

so. many. issues! 3 reinstalls of 2 OSes, new RAM and SATA cables, 2 different PERC firmwares and 3 different drivers, I'm at my wit's end.

ISSUE: BSOD when performing file copy operations to the RAID drive. No issue with card disconnected.

QUESTIONS: Is this fixable, or is the card borked? If it's fixable, how?

Dump logs attached per forum instructions. this OS install is only a few days old so it dosnt have all updates.

 

[axe0]

Hi ZeikHunter,

Welcome to the 7forums

Please ensure that Windows gets up to date a.s.a.p.

Please check your SSD for firmware updates.

Please make sure all your partitions have at least 15% free space to be on the safe side with Windows doing background stuff.

What are the specs of your memory? I cannot find any site with the right model.
I'm asking because you state in your system specs that you are running 2133MHz, but your motherboard does not support higher than 2000MHz which is OC for your motherboard.
The dumps say something else, but that is currently not relevant.

[Memory Device (Type 17) - Length 34 - Handle 0030h]
  Physical Memory Array Handle  002ch
  Memory Error Info Handle      [Not Provided]
  Total Width                   64 bits
  Data Width                    64 bits
  Size                          8192MB
  Form Factor                   09h - DIMM
  Device Set                    [None]
  Device Locator                Node0_Dimm1
  Bank Locator                  Node0_Bank0
  Memory Type                   18h - Specification Reserved
  Type Detail                   4080h - Synchronous
  Speed                         667MHz
  Manufacturer                  Undefined         
  Serial Number                             
  Asset Tag Number                            
  Part Number                   [COLOR="Red"]F3-2133C9-8GB[/COLOR]

Diagnostics Test

 HDD TEST

Run SeaTools to check the integrity of your HDD. SeaTools for DOS and Windows - How to Use - Windows 7 Help Forums
Run following tests

1. Short Drive Self Test
2. Short generic
3. Long generic

If the short generic fails, no need for the long generic.

   Note

Do not run SeaTools on an SSD as the results will be invalid.

Make a photo of the result and post it.

Run chkdsk
Disk Check - Windows 7 Help Forums

Run HDTune to

• scan for errors, no quick scan but full scan
• check the health,
• benchmark.

It may take some time, but please take the time you need to perform it properly.
When above is done please make screenshots of the following

• the error scan,
• the health,
• the benchmark incl. following
  • transfer rate,
  • access time,
  • burst rate,
  • cpu usage.

4: kd> k
 # Child-SP          RetAddr           Call Site
00 fffff880`083a8e38 fffff800`0390f4ec nt!KeBugCheckEx
01 fffff880`083a8e40 fffff800`035383b1 nt!VerifierBugCheckIfAppropriate+0x3c
02 fffff880`083a8e80 fffff800`035b5c73 nt!VerifierFreeTrackedPool+0x41
03 fffff880`083a8ec0 fffff880`012c986d nt!ExDeferredFreePool+0x129f
04 fffff880`083a8f70 fffff880`012a9441 [COLOR="red"]Ntfs[/COLOR]!NtfsCommonCreate+0x2336
05 fffff880`083a9150 fffff880`011b5367 [COLOR="red"]Ntfs[/COLOR]!NtfsNetworkOpenCreate+0x115
06 fffff880`083a9430 fffff880`011d6aed [COLOR="red"]fltmgr[/COLOR]!FltpPerformFastIoCall+0x357
07 fffff880`083a9490 fffff800`037821b2 [COLOR="Red"]fltmgr[/COLOR]!FltpFastIoQueryOpen+0x15d
08 fffff880`083a9530 fffff800`0377ddb8 nt!IopParseDevice+0x1249
09 fffff880`083a9690 fffff800`0377efd6 nt!ObpLookupObjectName+0x588
0a fffff880`083a9780 fffff800`0375d066 nt!ObOpenObjectByName+0x306
0b fffff880`083a9850 fffff800`03481e53 nt!NtQueryAttributesFile+0x145
0c fffff880`083a9ae0 00000000`7732168a nt!KiSystemServiceCopyEnd+0x13
0d 00000000`05fee028 00000000`00000000 0x7732168a

 

[ZeikHunter]

OS resides on the SSD
SSD firmware is current according to Samsung

the 5Tb drive is very full because i had to move stuff from a drive that was in use to put it into the array, trying to move stuff from that drive to the array is when the BSOD occurs. I'll disconnect it though.

the RAM is RipjawsX - F3-2133C9Q-32GXH - G.SKILL DDR3 Memory
its set a default values in BIOS for troubleshooting so im not tripping over overclocking issues while dealing with this. I have some ddr3-1600 that was in the machine previously, i can put that back in if it might help

I've had 3 more crashes since the original post. disconnected the 5Tb and the raid card so i could actually type a post and run chkdsk without a crash, as well as get updates to run.

Updates are installing, and this is the collector i ran a moment ago. checkdisk and hdtune for c: as well. (the CRC errors are from a bad SATA cable that has been replaced)

 

[ZeikHunter]

forgot to hit upload

 

[axe0]

0x24 is the NTFS system complaining
0x1A is the memory management complaining
0x50 is in this case likely defective hardware.
You might know what drive the event logs are talking about?

Event[976]:
  Log Name: System
  Source: Disk
  Date: 2016-05-21T00:55:25.050
  Event ID: 11
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: MORRIGAN
  Description: 
The driver detected a controller error on \Device\Harddisk1\DR1.

 

[ZeikHunter]

I imagine it's the raid device (still disconnected) though right now DR1 is my 4tb drive thats never given me problems at all.

if you can tell what driver is detecting it, the controller driver is percsas2

I've been stable for hours with just the 4&5Tb connected and running hdtune, which is telling enough

I was of the opinion that it was a bad card, but hoping it was a driver/software issue that could be fixed

Do you need any more info or can you render a verdict on my card?

 

[axe0]

I don't think that knowing what driver is detecting it would help you, though it looks pretty clear to me.

1 of the drives in your RAID is causing your issue.