Yeah so, Thoth, I blame you.

You posted about your different anti-virus programs finding shit, and I remember AVG and Avast! found the most, so, what did I do? I went and downloaded them, to see if my system was as clean as I thought it was.

I ran Avast!, it found nothing.

I ran AVG, and it found 4 things, 3 of which were worms embedded in some keygens I had that I had never used. My system wasn't infected mind you, it just had the potential for it. AVG removed them both, and the 4th thing was some potential malware or somecrap that wasn't really dangerous.

So, great. My system is clean. I became more confident in my ability to handle computers and software.





Then I saw this.



What the fuck.

So I rebooted, thought of it as a fluke.

An hour or so later, this happens:



Holy hell, what's going on? I google it and start looking around. MSN has a bunch of articles relating to problems with http.sys.

The system crashes again, while I'm trying to use it to diagnose itself.







I reboot in safe mode and surf there.

Turns out, with the vanilla version of Windows XP SP2, (no hotfixes) there is a conflict with some firewall and anti-virus software that tries to write to un-writeable memory in relation to http.sys.


The ANTI-VIRUS software, was causing symptoms of a VIRUS. WOWOWOWOWOW. The irony is palpable.

I uninstalled it, but it didn't help. I had to get on my roommates computer (valid windows ID ftw) and download 2 hotfixes, which seem to have fixed it now.


In closing, I hate you Thoth.

Every time you post something "computer", I get the big idea to try it out and get more exp.

So, stop it.

--Locane

Sounds like ye need to update yer windows.

All advice given by me is 'take at your own risk', technical or otherwise - unless money exchanges hands... Even then it depends on how much, and to whom.

Speaking of which - AVG do that to ye? Or Avast? (Hope not AVG -- I got clients I should expect calls from soon. >_>)
_________________
[i]“A world of unseen dictatorship is conceivable, still using the forms of democratic government.â€

...

Next time install the anti virus before the viruses infect your system files.

...

Actually, it blue screened over night.

I was running Prime95 to test out the ram and it came up with something else that I didn't get a picture of, but wasn't http.sys.

I guess it's possible I have some kind of virus, but it's really weird that I'd see this symptom after the install of AVG / Avast!.



I've scaled back a lot of the performance configs in my bios and running it now to see if that doesn't stop it. So much of troubleshooting is trial and error. I wish I could run some kind of software-based diagnostic on my physical components and just be done with it.

It could be that I have 4 gigs of ram in here maybe? Windows will only recognize 3.5, perhaps applications are attempting to "write" into a memory range windows doesn't know about.

--Locane

Rather than running Prime95 to test the ram, I suggest downloading and running Memtest86 or Memtest86+ which will do a much better job.

I usually suggest downloading UBCD (DOS) - www.ultimatebootcd.com/ or UBCD4Win - www.ubcd4win.com/ which both have memory testing programs included. UBCD is a bit easier since you just download and burn the image file but UBCD4Win does include some really nice apps for testing and/or troubleshooting plus it has several Anti-Virus and Anti-Spyware/Malware apps included. The only difference is you need a copy of an XP source and you have to build it...

If it's always http.sys, or almost always, there's a driver conflict or update needed. Funked memory does cause stop errors, but generally not DRIVER_IRQL_NOT_LESS_OR_EQUAL errors, much less ones generated repeatedly by a specific file.

If you have the memory.dmp, ye might be able to use the debugger to find out which specific driver is causing the issue. Most likely it's just a matter of getting windows update to work proper.
_________________
"There is a special providence in the fall of a sparrow." -Hamlet, 5:2:157
Thothie

Negative. Windows makes ram available to apps, thus in order to be written to windows must see it.

AHA!

http://www.nforcershq.com/forum/image-vp483301.html

I found a forum thread saying that Nvidia's Network Access Manager has been wreaking havoc with people's machines, causing BSOD.

Having an Asus Crosshair mobo, I had everything installed.

Uninstalling shit right now, and downloading new versions of the drivers.

Yay! Now I can put the other 2 gigs of ram back in my system!

--Locane