I don't know about the second problem, but in regard to the first one, if there was white text on those BSoDs, it would be very helpful if you posted it.

I also got BSoDs when I first got my Inspiron 8200, and the cause turned out to be a faulty memory module.

To read the BSOD without the computer restarting..right click "My Computer" choose Properties>Advanced Tab>Startup and Recovery..click on Settings>under System Failure uncheck "Automatically Restart".

Yeah I would post the text if I was able to, however the screen flashes the error message in a split second and the laptop reboots immediately. No prompt, no pause.

Some more information on the second problem: It may have something to do with plugging/unplugging AC power source while the laptop is in hibernation or standby. Is it not a good idea to be playing with the AC source when the laptop is in such a power state? And in the garbled mess of pixels I can barely make out my Windows desktop- some icons and text can barely be pieced together in all the scrambled images

Ah thanks for that automatic restart tip! Now when I get home I'll try to recreate that BSOD.

And about my screens crambling problem, looks like it has nothing do with AC afterall. I was just trying to demonstrate the problem to a friend of mine and sure enough, when I closed my computer lid to go into standby and reopened it- scrambled screen! I did not fiddle with the AC power plug this time. I was able to put my computer into hibernation using my Suspend key setting, and once I did that the scrambled screen disappeared (although the Windows screen telling you it's going into hibernation was slightly scrambled as well).

OK, I changed the settings and now I recreated the BSOD. A screen shot can be found here: http://members.verizon.net/~vze28272/screen.jpg (verizon has been acting up lately- you might get a 'locked' response but keep refreshing or reopen the browser)

Again, it happened when I used telnet to connect to a remote POP3 server. I can use a regular email client without problems...

Any ideas?

Which wireless card do you have installed? From looking around Google I think w22n51.sys refers to a driver for a wireless card; although I am not absolutely certain. Look in Device manager and see what it shows for drivers under your wireless card.

http://aumha.org/win5/kbestop.htm scroll down to D1 problems. It does state that a faulty driver may be a cause of this blue screen.

Message Edited by possumall on 07-08-2004 07:26 PM

Thanks for the reply Possumall!

I have the Intel PRO/Wireless 2200G card, and checking under device manager it does indeed have that driver. I looked at that link you provided and I could not find any mention of this driver... do they have any recommendations for solving this problem?

Dell shows a driver for the 2200bg:

http://support.dell.com/support/downloads/type.aspx?c=us&cs=19&l=en&s=dhs&SystemID=INS_PNT_P4M_8600&category=0&os=WW1&osl=en&deviceid=5896&devlib=5

Is this the card you have? All I can suggest is trying to update the driver; you can always roll it back. Look in Downloads under product Support above for your system and see what you can find if the link I gave you is the wrong card.

Message Edited by possumall on 07-10-2004 04:50 PM

Well, at least you can experiment without the BSOD. I'm no wiz at wireless but maybe you can go to the Wireless Networking Board and ask some questions there. I have pretty lucky with my wireless connection to our laptop since last October. Hope you get it figured out.

Oh check this out... when I called my wireless access point manufacturer (Motorola) for tech support for this wireless disocnnection problem I just explained, the guy told me I should try a different encryption scheme. I set it to WPA-PSK originally and he told me to try WEP. So I changed the settings on the access point and my laptop yesterday, but after using my latop for a few hours I got that disconnection again, so I was bummed out and figured it did nothing. But I just remembered I never tried telnet to see if I get the BSOD again, and it turns out I am able to use telnet right now without it crashing the OS... It's a bittersweet development though, because I'm not so much worried anymore about the OS crashing while using telnet as opposed to my wireless connection randomly dying off on me.