• Welcome to Overclockers Forums! Join us to reply in threads, receive reduced ads, and to customize your site experience!

Computer freezes when using Internet Connection

Overclockers is supported by our readers. When you click a link to make a purchase, we may earn a commission. Learn More.

Xfinity

New Member
Joined
Jul 8, 2005
Location
Sweden
I have just built a new system:

Asus A8N-E w/ NB47J
Athlon 64 3800+ Venice
Kingston 2x1024MB DDR PC3200 (Dual Channel) @ 3-3-3-8
Sapphire ATI Radeon X850XT
Seasonic S12 550w

Using Windows XP with SP2 and all the latest drivers (Chipset/Sound/Network/Graphic/etc.). I have tested the system with the following testing tools without any errors:

Memtest86+ (24h+)
Prime 95 (Small and blend, 8h+ each)
Super Pi
Without any activity

But if I surf the net, use outlook or download bittorrents my system freeze and lock up the system so I need to do a hard reset. This problem occurs when I haven’t used the system for a while. Very strange and very frustrating when there is no blue screen to see what causes this problem.

Any advice or help is most welcomed! Thanks!
 
Open Event Viewer (in order to access the error logs, and check for any critical errors)...Start | Run | Type eventvwr.msc and click OK | Highlight "Application" and "System" independently in the LH pane | Right click any error message(s) (critical errors are in Red), and select "Properties" | Write down a couple of the latest critical error messages exactly as they appear under the "Description" field, and post them in this thread.

Also, open the System Information tool by typing msinfo32 in the Run box | Expand "Components" | Highlight "Problem Devices", and look for any problems that might be listed there.
 
System Information
No problem devices.


Event Viewer

Application
1. WmiAdapter
Open of service failed.

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


System
1. Dhcp
The IP address lease 0.0.0.0 for the Network Card with network address 00A0CC546EFC has been denied by the DHCP server 192.168.0.1 (The DHCP Server sent a DHCPNACK message).

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

2. DCOM
DCOM got error "The service database is locked. " attempting to start the service netman with arguments "" in order to run the server:
{BA126AE5-2166-11D1-B1D0-00805FC1270E}

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

3. Service Control Manager
The Outpost Firewall Service service terminated unexpectedly. It has done this 1 time(s).

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


Log files
Application log here; System log here; Nothing in the Security log
 
Code:
WmiAdapter
Open of service failed.

For more information, see Help and Support Center at [URL]http://go.microsoft.com/fwlink/events.asp.[/URL]
I'd probably suggest giving this a try first (this will re-install WMI into the Registry) ...Start | Run | Type cmd, and click OK | Type each of the following commands, hitting ENTER after each ...

winmgmt /clearadap
winmgmt /kill
winmgmt /unregserver
winmgmt /regserver
winmgmt /resyncperf


While at the command prompt, type net stop winmgmt, then delete the %windir%\system32\wbem\repository directory. Once you've done that, type in net start winmgmt

If that doesn't help, try this ...re-open the command prompt, and type winmgmt /clearadap to clear prior WMI /resyncperf information from the Registry. Then type winmgmt /resyncperf to register the system performance libraries with WMI again.

Edit: I should also note that the default Services setting for Windows Management Instrumentation (WMI) is "Automatic".
 
Last edited:
I managed to reinstall WinXP again, hopefully I can use this version for more than 3 days :p.

The critical error caused by the WmiAdapter is gone and hopefully the problem I had before is gone forever.

Thanks!
 
As far as I remember, that problem was due of a botched driver of the MARVEL GIGABIT, wich caused random lockdowns, going back to a older version fixed this issue for me.

I also wondered if I had something wrong with my overclock, I moved everything until I found that more people were having the same behavior
 
Back