BSOD - Windows DeBugger log

I did some further research into BSOD it was recommended to download & run Windows DeBugger.
I did & here is the log, I was hoping someone could help me discern it:
Thank you


Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\WINDOWS\Minidump\Mini111110-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows XP Kernel Version 2600 (Service Pack 3) MP (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 2600.xpsp_sp3_gdr.100427-1636
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
Debug session time: Thu Nov 11 15:05:03.359 2010 (UTC + 13:00)
System Uptime: 0 days 6:10:28.281
Loading Kernel Symbols
.................................................. .............
...............................................
Loading User Symbols
Loading unloaded module list
....................
************************************************** *****************************
* *
* Bugcheck Analysis *
* *
************************************************** *****************************

Use !analyze -v to get detailed debugging information.

BugCheck F4, {3, 8a27ada0, 8a27af14, 805d2954}

unable to get nt!KiCurrentEtwBufferOffset
unable to get nt!KiCurrentEtwBufferBase
Probably caused by : hardware_disk ( +fc )

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

3: kd> !analyze -v
************************************************** *****************************
* *
* Bugcheck Analysis *
* *
************************************************** *****************************

CRITICAL_OBJECT_TERMINATION (f4)
A process or thread crucial to system operation has unexpectedly exited or been
terminated.
Several processes and threads are necessary for the operation of the
system; when they are terminated (for any reason), the system can no
longer function.
Arguments:
Arg1: 00000003, Process
Arg2: 8a27ada0, Terminating object
Arg3: 8a27af14, Process image file name
Arg4: 805d2954, Explanatory message (ascii)

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

unable to get nt!KiCurrentEtwBufferOffset
unable to get nt!KiCurrentEtwBufferBase

PROCESS_OBJECT: 8a27ada0

IMAGE_NAME: hardware_disk

DEBUG_FLR_IMAGE_TIMESTAMP: 0

FAULTING_MODULE: 00000000

PROCESS_NAME: csrss.exe

EXCEPTION_RECORD: a732f9d8 -- (.exr 0xffffffffa732f9d8)
ExceptionAddress: 75b7b3b9
ExceptionCode: c0000006 (In-page I/O error)
ExceptionFlags: 00000000
NumberParameters: 3
Parameter[0]: 00000008
Parameter[1]: 75b7b3b9
Parameter[2]: c000000e
Inpage operation failed at 75b7b3b9, due to I/O error c000000e

EXCEPTION_CODE: (NTSTATUS) 0xc0000006 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The required data was not placed into memory because of an I/O error status of "0x%08lx".

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

ERROR_CODE: (NTSTATUS) 0xc0000006 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The required data was not placed into memory because of an I/O error status of "0x%08lx".

EXCEPTION_PARAMETER1: 00000008

EXCEPTION_PARAMETER2: 75b7b3b9

EXCEPTION_PARAMETER3: c000000e

IO_ERROR: (NTSTATUS) 0xc000000e - A device which does not exist was specified.

EXCEPTION_STR: 0xc0000006_c000000e

FAULTING_IP:
+fc
75b7b3b9 ?? ???

BUGCHECK_STR: 0xF4_IOERR_C000000E

FOLLOWUP_IP:
+fc
75b7b3b9 ?? ???

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: hardware_disk

SYMBOL_NAME: +fc

STACK_COMMAND: kb

FAILURE_BUCKET_ID: 0xF4_IOERR_C000000E_+fc

BUCKET_ID: 0xF4_IOERR_C000000E_+fc

Followup: MachineOwner
 

Question Info


Last updated March 30, 2018 Views 1,321 Applies to:

Hi,

·        What is the exact Blue screen error message that you encounter?

 

Follow article and try the steps in Method 2 in the article mentioned below.

How to troubleshoot hardware and software driver problems in Windows XP 

http://support.microsoft.com/kb/322205#m2

 

For assistance with analyzing the dump file you may also suggest post in the following forum:

 Windows XP Service Pack 3 (SP3)

http://social.technet.microsoft.com/Forums/en-us/itproxpsp/threads

 

Thank you and Regards.           

Thahaseena M
Microsoft Answers Support Engineer.
Visit our
Microsoft Answers Feedback Forum and let us know what you think.

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

That dump inclues such phrases as:

Probably caused by : hardware_disk ( +fc )

MODULE_NAME: hardware_disk 

So at first glance, it looks like some kind of hardware error.

Have you just had one BSOD, are you just seeming to get them randomly?

Is there any particular thing you can think of that you know will generate a BSOD (like playing a games, watching videos, etc.)?  

If you know how to induce a BSOD any time you want, if you make some adjustments, you will know for sure that the problem has been fixed - when you are unable to reproduce the BSOD using your known failure scenario.

It is good to have the debugger installed for troubleshooting, but let's get some general information and use a different method to see the crash dump information and see if it is a little easier to interpret:

 

Please provide additional information about your system:

What is your system make and model?

What is your XP version and Service Pack?

Describe your current antivirus and anti malware situation:  McAfee, Norton, Spybot, AVG, Avira!, MSE, Defender, ZoneAlarm, PC Tools, Comodo, etc.

Does the afflicted system have a working CD/DVD drive?

Do you have a genuine bootable XP installation CD (this is not the same as any Recovery CDs that came with your system)?

Fill in the blank:  

My system was working fine until _________________________________________.

Click Start, Run and in the box enter:

msinfo32

Click OK, and when the System Summary info appears, click Edit, Select All, Copy and then paste the information back here.

For video driver information, expand the Components, click Display, click Edit, Select All, Copy and then paste the information back here.

There will be some personal information (like System Name and User Name), and whatever appears to be private information to you, just delete it from the pasted information.

This will minimize back and forth Q&A and eliminate guesswork.


Download BlueScreenView from here:


Unzip and run it (BSV installs nothing) and let it finish scanning all your crash dump files.  

If you double click on of the dumps, you will get some information about it (including the Caused By Driver field) and you may be able to spot the problem right away - especially if you see a pattern in the dumps where the Caused by Driver field is the same (start with that driver).

Select (highlight) one or more of the most recent dump files by clicking them and holding down the Ctrl key to select multiples files.  Try to select just the most recent ones that relate to your issue (maybe five or so dump files to get started).

Click File, Save Selected Items and save the information from the dumps to a text file on your desktop called BSOD.txt.  Open BSOD.txt with a text editor, copy all the text and paste it into your next reply.

Here is an example of the BSV report from a single BSOD that I initiated on purpose that shows the cause of the crash as the i8042prt.sys driver belonging to Microsoft Corporation:

==================================================
Dump File         : Mini062110-01.dmp
Crash Time        : 6/21/2010 11:51:31 AM
Bug Check String  : MANUALLY_INITIATED_CRASH
Bug Check Code    : 0x000000e2
Parameter 1       : 0x00000000
Parameter 2       : 0x00000000
Parameter 3       : 0x00000000
Parameter 4       : 0x00000000
Caused By Driver  : i8042prt.sys
Caused By Address : i8042prt.sys+27fb
File Description  : i8042 Port Driver
Product Name      : Microsoft® Windows® Operating System
Company           : Microsoft Corporation
File Version      : 5.1.2600.5512 (xpsp.080413-2108)
Processor         : 32-bit
Computer Name     : 
Full Path         : C:\WINDOWS\minidump\Mini062110-01.dmp
==================================================

Send the information from the last 5 memory dumps.

 


Do, or do not. There is no try.

I need YOUR votes and points for helpful replies and Propose as Answers. I am saving up for a pony!

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.