Bug Check Code 0x7A: http://msdn.microsoft.com/en-us/library/ff559211(v=VS.85).aspx Please use Microsoft Skydrive to upload dump files (c:\windows\minidumps). Once done, post a link here. You can also contact Microsoft CSS. This posting is provided "AS IS" with no warranties or guarantees , and confers no rights. Microsoft Student Partner 2010 / 2011 Microsoft Certified Professional Microsoft Certified Systems Administrator: Security Microsoft Certified Systems Engineer: Security Microsoft Certified Technology Specialist: Windows Server 2008 Active Directory, Configuration Microsoft Certified Technology Specialist: Windows Server 2008 Network Infrastructure, Configuration Microsoft Certified Technology Specialist: Windows Server 2008 Applications Infrastructure, Configuration Microsoft Certified Technology Specialist: Windows 7, Configuring Microsoft Certified IT Professional: Enterprise Administrator Microsoft Certified IT Professional: Server Administrator Microsoft Certified Trainer

Since getting my SSD (ADATA S596 Turbo 128G) a few months ago, I've been seeing occasional (and increasingly frequent) kernel_data_inpage_error crashes immediately after the PC resumes from standby (S3). The crashes are almost always first thing in the morning (after a few hours of standby; the PC wakes for a scheduled daily backup at 3am, then sleeps again until I wake it, which is when the occasional crashes occur). Additionally, there have been a few boot errors where the BIOS POST fails to recognize the SSD at all, and a few other times that the BIOS POST reports a SMART error for the SSD. The (albeit rare) recognition failure at boot-time is the main reason I suspect that the sleep-resume errors are also due to the SSD not coming back online promptly. (My other drives have never failed to be recognized at boot time.) The system is very stable except for the occasional morning-wakeup crashes (and the few boot failures). The SSD is my boot disk. It's about half full. Running chkdsk at boot time shows no errors (all my drives pass chkdsk with no errors). Windows Disk Management reports all drives healthy. I've run memtest86+ and the Prime95 torture test for hours; they show no errors. CoreTemp reports reasonable temperatures. I've re-seated all components and connectors, and replaced the SSD's SATA cable, all to no avail. The SSD has the latest available firmware (100730). I tried the hotfix at kb/977178 but it won't install (says it's not applicable, presumably superseded by Win7 SP1). The PC can go for a few weeks without any crashes, followed by a spate of morning-wakeup crashes several times per week. When the crashes occur, the PC always wakes and properly shows the user-unlock screen; but when I then enter my password, the red disk-activity light on the PC goes on solidly for about ten seconds, and then the kernel_data_inpage_error occurs. There is no dump or minidump file. The BSOD "technical details" on one crash are: *** STOP: 0x0000007A (0xFFFFF6FC4005FA30, 0xFFFFFFFFC0000056, 0x000000013AE7BBE0, 0xFFFFF8800BF4600) Should I just try an RMA for the drive? Is this problem likely to be a design flaw (or a firmware flaw) that will still be present in a replacement? Are any alternative causes likely, despite the above evidence? system details: GA-X58A-UD3Rr2.0(FF) AntecEA650 i7-950(3.06GHz) OCZ3G1600LV6GK(6GB) GTX260(280.26 WHQL) ADATA:S596TurboSSD128GB(100730), WDGreenPowerSATA(2TB, 1TB, 1TB) GGW-H20L(YL05) WinTV1600-1178 CoolerMasterHyper212+ Dell3007WFP(2560x1600) Win7Pro6.1.7601SP1x64 Avast6.0.1289

Bug Check Code 0x7A: http://msdn.microsoft.com/en-us/library/ff559211(v=VS.85).aspx Please use Microsoft Skydrive to upload dump files (c:\windows\minidumps). Once done, post a link here. You can also contact Microsoft CSS. This posting is provided "AS IS" with no warranties or guarantees , and confers no rights. Microsoft Student Partner 2010 / 2011 Microsoft Certified Professional Microsoft Certified Systems Administrator: Security Microsoft Certified Systems Engineer: Security Microsoft Certified Technology Specialist: Windows Server 2008 Active Directory, Configuration Microsoft Certified Technology Specialist: Windows Server 2008 Network Infrastructure, Configuration Microsoft Certified Technology Specialist: Windows Server 2008 Applications Infrastructure, Configuration Microsoft Certified Technology Specialist: Windows 7, Configuring Microsoft Certified IT Professional: Enterprise Administrator Microsoft Certified IT Professional: Server Administrator Microsoft Certified Trainer

Thanks, but unfortunately no dump files were produced. However, I see now that the second BSOD parameter (0xFFFFFFFFC0000056) corresponds, according to Ntstatus.h, to STATUS_DELETE_PENDING: "A non-close operation has been requested of a file object that has a delete pending." Not sure what to make of that but I'll see if I can find anything.

Hi, “Thanks, but unfortunately no dump files were produced.” Please enable debugging information in System Properties. 1. Click Start button, go to Control Panel -> System. 2. Click Advanced system setting. 3. Select Advanced tag, and click “Settings… “ under Startup and Recovery. 4. Select Small memory dump(128K), then check the small dump directory. Bug Check 0x7A: KERNEL_DATA_INPAGE_ERROR Stop 0x7A can be caused by bad sectors in the virtual memory paging file, disk controller error, virus infection, or memory hardware problems. In extremely rare cases, depleted non-paged pool resources can cause this error. To narrow down this kind of problem, please use “CHKDSK /F” command to check the disk. Another cause of Stop 0x7A is defective, malfunctioning, or failed memory hardware, such as memory modules, L2 SRAM cache, or video adapter RAM. If you added new hardware recently, remove and replace the hardware to determine whether it is causing or contributing to the problem. Run Windows Memory Diagnostics to check the memory. Also check the hardware manufacturer’s website for updates to disk adapter firmware or derivers that improve compatibility. Hope that helpsPlease remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Thanks, but unfortunately no dump files were produced. However, I see now that the second BSOD parameter (0xFFFFFFFFC0000056) corresponds, according to Ntstatus.h, to STATUS_DELETE_PENDING: "A non-close operation has been requested of a file object that has a delete pending." Not sure what to make of that but I'll see if I can find anything. As no dump files are generated, I would suspect hardware problems. For that, consider contacting your manufacturer Technical Support. This posting is provided "AS IS" with no warranties or guarantees , and confers no rights. Microsoft Student Partner 2010 / 2011 Microsoft Certified Professional Microsoft Certified Systems Administrator: Security Microsoft Certified Systems Engineer: Security Microsoft Certified Technology Specialist: Windows Server 2008 Active Directory, Configuration Microsoft Certified Technology Specialist: Windows Server 2008 Network Infrastructure, Configuration Microsoft Certified Technology Specialist: Windows Server 2008 Applications Infrastructure, Configuration Microsoft Certified Technology Specialist: Windows 7, Configuring Microsoft Certified IT Professional: Enterprise Administrator Microsoft Certified IT Professional: Server Administrator Microsoft Certified Trainer

Hi, “Thanks, but unfortunately no dump files were produced.” Please enable debugging information in System Properties. 1. Click Start button, go to Control Panel -> System. 2. Click Advanced system setting. 3. Select Advanced tag, and click “Settings… “ under Startup and Recovery. 4. Select Small memory dump(128K), then check the small dump directory. Bug Check 0x7A: KERNEL_DATA_INPAGE_ERROR Stop 0x7A can be caused by bad sectors in the virtual memory paging file, disk controller error, virus infection, or memory hardware problems. In extremely rare cases, depleted non-paged pool resources can cause this error. To narrow down this kind of problem, please use “CHKDSK /F” command to check the disk. Another cause of Stop 0x7A is defective, malfunctioning, or failed memory hardware, such as memory modules, L2 SRAM cache, or video adapter RAM. If you added new hardware recently, remove and replace the hardware to determine whether it is causing or contributing to the problem. Run Windows Memory Diagnostics to check the memory. Also check the hardware manufacturer’s website for updates to disk adapter firmware or derivers that improve compatibility. Hope that helpsPlease remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Thanks, but unfortunately no dump files were produced. However, I see now that the second BSOD parameter (0xFFFFFFFFC0000056) corresponds, according to Ntstatus.h, to STATUS_DELETE_PENDING: "A non-close operation has been requested of a file object that has a delete pending." Not sure what to make of that but I'll see if I can find anything. As no dump files are generated, I would suspect hardware problems. For that, consider contacting your manufacturer Technical Support. This posting is provided "AS IS" with no warranties or guarantees , and confers no rights. Microsoft Student Partner 2010 / 2011 Microsoft Certified Professional Microsoft Certified Systems Administrator: Security Microsoft Certified Systems Engineer: Security Microsoft Certified Technology Specialist: Windows Server 2008 Active Directory, Configuration Microsoft Certified Technology Specialist: Windows Server 2008 Network Infrastructure, Configuration Microsoft Certified Technology Specialist: Windows Server 2008 Applications Infrastructure, Configuration Microsoft Certified Technology Specialist: Windows 7, Configuring Microsoft Certified IT Professional: Enterprise Administrator Microsoft Certified IT Professional: Server Administrator Microsoft Certified Trainer

Hi, I wrote a post on troubleshooting this issue. Does your SSD vendor have any drive diagnostics that you can try, http://mikemstech.blogspot.com/2011/12/troubleshooting-0x0000007a.html-- Mike Burr Technology

Hi, I wrote a post on troubleshooting this issue. Does your SSD vendor have any drive diagnostics that you can try, http://mikemstech.blogspot.com/2011/12/troubleshooting-0x0000007a.html-- Mike Burr Technology

I recently purchased an ADATA mSATA SSD for my HP Elitebook 2740p and performed a clean install of Windows 8 RTM. The SSD is a "ADATA ASX300S3-256GM-C MSA" which they list on their website as the "XPG SX300". I also updated the drive to the latest firmware, 5.0.2a I also frequently experience the kernel_data_inpage_error crashes on Windows 8 after resuming from sleep, and the symptoms in the post above are exactly the same. The SSD is my boot disk. The Crash Dump analysis output (all the dumps are similar to this) shows the following: Loading Dump File [C:\Windows\Minidump\111512-10406-01.dmp] MODULE_NAME: nt FAULTING_MODULE: fffff80153400000 nt DEBUG_FLR_IMAGE_TIMESTAMP: 5063f8c8 ERROR_CODE: (NTSTATUS) 0xc00000c0 - This device does not exist. BUGCHECK_STR: 0x7a_c00000c0 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT CURRENT_IRQL: 0 LAST_CONTROL_TRANSFER: from fffff80153550a55 to fffff8015347ad40 STACK_TEXT: fffff880`08f9d448 fffff801`53550a55 : 00000000`0000007a fffff6fc`400092b8 ffffffff`c00000c0 00000001`3e6cf880 : nt+0x7ad40 fffff880`08f9d450 00000000`0000007a : fffff6fc`400092b8 ffffffff`c00000c0 00000001`3e6cf880 fffff880`01257000 : nt+0x150a55 fffff880`08f9d458 fffff6fc`400092b8 : ffffffff`c00000c0 00000001`3e6cf880 fffff880`01257000 00000000`00000204 : 0x7a fffff880`08f9d460 ffffffff`c00000c0 : 00000001`3e6cf880 fffff880`01257000 00000000`00000204 fffffa80`06c89330 : 0xfffff6fc`400092b8 fffff880`08f9d468 00000001`3e6cf880 : fffff880`01257000 00000000`00000204 fffffa80`06c89330 fffff801`5346d25a : 0xffffffff`c00000c0 fffff880`08f9d470 fffff880`01257000 : 00000000`00000204 fffffa80`06c89330 fffff801`5346d25a fffffa80`0c216698 : 0x00000001`3e6cf880 fffff880`08f9d478 00000000`00000204 : fffffa80`06c89330 fffff801`5346d25a fffffa80`0c216698 fffff801`5374fa01 : volmgrx fffff880`08f9d480 fffffa80`06c89330 : fffff801`5346d25a fffffa80`0c216698 fffff801`5374fa01 00010000`00000000 : 0x204 fffff880`08f9d488 fffff801`5346d25a : fffffa80`0c216698 fffff801`5374fa01 00010000`00000000 fffff801`00000000 : 0xfffffa80`06c89330 fffff880`08f9d490 fffffa80`0c216698 : fffff801`5374fa01 00010000`00000000 fffff801`00000000 fffff880`01257000 : nt+0x6d25a fffff880`08f9d498 fffff801`5374fa01 : 00010000`00000000 fffff801`00000000 fffff880`01257000 fffffa80`104be8b0 : 0xfffffa80`0c216698 fffff880`08f9d4a0 00010000`00000000 : fffff801`00000000 fffff880`01257000 fffffa80`104be8b0 ffffffff`ffffffff : nt+0x34fa01 fffff880`08f9d4a8 fffff801`00000000 : fffff880`01257000 fffffa80`104be8b0 ffffffff`ffffffff fffffa80`104be838 : 0x00010000`00000000 fffff880`08f9d4b0 fffff880`01257000 : fffffa80`104be8b0 ffffffff`ffffffff fffffa80`104be838 fffff6fc`400092b8 : 0xfffff801`00000000 fffff880`08f9d4b8 fffffa80`104be8b0 : ffffffff`ffffffff fffffa80`104be838 fffff6fc`400092b8 fffffa80`03bb46d0 : volmgrx fffff880`08f9d4c0 ffffffff`ffffffff : fffffa80`104be838 fffff6fc`400092b8 fffffa80`03bb46d0 fffffa80`104be768 : 0xfffffa80`104be8b0 fffff880`08f9d4c8 fffffa80`104be838 : fffff6fc`400092b8 fffffa80`03bb46d0 fffffa80`104be768 fffffa80`03bb46d0 : 0xffffffff`ffffffff fffff880`08f9d4d0 fffff6fc`400092b8 : fffffa80`03bb46d0 fffffa80`104be768 fffffa80`03bb46d0 fffff6fc`400092b8 : 0xfffffa80`104be838 fffff880`08f9d4d8 fffffa80`03bb46d0 : fffffa80`104be768 fffffa80`03bb46d0 fffff6fc`400092b8 fffff801`5374fa80 : 0xfffff6fc`400092b8 fffff880`08f9d4e0 fffffa80`104be768 : fffffa80`03bb46d0 fffff6fc`400092b8 fffff801`5374fa80 00000000`00000002 : 0xfffffa80`03bb46d0 fffff880`08f9d4e8 fffffa80`03bb46d0 : fffff6fc`400092b8 fffff801`5374fa80 00000000`00000002 fffffa80`104be740 : 0xfffffa80`104be768 fffff880`08f9d4f0 fffff6fc`400092b8 : fffff801`5374fa80 00000000`00000002 fffffa80`104be740 fffffa80`0c216200 : 0xfffffa80`03bb46d0 fffff880`08f9d4f8 fffff801`5374fa80 : 00000000`00000002 fffffa80`104be740 fffffa80`0c216200 00000000`00000002 : 0xfffff6fc`400092b8 fffff880`08f9d500 00000000`00000002 : fffffa80`104be740 fffffa80`0c216200 00000000`00000002 fffff880`08f9d5a0 : nt+0x34fa80 fffff880`08f9d508 fffffa80`104be740 : fffffa80`0c216200 00000000`00000002 fffff880`08f9d5a0 fffff801`5346c2a3 : 0x2 fffff880`08f9d510 fffffa80`0c216200 : 00000000`00000002 fffff880`08f9d5a0 fffff801`5346c2a3 00000000`00000002 : 0xfffffa80`104be740 fffff880`08f9d518 00000000`00000002 : fffff880`08f9d5a0 fffff801`5346c2a3 00000000`00000002 fffff880`08f9d5b0 : 0xfffffa80`0c216200 fffff880`08f9d520 fffff880`08f9d5a0 : fffff801`5346c2a3 00000000`00000002 fffff880`08f9d5b0 fffff801`5374fa80 : 0x2 fffff880`08f9d528 fffff801`5346c2a3 : 00000000`00000002 fffff880`08f9d5b0 fffff801`5374fa80 fffff880`08f9d5a0 : 0xfffff880`08f9d5a0 fffff880`08f9d530 00000000`00000002 : fffff880`08f9d5b0 fffff801`5374fa80 fffff880`08f9d5a0 fffffa80`07e93620 : nt+0x6c2a3 fffff880`08f9d538 fffff880`08f9d5b0 : fffff801`5374fa80 fffff880`08f9d5a0 fffffa80`07e93620 fffffa80`0c216200 : 0x2 fffff880`08f9d540 fffff801`5374fa80 : fffff880`08f9d5a0 fffffa80`07e93620 fffffa80`0c216200 00000ee6`fd5d2006 : 0xfffff880`08f9d5b0 fffff880`08f9d548 fffff880`08f9d5a0 : fffffa80`07e93620 fffffa80`0c216200 00000ee6`fd5d2006 00000000`00000000 : nt+0x34fa80 fffff880`08f9d550 fffffa80`07e93620 : fffffa80`0c216200 00000ee6`fd5d2006 00000000`00000000 00000000`00102000 : 0xfffff880`08f9d5a0 fffff880`08f9d558 fffffa80`0c216200 : 00000ee6`fd5d2006 00000000`00000000 00000000`00102000 fffff880`01257000 : 0xfffffa80`07e93620 fffff880`08f9d560 00000ee6`fd5d2006 : 00000000`00000000 00000000`00102000 fffff880`01257000 fffffa80`07e97010 : 0xfffffa80`0c216200 fffff880`08f9d568 00000000`00000000 : 00000000`00102000 fffff880`01257000 fffffa80`07e97010 00010000`00001e88 : 0x00000ee6`fd5d2006 STACK_COMMAND: kb FOLLOWUP_IP: nt+7ad40 fffff801`5347ad40 48894c2408 mov qword ptr [rsp+8],rcx SYMBOL_STACK_INDEX: 0 SYMBOL_NAME: nt+7ad40 FOLLOWUP_NAME: MachineOwner IMAGE_NAME: ntoskrnl.exe BUCKET_ID: WRONG_SYMBOLS Followup: MachineOwner