I have a secondhand compaq nx 8220 laptop, which when i got it had an unstable system (random crashes to name but one). So i rebooted with a clean version of xp home sp2 that i used on my old pc (which gave up last week and wasnt worth repairing).

The crashing problem is still there. It doesnt freeze but shuts down all together then auto restarts. There is a blue screen full of writing for less that 1/2 second, cant read a thing. On restart i get an error report message which reads.

c:\docume~1\davidd~1\locals~1temp\wer5fd2.dir00\mi ni111607-02.dmp
c:\docume~1\davidd~1\locals~1temp\wer5fd2.dir00\sy sdata.xml

as the machine is not on the web is there any way of identifying whats wrong.
Regards
Dave

Should i set up a web connection for a windows update?

"So i rebooted with a clean version of xp home sp2 that i used..."

I gather you mean "formatted/installed"?

"It doesnt freeze but shuts down all together then auto restarts. There is a blue screen full of writing for less that 1/2 second, cant read a thing."

You can preclude the auto-restart by (if you can get there) right clicking on My Computer, choose Properties, Advanced, and Settings under "Startup and Recovery". Clear the checkmark from the box for "Automatically restart".

This will allow you to record any error messages for analysis.

Analysis is done by checking System Events and the dump file associated with the "failed" event.

Also, here's the troubleshooting page for that model;

http://h20000.www2.hp.com/bizsupport...rtTaskId=11483

See if anything applies.

Hi Dan
Thank you for the reply. Yes i did mean a format and re-install.

Here is an update

switched off auto restart and started windows. Opened media player and a game and left running playing music, went to work. worked fine for 5 hours. On return i started playing pinball thats when it crashed, after several mouse commands.

blue screen said the following (ignoring the standard text)

kernal_data_inpage_error

tech info
stop. 0x00000007a (oxe17ad8f8 0xc00000e 0x3f916327 0x09163860)

win3k.sys, address bf916327 base at bf800000
date stamp 41107f79

after writing this down it took 2 attempts to reboot with blue screen stating a partmgr.sys fault

I only have windows xp home sp2, soundmax audio driver, ati graphics driver and synaptics mouse driver installed but it did crash once with only xp installed while playing cards!

Regards
Dave

Have ben reading about bsod and done some more checks.
I found an error notification in event viewer - system

source - system error
event id - 1003

this again gives a 0x0000007a code which i have found to be a 'kernal data inpage error' the following parameters read

par1 e17ad8f8
par2 c000000e
par 3 bf916327
par 4 091669860

following the initial error the system would not reboot (took 3 attempts) and i found these this error occuring twice.
source - atapi
event id - 9
the device.\device\ide\ideport0 did not respond within the timeout period

is there any clues within this lot
regards
dave

(Without researching yet), it would appear that there may be a problem with your disk setup/recognition, or the files controlling these elements;

partmgr.sys fault<== Partition manager file

source - atapi
event id - 9
the device.\device\ide\ideport0 did not respond within the timeout period<== Your DEVICE on the IDE buss IDEPORT0 would appear to be your primary IDE buss.

Don't know if you've come across this by jephree yet;
http://www.d-a-l.com/help/showthread.php?t=50190

At the end are tools and links worth a read. I'll do the same.

Thank you again Dan
I have read jephree's bsod thread and had a look through some of the links. I havent found anything in particular relating to my problem, pleanty of kernal data inpage error related material but nothing relating to the 2nd parameter 0xc000000e.

I did however find that this code itself relates to device not found and from reading other peoples forum threads is a sign of a faulty hdd / controller

regarding the ideport0 note i have also read in other areas that it could be the hdd or controller.

I see how the two problems are linked, ie fault occurs fault still occurring whils trying to boot up.

Im off to the hp site and see if they have a motherboard diagnostic tool. in the mean time i have removed and reseated my hdd and to be honest havent had a crash today.

Regards
Dave

Just had a crash, same fault came up on bsod, checked event viewer - same as before. This time there was a memory dump and i found a .dmp file in the windows folder. I have installed and run ms debuging tool along with debugwhiz. I have a long text document with the message 'your debugger is not using the correct symbols' appearing several times with other messages in between. any ideas on what to post from this text doc.

cheers
Dave

Post it all.

Here it is.

Opened log file 'c:\debuglog.txt'

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


Loading Dump File [C:\WINDOWS\Minidump\Mini111807-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: C:\WINDOWS;C:\WINDOWS\system32;C:\WINDOWS\system32 \drivers
*** ERROR: Symbol file could not be found. Defaulted to export symbols for ntkrnlpa.exe -
Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 2600.xpsp_sp2_rtm.040803-2158
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805531a0
Debug session time: Sun Nov 18 17:44:33.843 2007 (GMT+0)
System Uptime: 0 days 0:03:21.421
*** ERROR: Symbol file could not be found. Defaulted to export symbols for ntkrnlpa.exe -
Loading Kernel Symbols
.................................................. .................................................. ...............
Loading User Symbols
Loading unloaded module list
...........
************************************************** *****************************
* *
* Bugcheck Analysis *
* *
************************************************** *****************************

Use !analyze -v to get detailed debugging information.

BugCheck 7A, {e19a29c8, c000000e, bf93095d, f980860}

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

*** ERROR: Symbol file could not be found. Defaulted to export symbols for win32k.sys -
*** ERROR: Module load completed but symbols could not be loaded for atapi.sys
************************************************** ***********************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
************************************************** ***********************
************************************************** ***********************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!KPRCB ***
*** ***
************************************************** ***********************
************************************************** ***********************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
************************************************** ***********************
************************************************** ***********************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!KPRCB ***
*** ***
************************************************** ***********************
************************************************** ***********************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
************************************************** ***********************
************************************************** ***********************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
************************************************** ***********************
************************************************** ***********************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
************************************************** ***********************


Probably caused by : win32k.sys ( win32k!EngDeleteSurface+3ed8 )

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

kd> !analyze -v;r;kv;lmtn;.logclose;q
************************************************** *****************************
* *
* 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: e19a29c8, lock type that was held (value 1,2,3, or PTE address)
Arg2: c000000e, error status (normally i/o status code)
Arg3: bf93095d, current process (virtual address for lock type 3, or PTE)
Arg4: 0f980860, virtual address that could not be in-paged (or PTE contents if arg1 is a PTE address)

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

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

************************************************** ***********************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
************************************************** ***********************
************************************************** ***********************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!KPRCB ***
*** ***
************************************************** ***********************
************************************************** ***********************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
************************************************** ***********************
************************************************** ***********************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!KPRCB ***
*** ***
************************************************** ***********************
************************************************** ***********************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
************************************************** ***********************
************************************************** ***********************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
************************************************** ***********************
************************************************** ***********************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
************************************************** ***********************



MODULE_NAME: win32k

FAULTING_MODULE: 804d7000 nt

DEBUG_FLR_IMAGE_TIMESTAMP: 41107f7a

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

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WRONG_SYMBOLS

LAST_CONTROL_TRANSFER: from 80511d73 to 804f8925

STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
f7f65708 80511d73 0000007a e19a29c8 c000000e nt!KeBugCheckEx+0x1b
f7f65738 80512899 81b56a00 e19a29c8 bf93095d nt!MmIsAddressValid+0x20f1
f7f657b8 8051bdd4 e19a29c8 bf93095d c05fc980 nt!MmIsAddressValid+0x2c17
f7f6581c 8053f6ec 00000008 bf93095d 00000000 nt!MmTrimAllSystemPagableMemory+0x66a8
f7f65840 805d60d0 00000500 00000000 00000000 nt!Kei386EoiHelper+0x2674
f7f65900 bf814008 bc600940 00000082 00000000 nt!RtlAllocateHeap+0x8cc
f7f65940 bf80f470 bc600940 00000082 00000000 win32k!EngDeleteSurface+0x3ed8
f7f65964 bf8fbb67 bc600940 00000082 00000000 win32k!EngFreeUserMem+0x4095
f7f659b0 bf8fc169 bc600940 f7f659cc e1bffeb0 win32k!FONTOBJ_pxoGetXform+0x13e0
f7f659d8 bf8fbb58 bc600818 e1bffeb0 bc600818 win32k!FONTOBJ_pxoGetXform+0x19e2
f7f65a18 bf8fb5de bc600818 f7f65a58 00000000 win32k!FONTOBJ_pxoGetXform+0x13d1
f7f65a68 bf8aabf1 00000000 00000022 0071fff4 win32k!FONTOBJ_pxoGetXform+0xe57
f7f65d30 bf8c8602 bf9a8980 00000001 f7f65d54 win32k!EngFntCacheAlloc+0x162b
f7f65d40 bf800ff4 bf9a8980 f7f65d64 0071fff4 win32k!EngSort+0x2af
f7f65d54 8053c808 00000000 00000022 00000000 win32k+0xff4
f7f65ddc 80540fa2 8061bd30 00000001 00000000 nt!KeReleaseInStackQueuedSpinLockFromDpcLevel+0xb1 4
00000000 00000000 00000000 00000000 00000000 nt!KiDispatchInterrupt+0x5a2


STACK_COMMAND: kb

FOLLOWUP_IP:
win32k!EngDeleteSurface+3ed8
bf814008 8b4d20 mov ecx,dword ptr [ebp+20h]

SYMBOL_STACK_INDEX: 6

SYMBOL_NAME: win32k!EngDeleteSurface+3ed8

FOLLOWUP_NAME: MachineOwner

IMAGE_NAME: win32k.sys

BUCKET_ID: WRONG_SYMBOLS

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

eax=ffdff13c ebx=c000000e ecx=00000000 edx=00000000 esi=e19a29c8 edi=bf93095d
eip=804f8925 esp=f7f656f0 ebp=f7f65708 iopl=3 nv up ei ng nz na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00003286
nt!KeBugCheckEx+0x1b:
804f8925 5d pop ebp
ChildEBP RetAddr Args to Child
WARNING: Stack unwind information not available. Following frames may be wrong.
f7f65708 80511d73 0000007a e19a29c8 c000000e nt!KeBugCheckEx+0x1b
f7f65738 80512899 81b56a00 e19a29c8 bf93095d nt!MmIsAddressValid+0x20f1
f7f657b8 8051bdd4 e19a29c8 bf93095d c05fc980 nt!MmIsAddressValid+0x2c17
f7f6581c 8053f6ec 00000008 bf93095d 00000000 nt!MmTrimAllSystemPagableMemory+0x66a8
f7f65840 805d60d0 00000500 00000000 00000000 nt!Kei386EoiHelper+0x2674
f7f65900 bf814008 bc600940 00000082 00000000 nt!RtlAllocateHeap+0x8cc
f7f65940 bf80f470 bc600940 00000082 00000000 win32k!EngDeleteSurface+0x3ed8
f7f65964 bf8fbb67 bc600940 00000082 00000000 win32k!EngFreeUserMem+0x4095
f7f659b0 bf8fc169 bc600940 f7f659cc e1bffeb0 win32k!FONTOBJ_pxoGetXform+0x13e0
f7f659d8 bf8fbb58 bc600818 e1bffeb0 bc600818 win32k!FONTOBJ_pxoGetXform+0x19e2
f7f65a18 bf8fb5de bc600818 f7f65a58 00000000 win32k!FONTOBJ_pxoGetXform+0x13d1
f7f65a68 bf8aabf1 00000000 00000022 0071fff4 win32k!FONTOBJ_pxoGetXform+0xe57
f7f65d30 bf8c8602 bf9a8980 00000001 f7f65d54 win32k!EngFntCacheAlloc+0x162b
f7f65d40 bf800ff4 bf9a8980 f7f65d64 0071fff4 win32k!EngSort+0x2af
f7f65d54 8053c808 00000000 00000022 00000000 win32k+0xff4
f7f65ddc 80540fa2 8061bd30 00000001 00000000 nt!KeReleaseInStackQueuedSpinLockFromDpcLevel+0xb1 4
00000000 00000000 00000000 00000000 00000000 nt!KiDispatchInterrupt+0x5a2
start end module name
804d7000 806cd280 nt ntkrnlpa.exe Wed Aug 04 06:58:36 2004 (41107B0C)
806ce000 806ee380 hal halaacpi.dll Wed Aug 04 06:59:05 2004 (41107B29)
bf800000 bf9c0380 win32k win32k.sys Wed Aug 04 07:17:30 2004 (41107F7A)
bf9c1000 bf9d2580 dxg dxg.sys Wed Aug 04 07:00:51 2004 (41107B93)
bf9d3000 bfa15000 ati2dvag ati2dvag.dll Thu Mar 09 03:49:39 2006 (440FA5D3)
bfa15000 bfa54000 ati2cqag ati2cqag.dll Thu Mar 09 03:07:10 2006 (440F9BDE)
bfa54000 bfa8a000 atikvmag atikvmag.dll Thu Mar 09 03:13:23 2006 (440F9D53)
bfa8a000 bfd0db80 ati3duag ati3duag.dll Thu Mar 09 03:33:25 2006 (440FA205)
bfd0e000 bfde01e0 ativvaxx ativvaxx.dll Thu Mar 09 03:26:54 2006 (440FA07E)
f10e5000 f110ef00 kmixer kmixer.sys Wed Aug 04 07:07:46 2004 (41107D32)
f136f000 f13af380 HTTP HTTP.sys Wed Aug 04 07:00:09 2004 (41107B69)
f14c5000 f14d9400 wdmaud wdmaud.sys Wed Aug 04 07:15:03 2004 (41107EE7)
f16ba000 f170c180 srv srv.sys Wed Aug 04 07:14:44 2004 (41107ED4)
f1735000 f1761400 mrxdav mrxdav.sys Wed Aug 04 07:00:49 2004 (41107B91)
f18ea000 f18f8d80 sysaudio sysaudio.sys Wed Aug 04 07:15:54 2004 (41107F1A)
f1a32000 f1a47580 irda irda.sys Wed Aug 04 07:00:50 2004 (41107B92)
f1ad0000 f1ad3280 ndisuio ndisuio.sys Wed Aug 04 07:03:10 2004 (41107C1E)
f3bd8000 f3bef480 dump_atapi dump_atapi.sys Wed Aug 04 06:59:41 2004 (41107B4D)
f3c18000 f3c38f00 ipnat ipnat.sys Wed Aug 04 07:04:48 2004 (41107C80)
f3cd9000 f3d47380 mrxsmb mrxsmb.sys Wed Aug 04 07:15:14 2004 (41107EF2)
f3d48000 f3d73180 rdbss rdbss.sys Wed Aug 04 07:20:05 2004 (41108015)
f3d74000 f3d95d00 afd afd.sys Wed Aug 04 07:14:13 2004 (41107EB5)
f3d96000 f3dbdc00 netbt netbt.sys Wed Aug 04 07:14:36 2004 (41107ECC)
f3dbe000 f3e15a80 tcpip tcpip.sys Wed Aug 04 07:14:39 2004 (41107ECF)
f3e16000 f3e28400 ipsec ipsec.sys Wed Aug 04 07:14:27 2004 (41107EC3)
f7e91000 f7ec4200 update update.sys Wed Aug 04 06:58:32 2004 (41107B08)
f7ec5000 f7ed5e00 psched psched.sys Wed Aug 04 07:04:16 2004 (41107C60)
f7f76000 f7f8c680 ndiswan ndiswan.sys Wed Aug 04 07:14:30 2004 (41107EC6)
f7fa9000 f7fab900 Dxapi Dxapi.sys Fri Aug 17 21:53:19 2001 (3B7D843F)
f7fb5000 f7fe26a0 SynTP SynTP.sys Fri Nov 05 02:26:41 2004 (418AE4E1)
f7fe3000 f7ff6900 parport parport.sys Wed Aug 04 06:59:04 2004 (41107B28)
f7ff7000 f8016300 aeaudio aeaudio.sys Mon Nov 08 21:10:35 2004 (418FE0CB)
f8017000 f8039680 ks ks.sys Wed Aug 04 07:15:20 2004 (41107EF8)
f803a000 f805d980 portcls portcls.sys Wed Aug 04 07:15:47 2004 (41107F13)
f805e000 f809d700 smwdm smwdm.sys Wed Oct 13 20:25:52 2004 (416D8140)
f809e000 f80c0e80 USBPORT USBPORT.SYS Wed Aug 04 07:08:34 2004 (41107D62)
f80c1000 f80d4780 VIDEOPRT VIDEOPRT.SYS Wed Aug 04 07:07:04 2004 (41107D08)
f80d5000 f8253000 ati2mtag ati2mtag.sys Thu Mar 09 03:49:17 2006 (440FA5BD)
f82b2000 f82cc580 Mup Mup.sys Wed Aug 04 07:15:20 2004 (41107EF8)
f82cd000 f82f9a80 NDIS NDIS.sys Wed Aug 04 07:14:27 2004 (41107EC3)
f82fa000 f8386480 Ntfs Ntfs.sys Wed Aug 04 07:15:06 2004 (41107EEA)
f8387000 f839d780 KSecDD KSecDD.sys Wed Aug 04 06:59:45 2004 (41107B51)
f839e000 f83aff00 sr sr.sys Wed Aug 04 07:06:22 2004 (41107CDE)
f83b0000 f83ce780 fltMgr fltMgr.sys Wed Aug 04 07:01:17 2004 (41107BAD)
f83cf000 f83e6480 atapi atapi.sys Wed Aug 04 06:59:41 2004 (41107B4D)
f83e7000 f8405880 ftdisk ftdisk.sys Fri Aug 17 21:52:41 2001 (3B7D8419)
f8406000 f8423480 pcmcia pcmcia.sys Wed Aug 04 07:07:45 2004 (41107D31)
f8424000 f8434a80 pci pci.sys Wed Aug 04 07:07:45 2004 (41107D31)
f8435000 f8462d80 ACPI ACPI.sys Wed Aug 04 07:07:35 2004 (41107D27)
f8564000 f856cc00 isapnp isapnp.sys Fri Aug 17 21:58:01 2001 (3B7D8559)
f8574000 f8582e80 ohci1394 ohci1394.sys Wed Aug 04 07:10:05 2004 (41107DBD)
f8584000 f8591000 1394BUS 1394BUS.SYS Wed Aug 04 07:10:03 2004 (41107DBB)
f8594000 f859e500 MountMgr MountMgr.sys Wed Aug 04 06:58:29 2004 (41107B05)
f85a4000 f85b0c80 VolSnap VolSnap.sys Wed Aug 04 07:00:14 2004 (41107B6E)
f85b4000 f85bce00 disk disk.sys Wed Aug 04 06:59:53 2004 (41107B59)
f85c4000 f85d0200 CLASSPNP CLASSPNP.SYS Wed Aug 04 07:14:26 2004 (41107EC2)
f8624000 f8633180 nic1394 nic1394.sys Wed Aug 04 06:58:28 2004 (41107B04)
f8634000 f863cd00 intelppm intelppm.sys Wed Aug 04 06:59:19 2004 (41107B37)
f8644000 f8652b80 drmk drmk.sys Wed Aug 04 07:07:54 2004 (41107D3A)
f8654000 f865cc00 smcirda smcirda.sys Tue Apr 10 20:43:35 2001 (3AD36267)
f8664000 f8670e00 i8042prt i8042prt.sys Wed Aug 04 07:14:36 2004 (41107ECC)
f8674000 f867e380 imapi imapi.sys Wed Aug 04 07:00:12 2004 (41107B6C)
f8684000 f8690180 cdrom cdrom.sys Wed Aug 04 06:59:52 2004 (41107B58)
f8694000 f86a2080 redbook redbook.sys Wed Aug 04 06:59:34 2004 (41107B46)
f86a4000 f86b0880 rasl2tp rasl2tp.sys Wed Aug 04 07:14:21 2004 (41107EBD)
f86b4000 f86be200 raspppoe raspppoe.sys Wed Aug 04 07:05:06 2004 (41107C92)
f86c4000 f86cfd00 raspptp raspptp.sys Wed Aug 04 07:14:26 2004 (41107EC2)
f86d4000 f86dc900 msgpc msgpc.sys Wed Aug 04 07:04:11 2004 (41107C5B)
f86e4000 f86edf00 termdd termdd.sys Wed Aug 04 06:58:52 2004 (41107B1C)
f86f4000 f86fd480 NDProxy NDProxy.SYS Fri Aug 17 21:55:30 2001 (3B7D84C2)
f8724000 f8732100 usbhub usbhub.sys Wed Aug 04 07:08:40 2004 (41107D68)
f8754000 f875c700 netbios netbios.sys Wed Aug 04 07:03:19 2004 (41107C27)
f8764000 f876c880 Fips Fips.SYS Sat Aug 18 02:31:49 2001 (3B7DC585)
f8774000 f877c700 wanarp wanarp.sys Wed Aug 04 07:04:57 2004 (41107C89)
f8784000 f8792d80 arp1394 arp1394.sys Wed Aug 04 06:58:28 2004 (41107B04)
f87a4000 f87b3900 Cdfs Cdfs.SYS Wed Aug 04 07:14:09 2004 (41107EB1)
f87e4000 f87ea200 PCIIDEX PCIIDEX.SYS Wed Aug 04 06:59:40 2004 (41107B4C)
f87ec000 f87f0900 PartMgr PartMgr.sys Sat Aug 18 02:32:23 2001 (3B7DC5A7)
f880c000 f8811000 usbuhci usbuhci.sys Wed Aug 04 07:08:34 2004 (41107D62)
f8814000 f881a800 usbehci usbehci.sys Wed Aug 04 07:08:34 2004 (41107D62)
f881c000 f8822000 kbdclass kbdclass.sys Wed Aug 04 06:58:32 2004 (41107B08)
f8824000 f8829a00 mouclass mouclass.sys Wed Aug 04 06:58:32 2004 (41107B08)
f882c000 f8830c80 rasirda rasirda.sys Fri Aug 17 21:51:29 2001 (3B7D83D1)
f8834000 f8838880 TDI TDI.SYS Wed Aug 04 07:07:47 2004 (41107D33)
f883c000 f8840580 ptilink ptilink.sys Fri Aug 17 21:49:53 2001 (3B7D8371)
f8844000 f8848080 raspti raspti.sys Fri Aug 17 21:55:32 2001 (3B7D84C4)
f8864000 f8869200 vga vga.sys Wed Aug 04 07:07:06 2004 (41107D0A)
f886c000 f8870a80 Msfs Msfs.SYS Wed Aug 04 07:00:37 2004 (41107B85)
f8874000 f887b880 Npfs Npfs.SYS Wed Aug 04 07:00:38 2004 (41107B86)
f8884000 f8888500 watchdog watchdog.sys Wed Aug 04 07:07:32 2004 (41107D24)
f8974000 f8977000 BOOTVID BOOTVID.dll Fri Aug 17 21:49:09 2001 (3B7D8345)
f8978000 f897a480 compbatt compbatt.sys Fri Aug 17 21:57:58 2001 (3B7D8556)
f897c000 f897f700 BATTC BATTC.SYS Fri Aug 17 21:57:52 2001 (3B7D8550)
f8980000 f8982d80 ACPIEC ACPIEC.sys Fri Aug 17 21:57:55 2001 (3B7D8553)
f8a08000 f8a0ac00 irenum irenum.sys Wed Aug 04 07:00:45 2004 (41107B8D)
f8a14000 f8a17700 CmBatt CmBatt.sys Wed Aug 04 07:07:39 2004 (41107D2B)
f8a18000 f8a1a280 wmiacpi wmiacpi.sys Wed Aug 04 07:07:39 2004 (41107D2B)
f8a20000 f8a22580 ndistapi ndistapi.sys Fri Aug 17 21:55:29 2001 (3B7D84C1)
f8a2c000 f8a2fc80 mssmbios mssmbios.sys Wed Aug 04 07:07:47 2004 (41107D33)
f8a60000 f8a62280 rasacd rasacd.sys Fri Aug 17 21:55:39 2001 (3B7D84CB)
f8a64000 f8a65b80 kdcom kdcom.dll Fri Aug 17 21:49:10 2001 (3B7D8346)
f8a66000 f8a67100 WMILIB WMILIB.SYS Fri Aug 17 22:07:23 2001 (3B7D878B)
f8a68000 f8a69580 intelide intelide.sys Wed Aug 04 06:59:40 2004 (41107B4C)
f8a72000 f8a73280 USBD USBD.SYS Fri Aug 17 22:02:58 2001 (3B7D8682)
f8a74000 f8a75100 swenum swenum.sys Wed Aug 04 06:58:41 2004 (41107B11)
f8a76000 f8a77f00 Fs_Rec Fs_Rec.SYS Fri Aug 17 21:49:37 2001 (3B7D8361)
f8a78000 f8a79080 Beep Beep.SYS Fri Aug 17 21:47:33 2001 (3B7D82E5)
f8a7a000 f8a7b080 mnmdd mnmdd.SYS Fri Aug 17 21:57:28 2001 (3B7D8538)
f8a7c000 f8a7d080 RDPCDD RDPCDD.sys Fri Aug 17 21:46:56 2001 (3B7D82C0)
f8a7e000 f8a7f100 dump_WMILIB dump_WMILIB.SYS Fri Aug 17 22:07:23 2001 (3B7D878B)
f8aa4000 f8aa5a80 ParVdm ParVdm.SYS Fri Aug 17 21:49:49 2001 (3B7D836D)
f8b2c000 f8b2cd00 PCIIde PCIIde.sys Fri Aug 17 21:51:49 2001 (3B7D83E5)
f8b2d000 f8b2dd80 OPRGHDLR OPRGHDLR.SYS Fri Aug 17 21:57:55 2001 (3B7D8553)
f8bd7000 f8bd7b80 Null Null.SYS Fri Aug 17 21:47:39 2001 (3B7D82EB)
f8c12000 f8c12d00 dxgthk dxgthk.sys Fri Aug 17 21:53:12 2001 (3B7D8438)
f8c9a000 f8c9ac00 audstub audstub.sys Fri Aug 17 21:59:40 2001 (3B7D85BC)

Unloaded modules:
f1478000 f14a2000 kmixer.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
f14a2000 f14c5000 aec.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
f8b5b000 f8b5c000 drmkaud.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
f15f2000 f15ff000 DMusic.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
f1602000 f1610000 swmidi.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
f8abc000 f8abe000 splitter.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
f18ea000 f18fa000 Serial.SYS
Timestamp: unavailable (00000000)
Checksum: 00000000
f885c000 f8861000 Cdaudio.SYS
Timestamp: unavailable (00000000)
Checksum: 00000000
f8a5c000 f8a5f000 Sfloppy.SYS
Timestamp: unavailable (00000000)
Checksum: 00000000
f8854000 f8859000 Flpydisk.SYS
Timestamp: unavailable (00000000)
Checksum: 00000000
f884c000 f8853000 Fdc.SYS
Timestamp: unavailable (00000000)
Checksum: 00000000
Closing open log file c:\debuglog.txt


i have run a hdd test tool from bios but found no errors, does this kind of tool just look for actual errors on the disc?

Thanks for the continueing support
Dave

If the error status is 0xC000000E, 0xC000009C, 0xC000009D or 0xC0000185,
it means the disk subsystem has experienced a failure.


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


Who is the manufacturer of the hard drive?

Check the Device Manager under Disk drives.

I'd suggest running the manufacturers diagnostic.

Also have you run Check Disk? If not see my next post.


On the surface you have a failing hard drive.