Could "missing or corrupt hal.dll" be a symptom of hardware failure?
Over the last week I've been having more and more crashes. Below are a (I hope) representative selection of logs for them. Finally in frustration I removed all my hardware and reinstalled windows. All went well (for 5 minutes, as I basked in the glow of my achievement), then I tried to install a bluetooth device. A reboot was called for. Then I received "the following file is missing or corrupt <windows root>\system32\hal.dll". I've installed on a previously unused hd. I haven't connected to the web at all for any reason on the pc in question, so, could I sue the producers of the bluetooth software for time and effort (;-))? I'm thinking that my video card may be at fault, but I just don't know. Any ideas much appriciated.
Event Type: Error
Event Source: EventSystem
Event Category: (50)
Event ID: 4609
Date: 28/07/2004
Time: 10:53:38
User: N/A
Description:
The COM+ Event System detected a bad return code during its internal processing. HRESULT was 8007043C from line 44 of d:\nt_qxp\com\com1x\src\ev
Event Type: Error
Event Source: VSS
Event Category: None
Event ID: 8193
Date: 28/07/2004
Time: 10:53:38
User: N/A
Description: Volume Shadow Copy Service error: Unexpected error calling routine CoCreateInstance. hr = 0x80040206.
Data:
0000: 57 52 54 57 52 54 49 43 WRTWRTIC
0008: 32 31 31 33 00 00 00 00 2113....
0010: 57 52 54 57 52 54 49 43 WRTWRTIC
0018: 32 30 37 38 00 00 00 00 2078....
Event Type: Error
Event Source: DCOM
Event Category: None
Event ID: 10005
Date: 05/08/2004
Time: 09:53:49
User:
Description:
DCOM got error "The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. " attempting to start the service EventSystem with arguments "" in order to run the server:
{1BE1F766-5536-11D1-B726-0
Event Type: Error
Event Source: VSS
Event Category: None
Event ID: 8193
Date: 04/08/2004
Time: 11:30:56
User: N/A
Description:
Volume Shadow Copy Service error: Unexpected error calling routine CoCreateInstance. hr = 0x80040206.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 57 52 54 57 52 54 49 43 WRTWRTIC
0008: 32 31 31 33 00 00 00 00 2113....
0010: 57 52 54 57 52 54 49 43 WRTWRTIC
0018: 32 30 37 38 00 00 00 00 2078....
Event Type: Error
Event Source: EventSystem
Event Category: (50)
Event ID: 4609
Date: 04/08/2004
Time: 11:30:56
User: N/A
Description: The COM+ Event System detected a bad return code during its internal processing. HRESULT was 8007043C from line 44 of d:\nt_qxp\com\com1x\src\ev
Event Type: Error
Event Source: Application Hang
Event Category: (101)
Event ID: 1002
Date: 03/08/2004
Time: 18:14:20
User: N/A
Description: Hanging application iexplore.exe, version 6.0.2800.1106, hang module hungapp, version 0.0.0.0, hang address 0x00000000.
Data:
0000: 41 70 70 6c 69 63 61 74 Applicat
0008: 69 6f 6e 20 48 61 6e 67 ion Hang
0010: 20 20 69 65 78 70 6c 6f iexplo
0018: 72 65 2e 65 78 65 20 36 re.exe 6
0020: 2e 30 2e 32 38 30 30 2e .0.2800.
0028: 31 31 30 36 20 69 6e 20 1106 in
0030: 68 75 6e 67 61 70 70 20 hungapp
0038: 30 2e 30 2e 30 2e 30 20 0.0.0.0
0040: 61 74 20 6f 66 66 73 65 at offse
0048: 74 20 30 30 30 30 30 30 t 000000
0050: 30 30 00
Event Type: Error
Event Source: Application Error
Event Category: None
Event ID: 1000
Date: 03/08/2004
Time: 18:13:43
User: N/A
Description: Faulting application iexplore.exe, version 6.0.2800.1106, faulting module ntdll.dll, version 5.1.2600.1217, fault address 0x00033aed.
Data:
0000: 41 70 70 6c 69 63 61 74 Applicat
0008: 69 6f 6e 20 46 61 69 6c ion Fail
0010: 75 72 65 20 20 69 65 78 ure iex
0018: 70 6c 6f 72 65 2e 65 78 plore.ex
0020: 65 20 36 2e 30 2e 32 38 e 6.0.28
0028: 30 30 2e 31 31 30 36 20 00.1106
0030: 69 6e 20 6e 74 64 6c 6c in ntdll
0038: 2e 64 6c 6c 20 35 2e 31 .dll 5.1
0040: 2e 32 36 30 30 2e 31 32 .2600.12
0048: 31 37 20 61 74 20 6f 66 17 at of
0050: 66 73 65 74 20 30 30 30 fset 000
0058: 33 33 61 65 64 0d 0a 33aed..
Event Type: Error
Event Source: VSS
Event Category: None
Event ID: 8193
Date: 28/07/2004
Time: 11:10:16
User: N/A
Description: Volume Shadow Copy Service error: Unexpected error calling routine CoCreateInstance. hr = 0x80040206.
Data:
0000: 57 52 54 57 52 54 49 43 WRTWRTIC
0008: 32 31 31 33 00 00 00 00 2113....
0010: 57 52 54 57 52 54 49 43 WRTWRTIC
0018: 32 30 37 38 00 00 00 00 2078....
Event Type: Error
Event Source: EventSystem
Event Category: (50)
Event ID: 4609
Date: 28/07/2004
Time: 11:10:16
User: N/A
Description: The COM+ Event System detected a bad return code during its internal processing. HRESULT was 8007043C from line 44 of d:\nt_qxp\com\com1x\src\ev
Event Type: Error
Event Source: VSS
Event Category: None
Event ID: 8193
Date: 28/07/2004
Time: 10:53:38
User: N/A
Description: Volume Shadow Copy Service error: Unexpected error calling routine CoCreateInstance. hr = 0x80040206.
Data:
0000: 57 52 54 57 52 54 49 43 WRTWRTIC
0008: 32 31 31 33 00 00 00 00 2113....
0010: 57 52 54 57 52 54 49 43 WRTWRTIC
0018: 32 30 37 38 00 00 00 00 2078....
Event Type: Error
Event Source: EventSystem
Event Category: (50)
Event ID: 4609
Date: 28/07/2004
Time: 10:53:38
User: N/A
Description: The COM+ Event System detected a bad return code during its internal processing. HRESULT was 8007043C from line 44 of d:\nt_qxp\com\com1x\src\ev
Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7026
Date: 04/08/2004
Time: 11:32:21
User: N/A
Description:
The following boot-start or system-start driver(s) failed to load:
AmdK7
Fips
IPSec
KmxFw
MRxSmb
NetBIOS
NetBT
RasAcd
Rdbss
Tcpip
Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7001
Date: 04/08/2004
Time: 11:32:21
User: N/A
Description: The IPSEC Services service depends on the IPSEC driver service which failed to start because of the following error:
A device attached to the system is not functioning.
Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7001
Date: 04/08/2004
Time: 11:32:21
User: N/A
Description: The Messenger service depends on the NetBIOS Interface service which failed to start because of the following error:
A device attached to the system is not functioning.
Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7001
Date: 04/08/2004
Time: 11:32:21
User: N/A
Description: The DHCP Client service depends on the SYMTDI service which failed to start because of the following error:
The dependency service or group failed to start.
Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7001
Date: 04/08/2004
Time: 11:32:21
User: N/A
Description: The SYMTDI service depends on the TCP/IP Protocol Driver service which failed to start because of the following error:
A device attached to the system is not functioning.
Event Type: Information
Event Source: Save Dump
Event Category: None
Event ID: 1001
Date: 04/08/2004
Time: 11:30:54
User: N/A
Description:
The computer has rebooted from a bugcheck. The bugcheck was: 0x0000000a (0xc051d0c7, 0x00000002, 0x00000000, 0x8050bfd0). A dump was saved in: C:\WINDOWS\Minidump\Mini08
Event Type: Error
Event Source: EventSystem
Event Category: (50)
Event ID: 4609
Date: 28/07/2004
Time: 10:53:38
User: N/A
Description:
The COM+ Event System detected a bad return code during its internal processing. HRESULT was 8007043C from line 44 of d:\nt_qxp\com\com1x\src\ev
Event Type: Error
Event Source: VSS
Event Category: None
Event ID: 8193
Date: 28/07/2004
Time: 10:53:38
User: N/A
Description: Volume Shadow Copy Service error: Unexpected error calling routine CoCreateInstance. hr = 0x80040206.
Data:
0000: 57 52 54 57 52 54 49 43 WRTWRTIC
0008: 32 31 31 33 00 00 00 00 2113....
0010: 57 52 54 57 52 54 49 43 WRTWRTIC
0018: 32 30 37 38 00 00 00 00 2078....
Event Type: Error
Event Source: DCOM
Event Category: None
Event ID: 10005
Date: 05/08/2004
Time: 09:53:49
User:
Description:
DCOM got error "The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. " attempting to start the service EventSystem with arguments "" in order to run the server:
{1BE1F766-5536-11D1-B726-0
Event Type: Error
Event Source: VSS
Event Category: None
Event ID: 8193
Date: 04/08/2004
Time: 11:30:56
User: N/A
Description:
Volume Shadow Copy Service error: Unexpected error calling routine CoCreateInstance. hr = 0x80040206.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 57 52 54 57 52 54 49 43 WRTWRTIC
0008: 32 31 31 33 00 00 00 00 2113....
0010: 57 52 54 57 52 54 49 43 WRTWRTIC
0018: 32 30 37 38 00 00 00 00 2078....
Event Type: Error
Event Source: EventSystem
Event Category: (50)
Event ID: 4609
Date: 04/08/2004
Time: 11:30:56
User: N/A
Description: The COM+ Event System detected a bad return code during its internal processing. HRESULT was 8007043C from line 44 of d:\nt_qxp\com\com1x\src\ev
Event Type: Error
Event Source: Application Hang
Event Category: (101)
Event ID: 1002
Date: 03/08/2004
Time: 18:14:20
User: N/A
Description: Hanging application iexplore.exe, version 6.0.2800.1106, hang module hungapp, version 0.0.0.0, hang address 0x00000000.
Data:
0000: 41 70 70 6c 69 63 61 74 Applicat
0008: 69 6f 6e 20 48 61 6e 67 ion Hang
0010: 20 20 69 65 78 70 6c 6f iexplo
0018: 72 65 2e 65 78 65 20 36 re.exe 6
0020: 2e 30 2e 32 38 30 30 2e .0.2800.
0028: 31 31 30 36 20 69 6e 20 1106 in
0030: 68 75 6e 67 61 70 70 20 hungapp
0038: 30 2e 30 2e 30 2e 30 20 0.0.0.0
0040: 61 74 20 6f 66 66 73 65 at offse
0048: 74 20 30 30 30 30 30 30 t 000000
0050: 30 30 00
Event Type: Error
Event Source: Application Error
Event Category: None
Event ID: 1000
Date: 03/08/2004
Time: 18:13:43
User: N/A
Description: Faulting application iexplore.exe, version 6.0.2800.1106, faulting module ntdll.dll, version 5.1.2600.1217, fault address 0x00033aed.
Data:
0000: 41 70 70 6c 69 63 61 74 Applicat
0008: 69 6f 6e 20 46 61 69 6c ion Fail
0010: 75 72 65 20 20 69 65 78 ure iex
0018: 70 6c 6f 72 65 2e 65 78 plore.ex
0020: 65 20 36 2e 30 2e 32 38 e 6.0.28
0028: 30 30 2e 31 31 30 36 20 00.1106
0030: 69 6e 20 6e 74 64 6c 6c in ntdll
0038: 2e 64 6c 6c 20 35 2e 31 .dll 5.1
0040: 2e 32 36 30 30 2e 31 32 .2600.12
0048: 31 37 20 61 74 20 6f 66 17 at of
0050: 66 73 65 74 20 30 30 30 fset 000
0058: 33 33 61 65 64 0d 0a 33aed..
Event Type: Error
Event Source: VSS
Event Category: None
Event ID: 8193
Date: 28/07/2004
Time: 11:10:16
User: N/A
Description: Volume Shadow Copy Service error: Unexpected error calling routine CoCreateInstance. hr = 0x80040206.
Data:
0000: 57 52 54 57 52 54 49 43 WRTWRTIC
0008: 32 31 31 33 00 00 00 00 2113....
0010: 57 52 54 57 52 54 49 43 WRTWRTIC
0018: 32 30 37 38 00 00 00 00 2078....
Event Type: Error
Event Source: EventSystem
Event Category: (50)
Event ID: 4609
Date: 28/07/2004
Time: 11:10:16
User: N/A
Description: The COM+ Event System detected a bad return code during its internal processing. HRESULT was 8007043C from line 44 of d:\nt_qxp\com\com1x\src\ev
Event Type: Error
Event Source: VSS
Event Category: None
Event ID: 8193
Date: 28/07/2004
Time: 10:53:38
User: N/A
Description: Volume Shadow Copy Service error: Unexpected error calling routine CoCreateInstance. hr = 0x80040206.
Data:
0000: 57 52 54 57 52 54 49 43 WRTWRTIC
0008: 32 31 31 33 00 00 00 00 2113....
0010: 57 52 54 57 52 54 49 43 WRTWRTIC
0018: 32 30 37 38 00 00 00 00 2078....
Event Type: Error
Event Source: EventSystem
Event Category: (50)
Event ID: 4609
Date: 28/07/2004
Time: 10:53:38
User: N/A
Description: The COM+ Event System detected a bad return code during its internal processing. HRESULT was 8007043C from line 44 of d:\nt_qxp\com\com1x\src\ev
Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7026
Date: 04/08/2004
Time: 11:32:21
User: N/A
Description:
The following boot-start or system-start driver(s) failed to load:
AmdK7
Fips
IPSec
KmxFw
MRxSmb
NetBIOS
NetBT
RasAcd
Rdbss
Tcpip
Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7001
Date: 04/08/2004
Time: 11:32:21
User: N/A
Description: The IPSEC Services service depends on the IPSEC driver service which failed to start because of the following error:
A device attached to the system is not functioning.
Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7001
Date: 04/08/2004
Time: 11:32:21
User: N/A
Description: The Messenger service depends on the NetBIOS Interface service which failed to start because of the following error:
A device attached to the system is not functioning.
Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7001
Date: 04/08/2004
Time: 11:32:21
User: N/A
Description: The DHCP Client service depends on the SYMTDI service which failed to start because of the following error:
The dependency service or group failed to start.
Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7001
Date: 04/08/2004
Time: 11:32:21
User: N/A
Description: The SYMTDI service depends on the TCP/IP Protocol Driver service which failed to start because of the following error:
A device attached to the system is not functioning.
Event Type: Information
Event Source: Save Dump
Event Category: None
Event ID: 1001
Date: 04/08/2004
Time: 11:30:54
User: N/A
Description:
The computer has rebooted from a bugcheck. The bugcheck was: 0x0000000a (0xc051d0c7, 0x00000002, 0x00000000, 0x8050bfd0). A dump was saved in: C:\WINDOWS\Minidump\Mini08
My first guess by looking at these dumps would be to check the NIC card.
If you need to replace the hal.dll, you can do this with the Recovery Console and your Installation CD... just copy it from the i386 folder on the cd to your %systemfolder%\system32 folder..
FE
FE
you stated that you've had more and more crashes; i would then test everything as much as possible, assemble a basic system and in stall on that one; only then i would add more to it. And before installing, take out the NIC (or disable it) i've had troubles with some too...
test the HDD with the soft you find on the manufacturers site, or post back the type
a link to test the memory :
http://www.memtest.org/ memtest86+
hope it get's you on the road again...
nobus
test the HDD with the soft you find on the manufacturers site, or post back the type
a link to test the memory :
http://www.memtest.org/ memtest86+
hope it get's you on the road again...
nobus
Hi there
well this is easy to fix
Insert and boot from your WindowsXP CD.
At the first R=Repair option, press the R key
Press the number that corresponds to the correct location for the installation of Windows you want to repair.
Typically this will be #1
Type bootcfg /list to show the current entries in the BOOT.INI file
Type bootcfg /rebuild to repair it
Take out the CD ROM and type exit
But if this happens it means your hardrive have some seriuos errors and if it happend once it will happen again ....Take out the hard drive, and hook it to another system as a Slave drive, then within windows access the slave drive from Primary drive and copy all of the data.
after that hook back your drive to your system and format the drive and do a fresh installation after that just copy your data back
goodluck
well this is easy to fix
Insert and boot from your WindowsXP CD.
At the first R=Repair option, press the R key
Press the number that corresponds to the correct location for the installation of Windows you want to repair.
Typically this will be #1
Type bootcfg /list to show the current entries in the BOOT.INI file
Type bootcfg /rebuild to repair it
Take out the CD ROM and type exit
But if this happens it means your hardrive have some seriuos errors and if it happend once it will happen again ....Take out the hard drive, and hook it to another system as a Slave drive, then within windows access the slave drive from Primary drive and copy all of the data.
after that hook back your drive to your system and format the drive and do a fresh installation after that just copy your data back
goodluck
ASKER
I think theres something seriously wrong!! The system now won't finish POSTing. The beep code that it gives is "RAM failure on data bits xxxx of high byte of memory bus." The system is a dual processor tyan mb (s2466). I got the mb to POST ok after removing one of the processors, so I thought that it was probably that processor. Tried re-installing windows after testing all my components to see whether the system would POST, and then the beep code repeated itself. It may be that I've got too much thermal compound on the processors - could this fry them?
No, thermal compound will not conduct electrical current, so it is safe to say the it will not 'fry' them, but it is counterproductive to put too much on these. A small amount will suffice. I use Artic Silver (the best) on all my processors.. Here is a quick tutorial on application:
http://www.arcticsilver.com/arctic_silver_instructions.htm
http://www.arcticsilver.com/arctic_silver_instructions.htm
ASKER
Does anybody know what part of the POST the system is getting to? Is the POST error beep code testing the processor(s)? I've got thermal compund on parts of the processor other than the central die. Is the mobo dead?
You can determine the problem using the beep codes.. Again, here is a link from my webpage for this:
http://65.24.134.81/KipSolutions/bios/Bios.htm
You will need to know the BIOS manufacturer. Look at the bottom of the page for a listing of all the beep codes to determine the problem..
FE
http://65.24.134.81/KipSolutions/bios/Bios.htm
You will need to know the BIOS manufacturer. Look at the bottom of the page for a listing of all the beep codes to determine the problem..
FE
ASKER
Its phoenix 4.06. I've already looked the code up, as I said above. "RAM failure on data bits xxxx of high byte of memory bus." is my problem, but I'm not sure what this means/refers to. Where is the memory bus? - on the mobo? in the processor? I've ruled out extended ram, as the POST never gets anywhere near it.
ASKER
PS the mobo comes with an integrated NIC, which worked fine for a year, so I assume its not that.
ASKER
PPS I tried resetting the cmos just before getting the system to POST after I removed one of the processors.
Looks to me like a memory problem. If you have more than one stick of memory in there, take one out at a time and see if the problem still occurs.
ASKER
I suspect this now souodn't really bein this topic but in the hardware topic. Never mind.. and thanks in advance for all the help.
That is okay.. most all of the experts in the OS areas are also qualified to work on hardware also... :)
Just in case this is not deleted and ends up being paq'd, one thing to note regarding a missing HAL error.. This is usually just an error in the Boot.ini file. It can be corrected using the Recovery Console and running the bootcfg /rebuild command..
FE
FE
yip just As I also posted in my previous post ....
>>>>>>Type bootcfg /list to show the current entries in the BOOT.INI file
Glad that someone agrees with me ....thanks Fatal ;-)
>>>>>>Type bootcfg /list to show the current entries in the BOOT.INI file
Glad that someone agrees with me ....thanks Fatal ;-)
Ha.. LR.. did not see that in the post... :)
Fatal ..... don't worry ... .think the questioner also missed it .... ;-)
but its atleast there for future refrence ...... well I hope so ....
but its atleast there for future refrence ...... well I hope so ....
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
I had the same problem with hal.dll file. I was practically reinstalling XP everyday until I read this article that stated that sometimes the disk is so overloaded it won't display the correct capacity - so you are thinking you are okay but in reality you barely have enough room - so I followed the advice of the article which says to save what you can, reformat and partition, and go from there. It certainly worked for me as I haven't had any problems since doing that , other than the irritation and annoyance at having to redo the disk.
To resolve this problem, repair the Windows XP installation from your CD-ROM
http://www.jsiinc.com/SUBO/tip7100/rh7193.htm
http://www.jsiinc.com/SUBO/tip7100/rh7193.htm
There was a critical Problem in windows XP and 2003:
Symptoms:
1.Disappearing the Network Connections and Dcom objects (dcomcnfg), according to eventviewer logs there was log posted with ID:4609, Source: EventSystems.
2.Unable to configure new network connection like vpns and all, existing VPN connection is not working
3.But network is up, able to connect LAN machines and internet
Action taken: After removing the Service pack 2, working fine for some machines but not for all.
Desperately looking for solution since there was no link which gives the details or solution for specified problem.......Can any one take this challange????
Cheers,
Raja
Symptoms:
1.Disappearing the Network Connections and Dcom objects (dcomcnfg), according to eventviewer logs there was log posted with ID:4609, Source: EventSystems.
2.Unable to configure new network connection like vpns and all, existing VPN connection is not working
3.But network is up, able to connect LAN machines and internet
Action taken: After removing the Service pack 2, working fine for some machines but not for all.
Desperately looking for solution since there was no link which gives the details or solution for specified problem.......Can any one take this challange????
Cheers,
Raja
wb, you need to open a new thread for you problem... That way, the experts can see and respond to your questions..
FE
FE
You'd probably have to boot to the recovery console on your WinXP disk:
http://www.webtree.ca/windowsxp/repair_xp.htm has information on how to boot to the Recovery Disk
After you boot to there, run sfc /scannow and chkdisk and that should solve your problem.
Regards,
Zyloch