svchost keeps hanging the system.
This is a discussion about svchost keeps hanging the system. in the Windows Software category; This is becoming a pain in the ass: Application popup: svchost. exe - Application Error : The instruction at 0x77d4fb7d referenced memory at 0x00000001. The memory could not be written. IE5 does it too.
This is becoming a pain in the ass:
Application popup: svchost.exe - Application Error : The instruction at "0x77d4fb7d" referenced memory at "0x00000001". The memory could not be "written".
IE5 does it too. Any Ideas.
------------------
System Spec:
FIC VA-503+ 1.1b bios JE438
CPU Current Limiter Disabled
AMD K6-2 550 (300 when I talk to FIC tech support)
128Mb SSi PC100
STB Velocity 4400 16Mb PAL TV-Out
Hauppauge Wintv
Realtek 8029 LAN
Creative ES1371 (PCI64v)
56.6K (AkA 44k) ISA Modem
Creative 48mx CDROM
Memorex TriMaxx200(DVD/CDR/CDRW, 6,4,24)
Maxtor 91301U3 13Gb
LS120
and com and lpt i/o conflict error during bios startup.
Hardware fault caused by win2k beta3 and dodgy bios, now irrepairable.
Application popup: svchost.exe - Application Error : The instruction at "0x77d4fb7d" referenced memory at "0x00000001". The memory could not be "written".
IE5 does it too. Any Ideas.
------------------
System Spec:
FIC VA-503+ 1.1b bios JE438
CPU Current Limiter Disabled
AMD K6-2 550 (300 when I talk to FIC tech support)
128Mb SSi PC100
STB Velocity 4400 16Mb PAL TV-Out
Hauppauge Wintv
Realtek 8029 LAN
Creative ES1371 (PCI64v)
56.6K (AkA 44k) ISA Modem
Creative 48mx CDROM
Memorex TriMaxx200(DVD/CDR/CDRW, 6,4,24)
Maxtor 91301U3 13Gb
LS120
and com and lpt i/o conflict error during bios startup.
Hardware fault caused by win2k beta3 and dodgy bios, now irrepairable.
Participate in our website and join the conversation
This subject has been archived. New comments and votes cannot be submitted.
Jun 7
Jun 8
0
2 minutes
Responses to this topic
OP
This is the best one yet:
Event Type: Information
Event Source: Application Popup
Event Category: None
Event ID: 26
Date: 6/7/2000
Time: 4:36:58 AM
User: N/A
Computer: WIN2000
Description:
Application popup: iexplore.exe - Application Error : The instruction at "0x00000000" referenced memory at "0x00000000". The memory could not be "read".
Click on OK to terminate the program
Click on CANCEL to debug the program
I assume the address' are all zeros as all I had done was press CTRL-N to open a new window. I have also downloaded all critical updates, but to no avail.
Event Type: Information
Event Source: Application Popup
Event Category: None
Event ID: 26
Date: 6/7/2000
Time: 4:36:58 AM
User: N/A
Computer: WIN2000
Description:
Application popup: iexplore.exe - Application Error : The instruction at "0x00000000" referenced memory at "0x00000000". The memory could not be "read".
Click on OK to terminate the program
Click on CANCEL to debug the program
I assume the address' are all zeros as all I had done was press CTRL-N to open a new window. I have also downloaded all critical updates, but to no avail.
Yeah that was the way my old motherboard slowly died, memory could be written or read,
by the way I changed the case too, it was burning too much stuff lately, but the memory was ok, and so the error with the time
at booting up, got to reset it everytime i started the power switch on, now it's zero problem, new mother new supply/case combo.
by the way I changed the case too, it was burning too much stuff lately, but the memory was ok, and so the error with the time
at booting up, got to reset it everytime i started the power switch on, now it's zero problem, new mother new supply/case combo.
