Bsod

[ntgof]

Hi

im running OP ver 3.5 on an xpsp2 system, but occationally when brosing using firefox, i get a BSOD . with the error statement;

driver_irql_not_less_or_equal
STOP: 0x000000D1 (0xEEFA424E, 0x00000002, 0x00000000, 0xEEFA424E)
afd, sys = Address EEFA424E base at EEF9E000, Datestamp 41107eb5

i searched for this in this forum as well, and the closest i came was a hardware/driver failure possibly caused by my ethernet card (3com gigabit LOM (3C940) )

I have tried almost everything (except changing hardware so far) does anyone here have a hint as where i should look ?

My guess is its related to OP and firefox, but after reading fragments on the forum it may be related to hardware issues ?

Any help greatly appreciated as BSODs can be nearly impossible to locate...

regards Nolan

[wat0114]

Originally Posted by ntgof

im running OP ver 3.5 on an xpsp2 system, but occationally when brosing using firefox, i get a BSOD . with the error statement;

driver_irql_not_less_or_equal
STOP: 0x000000D1 (0xEEFA424E, 0x00000002, 0x00000000, 0xEEFA424E)
afd, sys = Address EEFA424E base at EEF9E000, Datestamp 41107eb5

According to my XP manual, Microsoft describes that error as a "software and device driver error". Have you updated drivers recently on any of your hardware? One thing you could try is: Start->Run, then type sigverif.exe and hit Enter. Hit the Start button to scan for unsigned drivers to see if you have any. You may see something that could be the culprit. I have run it on my system and it found only two unsigned drivers both of which are related to Acronis True Image, but they have not, luckily, interfered with my system yet.

[Manny Carvalho]

I presume that this stop error came from afd.sys (not afd, sys) which is part of the TCP/IP stack. Pre SP2 there was some memory leaks that caused non-paged pool memory to become exhausted and caused this error. Have you by any chance been fooling around with Winsock programs.

Take a look at: http://support.microsoft.com/kb/q296265/ and this old article that has some useful information - http://bdn2.borland.com/article/30362

Is there something that shows that this stop error is related to OP?

[ntgof]

Hi

thanks

the error message was actually afd, sys (att screenshot)
I cant recall havind fiddled with winsock progs - only indication of relation mto OP is only active progs are firefox and OP.

Ill try to buy another ethernet card.

Any other suggestions on the errer messages to guide me in the right direction ?

regards Nolan

[Manny Carvalho]

Just a bit off topic Nolan. That's a nice monitor. Do you like it? I have a Samsung 171V this is 3 years old and has performed very well. Yours looks like a real nice size.

Let us know how the new card works.

[ntgof]

Hi Manny

yes i know - but it seems there are many pro ressources gathered in this forum - som therefor my hope that any had some advice - BSODs are the worst sort of problems to solve in my experiance

(Still happy for some suggestions .......)

The monitor is a samsung syncmaster 215 TW (21") - and im really happy with it - the
only thing worth mentioning is that i see some small deviation in light intensity on the left side - it seems to be a little brighter there. Although its not noticeable in daily usage. Brilliant vibrant colors

I would buy it again - if i had to choose today

Regards Nolan

[Manny Carvalho]

Originally Posted by ntgof

Hi Manny

yes i know - but it seems there are many pro ressources gathered in this forum - som therefor my hope that any had some advice - BSODs are the worst sort of problems to solve in my experiance

I meant that my post about your monitor is a bit off topic not yours. We will be glad to help you if we can.

Thanks for the info on your monitor. Next time I purchase a monitor I think it will be something like yours. I appreciate the off-topic the discussion.

[ntgof]

Hi Manny

ill let you know wether changing the ethernet card did any difference,

regards Nolan

[ntgof]

Hi

changed the card - no difference - still BSOD related to afd.sys

regards Nolan

[FadeToBlack]

Reinstall Windows. See if this works. Then, if nothing bad happens use something like Acronis True Image to backup.

[FadeToBlack]

Hey, one more thing. I am having some kind of problems with KAV for WFS. So, maybe you should report this to Kaspersky too.

[minoka]

Please, if you are going to discuss kav for wfs or for whatever, start a new thread. The topic here is Bsod
Thanks.

[FadeToBlack]

No, I am not doing that. I had a similar problem and I pointed that out. I know that he has KAV and I think that it may be a conflict, who knows...

[Manny Carvalho]

Originally Posted by ntgof

Hi

changed the card - no difference - still BSOD related to afd.sys

regards Nolan

Too bad Nolan.

Here my next suggestion. Since afd.sys is part of the TCP/IP stack perhaps resetting the stack will help you. For this purpose you use the NetShell utility to return the stack back to the state it was when first installed.

To do this, from the command prompt type: netsh int ip reset [log_file_name] where [log_file_name] is any file name you want for the log file. For example netsh int ip reset c:\log.txt would be a valid command.

This MS article gives further details: How to reset Internet Protocol (TCP/IP) in Windows XP

If this doesn't help please look in the event viewer around the time this happened and see if you can find any additional error messages that might help.

I'm moving this thread to Computer Help forum where perhaps others might see it and offer more suggestions.

[Manny Carvalho]

Looking at this a little further this D1 stop message indicates that the system attempted to access pageable memory using a kernel process IRQL that was too high. The most typical cause is a bad device driver (one that uses improper addresses). It can also be caused by caused by faulty or mismatched RAM, or a damaged pagefile.

So the easiest thing at this point - after what I suggested above - is to:

1. Look in the event viewer for error messages regarding a bad driver.
2. Reset your pagefile by turning it off, rebooting and turn it back on again.

Here are further details:

Error Message with RAM Problems or Damaged Virtual Memory Manager
STOP:0xD1" Error Message When You Start Your Windows XP-Based Computer