[Jaekus]

So I tried to fix a small glitch and it's turned into 3 days with more problems mounting.

I guess I should really have known better but the advice I read around the net seemed to be good...

Anyway, here's a brief list of things :

Computer specs:

ASUS M2N-MX SE
AMD Athlon 64 x2 5200+
2gb RAM
Windows XP
NVIDIA GeForce 8500 GT (1gb)


Graphics card had artifacts in Battlefield 2, so I downloaded and installed updated drivers (after removing the old ones) in safe mode.

In device manager a little yellow mark next to "network adapters/nvidia nforce networking controller". Scrolling pages was very slow too.

Found some other drivers and installed those, this seemed to fix the problem.

Artifacts weren't gone, so I lowered my graphics settings in-game. Everything seemed fine, however...

When browsing the net would not load pages or my email, but it would be fine on my girlfriend's laptop (connected to the same wireless router).

Deleted cache and cookies, it was fine for MOST pages (banners still have the error - I have another thread about this).

I then used Driver Checker to update my drivers, it installed a Realtek HD driver, and from there my problems started again!

I reinstalled the nvidia drivers and network adapter driver but the yellow exclaimation mark is still there next to "nvidia nforce networking controller #2" and windows is very slow to boot (it used to boot from power on in about 30 seconds, now it takes more than 2 minutes) and has these little messages come up on the blue logoff screen like "playing logoff sound..."


I really don't know where to go from here. I fear if I keep mucking around with stuff I'll just make these problems worse and/or create new ones. Any help much appreciated!

[Advertisements]

try reinstalling your chipset driver...that will take care of the nvidia nforce networking controller issue

[happyrock]

try reinstalling your chipset driver...that will take care of the nvidia nforce networking controller issue

[Jaekus]

Thanks, I had a couple hassles with the net, so I ended up booting into safe mode, uninstalling any nvidia drivers I could then reinstalled them. After that I reinstalled the drivers for my wireless adapter.

XP is still booting up really slowly and it takes ages for the explorer windows to work. Once it's going it's like normal, but it never did this before. I'm at a bit of a loss here...

[Jaekus]

A few other things.

On startup it shows this message saying "executing c:/windows/system32/wlnotify.dll"

On shutdown, when windows logs out it has a message "playing logoff sound..."

Others seem to have slow issues with these messages, but I'm yet to find a fix from my searching, though I will keep doing so until someone replies.

The iTunes mini-player also appears in the taskbar very briefly then disappears on windows start.

My account is set to automatically login as I'm the only one who really uses this computer. The only other account is the admin account.

[happyrock]

wlnotify.dll is a process belonging to the Microsoft Windows Operating System program . wlnotify.dll is a library that contains application programming interface (API) functions to receive and handle notifications events generated by Winlogon like Logon, Logoff, and Shutdown....
do you have to close the window to make the message go away or does it just close itself...

click on start...run...type in msconfig...press enter...click on startup tab...
uncheck everything EXCEPT your AV and firewall...if its a laptop you have to be careful about what you uncheck or your touch pad and wireless and things like that will not function for you..

[Jaekus]

Thanks, but I had already done this a long time ago, it's probably why it was quick to boot in the first place. All I have checked now is avg tray, wireless adapter software and that's about it. Unfortunately it didn't make any difference to the lengthy boot up time.

[happyrock]

how long are you talking about...don't guess...use a watch

[Jaekus]

From boot up to welcome screen it took 46 seconds, then from welcome screen to desktop (no icons or taskbar) it took 45 seconds, then for the icons and taskbar to appear it took 1 minute 1 second (1:01). Before it used to take about 15 seconds from welcome screen to desktop with icons there immediately.

[Jaekus]

It appears I have solved my problem whilst trying to fix another problem.

I downloaded and ran RegCure, it found and repaired 897 registry errors. Now it's pretty much back to normal.

However, I still can't get rid of the "Error 324 (net::ERR_EMPTY_RESPONSE): Unknown error." I get in Google Chrome, and my yahoo mail is still slow to load (thread [url="http://It%20appears%20I%20have%20solved%20my%20problem%20whilst%20trying%20to%20fix%20another%20problem.%20I%20downloaded%20and%20ran%20RegCure,%20it%20found%20and%20repaired%20897%20registry%20errors.%20Now%20it's%20pretty%20much%20back%20to%20normal.%20However,%20I%20still%20can't%20get%20rid%20of%20the%20"Error%20324%20(net::ERR_EMPTY_RESPONSE):%20Unknown%20error."%20I%20get%20in%20Google%20Chrome,%20and%20my%20yahoo%20mail%20is%20still%20slow%20to%20load%20(thread%20here:"]here[/url]) but for now this topic appears to be resolved. Thanks for your help

[happyrock]

try this...launch chrome...open options...under the hood... and restore the defaults by pressing Reset to defaults
no joy...
uninstall chrome and reinstall it...

[Jaekus]

Thanks for the reply.

I've tried both reset to defaults and uninstalling -> reinstalling chrome. Unfortunately this didn't fix my problem.I did keep my history and bookmarks though - would this have made any difference?

[happyrock]

no... keeping your bookmarks will not be the problem...
you can try clearing out chromes cache and cookies...
no joy
lets try TCP/IP stack repair

For these commands click on Start.... Run..... type in...CMD ....click OK


To Reset WINSOCK entries to installation defaults...type in ... netsh winsock reset catalog .... press ...enter

To Reset TCP/IP stack to installation defaults...type in...... netsh int ip reset reset.log ... press ...enter

[Jaekus]

Hmm.. I cleared the cache and cookies again and I thought that may have worked, but it started doing it again.

I also reset WINSOCK and TCP/IP and rebooted, but it didn't seem to do anything different.

[happyrock]

Please download VEW the Event Viewer Tool by Vino Rosso from

here and save it to your Desktop...
Double-click VEW.exe
Under 'Select log to query...put ticks in both application and system
Under 'Select type to list... select both error and critical
Click the radio button for 'Number of events...Type 10 in the 1 to 20 box...


Then click the Run button.

Notepad will open with the output log.

Please post the Output log in your next reply

we may have to run sfc /scannow...

Edited by happyrock, 02 February 2010 - 07:48 AM.

[Jaekus]

Here's the log as per your instructions:
==========================================

Vino's Event Viewer v01c run on Windows XP in English
Report run at 03/02/2010 8:39:03 AM

Note: All dates below are in the format dd/mm/yyyy

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'Application' Log - error Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'Application' Date/Time: 03/02/2010 8:35:49 AM
Type: error Category: 0
Event: 5000 Source: HotFixInstaller
EventType visualstudio8setup, P1 microsoft .net framework 3.5-kb963707, P2 1033, P3 1635, P4 msi, P5 f, P6 9.0.31211.0, P7 install, P8 x86, P9 xp, P10 0.

Log: 'Application' Date/Time: 02/02/2010 1:29:49 PM
Type: error Category: 100
Event: 1000 Source: Application Error
Faulting application ANIWZCSdS.exe, version 1.0.3.7034, faulting module mfc42.dll, version 6.2.4131.0, fault address 0x000019e9.

Log: 'Application' Date/Time: 02/02/2010 1:29:33 PM
Type: error Category: 0
Event: 1 Source: JavaQuickStarterService
The event description cannot be found.

Log: 'Application' Date/Time: 02/02/2010 1:18:23 PM
Type: error Category: 0
Event: 1 Source: JavaQuickStarterService
The event description cannot be found.

Log: 'Application' Date/Time: 02/02/2010 12:15:40 PM
Type: error Category: 0
Event: 1 Source: JavaQuickStarterService
The event description cannot be found.

Log: 'Application' Date/Time: 01/02/2010 10:50:30 AM
Type: error Category: 100
Event: 1000 Source: Application Error
Faulting application ANIWZCSdS.exe, version 1.0.3.7034, faulting module user32.dll, version 5.1.2600.5512, fault address 0x00014acd.

Log: 'Application' Date/Time: 01/02/2010 10:48:16 AM
Type: error Category: 0
Event: 1103 Source: .NET Runtime Optimization Service
.NET Runtime Optimization Service (clr_optimization_v2.0.50727_32) - Tried to start a service that wasn't the latest version of CLR Optimization service. Will shutdown


Log: 'Application' Date/Time: 31/01/2010 12:21:11 PM
Type: error Category: 101
Event: 1002 Source: Application Hang
Hanging application _iu14D2N.tmp, version 51.46.0.0, hang module hungapp, version 0.0.0.0, hang address 0x00000000.

Log: 'Application' Date/Time: 31/01/2010 12:09:24 PM
Type: error Category: 0
Event: 0 Source: Lavasoft Ad-Aware Service
The event description cannot be found.

Log: 'Application' Date/Time: 31/01/2010 11:48:38 AM
Type: error Category: 0
Event: 1103 Source: .NET Runtime Optimization Service
.NET Runtime Optimization Service (clr_optimization_v2.0.50727_32) - Tried to start a service that wasn't the latest version of CLR Optimization service. Will shutdown


~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'System' Log - error Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'System' Date/Time: 03/02/2010 8:36:47 AM
Type: error Category: 8
Event: 20 Source: Windows Update Agent
Installation Failure: Windows failed to install the following update with error 0x80070643: Update to .NET Framework 3.5 Service Pack 1 for the .NET Framework Assistant 1.0 x86 (KB963707).

Log: 'System' Date/Time: 03/02/2010 8:34:32 AM
Type: error Category: 0
Event: 2000 Source: Srv
The server's call to a system service failed unexpectedly.

Log: 'System' Date/Time: 03/02/2010 8:34:32 AM
Type: error Category: 0
Event: 2000 Source: Srv
The server's call to a system service failed unexpectedly.

Log: 'System' Date/Time: 03/02/2010 8:34:32 AM
Type: error Category: 0
Event: 2000 Source: Srv
The server's call to a system service failed unexpectedly.

Log: 'System' Date/Time: 03/02/2010 8:34:32 AM
Type: error Category: 0
Event: 4191 Source: Tcpip
IP could not open the registry key for adapter TCPIP\Parameters\Adapters\NDISWANIP. Interfaces on this adapter will not be initialized.

Log: 'System' Date/Time: 02/02/2010 2:36:02 PM
Type: error Category: 0
Event: 2000 Source: Srv
The server's call to a system service failed unexpectedly.

Log: 'System' Date/Time: 02/02/2010 2:36:02 PM
Type: error Category: 0
Event: 2000 Source: Srv
The server's call to a system service failed unexpectedly.

Log: 'System' Date/Time: 02/02/2010 2:36:02 PM
Type: error Category: 0
Event: 2000 Source: Srv
The server's call to a system service failed unexpectedly.

Log: 'System' Date/Time: 02/02/2010 2:36:02 PM
Type: error Category: 0
Event: 4191 Source: Tcpip
IP could not open the registry key for adapter TCPIP\Parameters\Adapters\NDISWANIP. Interfaces on this adapter will not be initialized.

Log: 'System' Date/Time: 02/02/2010 2:06:42 PM
Type: error Category: 0
Event: 2000 Source: Srv
The server's call to a system service failed unexpectedly.