ISATAP Adapter #8 error code 31

When exactly in the boot process does this occur? Are you hearing any beeps before Windows starts to load?

Is the new CPU fan working correctly?

one thing I'd like to add is that I just found windows has created pagefile.sys as large as 16 Gb in drive C:\ and drive F:\

Is there anything wrong with my RAM and System Memory?

wither 2 said:

When exactly in the boot process does this occur? Are you hearing any beeps before Windows starts to load?

Is the new CPU fan working correctly?

after beeping and all the DOS stuff (sry for being a noob) and after the windows seven animated logo. Exactly before the log on screen. The fan is working properly tough.

I asked because two beeps before Windows starts to load indicates a potential memory problem.

Best way to check is to use memtest86+. You can get it here-

Memtest86+ - Advanced Memory Diagnostic Tool

I grabbed some instructions on how to prep it for use on a USB flash drive from another website-

"Grab an unused USB flash drive and connect it to your PC.
Download the Windows MemTest86 USB image.
Right click on the image file, and select the "Extract to Here" option. Extract the file folder anywhere you can get to easily (eg. your Desktop).
Inside the extracted folder, run the included imageUSB tool, and choose your plugged in USB drive to turn into a bootable drive. CAUTION: this action will erase all data on the USB drive.
Memtest86 will now be installed on your USB and you are ready to test for the possible source of srvnet.sys errors.
Restart your PC with the USB drive installed.
Memtest86 will begin testing for memory corruption.
Follow the on-screen commands."

One thing not mentioned here is that you will need to ensure that a USB drive is set to boot before the hard drive in the BIOS.

wither 2 said:

I asked because two beeps before Windows starts to load indicates a potential memory problem.

Best way to check is to use memtest86+. You can get it here-

Memtest86+ - Advanced Memory Diagnostic Tool

I grabbed some instructions on how to prep it for use on a USB flash drive from another website-

"Grab an unused USB flash drive and connect it to your PC.
Download the Windows MemTest86 USB image.
Right click on the image file, and select the "Extract to Here" option. Extract the file folder anywhere you can get to easily (eg. your Desktop).
Inside the extracted folder, run the included imageUSB tool, and choose your plugged in USB drive to turn into a bootable drive. CAUTION: this action will erase all data on the USB drive.
Memtest86 will now be installed on your USB and you are ready to test for the possible source of srvnet.sys errors.
Restart your PC with the USB drive installed.
Memtest86 will begin testing for memory corruption.
Follow the on-screen commands."

One thing not mentioned here is that you will need to ensure that a USB drive is set to boot before the hard drive in the BIOS.

Dear wither 2 -

I used the tool and for 1 pass no errors were found (dont know how many passes should be taken) so I assume my system memory is fine. But the boot problem that happens from time to time and irregularly, still exists I think. Btw My KasperTotalSec has found another trojan today in sys32 directory which I provided the pic for you in case that might be the cause of the issue.

You didn't mention if it was two beeps before the Windows log on. However, seems memory is okay.

In re-reading, the problem occurs after Windows has started booting.

In reading about that .dll, it isn't necessarily caused by a trojan/virus since it's used by some browsers. If you quarantine it in Kapersky or remove it following the instructions provided in other blogs and the problem goes away, then you have your answer. However, your screenshot from 3 days ago shows the presence of the same .dll.

I think you should run the procedure I provided for a clean boot just to see if it occurs. It's tough to figure out because your getting the error sporadically and you shouldn't leave your system in the clean boot configuration for a significant amount of time.

The other thing I think you should do is provide the bluescreenview when it happens the next time. In addition, run eventvwr and provide the eventlog.