seasonic Posted June 5, 2011 Share Posted June 5, 2011 Getting this BSOD...Didnt install anything new AFAIK so this just happened out of nowhere. Happens when I leave my PC. After returning after a few hours, this comes up. Help? Thanks :) Link to comment Share on other sites More sharing options...
Tews Posted June 5, 2011 Share Posted June 5, 2011 please navigate to c:/windows/minidump, zip up any .dmp files and attach them to your next post for analysis ... ;) Link to comment Share on other sites More sharing options...
Farstrider Posted June 5, 2011 Share Posted June 5, 2011 1.6MB Image!! :huh: 0xC000009D, or STATUS_DEVICE_NOT_CONNECTED, indicates defective or loose cabling, termination, or that the controller does not see the hard disk. Another common cause of this error message is defective hardware or failing RAM. Check that all the adapter cards in the computer are properly seated. Use an ink eraser or an electrical contact treatment, available at electronics supply stores, to ensure adapter card contacts are clean. KERNEL_DATA_INPAGE_ERROR STOP: 0x0000007A Windows could not read a file from the disk that is supposed to be there. It may indicate the hard disk has bad sectors, hardware (disk, controller, memory) issues, a virus infection or a bug in a device driver. Link to comment Share on other sites More sharing options...
Tews Posted June 5, 2011 Share Posted June 5, 2011 WinDbg Help File Entry:The KERNEL_DATA_INPAGE_ERROR bug check has a value of 0x0000007A. This bug check indicates that the requested page of kernel data from the paging file could not be read into memory. Parameters The four parameters that are listed in the message can have three possible meanings. If the first parameter is 1 or 2, or 3 and the third parameter is 0, the parameters have the following definitions. Parameter Description 1 The lock type that was held (1, 2, or 3) 2 The error status (usually an I/O status code) 3 If Lock Type is 1: the current process If Lock Type is 2 or 3: 0 4 The virtual address that could not be paged into memory If the first parameter is 3 (and the third parameter is nonzero) or 4, the parameters have the following definitions. Parameter Description 1 The lock type that was held (3 or 4) 2 The error status (typically an I/O status code) 3 The address of the InPageSupport structure 4 The faulting address Otherwise, the parameters have the following definitions. Parameter Description 1 The address of the page table entry (PTE) 2 The error status (usually an I/O status code) 3 The PTE contents 4 The faulting address Cause Frequently, you can determine the cause of the KERNEL_DATA_INPAGE_ERROR bug check from the error status (Parameter 2). Some common status codes include the following: 0xC000009A, or STATUS_INSUFFICIENT_RESOURCES, indicates a lack of nonpaged pool resources. 0xC000009C, or STATUS_DEVICE_DATA_ERROR, typically indicates bad blocks (sectors) on the hard disk. 0xC000009D, or STATUS_DEVICE_NOT_CONNECTED, indicates defective or loose cabling, termination, or that the controller does not see the hard disk. 0xC000016A, or STATUS_DISK_OPERATION_FAILED, indicates bad blocks (sectors) on the hard disk. 0xC0000185, or STATUS_IO_DEVICE_ERROR, indicates improper termination or defective cabling on SCSI devices or that two devices are trying to use the same IRQ. These status codes are the most common ones that have specific causes. For more information about other possible status codes that can be returned, see the Ntstatus.h file in the Microsoft Windows Driver Kit (WDK). Another common cause of this error message is defective hardware or failing RAM. A virus infection can also cause this bug check. Resolving the Problem Resolving a bad block problem: An I/O status code of 0xC000009C or 0xC000016A typically indicates that the data could not be read from the disk because of a bad block (sector). If you can restart the computer after the error, Autochk runs automatically and attempts to map the bad sector to prevent it from being used anymore. If Autochk does not scan the hard disk for errors, you can manually start the disk scanner. Run Chkdsk /f /r on the system partition. You must restart the computer before the disk scan begins. If you cannot start the computer because of the error, use the Recovery Console and run Chkdsk /r. Warning If your system partition is formatted with the FAT file system, the long file names that the Windows operating system uses might be damaged if you use Scandisk or another MS-DOS-based hard disk tool to verify the integrity of your hard disk from MS-DOS. Always use the version of Chkdsk that matches your version of Windows. Resolving a defective hardware problem: If the I/O status is C0000185 and the paging file is on an SCSI disk, check the disk cabling and SCSI termination for problems. Resolving a failing RAM problem: Run the hardware diagnostics that the system manufacturer supplies, especially the memory scanner. For more information about these procedures, see the owner's manual for your computer. Check that all the adapter cards in the computer are properly seated. Use an ink eraser or an electrical contact treatment, available at electronics supply stores, to ensure adapter card contacts are clean. Check the System Log in Event Viewer for additional error messages that might help identify the device that is causing the error. You can also disable memory caching of the BIOS to try to resolve this error. Make sure that the latest Windows Service Pack is installed. If the preceding steps do not resolve the error, take the system motherboard to a repair facility for diagnostic testing. A crack, a scratched trace, or a defective component on the motherboard can cause this error. Resolving a virus infection: Check your computer for viruses by using any up-to-date, commercial virus scanning software that examines the Master Boot Record of the hard disk. All Windows file systems can be infected by viruses. See Also Bug Check 0x77 (KERNEL_STACK_INPAGE_ERROR) WinDbg Output Example: 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: 8dd047f8, lock type that was held (value 1,2,3, or PTE address) Arg2: c0000056, error status (normally i/o status code) Arg3: 2d113864, current process (virtual address for lock type 3, or PTE) Arg4: 902f90ba, virtual address that could not be in-paged (or PTE contents if arg1 is a PTE address) source Link to comment Share on other sites More sharing options...
George P Global Moderator Posted June 5, 2011 Global Moderator Share Posted June 5, 2011 I'm going to take a guess by it seems to be pagefile related and thus maybe even HDD? Did you run any hdd checkers etc? Link to comment Share on other sites More sharing options...
seasonic Posted June 5, 2011 Author Share Posted June 5, 2011 please navigate to c:/windows/minidump, zip up any .dmp files and attach them to your next post for analysis ... ;) Attached :) 060511-22354-01.zip I'm going to take a guess by it seems to be pagefile related and thus maybe even HDD? Did you run any hdd checkers etc? Could you recommend one to test correctly? :) Link to comment Share on other sites More sharing options...
seasonic Posted June 5, 2011 Author Share Posted June 5, 2011 No information? The copy/paste is nice and thanks but I thought from the dump more information would be given :) Link to comment Share on other sites More sharing options...
seasonic Posted June 6, 2011 Author Share Posted June 6, 2011 BSOD again. I ran chkdsk on both my RAID5 volume and my system drive. Link to comment Share on other sites More sharing options...
Seizure1990 Posted June 7, 2011 Share Posted June 7, 2011 To test (and repair your HDD, if needed), you can try http://www.hdat2.com/ Run the .exe provided. It will create an .ISO which you can burn to CD and boot off of. Link to comment Share on other sites More sharing options...
seasonic Posted June 7, 2011 Author Share Posted June 7, 2011 Another just about a hour ago To test (and repair your HDD, if needed), you can try http://www.hdat2.com/ Run the .exe provided. It will create an .ISO which you can burn to CD and boot off of. Thanks :) Ill try as soon as I get a chance and Ill get back on this thread. Link to comment Share on other sites More sharing options...
seasonic Posted June 10, 2011 Author Share Posted June 10, 2011 3-4 more BSODs have popped up :( Link to comment Share on other sites More sharing options...
Southern Patriot Posted June 10, 2011 Share Posted June 10, 2011 3-4 more BSODs have popped up :( LIES I SAY!!!!1111oneoneone Everyone here knows that BSODs ended with XP!!!!! /requisite sarcastic post :D :D :D :D Link to comment Share on other sites More sharing options...
seasonic Posted June 10, 2011 Author Share Posted June 10, 2011 Your post was very helpful :( Link to comment Share on other sites More sharing options...
seasonic Posted June 11, 2011 Author Share Posted June 11, 2011 Using Intel's RAID software, I was able to scan/repair for errors and (for now) I havent seen a BSOD (I did this yesterday so). Lets see how this goes... Link to comment Share on other sites More sharing options...
Seizure1990 Posted June 11, 2011 Share Posted June 11, 2011 HDD errors can easily cause constant BSODing.* LIES I SAY!!!!1111oneoneone Everyone here knows that BSODs ended with XP!!!!! including on Macs /requisite defense post ;) Anyways, the last time I saw a fatal error on a Mac, the screen just went completely blue, but otherwise blank (Ie, a BSOD :p). What happened to Kernel Panic? *Does the RAID software scan for only filesystem errors, or does it also run a surface scan? Link to comment Share on other sites More sharing options...
Eorxroa Akbar Posted June 12, 2011 Share Posted June 12, 2011 try bsod error my windows 7 :unsure: Link to comment Share on other sites More sharing options...
The_Decryptor Veteran Posted June 12, 2011 Veteran Share Posted June 12, 2011 I was getting this exact same error on my new computer build, in that case the hard drive was dying (actually caused by a bad chip on the mobo, which killed the drives) Link to comment Share on other sites More sharing options...
epk Posted June 18, 2011 Share Posted June 18, 2011 Just to check, you could swtich the SATA port your HDD is using. One of my ports doesn't work well and it was giving me errors like that. Or could be the hard drive, like others said. You could use HDTune to test it. Link to comment Share on other sites More sharing options...
Recommended Posts