BSOD 0x7a_c000009d -Memory or Hdd error?

Hi all,

Nice to find this useful forum.

We have a "tool" that actually works with 3 exactly similar small pcs(same devices-same programs, etc). So after the first BSODs I took an image from the pc that was ok and restored the the problematic pc. Everything worked at first but after about an hour the BSOD returned.After the BSOD the computer cannot log in to windows, not even at safe mode.Only option I have to restore from the image again but the problem occurs again after some time.I took memory.dmp file and analyze it with windows debugger.So below you can see the results:

*******************************************************************************
* *
* 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: 00000020, lock type that was held (value 1,2,3, or PTE address)
Arg2: c000009d, error status (normally i/o status code)
Arg3: 86241bdc, current process (virtual address for lock type 3, or PTE)
Arg4: 00000000, 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: INTEL_CPU_MICROCODE_ZERO

PROCESS_NAME: System

CURRENT_IRQL: 1

LAST_CONTROL_TRANSFER: from 82c48a90 to 82c88b5c

STACK_TEXT:
8ad48c04 82c48a90 86241ba0 86241ba8 00000000 nt!MiWriteComplete+0x22d
8ad48c24 82cc5746 8679c048 8ad48c50 8ad48c5c nt!IopCompletePageWrite+0x4d
8ad48c74 82c92685 00000000 00000000 00000000 nt!KiDeliverApc+0x111
8ad48cb8 82c914f7 84cb5e08 84cb5d48 82d5dd90 nt!KiSwapThread+0x24e
8ad48ce0 82cbd2a8 84cb5d48 84cb5e08 00000000 nt!KiCommitThreadWait+0x1df
8ad48d24 82c46ed8 00000000 00000000 84cb5d48 nt!KeWaitForGate+0x158
8ad48d50 82e1df5e 00000000 94996613 00000000 nt!MiModifiedPageWriter+0x39
8ad48d90 82cc5219 82c46e9f 00000000 00000000 nt!PspSystemThreadStartup+0x9e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!MiWriteComplete+22d
82c88b5c cc int 3

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: nt!MiWriteComplete+22d

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP: 4ce78a09

IMAGE_NAME: memory_corruption

FAILURE_BUCKET_ID: 0x7a_c000009d_nt!MiWriteComplete+22d

BUCKET_ID: 0x7a_c000009d_nt!MiWriteComplete+22d

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

So what do you think the problem is?Memory or Hdd error?Or it can be something else?
I also run memtest (only one pass) but no problem detected.
Unfortunately I cannot replace any memory or hdd, because the tool is under guarantee so I cannot physically open it and change hdds/memories etc between pcs.

So I would be grateful if you could suggest me any other test I could run, or if you recognise the problem.

Thanks in advance,

Please forgive me for any mistakes , since this is my first post.

We do need the DMP file as it contains the only record of the sequence of events leading up to the crash, what drivers were loaded, and what was responsible.

You may be able to get the DMP files without crashing by booting into safe mode (F8) with networking.

To enable us to assist you with your computer's BSOD symptoms, upload the contents of your "\Windows\Minidump" folder.

The procedure:

* Copy the contents of \Windows\Minidump to another (temporary) location somewhere on your machine.
* Zip up the copy.
* Attach the ZIP archive to your post using the "paperclip" (file attachments) button.
*If the files are too large please upload them to a file sharing service like "Rapidshare" and put a link to them in your reply.

To ensure minidumps are enabled:

* Go to Start, in the Search Box type: sysdm.cpl, press Enter.
* Under the Advanced tab, click on the Startup and Recovery Settings... button.
* Ensure that Automatically restart is unchecked.
* Under the Write Debugging Information header select Small memory dump (256 kB) in the dropdown box (the 256kb varies).
* Ensure that the Small Dump Directory is listed as %systemroot%\Minidump.
* OK your way out.
* Reboot if changes have been made.

Hi zigzag and thank you very much for the help.

I don't have the tool right now so I cannot take mini dump.We have it set to normal kernel so i have a large MEMORY.dmp and some small dump file which I attach you but I don't know if it is useful (after recovering first time windows showed taht they recovered from a serious error and gave me its location at Users/AppData/Local/temp for the dump file).

As soon as I have the tool back I will restore it and I will get minidump as you proposed.

Though running on safe mode is not an option because since the BSOD start the system fails to start with any option at F8 menu(safe mode-recovery-last known good configuration etc.)I guess my option is to start with a live cd and copy the data to a usb.

I attach you the small dump file which I dont know if it is useful.
Again thanks for the help

GioLas said:

Hi zigzag and thank you very much for the help.

I don't have the tool right now so I cannot take mini dump.We have it set to normal kernel so i have a large MEMORY.dmp and some small dump file which I attach you but I don't know if it is useful (after recovering first time windows showed taht they recovered from a serious error and gave me its location at Users/AppData/Local/temp for the dump file).

As soon as I have the tool back I will restore it and I will get minidump as you proposed.

Though running on safe mode is not an option because since the BSOD start the system fails to start with any option at F8 menu(safe mode-recovery-last known good configuration etc.)I guess my option is to start with a live cd and copy the data to a usb.

I attach you the small dump file which I dont know if it is useful.
Again thanks for the help

If by "tool" you mean an app like "bluescreen view" please note it isnt completely reliable.


These one was related to an error with disk hardware.


Please run chkdsk

A- CHKDSK /R /F:

Run CHKDSK /R /F from an elevated (Run as administrator) Command Prompt.

Do this for each hard drive on your system.

When it tells you it can't do it right now - and asks you if you'd like to do it at the next reboot - answer Y (for Yes) and press Enter.

Then reboot and let the test run.

It may take a while for it to run, but keep an occasional eye on it to see if it generates any errors.

See "CHKDSK LogFile" below in order to check the results of the test.

B- Elevated Command Prompt:

Go to Start and type in "cmd.exe" (without the quotes)

At the top of the Search Box, right click on Cmd.exe and select "Run as administrator"

C-CHKDSK LogFile:

Go to Start and type in "eventvwr.msc" (without the quotes) and press Enter

Expand the Windows logs heading, then select the Application log file entry.

Double click on the Source column header.

Scroll down the list until you find the Chkdsk entry (wininit for Win7) (winlogon for XP).

Copy/paste the results into your next post.

Actually by tool I was meaning the pc.

Hopefully I will have it back at wednesday when i will be able to run chkdsks and have more dump files for analysis.

It only has one hdd about 53 gb where the OS is installed.I run chkcdsk once before with no problems at the clusters and also it was no fragmented(4%).
I will do it again asap so I can post the results.

GioLas said:

Actually by tool I was meaning the pc.

Hopefully I will have it back at wednesday when i will be able to run chkdsks and have more dump files for analysis.

It only has one hdd about 53 gb where the OS is installed.I run chkcdsk once before with no problems at the clusters and also it was no fragmented(4%).
I will do it again asap so I can post the results.

Good luck