Archived from groups: microsoft.public.windowsxp.help_and_support (
More info?)
You'll notice that your status code (0xC0000185)
has two possible causes. Do you have a SCSI disk (they aren't common on home computers).
Check the IRQ of the hard drive with the paging file and see if anything else is set to use it. Use device manager to do this (type it in help if you don't know what it is). Choose on the View menu Resources By <doesn't matter> and see if anything is paired up. It's normal for IRQs to be shared - you are looking for something to do with the hard drive or disk controller.
This is a general how to. I don't know that verifier and minidumps are useful here.
Type verifier in Start Run, follow the wizard but choose All Drivers. This will slow down your computer and cause more blue screen crashes but will pinpoint what is causing the crash (if the original error message didn't). Once you fix it you rerun verifier and turn it off.
If you can't start after enabling verifier
choose Last Known Good Configuration at the Failed Boot menu (which will
start without verifier).
You will be creating a crash dump file in c:\windows\minidump every blue screen. Make sure you are set to record minidumps (Small Memory Dumps) - type it in Help to see how.
Then
If you have the XP SP2 Security Update CD (else see
http://www.microsoft.com/whdc/Âdevtools/debugging/symbolpkg.mÂspx
)
Install symbols from <CD Drive Letter>:\SUPPORT\SYMBOLS
Download
http://www.microsoft.com/whdc/devtools/debugging/installx86.mspx
Load the crash dump file into windbg
and read what it says. You may need to tell it where the symbols are. Read it.
Type
!Analyze -v
into Windbg's command line.
(this will hopefully tell you the faulty component)
If the above is too technical then email the crash dump files to davidc @ mvps.org. Don't send me lots of them. Just the one from your last crash after you turn verifier on. And only one per mail.
You can look up specific details here
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/ddtools/hh/ddtools/BCIntro_ea8b9fd0-2d81-4a04-a7ed-c1c6a80bd501.xml.asp
If it indicates faulty memory might be the cause you can get a memory tester
here
http://oca.microsoft.com/en/wiÂndiag.asp
If it mentions a core windows system file, meaning it a MS fix is required,
upload a minidump to
http://oca.microsoft.com
Also try typing the main error code in Help while online (ie,
Stop 0x50
and also try in the 8 digit form
stop 0x00000050)
and if there are too many hits use a filename if available. Generally memory
addresses are different for each computer (as each computer has a different
mix of drivers) so parameters that are memory addresses aren't that useful for searching, but NTStatus codes are (plus you can look them up here http://cvs.sourceforge.net/viewcvs.py/mingw/w32api/include/ddk/ntstatus.h?rev=1.2).
Driver Development Tools: Windows DDK
Bug Check 0x7A: KERNEL_DATA_INPAGE_ERROR
The KERNEL_DATA_INPAGE_ERROR bug check has a value of 0x0000007A. This indicates that the requested page of kernel data from the paging file could not be read into memory.
Parameters
The four parameters listed in the message can have two possible meanings. If the first parameter is one, two, or three, the following definitions should be used:
Parameter Description
1 Lock type that was held (1, 2, or 3)
2 Error status (usually an I/O status code)
3 If Lock Type is 1 or 2: current process
If Lock Type is 3: virtual address
4 Virtual address that could not be paged into memory
Otherwise, use the following definitions:
Parameter Description
1 Page Table Entry (PTE) address
2 Error status (usually an I/O status code)
3 Virtual address
4 Virtual address that could not be paged into memory
Cause
Frequently, the cause of this error can be determined from the error status (Parameter 2). Some common status codes are:
a.. 0xC000009A, or STATUS_INSUFFICIENT_RESOURCES, is caused by lack of nonpaged pool resources. • 0xC000009C, or STATUS_DEVICE_DATA_ERROR, is typically due to bad blocks (sectors) on the hard disk.
b.. 0xC000009D, or STATUS_DEVICE_NOT_CONNECTED, indicates defective or loose cabling, termination, or the controller not seeing the hard disk.
c.. 0xC000016A, or STATUS_DISK_OPERATION_FAILED, is also caused by bad blocks (sectors) on the hard disk.
d.. 0xC0000185, or STATUS_IO_DEVICE_ERROR, is caused by improper termination or defective cabling on SCSI devices, or two devices attempting to use the same IRQ.
These codes are the most common ones for which specific causes have been determined. For information about other possible status codes that can be returned, see the file ntstatus.h in the Windows DDK.
Another common cause of this error message is defective hardware or failing RAM.
This bug check can also be caused by a virus infection.
Resolving the Problem
Resolving a bad block problem: An I/O status code of 0xC000009C or 0xC000016A normally indicates that the data could not be read from the disk due to a bad block (sector). If you can restart the system after the error, Autochk runs automatically and attempts to map the bad sector to prevent it’s further use.
If Autochk does not scan the hard disk for errors, you can manually launch the disk scanner. Run Chkdsk /f /r on the system partition. You must restart the system before the disk scan begins. If you cannot start the system due to the error, use the Recovery Console and run Chkdsk /r.
Warning If your system partition is formatted with the FAT file system, the long filenames used by Windows can be damaged if Scandisk or another MS-DOS-based hard disk tool is used to verify the integrity of your hard disk from MS-DOS. Always use the version of Chkdsk that matches your Windows version.
Resolving a defective hardware problem: If the I/O status is C0000185 and the paging file is on an SCSI disk, the disk cabling and SCSI termination should be checked for problems.
Resolving a failing RAM problem: Run the hardware diagnostics supplied by the system manufacturer, especially the memory scanner. For details on 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 pinpoint the device that is causing the error. Disabling memory caching of the BIOS might also resolve this error.
Make sure that the latest Windows Service Pack is installed.
If the preceding steps fail to 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: You should check your computer for viruses 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)
Send feedback on this topic. / Built on Thursday, February 13, 2003
See Also
Bug Check 0x77 (KERNEL_STACK_INPAGE_ERROR)
--
--------------------------------------------------------------------------------------------------
http://webdiary.smh.com.au/archives/_comment/001075.html
=================================================
"hallapena" <hallapena@discussions.microsoft.com> wrote in message news:01CE88C4-07CE-41E8-A603-F7F21E6CB9E5@microsoft.com...
>I am pretty ignorant when it somes to computers. As far as the verbage goes
> I didn't copy that but I got the numbers 0x0000007a(0xc07b8420, 0xc0000185,
> 0xf7084b02, 0x3f204860) My friend built the computer for me but he's in the
> states for 3 months. What should I do?
>
> "David Candy" wrote:
>
>> Is there a reason you did not post the whole message.
>>
>> --
>> --------------------------------------------------------------------------------------------------
>>
http://webdiary.smh.com.au/archives/_comment/001075.html
>> =================================================
>> "hallapena" <hallapena@discussions.microsoft.com> wrote in message news:93401C09-615C-4E44-9069-4FDC7AA2DCC8@microsoft.com...
>> >I don't know what is wrong with my computer it keeps restarting. My error
>> > messages on the BSOD are 0x0000007a kernal_data_image_error. I am pretty
>> > sure that I have a virus or something but nothing is being detected. Help,
>> > please!
>>
Facebook
Twitter
Instagram