Tech Support Guy banner
  • Please post in our Community Feedback thread for help with the new forum software! If you are having trouble logging in, please Contact Us for assistance.
Status
Not open for further replies.
1 - 3 of 3 Posts

·
Registered
Joined
·
2 Posts
Discussion Starter · #1 ·
Hi Everyone,


I am new to this forum so hi to all and I apologise for the length of this post but here goes......

I have a problem with my PC giving a bugcheck and wondered if someone can point me in the right direction before I shell out some cash on a new MOBO and HDD.
I’m running Windows 7 Ultimate RTM and I occasionally get a system freeze and sometimes a BSOD. I can pretty much reproduce the issue by running a backup using the built-in Backup and restore. I back up my C drive (circa 80 out of 250Gb used) to a 400Gb USB hard drive. It is not only the backup that does cause it but this is the best way to reproduce it fairly consistently.
The C Drive is a Seagate SATA drive and the USB drive is a regular Maxtor IDE
I have installed a second USB controller in to the PCI slot to eliminate that as a cause but no joy. The w7 was an upgrade from Vista Ultimate but I have now completely wiped and then reinstalled W7 from fresh and the problem persists. The problem also occurred on the Vista build.
I have run the SEATOOLS on a quick test and it tells me nothing was wrong with the source disk and I ran the Maxtor equivalent on the USB drive (removed it from the enclosure and installed it into the PC. I also ran Spinrite on a level 4 on the SATA disk (source) for 24 hours but got bored as it only completed 20%. This shoed no errors up the point where I cancelled it.
I have loaded Windbg and run a check of the memory.dmp and it comes up with the information below (two dumps – I will add more as they happen if they vary). It does suggest the drive is bad but I am not so sure and think it could be the mainboard drivers or the mainboard or SATA cable or even the RAM (it has two x 1Gb matched . The mainboard is quite old and there are no more BIOS or driver updates for it (MAXDATA MS-7253 5123660003) which is a cronky old mobo that came with a MaxData PC but has been flashed to the most recent maxdata had before they went bust.
I run NOD32 v4 A/V and I have purposely not installed this on the new build to eliminate that as a cause (filter driver conflict or some such).
I get fairly regular errors like: The device, \Device\Harddisk3\DR3, has a bad block. And The device, \Device\Harddisk3\DR4, has a bad block. I just installed Backup4all professional to try another app that uses VSS and I had it running fine yesterday but today I also noticed the following error in the event log 15 minutes after the daily incremental backup kicked in,:

Time: 20:05hrs
Volume Shadow Copy Service error: Unexpected error querying for the IVssWriterCallback interface. hr = 0x80070005, Access is denied.
. This is often caused by incorrect security settings in either the writer or requestor process.

Operation:
Gathering Writer Data

Context:
Writer Class Id: {e8132975-6f93-4464-a53e-1050253ae220}
Writer Name: System Writer
Writer Instance ID: {75141468-b4aa-4b77-8da2-e49c0f1b4a50}

This was preceeded by several The device, \Device\Harddisk3\DR4, has a bad block. Errors and then..... at 20:18 the DUMP2 below was produced and the system restarted.


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


Loading Dump File [C:\temp\dumps\30aug\MEMORY.DMP]
Kernel Summary Dump File: Only kernel address space is available

Symbol search path is: SRV*c:\symbols cache*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.x86fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0x8283d000 PsLoadedModuleList = 0x82985810
Debug session time: Sun Aug 30 23:06:27.070 2009 (GMT+1)
System Uptime: 0 days 3:28:14.023
Loading Kernel Symbols
...............................................................
................................................................
.............
Loading User Symbols

Loading unloaded module list
.......
1: kd> !analyze -v
*******************************************************************************
* *
* 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: c04157d8, lock type that was held (value 1,2,3, or PTE address)
Arg2: c000000e, error status (normally i/o status code)
Arg3: 0399d860, current process (virtual address for lock type 3, or PTE)
Arg4: 82afbe2b, virtual address that could not be in-paged (or PTE contents if arg1 is a PTE address)

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


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

DISK_HARDWARE_ERROR: There was error with disk hardware

BUGCHECK_STR: 0x7a_c000000e

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: System

CURRENT_IRQL: 0

TRAP_FRAME: 8a927a14 -- (.trap 0xffffffff8a927a14)
ErrCode = 00000010
eax=8559a901 ebx=00010000 ecx=2c000128 edx=00010000 esi=8559a888 edi=8557da80
eip=82afbe2b esp=8a927a88 ebp=8a927ab0 iopl=0 nv up ei pl nz na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010206
nt!PnpRequestDeviceRemoval:
82afbe2b f8 clc
Resetting default scope

LOCK_ADDRESS: 829a2f60 -- (!locks 829a2f60)

Resource @ nt!PiEngineLock (0x829a2f60) Exclusively owned
Contention Count = 12
Threads: 848bb020-01<*>
1 total locks, 1 locks currently held

PNP_TRIAGE:
Lock address : 0x829a2f60
Thread Count : 1
Thread address: 0x848bb020
Thread wait : 0xc3381

LAST_CONTROL_TRANSFER: from 828f160a to 82919d10

STACK_TEXT:
8a92786c 828f160a 0000007a c04157d8 c000000e nt!KeBugCheckEx+0x1e
8a9278e0 828e90d5 84b1b3b4 8a927938 82971540 nt!MiWaitForInPageComplete+0x2fd
8a927974 828c4e3f 82971540 82afbe2b 84b1b320 nt!MiIssueHardFault+0x3b2
8a9279fc 828835f8 00000008 82afbe2b 00000000 nt!MmAccessFault+0x2656
8a9279fc 82afbe2b 00000008 82afbe2b 00000000 nt!KiTrap0E+0xdc
8a927ab0 829e4a73 84960ac8 8557da80 00000002 nt!PnpRequestDeviceRemoval
8a927ca4 829de61a 8557da80 84960ac8 8a927cd0 nt!PipProcessDevNodeTree+0x352
8a927cd8 82850f7c 829a0e80 848bb020 829775bc nt!PiProcessReenumeration+0x74
8a927d00 828aaf2b 00000000 00000000 848bb020 nt!PnpDeviceActionWorker+0x224
8a927d50 82a4b66d 00000001 95405044 00000000 nt!ExpWorkerThread+0x10d
8a927d90 828fd0d9 828aae1e 00000001 00000000 nt!PspSystemThreadStartup+0x9e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!MiWaitForInPageComplete+2fd
828f160a cc int 3

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt!MiWaitForInPageComplete+2fd

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc007

IMAGE_NAME: memory_corruption

FAILURE_BUCKET_ID: 0x7a_c000000e_nt!MiWaitForInPageComplete+2fd

BUCKET_ID: 0x7a_c000000e_nt!MiWaitForInPageComplete+2fd

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


DUMP2

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


Loading Dump File [C:\temp\dumps\2Sept\MEMORY.DMP]
Kernel Summary Dump File: Only kernel address space is available

Symbol search path is: SRV*c:\symbols cache*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.x86fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0x82a3f000 PsLoadedModuleList = 0x82b87810
Debug session time: Wed Sep 2 20:16:44.515 2009 (GMT+1)
System Uptime: 0 days 2:53:06.468
Loading Kernel Symbols
...............................................................
................................................................
...........
Loading User Symbols
PEB is paged out (Peb.Ldr = 7ffd500c). Type ".hh dbgerr001" for details
Loading unloaded module list
......
1: kd> !analyze -v
*******************************************************************************
* *
* 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: c0415d50, lock type that was held (value 1,2,3, or PTE address)
Arg2: c000000e, error status (normally i/o status code)
Arg3: 44d67860, current process (virtual address for lock type 3, or PTE)
Arg4: 82baa005, virtual address that could not be in-paged (or PTE contents if arg1 is a PTE address)

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

PEB is paged out (Peb.Ldr = 7ffd500c). Type ".hh dbgerr001" for details
PEB is paged out (Peb.Ldr = 7ffd500c). Type ".hh dbgerr001" for details

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

DISK_HARDWARE_ERROR: There was error with disk hardware

BUGCHECK_STR: 0x7a_c000000e

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: services.exe

CURRENT_IRQL: 0

TRAP_FRAME: a17c16a0 -- (.trap 0xffffffffa17c16a0)
ErrCode = 00000010
eax=00000000 ebx=a17c1800 ecx=82af6598 edx=a17c15b0 esi=00000000 edi=00000000
eip=82baa005 esp=a17c1714 ebp=a17c1758 iopl=0 nv up ei pl zr na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246
nt!EtwUnregister:
82baa005 0000 add byte ptr [eax],al ds:0023:00000000=??
Resetting default scope

EXCEPTION_RECORD: a17c1ce0 -- (.exr 0xffffffffa17c1ce0)
ExceptionAddress: 773ad764
ExceptionCode: c0000006 (In-page I/O error)
ExceptionFlags: 00000000
NumberParameters: 3
Parameter[0]: 00000000
Parameter[1]: 773dfee0
Parameter[2]: c000000e
Inpage operation failed at 773dfee0, due to I/O error c000000e

LAST_CONTROL_TRANSFER: from 82af360a to 82b1bd10

STACK_TEXT:
a17c14fc 82af360a 0000007a c0415d50 c000000e nt!KeBugCheckEx+0x1e
a17c1570 82aeb0d5 8521cabc a17c15c8 82b73540 nt!MiWaitForInPageComplete+0x2fd
a17c1604 82ac6e3f 82b73540 82baa005 8521ca28 nt!MiIssueHardFault+0x3b2
a17c1688 82a855f8 00000008 82baa005 00000000 nt!MmAccessFault+0x2656
a17c1688 82baa005 00000008 82baa005 00000000 nt!KiTrap0E+0xdc
a17c1758 82cd1700 80010001 00000000 862f6c98 nt!EtwUnregister
a17c17e0 82c54f55 a17c1ce0 a17c1800 00000000 nt!DbgkpSendErrorMessage+0x2d
a17c18ac 82afc64e a17c1ce0 00000000 00000001 nt!DbgkForwardException+0xf2
a17c1cc4 82a83016 a17c1ce0 00000000 a17c1d34 nt!KiDispatchException+0x486
a17c1d2c 82a8573b 00f510c8 773ad764 badb0d00 nt!CommonDispatchException+0x4a
a17c1d2c 773ad764 00f510c8 773ad764 badb0d00 nt!KiTrap0E+0x21f
WARNING: Frame IP not in any known module. Following frames may be wrong.
00f510c8 00000000 00000000 00000000 00000000 0x773ad764


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!MiWaitForInPageComplete+2fd
82af360a cc int 3

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt!MiWaitForInPageComplete+2fd

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc007

IMAGE_NAME: memory_corruption

FAILURE_BUCKET_ID: 0x7a_c000000e_nt!MiWaitForInPageComplete+2fd

BUCKET_ID: 0x7a_c000000e_nt!MiWaitForInPageComplete+2fd

Followup: MachineOwner
---------
Can anyone offer any advice?

Many thanks
Paul

 

·
Registered
Joined
·
356 Posts
Hey. I've taken some time to read through the dump analysis. It appears that the BSODs are being caused by the kernel not being able to page-in some data from the page file. Specifically the error codes refer to the unavailability of the hard drive where the page file is located. I would say the disk is on its way out. Make sure you've backed up all your important stuff!

More info here: http://support.microsoft.com/kb/228753

EDIT: Just another thought, you can try clearing the CMOS and try another cable. Be careful not to bend it at all, I once had a very slow hard drive because the SATA cable had a 90 degree bend in it, not a good idea!
 

·
Registered
Joined
·
2 Posts
Discussion Starter · #3 ·
Hi Syst3mSh0ck,

Thanks for the quick reply. I noticed this too but was thinking that it could even be the disk controller (i.e. Mobo) or possibly the memory. The Mobo is old and cheap and I am leaning towards giving this a go but will by a new SATA cable first as this is the cheapest option.

The odd thing is that Spinrite and Seatools say the disk is good.

What a pain!

Thanks
Paul
 
1 - 3 of 3 Posts
Status
Not open for further replies.
Top