BSOD in WinXP Pro...


Recommended Posts

Okay... I want to know if anyone has had this problem... or knows what may be causing it.

I keep getting a BSOD on my system... no pattern to it, and it doesn't matter what program I'm using. I've had it happen in MS Paint, Internet Explorer, MSN Messenger, and Microsoft Photo Editor... just to name a few. It doesn't seem to matter how long the system has been on... but it tends to do it more oten if it's been on longer than 10 hours.

Here is the info I got:

DRIVER_IRQL_NOT_LESS_OR_EQUAL

Stop: 0x000000D1 (0x00000002, 0x00000000, 0x0f98fbf35)

NDIS.sys - Address f98fbf35 base at f98ea000. Date Stamp 3b7dc561

Now, I've looked online and on the MS knowlege base... but couldn't find anything. If I had technet still I'd check that... but I don't. I haven't added any new hardware to the system... and the only driver updates I've done have been after this started. As far as the last thing I did before it started... that would have to be installing XP... hahaha So if anyone out there thinks they can help... please do! It's getting rather annoying. If you need any more info, just ask...

Link to comment
Share on other sites

I got the same thing happening to me but it was fwdrv.sys, which was Kerio firewall file.

I just searched for the file then move it rebooted and Kerio wouldn't work.

So I dumped Kerio, but I still get other blue screens.

LOL XP = POS

Link to comment
Share on other sites

I was going to do that... in fact it's the only non-updated driver I have... but here is the catch. I'm on a wireless Network using all D-Link hardware. I found the new driver, but upon installing it, it kicks me offline... none of my settings ever change and even if I reboot the network, I'm still off. So there is a good chance that's doing it, but I don't know how to fix it and still stay online. Wow... after reading that it seems like I don't know much at all... how did they ever let me tech networks at my previous job? lol And how did I always resolve the problem? hahaha I think I'll blame the D-Link software. lol But does anyone have it and know how to configure the newest XP driver to work?

Link to comment
Share on other sites

Updating Drivers, from IRQ crashes, in NT...usually fix the problem, because it seems that your system isn't sharing IRQ's properly, and xp isn't liking it with your current setup

just update your driver, and then resetup your wireless,

using 802.11x Seemless connection.

Link to comment
Share on other sites

Which D-Link NIC are you using? I had trouble at work with the older model of DFE-530TX and Windows 2000 because there was not a good driver. Unfortunately the newer card doesn't seem to be any good. They switched to a cheaper chipset on the card.

Link to comment
Share on other sites

Originally posted by mtgriffith

Which D-Link NIC are you using? I had trouble at work with the older model of DFE-530TX and Windows 2000 because there was not a good driver. Unfortunately the newer card doesn't seem to be any good. They switched to a cheaper chipset on the card.

Well, I thought I had a DWL-120 (seeing as how it says it on the box, device, and driver)... but being curious as i am, I went to the D-Link site once again... and found out I DON'T have a DWL-120... oh no... I have a DWL-120a. How did I figure this out? Well, seeing as how it doesn't tell you anywhere, there is a site showing the difference. On the back with the barcode... if you have just an exclamation point in a circle... it's a DWL-120. If next to that you have a checkmark... it's a DWL-120a. And if you have both the exclamation point AND the checkmark, and your barcode says a special set of letters, it's a DWL-120d. And guess what? There are different drivers for all models. So apparently what was happening was I've been using the DWL-120 drivers... not the DWL-120a. Well, I just downloaded them and installed them... network is still up and the driver is updated now. So we'll see what happens. I'll be sure to post again if the BSOD happens again. Thanks for all of your help! It's much appreciated!

Link to comment
Share on other sites

Microsoft's Answer

Basically what they are saying...

Stop 0xD1 messages can occur after installing faulty drivers or system services. If a driver is listed by name, disable, remove, or roll back that driver to confirm that this resolves the error.

...is that whatever error you are getting comes from a Driver, which has a problem with it. You need to UNINSTALL all copies of that driver. And if that solves the problem. Go get an updated version of that driver that is designed for Windows XP.

Link to comment
Share on other sites

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.