Very Random Restarts - System Stable? Unstable?

[acuransx]

Hi

Recently, I have been experiencing random restarts.


System restarts randomly.

Tested MemTest86+ (3 Rounds) -> Passed OK
Tested Prime95 (3 hours) -> Passed OK
Tested 3DMark06 (3 times)-> Passed OK

I just want to know whether it is software or hardware relating (likely cause).

I have included my minidumps. Hope you guys can help me.

The first few minidumps are caused by "ntoskrnl.exe". After I replaced with a newer version of "ntoskrnl.exe", the Minidump then reports the error is caused by ipnat.sys.

Thank you

 

[Route44]

What firewall are you using?

 

[acuransx]

Windows XP default Firewall

I also have PeerGuardian running in the background.

I have also attached new Minidumps, BSOD an hour ago...

 

[Route44]

First, XP firewall is a very poor firewall. There are much better options that are free: Comodo and Online Armor's free version (it even has HIPS).

Second, your error codes are various and all dump files only cite Windows OS drivers which are normally too general to be of much help. However, ipnat.sys does come up regularly and if you do a search this driver and the Windows firewall will conflict.

Here are some suggestions:

1. Your NIC/wireless card may need to have its drivers updated.

2. Your NIC/wireless card may need to be replaced.

3. Disable the XP firewall and download and install one of the two suggestions above. Both have a great support community. Comodo may take a bit of tweaking on your part. Keep in mind that when installing a new firewall it will take some time to learn your habits.

Also, for future reference, MemTest needs to run for a minimum of 7 Passes and the more the bettrer. It would be a good idea to let it run overnight.

 

[acuransx]

ntoskrnl.exe BSOD comes back again...

possible hardware error ?

S.M.A.R.T reports ok, I guess the drivers are not corrupted

Pls advise

Thanks

 

[Route44]

S.M.A.R.T. will not tell us if the drivers are corruptible or not. That is a harddrive diagnostic test for the physical condition of your drive and not drivers.

Have you tried any of the previous advice I gave you?

 

[acuransx]

I passed Memtest 7 times and switched off Windows Firewall... still monitoring for BSOD

 

[Route44]

Keep us up-to-date but get yourself a firewall as soon as you can. Also, I assume you are behind a router, correct?

 

[acuransx]

Yes, Linksys WRT54GC

 

[acuransx]

BSOD, 5 mins ago

DRIVER_CORRUPTED_EXPOOL (c5)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is
caused by drivers that have corrupted the system pool. Run the driver
verifier against any new (or suspect) drivers, and if that doesn't turn up
the culprit, then use gflags to enable special pool.

Arguments:
Arg1: 00000004, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000001, value 0 = read operation, 1 = write operation
Arg4: 8054afd2, address which referenced memory

Possible, mobo chipset failure ?

 

[Route44]

The dump simply cited a Windows OS driver as the issue but they are usually too general to be of much help.

Try this: Uninstall Peer Guardian and see if that brings stability. Also, make sure you get a firewall.

 

[acuransx]

I updated my drivers for

Network card
Graphics
Audio

Other than these, the rest are generic drivers from Microsoft...

I see if the drivers issues helps the BSOD...

 

[acuransx]

Now, this is really wierd...

I can boot to windows, however, I cannot boot to safe mode.