Win7 x64 BSOD Error 0x7A

[dknight]

Greetings,

For the past couple of weeks I've been having this strange BSOD. I've tried doing RAM tests and scannow/chkdsk, It found some corrupted files, but could not repair all of them. I tried to analyze the minidump file, but I can't quite figure it out myself. On the .dmp file it mentions CLASSPNP.SYS, but on the actuall BSOD it mentions NTFS.SYS. I thought about a bad page file, or drive controller issues, but I'm not sure.

The BSOD is very random. I might get it today once, then not get it tomorrow or the next day, then get it again on the day after that. Hardware seems to work quite well with no slowdown until the sudden blue screen. I can play graphic-intensive games fine. I rather get an opinion from an expert before I make drastic changes that might mess up my system while troubleshooting.

Thanks in advance!

--------------------------------
Asus P6X58D-E
Intel i7 950
Corsair Dominator 6GB
GTX460 SLI
Crucal SSD C300 SATA-III 6GB/s 64GB (OS)
WD Velociraptor SATA-III 6GB/s 600GB
Windows 7 64-bit

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

KERNEL_DATA_INPAGE_ERROR (7a)
The requested page of kernel data could not be read in. Typically caused by
a bad block in the paging file or disk controller error. Also see
KERNEL_STACK_INPAGE_ERROR.
If the error status is 0xC000000E, 0xC000009C, 0xC000009D or 0xC0000185,
it means the disk subsystem has experienced a failure.
If the error status is 0xC000009A, then it means the request failed because
a filesystem failed to make forward progress.
Arguments:
Arg1: 0000000000000020, lock type that was held (value 1,2,3, or PTE address)
Arg2: ffffffffc000009d, error status (normally I/o status code)
Arg3: fffffa8006e83078, current process (virtual address for lock type 3, or PTE)
Arg4: 0000000000000000, virtual address that could not be in-paged (or PTE contents if arg1 is a PTE address)

Debugging Details:
------------------


ERROR_CODE: (NTSTATUS) 0xc000009d - STATUS_DEVICE_NOT_CONNECTED

DISK_HARDWARE_ERROR: There was error with disk hardware

BUGCHECK_STR: 0x7a_c000009d

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: System

CURRENT_IRQL: 1

LAST_CONTROL_TRANSFER: from fffff80003707bec to fffff800036cff00

STACK_TEXT:
fffff880`0aa35558 fffff800`03707bec : 00000000`0000007a 00000000`00000020 ffffffff`c000009d fffffa80`06e83078 : nt!KeBugCheckEx
fffff880`0aa35560 fffff800`036b9e67 : fffffa80`06e83010 fffffa80`c000009d fffff880`00000000 fffffa80`06e830a8 : nt! ?? ::FNODOBFM::`string'+0x4c830
fffff880`0aa35620 fffff800`036ac92f : fffffa80`05516680 fffffa80`055166d0 fffffa80`00000002 fffff880`05159000 : nt!IopCompletePageWrite+0x57
fffff880`0aa35650 fffff800`036acce7 : fffffa80`05a6b450 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDeliverApc+0x1d7
fffff880`0aa356d0 fffff880`01169990 : fffffa80`05a6b450 00000000`00000004 00000000`00000000 00000000`00000000 : nt!KiApcInterrupt+0xd7
fffff880`0aa35860 fffff880`0116efc4 : fffffa80`061cee10 fffffa80`059bc880 fffffa80`05a6b450 fffffa80`061cee10 : SCSIPORT!ScsiPortFdoDispatch+0x390
fffff880`0aa358e0 fffff880`01ada445 : 00000000`00000000 00000000`00000008 fffffa80`05a6b330 0000000a`97f23000 : SCSIPORT!ScsiPortPdoScsi+0x214
fffff880`0aa35910 fffff880`01ada695 : fffffa80`06d83010 fffffa80`063b9050 00000000`00020000 fffff880`00000001 : CLASSPNP!ServiceTransferRequest+0x355
fffff880`0aa359b0 fffff880`0100e0af : fffffa80`07dc2c60 00000000`00000100 fffffa80`07dc2e08 fffffa80`062362ee : CLASSPNP!ClassReadWrite+0xd5
fffff880`0aa35a00 fffff880`00f3212c : fffffa80`069fec20 fffffa80`07dc2c60 fffffa80`07dc2c60 fffff880`00f32010 : partmgr!PmGlobalDispatch+0x9f
fffff880`0aa35a30 fffff880`01a8a2ca : 00000000`00000100 fffffa80`06bd5a90 fffffa80`07dc2c60 fffffa80`078c03f0 : volmgr!VmReadWrite+0x11c
fffff880`0aa35a70 fffff880`01a8a54c : fffffa80`06bd5a90 00000000`00a91a43 00000000`00a91943 fffff880`00e090fb : fvevol!FveReadWrite+0x52
fffff880`0aa35ab0 fffff880`01a8a5a3 : fffffa80`06bd6d90 00000000`000a0045 00000000`00000200 00000000`00000000 : fvevol!FveFilterRundownReadWrite+0x1dc
fffff880`0aa35b10 fffff880`00e0a13d : 00000000`00000000 00000000`00000001 00000000`00000000 00000000`00000021 : fvevol!FveFilterRundownWrite+0x2f
fffff880`0aa35b40 fffff880`00e0947d : fffffa80`06bd6d90 fffffa80`07dc2c60 00000000`00000002 fffff880`00e0947d : rdyboost!SmdProcessReadWrite+0xc8d
fffff880`0aa35cb0 fffff880`00d8d108 : fffffa80`07dc2c60 fffff880`035d9a30 fffffa80`07dc2f28 00000000`00000000 : rdyboost!SmdDispatchReadWrite+0xd9
fffff880`0aa35ce0 fffff880`0141754a : fffff880`035d9a30 fffffa80`05516680 00000000`00000000 fffffa80`0911f060 : volsnap!VolsnapWriteFilter+0xf8
fffff880`0aa35d30 fffff800`036c7d87 : fffff880`0a650690 00000000`00007f00 00000000`00000001 00000000`02f2fdd4 : Ntfs!NtfsStorageDriverCallout+0x16
fffff880`0aa35d60 fffff800`036c7d41 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KySwitchKernelStackCallout+0x27
fffff880`035d97a0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSwitchKernelStackContinue


STACK_COMMAND: kb

FOLLOWUP_IP:
CLASSPNP!ServiceTransferRequest+355
fffff880`01ada445 85c0 test eax,eax

SYMBOL_STACK_INDEX: 7

SYMBOL_NAME: CLASSPNP!ServiceTransferRequest+355

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: CLASSPNP

IMAGE_NAME: CLASSPNP.SYS

DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc11e

FAILURE_BUCKET_ID: X64_0x7a_c000009d_CLASSPNP!ServiceTransferRequest+355

BUCKET_ID: X64_0x7a_c000009d_CLASSPNP!ServiceTransferRequest+355

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

 

[Route44]

It would be helpful if we could read the minidump files for ourselves.

How to find and post your Minidump Files:

My Computer > C Drive > Windows Folder > Minidump Folder > Minidump Files.

It is these files that we need (not the folder). Attach to your next post the five most recent dumps. Notice the Manage Attachments button at the bottom when you go to post the next time. You can Zip up to five files per Zip; if you only have one or two you don’t need to zip them, just attach as is. Please do us a favor and don’t Zip each one individually.

 

[dknight]

The file was over 200kb so I didn't include it initially. I had to zip it individually unfortunately. I would have more .dmp files but the BSOD often restarted my computer without finishing the process of creating the file. This one is the only one I have. Thanks!

 

[Route44]

Nothing definitive was cited. Have you been infected at all recently?

What RAM tests did you do?

 

[dknight]

I ran memtest v4.20 and after about 35mins it passed the test with no errors. I have COMODO Security Suite so as far as I know my system is clean. I ran a scan 2 days ago and the only thing I found was a adware item in the temp folder.

There may be another way to check if I am infected, but I am unaware of it (if COMODO alone isn't enough).

 

[Route44]

Memtest needs to run for a minimum of 7 Passes and the more after 7 the better. Many people will start it and then go to bed checking it the next day.

 

[dknight]

Hmmm, I might as well take advantage of the time and start memtest before going to bed right now. I will post the results tomorrow. Thanks.

 

[dknight]

This morning after I woke up Memtest86+ was on its 11th pass. All previous passes showed no errors after a little more of 10hrs of testing. The weird thing now is the OS doesn't want to boot. After showing the Windows logo, a BSOD appears for probably less than half a second, too fast to actually read what it says, and then goes away and reboots the system.

I could hear a small powering up sound followed by a clicking sound coming from the SSD. But when I checked the BIOS both the SSD and the Velociraptor show as "undetected" by the system. This is what's strange because I doubt both drives died at the same time by coincidence. I tried loading Acronis to see if I could backup some data and it said it could not detect any hard drives on my system. So I was thinking if it could be the motherboard, but then it wouldn't explain the strange sounds coming from the SSD.

I bought all parts of my system back in August, so they still may be under warranty. But first I need to know the cause of the problem so I know what to RMA exactly.

I'm so confused. o.O

Edit: The Velociraptor was the one making the sound, not the SSD.

 

[dknight]

I did further testing and Windows detects my drives when I load the Windows OS disc for a repair or new install. It took longer than usual to load, but it did after 2-3 mins. Right now it is "attempting to repair" since it said "no OS files found on drive" as the cause of the problems. But that is just plain strange since it even let me browse my C: drive and everything looked to be in order.

Edit: After attempting to repair it says "Startup repair cannot repair this computer automatically." I'll try a new install and see it goes well. Still it would explain the strange sounds from earlier. How would the drive lose the OS files anyway? It was running fine yesterday.

 

[dknight]

Before the new install I update the motherboard BIOS and it did boot fine, but didn't detect the Velociraptor. The BIOS still does not detect any drives. If I unplug the Raptor , the system boots fast and no problems. If it's plugged, sometimes it doesn't boot or boots very slow. I guess it's damaged, but still doesn't explain why the none can be detected by the BIOS, before of after the flash.

 

[Route44]

The veliceraptor could be bad. Have you ever run a harddrive diagnostics before?

 

[dknight]

I didn't before. I occasionally used the Windows error-checking tool but that's it. Right now I'm trying to use WD's hard drive diagnostic tool, but unfortunately does not find the drive. I can still hear the clicking sounds, so it's safe to safe it is damaged, just not entirely dead... yet.

Trying to see if I can salvage the data as a last resort before sending it in for warranty. But if the OS doesn't see the disc, I'm not sure how I'm going to do that, if possible at all.

 

[Route44]

Slave that drive into another PC and see if you can access this drive through said system.

You may be able to access your data.

 

[dknight]

I will try tomorrow at work with another PC and and also with a IDE/SATA to USB enclosure to see if I have any luck. About the SSD not being recognized in the BIOS, I did some research and updated the Marvell drives and messed a little with the AHCI configuration. It's not displayed as a regular SATA device in the BIOS, but on the other settings and on the Marvell BIOS it is displayed.

In any case, I appreciate your assistance. It is easier to troubleshoot with someone else than alone. Thanks.

 

[Route44]

You're welcome and thanks for getting back to us. You are one of many that I have been reading about with issues pertaining to SSD and the Marvell drives.

On the SSD I think I'll wait at least until the 5th generation before seriously considering to purchase.