Vista Blue Screens ("Maybe" a Resolution)

[jholland1964]

I need some input here...
Been working with a lady for over a month who is experiencing BSOD's on her Vista(factory installed computer. Computer specs are the following;

Model # a1510y
HP Pavilion desk top computer, Direct X version 10.0
vista home basic 32 bit
H/P intel R Pentium R 4
CPU 3.00 GHz 2.99 GHz
Mem. 1.75 GB


Under display: ATI RADEON XPRESS 1100 series
ATI Technologies Inc. Driver version 8.383.0.0

Undr system devices: ATI PCI express 3G10 filter driver

Microsoft Syst. Mgmt. Bios Driver, Version 6.0.0000.16386
Total available graphics memory 895 MB,
Dedicated Video Memory 256 MB
System Video Memory O MB
Shared System Memory 639 MB

21" Flat screen Acer Monitor (Acer driver is NOT loaded. Shows Generic PnP Monitor in Device Manager


AVG 7.5 antivirus, AVG anti spyware, Spybot SD, SpywareBlaster, Win. Defender/firewall.
I.E. 7 dial up.

Now these blue screens have NO message on them, blue screen then shut down. Happens most often when she is waiting for picture on websites to load, but have also happened at random times also. Believe she is always online when they happen however. Had her disable automatic reboot during blue screen to see if a message could be seen, none available.

She has checked Event Viewer...millions of times almost and here are the most prevalent error notations;
Log Name: System
Source: IPRIP
Event ID: 29031
IPRIP was unable to add a route to the system route table. The data is the error code.

Log Name: Application
Source: Microsoft-Windows-EventSystem
Date: 3/8/2008 10:10:38 PM
Event ID: 4621
Description:
The COM+ Event System could not remove the EventSystem.EventSubscription object


Log Name: System
Source: Tcpip
Event ID: 4227
Description:
TCP/IP failed to establish an outgoing connection because the selected local endpoint was recently used to connect to the same remote endpoint. This error typically occurs when outgoing connections are opened and closed at a high rate, causing all available local ports to be used and forcing TCP/IP to reuse a local port for an outgoing connection. To minimize the risk of data corruption, the TCP/IP standard requires a minimum time period to elapse between successive connections from a given local endpoint to a given remote endpoint.

Multiple listings like this after Blue Screens also;
Log Name: ACEEventLog
Source: ACEEventLogSource
Event ID: 0
Task Category: None
Level: Information
Calling _iDEM_PP.GetPowerplayFeatureSettings method failed and the result is: 0
Error Called by: ATI.ACE.CLI.Aspect.PowerPlayDPPE.Graphics.Runtime. RT_PowerPlayDPPE::Check processID:03068 threadIDCLIRuntime ; domainNameCLI.EXE ; assemblyNameCLI.Aspect.PowerPlayDPPE.Graphics.Ru ntime, Version=2.0.2488.36842, Culture=neutral, PublicKeyToken=90ba9c70f846762e

Log Name: ACEEventLog
Source: ACEEventLogSource
Event ID: 0
Task Category: None
Level: Information

Thus far she has done the following..Generally followed PP's "Read Me before..etc." thread, including HJT log. Nothing found.

Checked and made sure video drivers were up to date, deleted and reinstalled her dial-up connection. Windows updates are also current.

I am at a loss really. These began shortly AFTER the computer warranty was up...of course. She added more RAM thinking maybe memory was the problem but it made no difference whatsoever.

So?

[cauzomb]

Try to disable and uninstall the network adapter via bios and windows to see if that changes anything.

[jholland1964]

Boy, don't know if I can get her to attempt this...took instructions multiple times to get the Event Viewer info from her.
How about just via Device Manager?

[Gizmokid2005]

I'm with cauz. It sounds like a network card/adapter error. You should be able to disable it via device manager and see if that helps. It might even be a bad modem (yes I know its new, but it's still possible).

[jholland1964]

Had her get start up list via HJT and have attached. Is that Enumerating Winsock LSP files normal or correct?
There are NONE showing in HJT log.

The ones I really wonder about are the two pnrpnsp.dll entries. All I can find about this is that it is part of the Advanced Networking Pack is only for computers that are running Windows XP with SP1
Why would these be on a Vista computer? I find no mention of this whatsoever in anything having to do with Vista, unless I am not looking in the right place.

Also an item in the HJT log which I failed to notice before is O13 - Gopher Prefix:
From all I could find there are fewer than 100 Gopher servers now and Gopher support was actually discontinued for Internet Explorer back in June of 2002. Though you can use Gopher with IE7 by doing a registry edit. This lady would NOT have done this...took days, as I said before, to have her figure out how to use and copy entries in the Event Viewer. In IE7 Gopher support was removed on the WinINET level. Now you know me, had no clue what this was but when I found the info

WinInet limits the number of simultaneous connections that it makes to a single HTTP server. If you exceed this limit, the requests block until one of the current connections has completed.

a "light went off" BECAUSE several of her entries in her event viewer logs are this, as noted above;

TCP/IP failed to establish an outgoing connection because the selected local endpoint was recently used to connect to the same remote endpoint.

Am I wrong to think this stuff may be part of her problem? Or have I just gone "daffier" ?

[jholland1964]

In trying to find a solution for this lady's problems one thing I learned about it is this...this problem right now seems pretty much limited to people using Vista.

Now some people may all ready know all this or understand it but this explanation is for those who don't...(like me until I began working on this and YES, I still might not quite get it but here goes)

First here is what it involved...Internet Protocol...to put it as simply as possible...our internet "addresses" represented by numbers...we all have one, we don't see it, but we do. Currently the Internet Protocol most in use is version 4.... hence IPv4. I am not going into the actual numbers involved...in the billions...but with wide use of these IPv4 addresses today there is fear that we will run out of them. So this pushed towards development of IPv6 which really is in the early stages of development. But will give many, many more IP addresses.

The problem this lady and others have involves IPv6 and the transition technologies needed for it at this time in order to transition between it and IPv4. IPv6 support is provided for in XP with SP1 and SP2, Windows Vista, Windows Server 2008, Windows Server 2003 but I think the problem comes with the fact that in Windows Vista and Windows Server 2008 come with an integrated IPv4 and IPv6 implementation known as the Next Generation TCP/IP stack and the very items which showed all of the errors on her machine...Tunneling, ISATAP, 6to4, Teredo seem to come automatically enabled on Vista (as I said I could be wrong but could find nothing to state otherwise) but they do not allow for the fact that, especially people on dial-up, for NOW, do not need these enabled. Her dial-up uses IPv4, as do most of them still today, and her machine was attempting to use these integration items that it had no use for at this time, but WERE enabled and so it would freeze, shut down, disconnect because they didn't work since there really was no integration needed but the computer was attempting this integration. The solution I found in multiple places, finally, was to disable all noted in blue of the above . This is what we did on her machine along with her ethernet card, which was also enabled. Thus far she has been surfing along fine, without freezes, blue screens, or disconnects. We DID NOT remove any of them, just turned them off and then disabled them. If she needs them later she can just go back in and re-enable them.

This is a complaint I have with Vista, it is fancy and sleek...but with major flaws and now the SP1 update which is "supposed" to address, among other things, this very issue (so obviously it IS a problem for many), has been pushed back and won't be released to the general public until later. You can get ahold of Beta (test) versions but that is never something I recommend.

[cauzomb]

Cool. I was getting to the networking issues, but you caught it and found the issue... In network device manager, should only need TCP/IP to get online, client for ms networks etc all un-necesarry for browsing the net. Did you find these in "services" or device manager, or network configuration etc..? maybe write a brief procedural path to the culprits...

[jholland1964]

Am working on step by step of what we did to find and correct all. Will post it later...took nearly two solid weeks to find what HOPEFULLY IS the answer.

[jholland1964]

Now sorry but this will repeat some of my post above but have no idea of any other way to post all this;

Lady had been having "blue screens" for several months...of course right AFTER warranty ran out. Running Vista, AVG 7.5 antivirus, AVG anti spyware, Spybot SD, SpywareBlaster, Win. Defender/firewall.
I.E. 7 dial up. She added 1GB of RAM thinking maybe not enough RAM was the cause. Blue screens generally happened when waiting for a photo to come up on photo page. Occasionally while original Norton anti-virus was updating. She remove Norton knowing it is a resource hog and installed AVG Free.
Had her run as many steps of PP's sticky as she could...online scans would cause the "blue screen" however so we stopped that. Ran all of her anti-spy programs, her AVG program, and then an HJT scan...all done off-line without difficulty which should have given me a clue...I am dense and didn't figure that out THEN. Really nothing showed anything, except out of date Java. Uninstalled old version, installed new version and computer seemed ok for couple days and then again blue screen. Had her do checkdisk/fix, nothing changed and only a couple fixes needed. Blue screens continued...WHEN ONLINE only...still didn't catch on! In fact she didn't mention it either. No message on the screen however, it would show screen and then reboot. Had her disable auto reboot during blue screen but it still did not display any message. Also had her update video card. Still had the same difficulties. Finally had her use Event Viewer and give me errors showing before or during time of blue screens. They all were pretty much what is shown below.

Source: IPRIP
IPRIP was unable to add a route to the system route table.

Source: Tcpip
TCP/IP failed to establish an outgoing connection because the selected local endpoint was recently used to connect to the same remote endpoint.
She ran the Dell Diagnostic Tool
Dell Diagnostic Tool Info
Microsoft ISATAP Adapter, is reporting "tv_ConfigMgrErr31
Microsoft 6to4 Adapter, is reporting "tv_ConfigMgrErr31
Teredo Tunneling Pseudo Interface error, though can't find now what the wording of the error was...I have "tons" of saved files on this problem!

Then had her go to Device Manager and these items all showed errors;

Network adapters: shown are SIX , 6TO4 Adapter listings.
isatap, (FB4F3505-C1CB-4F2E-8604-90D580B8BAE3} , shown 5 times..
The isatap when right clicked says, 'this device is not working properly because Windows cannot load the drivers required for this service.
It is enabled.

6TO4 right click says same as above, enabled...not working properly etc.
Teredo Tunneling Pseudo Interface enabled...not working properly.

She then ran the Vista Reliability and Performance Diagnostic check
The basic system checks showed "passed"........with the exception of Hardware Device and Driver Checks, which 'failed'
Microsoft ISATAP Adapter, is reporting "tv_ConfigMgrErr31
Microsoft 6to4 Adapter, is reporting "tv_ConfigMgrErr31
Teredo Tunneling Pseudo Interface failed

First site I found said that the excessive number of 6TO4 Adapters and ISATAP Adapters were due to the fact that the devices were not working properly so with each reboot the system would try to install a new one. All those showing errors (there would always be at least one NOT showing an error) should be removed, which she did. BUT with each reboot a new one would be added...because of course they were not working properly. Finally on the site which gave me the solution the first step was to Uninstall those with errors but NOT reboot but THEN disable those without errors and THEN reboot. These were the ones I had her disable;
Microsoft ISATAP Adapter
Microsoft 6to4 Adapter,
Teredo Tunneling Pseudo Interface
NONE of these are needed with dial-up. Those using dial-up and Vista seemed to be the ones having the problems.
After disabling all, she rebooted and no more blue screens.I finally found the solution by searching for those exact errors. Even that took awhile, blue screen problem for Vista was listed on countless websites but no solutions. Then I began searching using terms, Vista, Blue Screens, dial-up and adding one of those items above. Soon found answer on about three sites, all led to one link but now for the life of me I cannot find it, but on all of the three other sites the poster reported success using fix given.

I would suggest somebody on dial-up experiencing the same problems first of course be sure the computer is clean of viruses, malware, etc.
But THEN check the Device Manager for those three devices showing a problem. Uninstall the extras which will show the Yellow Exclamation point indicating a problem. THEN disable those devices and she also disabled NIC card since she is using dial-up.
So far so good. We are keeping our fingers crossed that this will be the final solution.

[jholland1964]

We cheered too soon....she got another blue screen on Tuesday night while viewing small images on google 'images' which happened at 9:18 PM...note the times on these errors...
Here are the errors;

Log Name: System
Source: EventLog
Date: 3/18/2008 9:20:21 PM
Event ID: 6008
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: Sharons-PC
Description:
The previous system shutdown at 9:18:54 PM on 3/18/2008 was unexpected

.

Next one;

Log Name: Security
Source: Microsoft-Windows-Security-Auditing
Date: 3/18/2008 9:21:14 PM
Event ID: 5032
Task Category: Other System Events
Level: Information
Keywords: Audit Failure
User: N/A
Computer: Sharons-PC
Description:
Windows Firewall was unable to notify the user that it blocked an application from accepting incoming connections on the network.
Error Code: 2

And this one;

Log Name: System
Source: IPRIP
Date: 3/18/2008 9:26:33 PM
Event ID: 29031
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: Sharons-PC
Description:
IPRIP was unable to add a route to the system route table. The data is the error code

There were NO errors noted up to 4 hours prior to this happening. The one noted then was also that IPRIP error.
She had no warning, just the blue screen and shut down.
Ok folks I am totally at a loss here! Noted everything we did in my above post...have no clue what else to do...