possible hardware damage from virus/adware?

[pwnt by pat]

I'm sure this is the wrong place but it's more than just adware/virus stuff...

Well. Everything was fine - perfect. Then I clicked a wrong link on Entensity.net and it took me to a porn site. From there, popups kept coming up and I was completely infected with adware/spyware and a possible virus or two. I had to reboot to safe mode to clean everything off. Then I got a boot error, net something.inf or something like that. I had to reformat. I did a repair install of 2k and worked once, rebooted, same error. Tried again, Driver_Irql_not_less_or_equal error. Then through 7 or 8 installs, I kept getting the netsomting.inf error or Driver_Irql_not_less_or_equal. I thought rebuilding my raid array would solve the problem. nope. clear cmos, same problem.

Finally, I get a 'stable' system at stock. In bios, optomized with ram 1/1 (was by speed @ 200mhz for 133 cpu) 2.5v. Blue screenDriver_Irql_not_less_or_equal. 3.3, so far nothing.

So before, I was running
mobile 2600
2x512 mushkin level 2 2-2-2-5 @ 2.5 pc3500 dc
Infinity 6-19
wd360 raid 0

perfectly stable

Now I have the same thing but the ram is 2-2-2-11 (thought changing might help - blue screen at 2.5, so far once at 3.3)

Is it possible that some script might have ran and damaged my hardware, mobo or ram? Microsoft say's Driver_Irql_not_less_or_equal is from a ram error buy I'm running well below stock (was stock before everything happened 1/1)

[RJARRRPCGP]

I'm sure this is the wrong place but it's more than just adware/virus stuff...

Well. Everything was fine - perfect. Then I clicked a wrong link on Entensity.net and it took me to a porn site. From there, popups kept coming up and I was completely infected with adware/spyware and a possible virus or two. I had to reboot to safe mode to clean everything off. Then I got a boot error, net something.inf or something like that. I had to reformat. I did a repair install of 2k and worked once, rebooted, same error. Tried again, Driver_Irql_not_less_or_equal error. Then through 7 or 8 installs, I kept getting the netsomting.inf error or Driver_Irql_not_less_or_equal. I thought rebuilding my raid array would solve the problem. nope. clear cmos, same problem.

Finally, I get a 'stable' system at stock. In bios, optomized with ram 1/1 (was by speed @ 200mhz for 133 cpu) 2.5v. Blue screenDriver_Irql_not_less_or_equal. 3.3, so far nothing.

So before, I was running
mobile 2600
2x512 mushkin level 2 2-2-2-5 @ 2.5 pc3500 dc
Infinity 6-19
wd360 raid 0

perfectly stable

Now I have the same thing but the ram is 2-2-2-11 (thought changing might help - blue screen at 2.5, so far once at 3.3)

Is it possible that some script might have ran and damaged my hardware, mobo or ram? Microsoft say's Driver_Irql_not_less_or_equal is from a ram error buy I'm running well below stock (was stock before everything happened 1/1)

The driver IRQL error is probably not RAM related. It's probably caused by driver corruption.

If there was a RAM error, you probably would have a BSOD that looks like this instead:

***STOP: 0x00000050 PAGE_FAULT_IN_NON_PAGED_AREA

--or--

***STOP: 0x0000004E PFN_LIST_CORRUPT

I have gotten the second BSOD before from a FSB overclock. Probably caused by overheating RAM. When launching a defrag job one day, when scanning the HDD, boom, a black screen briefly then rebooted.


That was when overclocking my 256 MB Kingston PC2100 DDR SDRAM with Hynix chips when at 138 mhz, but later on, I was then able get 138 mhz FSB stabily, thus seemed to be an overheating problem, because it went away.

[pwnt by pat]

Well with 3.3 on the ram, it hasn't crashed under an hour and a half of CSS. I'll run memtest on the each ram stick just to be sure. It wasn't heat here as it was happening at random at idle or while installing the os/drivers/copying files/formatting the hdd.

http://www.microsoft.com/resources/documentation/Windows/XP/all/reskit/en-us/Default.asp?url=/resources/documentation/windows/xp/all/reskit/en-us/prmd_stp_ottj.asp

Could it just be a bad driver install from a fingerprint on my cd? Corruption of the 'stable' drivers from the adware cleaning?

[pwnt by pat]

css crashed
windows crashed
blue screen no text - reboot
set ram voltage to 2.7
driver_irql on loading os
reset cmos
kmode_exception_not_handled instant reboot
kmode_exception_not_handled manual reboot
reset cmos
set divier to 1/1 from auto
boot to windows at 800mhz


css crashed after 2 minutes
windows froze
pfn_list_conflict (I think, rebooted too fast) error
reboot, set multi on mobilexp to 13.5, voltage to 1.625
kernel error - loading required dll's on os load
reboot
enters windows

crash
reboot no message
comp doesn't return on after 'reboot'
shut down with front switch
boot to windows

[pwnt by pat]

up

windows crash
pfn_list_corrupt
reboot
error loading dll
reboot to windows
crash after two minutes online
registry_error
reboot
netoskrnl.exe on windows load
reboot
computer refuses to post - bios corrupt
still can't get it posting - swapped cpu, vid card - can't ram or mobo yet
replaced bios chip with 'I think' working one, might have been corrupt - no avail

waiting for my other board to return home to try

[Mr.Guvernment]

what about NIC card? built in or external - try a PCI NIC card :D

[pwnt by pat]

built in - I will try external and see what that does when I get the bios uncorrupted...

What good would that do, though?

[Mr.Guvernment]

disable the nic onboard - could be the drivers for that are corrupting if the virus sucked up your bandwidth it may have killed your nic?

not sure really - just process of elimination :D

[pwnt by pat]

Possibility, I guess. Then the nic could be generating errors in the windows install? I know it's not something coming across the networks as I started with it at work and played more with it at home. Like I said, when I get my bios back and the board working again, I'll give it a try. It just seems to have started with one error and degraded the whole system.

I also saw another thread for some of the errors on another forum. The cause was mismatched or bad ram but it worked before.

[RJARRRPCGP]

Maybe the symptoms you're getting are symptoms of too low tight RAM timings.

Maybe 2.0-3-3-6 will solve the problem. If not, try 2.5-3-3-7.

[pwnt by pat]

It's speced 2-2-2-6 (runs at 5 @ by speed) at 215mhz, I ran 200, at 2.5v. It ran fine for quite some time before that at 200. I'm sure it's not the timings.