BSOD BAD POOL HEADER/CALLER while using Cubase or after closing

Code:

BugCheck 19, {20, fffffa800baad000, fffffa800baad200, 4200000}

GetPointerFromAddress: unable to read from fffff800034fc0e0
GetUlongFromAddress: unable to read from fffff800034fc198
Probably caused by : ntkrnlmp.exe ( nt!CcWriteBehind+5bc )

Code:

Usual causes:  Device driver

This can also be caused by hard disk corruption and RAM.

The bugcheck indicates that a pool block header size is corrupt, the pool header is used to provide information about the allocation, such as the size of the pool allocation and the owner of the allocation.

Code:

7: kd> !pool fffffa800baad000
Pool page fffffa800baad000 region is Nonpaged pool
*fffffa800baad000 size:  200 previous size:    0  (Free ) *CcSc
		Pooltag CcSc : Cache Manager Shared Cache Map, Binary : nt!cc

The pool block which were looking at within the pool page belongs to the Cache Manager.

Code:

7: kd> dt nt!_POOL_HEADER fffffa800baad000
   +0x000 PreviousSize     : 0y00000000 (0)
   +0x000 PoolIndex        : 0y00000000 (0)
   +0x000 BlockSize        : 0y00100000 (0x20)
   +0x000 PoolType         : 0y00000100 (0x4)
   +0x000 Ulong1           : 0x4200000
   +0x004 PoolTag          : 0x63536343
   +0x008 ProcessBilled    : 0xfffffa80`0c2bcb30 _EPROCESS
   +0x008 AllocatorBackTraceIndex : 0xcb30
   +0x00a PoolTagHash      : 0xc2b

Code:

7: kd> !poolval fffffa800baad000
Pool page fffffa800baad000 region is Nonpaged pool

Validating Pool headers for pool page: fffffa800baad000

Pool page [ fffffa800baad000 ] is __inVALID.

Analyzing linked list...
[ fffffa800baad000 --> fffffa800baad460 (size = 0x460 bytes)]: Corrupt region

As, we can see, this wasn't the next pool entry which we were expecting, a driver has either overwritten the pool block or it could theoretically be due to bad RAM.

Code:

7: kd> dt nt!_POOL_HEADER fffffa800baad200
   +0x000 PreviousSize     : 0y00000000 (0)
   +0x000 PoolIndex        : 0y00000000 (0)
   +0x000 BlockSize        : 0y00000000 (0)
   +0x000 PoolType         : 0y00000000 (0)
   +0x000 Ulong1           : 0
   +0x004 PoolTag          : 0
   +0x008 ProcessBilled    : (null) 
   +0x008 AllocatorBackTraceIndex : 0
   +0x00a PoolTagHash      : 0

The fields within the Pool Header data structure for the next pool entry seem to be empty, which would suggest the structure is now corrupt.

---------------------------------------------------------------

Run Driver Verifier to scan for any corrupted drivers which may be causing problems, this program works by running various stress tests on drivers, in order to produce a BSOD which will locate the driver; run for least 24 hours:

• Driver Verifier - Enable and Disable

   Information

Additional Help - Using Driver Verifier to identify issues with Drivers

How many passes did you run MemTest86+ for?

im just running driver verifier now and will post the files if anything happens and if not ill run the memtest and see what comes up, cheers so far :)

Thanks, and with MemTest86+ run the test for least 9-10 passes :)

well i tried using memtest and when my computer boots it just bluescreens and then just reboots and says startup repair or start normally so i start normally and it just brings me back to the normal desktop no memtesting whatsoever :/ any advice?

Did Driver Verifier create any BSODs? What were the results of MemTest86+ previously?

ok just ran Memtest for 13 passes and got no errors and Driver verifier didnt seem to create any blue screens, ill turn it back on and check again however

I'll try running some hard drive diagnostics too -

Run some hard-drive diagnostics and follow these steps:

• Hard Drive Diagnostic Procedure

Find your hard-drive manufacturer and run their tests.

Additional Tests:

• SeaTools for DOS | Seagate
• CrystalDiskInfo - Software - Crystal Dew World

Post a screenshot of Crystal Disk Info summary:

• Screenshots and Files - Upload and Post in Seven Forums

writhziden said:

If you have an SSD, make sure the following are up to date:

• SSD firmware
• BIOS Version
• Chipset Drivers
• Hard disk controller drivers/SATA drivers
• If you have a Marvell IDE ATA/ATAPI device, make sure the drivers are up to date from the Intel site or Marvell site and not from your motherboard/vendor support site.

Check for any file system errors and bad sectors using Option #2 of:

• Disk Check

Use this command with Disk Check:

Code:

chkdsk C: /f /r

well it only seems to happen in cubase, i will try reinstalling it if that will help