Jump to content

Welcome to Geeks to Go - Register now for FREE

Geeks To Go is a helpful hub, where thousands of volunteer geeks quickly serve friendly answers and support. Check out the forums and get free advice from the experts. Register now to gain access to all of our features, it's FREE and only takes one minute. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more.

Create Account How it Works
Photo

Unexpected shutdown to Data Dump - Old and New HD


  • Please log in to reply

#1
Walt B

Walt B

    New Member

  • Member
  • Pip
  • 7 posts
It may take 10 times to get it to stay booted up, then bang, it shuts down to data dump with the C000021a Fatal System Error. Replaced boot drive with a new one, fresh XP installation. Same thing happens. I've re-Installed XP 3 or 4 times now, but not complete installation - clicked second "R".
Do I have a MotherBoard problem? Homebuilt with mother board 945P-A7A

I've let it sit in Bios setup mode for 4 hours and no shutdown. Then when it boots to XP, it will shut down in a couple of seconds to 10 minutes.

Can this be a hardware problem if it will stay in BIOS setup for 4 hours? I've wondered about the Intel processor, the memory, the mother board. But they work swell in BIOS setup, so can it be a hardware problem? And I've started with new HD and fresh XP install. I'm perplexed. Temperature doesn't seem to be a factor, it happens when the CPU is hot or cold.

I have data dumps and event viewer listings. I think the SQL error is a red herring because the program that uses it isn't installed and the shutdown problem occured before the SQL software was installed. I don't think it is related to installed software because the shutdowns happened on the old HD with XP, then after I ran XP install to repair on the old HD, then after to the fresh install on a new hardrive but before installing any software.

This computer is used in production in my business and help would be appreciated.

Walt B

Events first:

---------

Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7024
Date: 7/16/2009
Time: 6:50:17 AM
User: N/A
Computer: WALT-PRODUCTION
Description:
The SQL Server (SQLEXPRESS) service terminated with service-specific error 3417 (0xD59).

For more information, see Help and Support Center at http://go.microsoft....link/events.asp.

=========================================

Event Type: Error
Event Source: W32Time
Event Category: None
Event ID: 4
Date: 7/15/2009
Time: 2:32:02 PM
User: N/A
Computer:
Description:
The time provider 'NtpClient' failed to start due to the following error: The system cannot find the path specified. (0x80070003)

For more information, see Help and Support Center at http://go.microsoft....link/events.asp.

========================================

Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7024
Date: 7/15/2009
Time: 8:48:12 AM
User: N/A
Computer: WALT-PRODUCTION
Description:
The SQL Server (SQLEXPRESS) service terminated with service-specific error 3417 (0xD59).

For more information, see Help and Support Center at http://go.microsoft....link/events.asp.

=======================================

Event Type: Error
Event Source: DCOM
Event Category: None
Event ID: 10010
Date: 7/15/2009
Time: 8:41:13 AM
User: NT AUTHORITY\SYSTEM
Computer: WALT-PRODUCTION
Description:
The server {C7E39D60-7A9F-42BF-ABB1-03DC0FA4F493} did not register with DCOM within the required timeout.

For more information, see Help and Support Center at http://go.microsoft....link/events.asp.

=====================================

Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7024
Date: 7/15/2009
Time: 8:40:45 AM
User: N/A
Computer: WALT-PRODUCTION
Description:
The SQL Server (SQLEXPRESS) service terminated with service-specific error 3417 (0xD59).

For more information, see Help and Support Center at http://go.microsoft....link/events.asp.

======================================

Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7024
Date: 7/15/2009
Time: 6:15:23 AM
User: N/A
Computer: WALT-PRODUCTION
Description:
The SQL Server (SQLEXPRESS) service terminated with service-specific error 3417 (0xD59).

For more information, see Help and Support Center at http://go.microsoft....link/events.asp.

=======================================

Event Type: Warning
Event Source: Dhcp
Event Category: None
Event ID: 1005
Date: 7/14/2009
Time: 8:07:18 AM
User: N/A
Computer: WALT-PRODUCTION
Description:
Your computer has detected that the IP address 192.168.0.101 for the Network Card with network address 00192143A430 is already in use on the network. Your computer will automatically attempt to obtain a different address.

For more information, see Help and Support Center at http://go.microsoft....link/events.asp.

===========

Event Type: Information
Event Source: Save Dump
Event Category: None
Event ID: 1001
Date: 7/16/2009
Time: 7:05:22 AM
User: N/A
Computer: WALT-PRODUCTION
Description:
The computer has rebooted from a bugcheck. The bugcheck was: 0xc000021a (0xe1a46a40, 0xc0000005, 0x7c9106c3, 0x00c8ed04). A dump was saved in: C:\WINDOWS\MEMORY.DMP.

For more information, see Help and Support Center at http://go.microsoft....link/events.asp.

===========

Event Type: Information
Event Source: Save Dump
Event Category: None
Event ID: 1001
Date: 7/16/2009
Time: 7:04:03 AM
User: N/A
Computer: WALT-PRODUCTION
Description:
The computer has rebooted from a bugcheck. The bugcheck was: 0xc000021a (0xe161ccd0, 0xc0000005, 0x7c9106c3, 0x0069ed04). A dump was saved in: C:\WINDOWS\MEMORY.DMP.

For more information, see Help and Support Center at http://go.microsoft....link/events.asp.

===========

Event Type: Information
Event Source: Save Dump
Event Category: None
Event ID: 1001
Date: 7/16/2009
Time: 7:02:43 AM
User: N/A
Computer: WALT-PRODUCTION
Description:
The computer has rebooted from a bugcheck. The bugcheck was: 0xc000021a (0xe18bcc08, 0xc0000005, 0x7c9106c3, 0x0105ed04). A dump was saved in: C:\WINDOWS\MEMORY.DMP.

For more information, see Help and Support Center at http://go.microsoft....link/events.asp.

==========

Event Type: Information
Event Source: Save Dump
Event Category: None
Event ID: 1001
Date: 7/16/2009
Time: 7:01:21 AM
User: N/A
Computer: WALT-PRODUCTION
Description:
The computer has rebooted from a bugcheck. The bugcheck was: 0xc000021a (0xe1b271c0, 0xc0000005, 0x7c9106c3, 0x0114ed04). A dump was saved in: C:\WINDOWS\MEMORY.DMP.

For more information, see Help and Support Center at http://go.microsoft....link/events.asp.

==========

Event Type: Information
Event Source: Save Dump
Event Category: None
Event ID: 1001
Date: 7/16/2009
Time: 6:59:45 AM
User: N/A
Computer: WALT-PRODUCTION
Description:
The computer has rebooted from a bugcheck. The bugcheck was: 0xc000021a (0xe1875c20, 0xc0000005, 0x7c9106c3, 0x00c8f36c). A dump was saved in: C:\WINDOWS\MEMORY.DMP.

For more information, see Help and Support Center at http://go.microsoft....link/events.asp.

==========

Event Type: Information
Event Source: Save Dump
Event Category: None
Event ID: 1001
Date: 7/16/2009
Time: 6:58:22 AM
User: N/A
Computer: WALT-PRODUCTION
Description:
The computer has rebooted from a bugcheck. The bugcheck was: 0xc000021a (0xe1998948, 0xc0000005, 0x7c9106c3, 0x0069ed04). A dump was saved in: C:\WINDOWS\MEMORY.DMP.

For more information, see Help and Support Center at http://go.microsoft....link/events.asp.

==============

Event Type: Information
Event Source: Save Dump
Event Category: None
Event ID: 1001
Date: 7/16/2009
Time: 6:56:59 AM
User: N/A
Computer: WALT-PRODUCTION
Description:
The computer has rebooted from a bugcheck. The bugcheck was: 0xc000021a (0xe18f8468, 0xc0000005, 0x7c9106c3, 0x00c7ed04). A dump was saved in: C:\WINDOWS\MEMORY.DMP.

For more information, see Help and Support Center at http://go.microsoft....link/events.asp.

=========

Event Type: Information
Event Source: Save Dump
Event Category: None
Event ID: 1001
Date: 7/16/2009
Time: 6:54:13 AM
User: N/A
Computer: WALT-PRODUCTION
Description:
The computer has rebooted from a bugcheck. The bugcheck was: 0xc000021a (0xe1b13490, 0xc0000005, 0x7c9106c3, 0x0052f36c). A dump was saved in: C:\WINDOWS\MEMORY.DMP.

For more information, see Help and Support Center at http://go.microsoft....link/events.asp.

========

Event Type: Information
Event Source: Save Dump
Event Category: None
Event ID: 1001
Date: 7/16/2009
Time: 6:52:53 AM
User: N/A
Computer: WALT-PRODUCTION
Description:
The computer has rebooted from a bugcheck. The bugcheck was: 0xc000021a (0xe17c0f70, 0xc0000005, 0x7c9106c3, 0x00c8ed04). A dump was saved in: C:\WINDOWS\MEMORY.DMP.

For more information, see Help and Support Center at http://go.microsoft....link/events.asp.

=========

Event Type: Information
Event Source: Save Dump
Event Category: None
Event ID: 1001
Date: 7/16/2009
Time: 6:51:32 AM
User: N/A
Computer: WALT-PRODUCTION
Description:
The computer has rebooted from a bugcheck. The bugcheck was: 0xc000021a (0xe1a578b8, 0xc0000005, 0x7c9106c3, 0x0069f074). A dump was saved in: C:\WINDOWS\MEMORY.DMP.

For more information, see Help and Support Center at http://go.microsoft....link/events.asp.

========

Event Type: Information
Event Source: Save Dump
Event Category: None
Event ID: 1001
Date: 7/16/2009
Time: 6:49:55 AM
User: N/A
Computer: WALT-PRODUCTION
Description:
The computer has rebooted from a bugcheck. The bugcheck was: 0xc000021a (0xe1e5e2e0, 0xc0000005, 0x7c9106c3, 0x00c8f36c). A dump was saved in: C:\WINDOWS\MEMORY.DMP.

For more information, see Help and Support Center at http://go.microsoft....link/events.asp.

=======

Event Type: Information
Event Source: Save Dump
Event Category: None
Event ID: 1001
Date: 7/16/2009
Time: 6:48:35 AM
User: N/A
Computer: WALT-PRODUCTION
Description:
The computer has rebooted from a bugcheck. The bugcheck was: 0xc000021a (0xe1879a88, 0xc0000005, 0x7c9106c3, 0x0052f36c). A dump was saved in: C:\WINDOWS\MEMORY.DMP.

For more information, see Help and Support Center at http://go.microsoft....link/events.asp.

=========

=========================================
DATA DUMP
=========================================
Opened log file 'c:debuglog.txt'

Microsoft ® Windows Debugger Version 6.11.0001.404 X86
Copyright © Microsoft Corporation. All rights reserved.


Loading Dump File [C:\WINDOWS\Minidump\Mini071509-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
Windows XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86 compatible
Product: WinNt
Built by: 2600.xpsp_sp2_rtm.040803-2158
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055c700
Debug session time: Wed Jul 15 06:21:05.375 2009 (GMT-7)
System Uptime: 0 days 0:00:49.078
Loading Kernel Symbols
...............................................................
............................................
Loading User Symbols
Loading unloaded module list
....
*************************************************************************** ****
* *
* Bugcheck Analysis *
* *
*************************************************************************** ****

Use !analyze -v to get detailed debugging information.

BugCheck C000021A, {e1993398, c0000005, 7c9106c3, c7f36c}

unable to get nt!KiCurrentEtwBufferOffset
unable to get nt!KiCurrentEtwBufferBase
<Failed to Read Entire ETW Buffer (expected 0, read 0)>Probably caused by : ntkrpamp.exe ( nt!KiFastCallEntry+fc )

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

0: kd> !analyze -v;r;kv;lmtn;.logclose;q
*************************************************************************** ****
* *
* Bugcheck Analysis *
* *
*************************************************************************** ****

WINLOGON_FATAL_ERROR (c000021a)
The Winlogon process terminated unexpectedly.
Arguments:
Arg1: e1993398, String that identifies the problem.
Arg2: c0000005, Error Code.
Arg3: 7c9106c3
Arg4: 00c7f36c

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

unable to get nt!KiCurrentEtwBufferOffset
unable to get nt!KiCurrentEtwBufferBase
<Failed to Read Entire ETW Buffer (expected 0, read 0)>
ERROR_CODE: (NTSTATUS) 0xc000021a - {Fatal System Error} The %hs system process terminated unexpectedly with a status of 0x%08x (0x%08x 0x%08x). The system has been shut down.

EXCEPTION_CODE: (NTSTATUS) 0xc000021a - {Fatal System Error} The %hs system process terminated unexpectedly with a status of 0x%08x (0x%08x 0x%08x). The system has been shut down.

EXCEPTION_PARAMETER1: e1993398

EXCEPTION_PARAMETER2: c0000005

EXCEPTION_PARAMETER3: 7c9106c3

EXCEPTION_PARAMETER4: c7f36c

BUGCHECK_STR: 0xc000021a_c0000005

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

LAST_CONTROL_TRANSFER: from 805c5a5a to 804f9c37

STACK_TEXT:
baad7934 805c5a5a 0000004c c000021a baad79b0 nt!KeBugCheckEx+0x1b
baad7970 80655377 00000001 0000004c c000021a nt!PoShutdownBugCheck+0x5c
baad7b28 8061284a c000021a 00000004 00000001 nt!ExpSystemErrorHandler+0x511
baad7cd4 80612dcb c000021a 00000004 00000001 nt!ExpRaiseHardError+0x9a
baad7d44 8054060c c000021a 00000004 00000001 nt!NtRaiseHardError+0x16b
baad7d44 7c90eb94 c000021a 00000004 00000001 nt!KiFastCallEntry+0xfc
WARNING: Frame IP not in any known module. Following frames may be wrong.
00c7f234 00000000 00000000 00000000 00000000 0x7c90eb94


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!KiFastCallEntry+fc
8054060c 8be5 mov esp,ebp

SYMBOL_STACK_INDEX: 5

SYMBOL_NAME: nt!KiFastCallEntry+fc

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrpamp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 41107b0d

FAILURE_BUCKET_ID: 0xc000021a_c0000005_nt!KiFastCallEntry+fc

BUCKET_ID: 0xc000021a_c0000005_nt!KiFastCallEntry+fc

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

eax=ffdff13c ebx=baad79b0 ecx=00000000 edx=804ff7f5 esi=0000004c edi=c000021a
eip=804f9c37 esp=baad791c ebp=baad7934 iopl=0 nv up ei ng nz na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00000286
nt!KeBugCheckEx+0x1b:
804f9c37 5d pop ebp
ChildEBP RetAddr Args to Child
baad7934 805c5a5a 0000004c c000021a baad79b0 nt!KeBugCheckEx+0x1b (FPO: [5,0,0])
baad7970 80655377 00000001 0000004c c000021a nt!PoShutdownBugCheck+0x5c (FPO: [6,5,0])
baad7b28 8061284a c000021a 00000004 00000001 nt!ExpSystemErrorHandler+0x511 (FPO: [Non-Fpo])
baad7cd4 80612dcb c000021a 00000004 00000001 nt!ExpRaiseHardError+0x9a (FPO: [Non-Fpo])
baad7d44 8054060c c000021a 00000004 00000001 nt!NtRaiseHardError+0x16b (FPO: [Non-Fpo])
baad7d44 7c90eb94 c000021a 00000004 00000001 nt!KiFastCallEntry+0xfc (FPO: [0,0] TrapFrame @ baad7d64)
WARNING: Frame IP not in any known module. Following frames may be wrong.
00c7f234 00000000 00000000 00000000 00000000 0x7c90eb94
start end module name
804d7000 806e2000 nt ntkrpamp.exe Tue Aug 03 22:58:37 2004 (41107B0D)
806e2000 80702d00 hal halmacpi.dll Tue Aug 03 22:59:09 2004 (41107B2D)
b937b000 b93cd180 srv srv.sys Tue Aug 03 23:14:44 2004 (41107ED4)
b941e000 b944a400 mrxdav mrxdav.sys Tue Aug 03 23:00:49 2004 (41107B91)
b982f000 b9832280 ndisuio ndisuio.sys Tue Aug 03 23:03:10 2004 (41107C1E)
ba083000 ba09a480 dump_atapi dump_atapi.sys Tue Aug 03 22:59:41 2004 (41107B4D)
ba163000 ba192820 mfehidk mfehidk.sys Thu Aug 16 08:51:29 2007 (46C47281)
ba193000 ba201380 mrxsmb mrxsmb.sys Tue Aug 03 23:15:14 2004 (41107EF2)
ba202000 ba22d180 rdbss rdbss.sys Tue Aug 03 23:20:05 2004 (41108015)
ba22e000 ba24fd00 afd afd.sys Tue Aug 03 23:14:13 2004 (41107EB5)
ba250000 ba277c00 netbt netbt.sys Tue Aug 03 23:14:36 2004 (41107ECC)
ba278000 ba298f00 ipnat ipnat.sys Tue Aug 03 23:04:48 2004 (41107C80)
ba2c1000 ba2e5000 Mpfp Mpfp.sys Fri Jul 13 07:20:23 2007 (46978A27)
ba2e5000 ba33ca80 tcpip tcpip.sys Tue Aug 03 23:14:39 2004 (41107ECF)
ba33d000 ba34f400 ipsec ipsec.sys Tue Aug 03 23:14:27 2004 (41107EC3)
ba370000 ba383780 VIDEOPRT VIDEOPRT.SYS Tue Aug 03 23:07:04 2004 (41107D08)
ba3ac000 ba3df200 update update.sys Tue Aug 03 22:58:32 2004 (41107B08)
ba3e0000 ba3e2900 Dxapi Dxapi.sys Fri Aug 17 13:53:19 2001 (3B7D843F)
ba3f4000 ba3f7a00 kbdhid kbdhid.sys Tue Aug 03 22:58:33 2004 (41107B09)
ba3f8000 ba3fa580 hidusb hidusb.sys Fri Aug 17 14:02:16 2001 (3B7D8658)
ba408000 ba438100 rdpdr rdpdr.sys Tue Aug 03 23:01:10 2004 (41107BA6)
ba50c000 ba51ce00 psched psched.sys Tue Aug 03 23:04:16 2004 (41107C60)
ba51d000 ba533680 ndiswan ndiswan.sys Tue Aug 03 23:14:30 2004 (41107EC6)
ba534000 ba556680 ks ks.sys Tue Aug 03 23:15:20 2004 (41107EF8)
ba557000 ba56a900 parport parport.sys Tue Aug 03 22:59:04 2004 (41107B28)
ba56b000 ba58de80 USBPORT USBPORT.SYS Tue Aug 03 23:08:34 2004 (41107D62)
ba5ca000 ba5cc280 rasacd rasacd.sys Fri Aug 17 13:55:39 2001 (3B7D84CB)
ba5ee000 ba608580 Mup Mup.sys Tue Aug 03 23:15:20 2004 (41107EF8)
ba609000 ba635a80 NDIS NDIS.sys Tue Aug 03 23:14:27 2004 (41107EC3)
ba636000 ba6c2480 Ntfs Ntfs.sys Tue Aug 03 23:15:06 2004 (41107EEA)
ba6c3000 ba6d9780 KSecDD KSecDD.sys Tue Aug 03 22:59:45 2004 (41107B51)
ba6da000 ba6ebf00 sr sr.sys Tue Aug 03 23:06:22 2004 (41107CDE)
ba6ec000 ba70a780 fltMgr fltMgr.sys Tue Aug 03 23:01:17 2004 (41107BAD)
ba70b000 ba722480 atapi atapi.sys Tue Aug 03 22:59:41 2004 (41107B4D)
ba723000 ba748700 dmio dmio.sys Tue Aug 03 23:07:13 2004 (41107D11)
ba749000 ba767880 ftdisk ftdisk.sys Fri Aug 17 13:52:41 2001 (3B7D8419)
ba768000 ba778a80 pci pci.sys Tue Aug 03 23:07:45 2004 (41107D31)
ba779000 ba7a6d80 ACPI ACPI.sys Tue Aug 03 23:07:35 2004 (41107D27)
ba8a8000 ba8b0c00 isapnp isapnp.sys Fri Aug 17 13:58:01 2001 (3B7D8559)
ba8b8000 ba8c6e80 ohci1394 ohci1394.sys Tue Aug 03 23:10:05 2004 (41107DBD)
ba8c8000 ba8d5000 1394BUS 1394BUS.SYS Tue Aug 03 23:10:03 2004 (41107DBB)
ba8d8000 ba8e2500 MountMgr MountMgr.sys Tue Aug 03 22:58:29 2004 (41107B05)
ba8e8000 ba8f4c80 VolSnap VolSnap.sys Tue Aug 03 23:00:14 2004 (41107B6E)
ba8f8000 ba900e00 disk disk.sys Tue Aug 03 22:59:53 2004 (41107B59)
ba908000 ba914200 CLASSPNP CLASSPNP.SYS Tue Aug 03 23:14:26 2004 (41107EC2)
ba978000 ba980d00 intelppm intelppm.sys Tue Aug 03 22:59:19 2004 (41107B37)
ba988000 ba997180 nic1394 nic1394.sys Tue Aug 03 22:58:28 2004 (41107B04)
ba998000 ba9a7d80 serial serial.sys Tue Aug 03 23:15:51 2004 (41107F17)
ba9a8000 ba9b4e00 i8042prt i8042prt.sys Tue Aug 03 23:14:36 2004 (41107ECC)
ba9b8000 ba9c2380 imapi imapi.sys Tue Aug 03 23:00:12 2004 (41107B6C)
ba9c8000 ba9d4180 cdrom cdrom.sys Tue Aug 03 22:59:52 2004 (41107B58)
ba9d8000 ba9e6080 redbook redbook.sys Tue Aug 03 22:59:34 2004 (41107B46)
ba9e8000 ba9f4880 rasl2tp rasl2tp.sys Tue Aug 03 23:14:21 2004 (41107EBD)
ba9f8000 baa02200 raspppoe raspppoe.sys Tue Aug 03 23:05:06 2004 (41107C92)
baa08000 baa13d00 raspptp raspptp.sys Tue Aug 03 23:14:26 2004 (41107EC2)
baa18000 baa20900 msgpc msgpc.sys Tue Aug 03 23:04:11 2004 (41107C5B)
baa38000 baa41f00 termdd termdd.sys Tue Aug 03 22:58:52 2004 (41107B1C)
baa48000 baa51480 NDProxy NDProxy.SYS Fri Aug 17 13:55:30 2001 (3B7D84C2)
baa58000 baa66100 usbhub usbhub.sys Tue Aug 03 23:08:40 2004 (41107D68)
baa78000 baa80080 ipfltdrv ipfltdrv.sys Fri Aug 17 13:55:07 2001 (3B7D84AB)
baa88000 baa90700 wanarp wanarp.sys Tue Aug 03 23:04:57 2004 (41107C89)
baa98000 baaa6d80 arp1394 arp1394.sys Tue Aug 03 22:58:28 2004 (41107B04)
baaa8000 baab0700 netbios netbios.sys Tue Aug 03 23:03:19 2004 (41107C27)
baab8000 baac0880 Fips Fips.SYS Fri Aug 17 18:31:49 2001 (3B7DC585)
baad8000 baae7900 Cdfs Cdfs.SYS Tue Aug 03 23:14:09 2004 (41107EB1)
baaf8000 bab00d80 HIDCLASS HIDCLASS.SYS Tue Aug 03 23:08:18 2004 (41107D52)
bab28000 bab2e200 PCIIDEX PCIIDEX.SYS Tue Aug 03 22:59:40 2004 (41107B4C)
bab30000 bab34900 PartMgr PartMgr.sys Fri Aug 17 18:32:23 2001 (3B7DC5A7)
bab88000 bab8d000 usbuhci usbuhci.sys Tue Aug 03 23:08:34 2004 (41107D62)
bab90000 bab96800 usbehci usbehci.sys Tue Aug 03 23:08:34 2004 (41107D62)
bab98000 bab9c280 usbohci usbohci.sys Tue Aug 03 23:08:34 2004 (41107D62)
baba0000 baba5200 RTL8139 RTL8139.SYS Thu Jun 12 22:29:46 2003 (3EE9614A)
baba8000 babaeb00 fdc fdc.sys Tue Aug 03 22:59:25 2004 (41107B3D)
babb0000 babb5a00 mouclass mouclass.sys Tue Aug 03 22:58:32 2004 (41107B08)
babb8000 babbe000 kbdclass kbdclass.sys Tue Aug 03 22:58:32 2004 (41107B08)
babc0000 babc4880 TDI TDI.SYS Tue Aug 03 23:07:47 2004 (41107D33)
babc8000 babcc580 ptilink ptilink.sys Fri Aug 17 13:49:53 2001 (3B7D8371)
babd0000 babd4080 raspti raspti.sys Fri Aug 17 13:55:32 2001 (3B7D84C4)
babe8000 babee180 HIDPARSE HIDPARSE.SYS Tue Aug 03 23:08:15 2004 (41107D4F)
babf0000 babf5200 vga vga.sys Tue Aug 03 23:07:06 2004 (41107D0A)
babf8000 babfca80 Msfs Msfs.SYS Tue Aug 03 23:00:37 2004 (41107B85)
bac00000 bac07880 Npfs Npfs.SYS Tue Aug 03 23:00:38 2004 (41107B86)
bac20000 bac26780 USBSTOR USBSTOR.SYS Tue Aug 03 23:08:44 2004 (41107D6C)
bac28000 bac2fb80 usbccgp usbccgp.sys Tue Aug 03 23:08:45 2004 (41107D6D)
bac30000 bac34500 watchdog watchdog.sys Tue Aug 03 23:07:32 2004 (41107D24)
bacb8000 bacbb000 BOOTVID BOOTVID.dll Fri Aug 17 13:49:09 2001 (3B7D8345)
bad44000 bad47c80 serenum serenum.sys Tue Aug 03 22:59:06 2004 (41107B2A)
bad4c000 bad4e580 ndistapi ndistapi.sys Fri Aug 17 13:55:29 2001 (3B7D84C1)
bad68000 bad6bc80 mssmbios mssmbios.sys Tue Aug 03 23:07:47 2004 (41107D33)
bada8000 bada9b80 kdcom kdcom.dll Fri Aug 17 13:49:10 2001 (3B7D8346)
badaa000 badab100 WMILIB WMILIB.SYS Fri Aug 17 14:07:23 2001 (3B7D878B)
badac000 badad700 dmload dmload.sys Fri Aug 17 13:58:15 2001 (3B7D8567)
badb8000 badb9100 swenum swenum.sys Tue Aug 03 22:58:41 2004 (41107B11)
badba000 badbb280 USBD USBD.SYS Fri Aug 17 14:02:58 2001 (3B7D8682)
badbc000 badbdf00 Fs_Rec Fs_Rec.SYS Fri Aug 17 13:49:37 2001 (3B7D8361)
badbe000 badbf080 Beep Beep.SYS Fri Aug 17 13:47:33 2001 (3B7D82E5)
badc0000 badc1080 mnmdd mnmdd.SYS Fri Aug 17 13:57:28 2001 (3B7D8538)
badc2000 badc3080 RDPCDD RDPCDD.sys Fri Aug 17 13:46:56 2001 (3B7D82C0)
badcc000 badcd100 dump_WMILIB dump_WMILIB.SYS Fri Aug 17 14:07:23 2001 (3B7D878B)
bae1a000 bae1ba80 ParVdm ParVdm.SYS Fri Aug 17 13:49:49 2001 (3B7D836D)
bae70000 bae70d00 pciide pciide.sys Fri Aug 17 13:51:49 2001 (3B7D83E5)
baeb4000 baeb4b80 Null Null.SYS Fri Aug 17 13:47:39 2001 (3B7D82EB)
baf44000 baf44c00 audstub audstub.sys Fri Aug 17 13:59:40 2001 (3B7D85BC)
bafc2000 bafc2d00 dxgthk dxgthk.sys Fri Aug 17 13:53:12 2001 (3B7D8438)
bf800000 bf9c0380 win32k win32k.sys Tue Aug 03 23:17:30 2004 (41107F7A)
bf9c1000 bf9d2580 dxg dxg.sys Tue Aug 03 23:00:51 2004 (41107B93)
bff50000 bff52480 framebuf framebuf.dll Wed Aug 04 00:56:31 2004 (411096AF)
bffa0000 bffe5c00 ATMFD ATMFD.DLL Wed Aug 04 00:56:56 2004 (411096C8)

Unloaded modules:
bada4000 bada8000 kbdhid.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
babe0000 babe5000 Cdaudio.SYS
Timestamp: unavailable (00000000)
Checksum: 00000000
bada0000 bada3000 Sfloppy.SYS
Timestamp: unavailable (00000000)
Checksum: 00000000
babd8000 babdd000 Flpydisk.SYS
Timestamp: unavailable (00000000)
Checksum: 00000000
Closing open log file c:debuglog.txt
  • 0

Advertisements


#2
123Runner

123Runner

    Member 4k

  • Member
  • PipPipPipPipPipPipPip
  • 4,307 posts
Welcome to Geeks to Go.
It seems that you have eliminated it being the OS. Indications are that its conflicting software or drivers though. And, of course, it could be hardware.
Sitting in BIOS is not exercising the computer. There are no programs running and there is no heat generated. I do not suspect the CPU as of yet for heat because it does not shut down in BIOS.
The next step is to see if you can load safemode. Try just safemode, and then safe mode with networking. Safe mode loads basic drivers. If safemode works and safemode with networking does not, then we have a conflict.

I need to verify. I believe you staed that all you have loaded is the OS (no other software). Is this correct? and it still shuts down.
We could be looking at a weak/bad PSU. With minimal running, there is no "demand" on the PSU. can you swap a PSU for a test?
  • 0

#3
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
Have you tried to boot into Safe Mode and see if the issue occurs there?
If not then I would say it's a drivers issue.
  • 0

#4
Walt B

Walt B

    New Member

  • Topic Starter
  • Member
  • Pip
  • 7 posts

Welcome to Geeks to Go.
It seems that you have eliminated it being the OS. Indications are that its conflicting software or drivers though. And, of course, it could be hardware.
Sitting in BIOS is not exercising the computer. There are no programs running and there is no heat generated. I do not suspect the CPU as of yet for heat because it does not shut down in BIOS.
The next step is to see if you can load safemode. Try just safemode, and then safe mode with networking. Safe mode loads basic drivers. If safemode works and safemode with networking does not, then we have a conflict.

I need to verify. I believe you staed that all you have loaded is the OS (no other software). Is this correct? and it still shuts down.
We could be looking at a weak/bad PSU. With minimal running, there is no "demand" on the PSU. can you swap a PSU for a test?

I do have some software installed now, but I had the problem right after the fresh XP install, and of course before changing HD's. The problem was the reason for changing HD's.

The computer will shut down to data dump when the CPU hasn't had much chance to warm up, and when it has been running awhile.

I booted to SAFE and no problems after 10 minutes. I booted to SAFE with NETWORKING and left that running the TOUR WINDOWS XP animated thingy for 2 hours w/o problem. Everything seems to work swell.

What's the diagnosis? How to I fix an unknown driver problem?

I do not have a second PSU to test with.

Walt B
  • 0

#5
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
Download WhoCrashed from the link in my signature below
This program checks for any drivers which may have been causing your computer to crash....

Click on the file you just downloaded and run it.
Put a tick in Accept then click on Next
Put a tick in the Don't create a start menu folder then click Next
Put a tick in Create a Desktop Icon then click on Install and make sure there is a tick in Launch Whocrashed before clicking Finish
Click Analyze
It will want to download the Debugger and install it Say Yes

WhoCrashed will create report but you have to scroll down to see it
Copy and paste it into your next reply
  • 0

#6
Walt B

Walt B

    New Member

  • Topic Starter
  • Member
  • Pip
  • 7 posts

Download WhoCrashed from the link in my signature below
This program checks for any drivers which may have been causing your computer to crash....

Click on the file you just downloaded and run it.
Put a tick in Accept then click on Next
Put a tick in the Don't create a start menu folder then click Next
Put a tick in Create a Desktop Icon then click on Install and make sure there is a tick in Launch Whocrashed before clicking Finish
Click Analyze
It will want to download the Debugger and install it Say Yes

WhoCrashed will create report but you have to scroll down to see it
Copy and paste it into your next reply




--------------------------------------------------------------------------------
Welcome to WhoCrashed Home Edition 1.01

--------------------------------------------------------------------------------
Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\WINDOWS\Minidump

Crash dumps are enabled on your computer.


On Fri 7/17/2009 10:38:17 PM your computer crashed
This was likely caused by the following module: ipnat.sys
Bugcheck code: 0xFFFFFFFFC000021A (0xE1E1B498, 0xC0000005, 0x7C9106C3, 0x69F36C)
Error: STATUS_SYSTEM_PROCESS_TERMINATED
file path: C:\WINDOWS\system32\drivers\ipnat.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: IP Network Address Translator
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



On Fri 7/17/2009 7:19:04 PM your computer crashed
This was likely caused by the following module: ntkrnlpa.exe
Bugcheck code: 0xFFFFFFFFC000021A (0xE17046F0, 0xC0000005, 0x7C9106C3, 0xCDED04)
Error: STATUS_SYSTEM_PROCESS_TERMINATED
file path: C:\WINDOWS\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



On Fri 7/17/2009 6:05:10 PM your computer crashed
This was likely caused by the following module: ntkrnlpa.exe
Bugcheck code: 0xFFFFFFFFC000021A (0xE1066F08, 0xC0000005, 0x7C9106C3, 0xC7F36C)
Error: STATUS_SYSTEM_PROCESS_TERMINATED
file path: C:\WINDOWS\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



On Fri 7/17/2009 5:48:01 PM your computer crashed
This was likely caused by the following module: ntkrnlpa.exe
Bugcheck code: 0xFFFFFFFFC000021A (0xE1742B88, 0xC0000005, 0x7C9106C3, 0x69ED04)
Error: STATUS_SYSTEM_PROCESS_TERMINATED
file path: C:\WINDOWS\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



On Fri 7/17/2009 5:26:56 PM your computer crashed
This was likely caused by the following module: ntkrnlpa.exe
Bugcheck code: 0xFFFFFFFFC000021A (0xE19AD768, 0xC0000005, 0x7C9106C3, 0xC7EFC8)
Error: STATUS_SYSTEM_PROCESS_TERMINATED
file path: C:\WINDOWS\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



On Thu 7/16/2009 4:28:28 PM your computer crashed
This was likely caused by the following module: ntkrnlpa.exe
Bugcheck code: 0xFFFFFFFFC000021A (0xE1A96E98, 0xC0000005, 0x7C9106C3, 0xC7ED04)
Error: STATUS_SYSTEM_PROCESS_TERMINATED
file path: C:\WINDOWS\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



On Thu 7/16/2009 2:04:02 PM your computer crashed
This was likely caused by the following module: ntkrnlpa.exe
Bugcheck code: 0xFFFFFFFFC000021A (0xE161CCD0, 0xC0000005, 0x7C9106C3, 0x69ED04)
Error: STATUS_SYSTEM_PROCESS_TERMINATED
file path: C:\WINDOWS\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



On Thu 7/16/2009 2:02:42 PM your computer crashed
This was likely caused by the following module: ntkrnlpa.exe
Bugcheck code: 0xFFFFFFFFC000021A (0xE18BCC08, 0xC0000005, 0x7C9106C3, 0x105ED04)
Error: STATUS_SYSTEM_PROCESS_TERMINATED
file path: C:\WINDOWS\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



On Thu 7/16/2009 1:59:44 PM your computer crashed
This was likely caused by the following module: ntkrnlpa.exe
Bugcheck code: 0xFFFFFFFFC000021A (0xE1875C20, 0xC0000005, 0x7C9106C3, 0xC8F36C)
Error: STATUS_SYSTEM_PROCESS_TERMINATED
file path: C:\WINDOWS\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



On Thu 7/16/2009 1:58:20 PM your computer crashed
This was likely caused by the following module: ntkrnlpa.exe
Bugcheck code: 0xFFFFFFFFC000021A (0xE1998948, 0xC0000005, 0x7C9106C3, 0x69ED04)
Error: STATUS_SYSTEM_PROCESS_TERMINATED
file path: C:\WINDOWS\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



On Thu 7/16/2009 1:54:12 PM your computer crashed
This was likely caused by the following module: ntkrnlpa.exe
Bugcheck code: 0xFFFFFFFFC000021A (0xE1B13490, 0xC0000005, 0x7C9106C3, 0x52F36C)
Error: STATUS_SYSTEM_PROCESS_TERMINATED
file path: C:\WINDOWS\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



On Thu 7/16/2009 1:52:52 PM your computer crashed
This was likely caused by the following module: ntkrnlpa.exe
Bugcheck code: 0xFFFFFFFFC000021A (0xE17C0F70, 0xC0000005, 0x7C9106C3, 0xC8ED04)
Error: STATUS_SYSTEM_PROCESS_TERMINATED
file path: C:\WINDOWS\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



On Thu 7/16/2009 1:49:54 PM your computer crashed
This was likely caused by the following module: ntkrnlpa.exe
Bugcheck code: 0xFFFFFFFFC000021A (0xE1E5E2E0, 0xC0000005, 0x7C9106C3, 0xC8F36C)
Error: STATUS_SYSTEM_PROCESS_TERMINATED
file path: C:\WINDOWS\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



On Thu 7/16/2009 1:48:33 PM your computer crashed
This was likely caused by the following module: ntkrnlpa.exe
Bugcheck code: 0xFFFFFFFFC000021A (0xE1879A88, 0xC0000005, 0x7C9106C3, 0x52F36C)
Error: STATUS_SYSTEM_PROCESS_TERMINATED
file path: C:\WINDOWS\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



On Wed 7/15/2009 6:52:36 PM your computer crashed
This was likely caused by the following module: ntkrnlpa.exe
Bugcheck code: 0xFFFFFFFFC000021A (0xE15BE0F0, 0xC0000005, 0x7C9106C3, 0x52ED04)
Error: STATUS_SYSTEM_PROCESS_TERMINATED
file path: C:\WINDOWS\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



On Wed 7/15/2009 5:55:42 PM your computer crashed
This was likely caused by the following module: ntkrnlpa.exe
Bugcheck code: 0xFFFFFFFFC000021A (0xE177D090, 0xC0000005, 0x7C9106C3, 0x69ED04)
Error: STATUS_SYSTEM_PROCESS_TERMINATED
file path: C:\WINDOWS\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



On Wed 7/15/2009 3:47:50 PM your computer crashed
This was likely caused by the following module: ntkrnlpa.exe
Bugcheck code: 0xFFFFFFFFC000021A (0xE19791C0, 0xC0000005, 0x7C9106C3, 0x52F36C)
Error: STATUS_SYSTEM_PROCESS_TERMINATED
file path: C:\WINDOWS\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



On Wed 7/15/2009 1:32:17 PM your computer crashed
This was likely caused by the following module: ntkrnlpa.exe
Bugcheck code: 0xFFFFFFFFC000021A (0xE1993398, 0xC0000005, 0x7C9106C3, 0xC7F36C)
Error: STATUS_SYSTEM_PROCESS_TERMINATED
file path: C:\WINDOWS\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



On Tue 7/14/2009 8:56:32 PM your computer crashed
This was likely caused by the following module: ntkrnlpa.exe
Bugcheck code: 0xFFFFFFFFC000021A (0xE107E1C0, 0xC0000005, 0x7C9106C3, 0x69ED04)
Error: STATUS_SYSTEM_PROCESS_TERMINATED
file path: C:\WINDOWS\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



On Tue 7/14/2009 7:41:35 PM your computer crashed
This was likely caused by the following module: ntkrnlpa.exe
Bugcheck code: 0xFFFFFFFFC000021A (0xE1E31168, 0xC0000005, 0x7C9106C3, 0x52ED04)
Error: STATUS_SYSTEM_PROCESS_TERMINATED
file path: C:\WINDOWS\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



On Tue 7/14/2009 5:44:12 PM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0xFFFFFFFFC000021A (0xE10CE488, 0xC0000005, 0x75E91941, 0xD3DF58)
Error: STATUS_SYSTEM_PROCESS_TERMINATED
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.




--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

21 crash dumps have been found and analyzed. Note that it's not always possible to state with certainty whether a reported driver is really responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.
  • 0

#7
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
I see only three files causing your crashes. The first and last happened one time. The middle one happened 19 times in the last 3 days.
First one is ipnat.sys...this seems to be related to a firewall


The second is ntkrnlpa.exe
This i'm researching to see what it is for sure. It is part of the windows system files .


Third is ntoskrnl.exe... this is a system file.

My first suggestion would be to run chkdsk /r
To do this follow the next steps....

Go to
Start and then to Run
Type in Chkdsk /r Note the space between k and /
Click Enter ...It will probably ask if you want to do this on the next reboot...click Y

If the window doesn't shutdown on its own then reboot the system manually. On reboot the system will start the chkdsk operation
This one will take longer then chkdsk /f

Note... there are 5 stages...
It may appear to hang at a certain percent for a hour or more or even back up and go over the same area...this is normal...
DO NOT SHUT YOUR COMPUTER DOWN WHILE CHKDSK IS RUNNING OR YOU CAN HAVE SEVERE PROBLEMS
This can take several hours to complete.
When completed it will boot the system back into windows.

Let me know if this fixes the problem

Edited by rshaffer61, 17 July 2009 - 11:51 PM.

  • 0

#8
Walt B

Walt B

    New Member

  • Topic Starter
  • Member
  • Pip
  • 7 posts
"It may appear to hang at a certain percent for a hour or more or even back up and go over the same area...this is normal...
DO NOT SHUT YOUR COMPUTER DOWN WHILE CHKDSK IS RUNNING OR YOU CAN HAVE SEVERE PROBLEMS
This can take several hours to complete.
When completed it will boot the system back into windows."


This is going to be a problem unless I can run it in SAFE mode. In normal mode it will crash in minutes or seconds.

Walt B
  • 0

#9
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
Chkdsk does not run in windows. The system will have to reboot and it runs before windows loads.
Basically what was once DOS mode.
Therefor the system should stay running
  • 0

#10
Walt B

Walt B

    New Member

  • Topic Starter
  • Member
  • Pip
  • 7 posts
ok, it is in stage 4 of 5 at 46 percent. I'll let it run overnight and check it in the AM.

WB
  • 0

#11
Walt B

Walt B

    New Member

  • Topic Starter
  • Member
  • Pip
  • 7 posts
chkdsk is complete.

"Disk is clean"

It rebooted to Windows, I'm looking at the desktop. Hasn't crashed. I'll let it sit overnight.

Thanks. Hope this does it. Pretty exciting if it's fixed!

WB
  • 0

#12
Walt B

Walt B

    New Member

  • Topic Starter
  • Member
  • Pip
  • 7 posts
Dang. It stayed alive in Windows for about 4 or 5 minutes, and then shut down.

wb
  • 0

#13
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
OK your problem is in normal windows then the problem is a driver, try this


Go Start and then to Run ("Start Search" in Vista),
Type in: sfc /scannow
Click OK (Enter in Vista).
Have Windows CD/DVD handy.
If System File Checker (sfc) finds any errors, it may ask you for the CD/DVD.
If sfc does not find any errors in Windows XP, it will simply quit, without any message.
In Vista you will receive the following message: "Windows resource protection did not find any integrity violations".

For Vista users ONLY: Navigate to C:\Windows\Logs\CBS folder. You'll see CBS.log file.
Usually, it's pretty big file, so upload it to Flyupload, and post download link.


If you don't have Windows CD....
This applies mostly to Windows XP, since Vista rarely requires use of its DVD while running "sfc"
Note This method will not necessarily work as well, as when using Windows CD, because not always ALL system files are backed up on your hard drive. Also, backed up files may be corrupted as well.

Go Start and then Run
type in regedit and click OK


Navigate to the following key:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Setup

You will see various entries Values on the right hand side.

The one we want is called: SourcePath

It probably has an entry pointing to your CD-ROM drive, usually D and that is why it is asking for the XP CD.
All we need to do is change it to: C:
Now, double click the SourcePatch setting and a new box will pop up.
Change the drive letter from your CD drive to your root drive, usually C:
Close Registry Editor.

Now restart your computer and try sfc /scannow again!
  • 0






Similar Topics

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users

As Featured On:

Microsoft Yahoo BBC MSN PC Magazine Washington Post HP