In article <d8fe9l$9pp$1@inews.gazeta.pl>, Yawn says...
> ...
> It says: "System error" and gives the error codes: 100000d1, parameter 1 
> 82400000, parameter 2 00000002, parameter 3 00000000, parameter 4 f80bca98. 
> Before it restarts, there is a blue screen for a short while, and after the 
> restart it shows "The system returned to work after a critical error.".
> ...

Sorry for jumping in so late--been on the road for awhile, but I'll add to 
what's been offered and maybe it will help (or not).

First, relating to the event log message quoted above, please find it 
again and pull it up to view on your screen. In the message window is a 
link to follow for more information. Follow the link. Perhaps it will be 
useless, but sometimes it is very helpful and tags the problem exactly. 
You'll need to have Windows' "Help and Support" enabled for the link to 
work. Check your START button and see if "Help and Support" is listed just 
above the START button. If not, you'll either need to load it from your 
OEM disc via Add/Remove Programs (Add/Remove Windows Components from that 
screen), or do without the extra information.

The above failing to help you...

Has your machine always done this since the day you started using WiFi, or 
is this new behavior? If new, then something has changed in your software 
or firmware (or possibly, you have a hardware component that is in the act 
of failing). Things to consider:

1. You have a virus or trojan horse that is attempting to access the 
network but is (thankfully) crudely written and failing in its attempts. 
Update your virus scanner software and database and run a full scan. Do 
the same with anti-adware tools.

2. Your network is not secured properly. You may have a neighbor trying to 
log onto your network or attempt peer-to-peer connection with your laptop. 
Something in your configuration is causing a crash when that attempt 
occurs (again, thankfully, else your neighbor could monitor all your 
communications and steal information). Check your security options on your 
laptop's WiFi card and also in your WiFi router. Lock it down TIGHT! Many 
recently-made routers come with an option to permit only specific MAC 
addresses to connect to it. Turn on all your computers so they are talking 
to the router, then access your router configuration and see all the MAC 
addressed connected. Write them down. Then find (if it is an option 
available to you) the router screen that lets you specify which MACs can 
talk to the router. Enter the numbers you wrote, and tell the router not 
to allow any other MAC to connect.

3. You installed or uninstalled some software that has, effectively, 
ruined a common piece of code that is critical to your WiFi card's use. If 
you installed something before the problem started, uninstall it and test. 
If you uninstalled something, reinstall it and test.

4. You didn't state your OS, but I'll presume it's Windows XP. In that 
case, make sure you have all the updates installed from the Windows Update 
site, especially any driver updates.

5. You "tweaked" your system by following some advice that had you modify 
your registry. Undo whatever you did.

6. Something already installed and running for a long time has performed a 
self-update to itself. For example, a software firewall has fetched new 
code, installed it, and is now running on a newer version of itself. Look 
at your anti-virus, firewall, anti-spyware, etc., programs and see when 
they last updated themselves. Anything updated just prior to your getting 
this trouble? If so, disable that software for a day and see if the 
problem continues.

7. Can't imagine why this would cause a blue-screen error, but check your 
WiFi card settings for "Wake system on LAN." If set to on, turn it off. 
Unless you have a reason to have your laptop wake up when another computer 
on your LAN needs something off of it, there's no point in having this 
setting turned on.

8. If you run peer-to-peer or WorkGroup local network, check to see if 
your NetBIOS is disabled. It is safe to disable it provided you've 
designate a host to control the directory. If you haven't done so, then 
the lack of NetBIOS support can certainly cause lock-ups, but I'd be 
astonished that it would cause a blue screen. To do so, you'd also have to 
have another problem, somewhere, but reinabling it might stop the reboots 
even if it doesn't solve the other problem (whatever it may be). By 
default, it is on. You'd either have to disable this service manually (you 
should know if you did), or you used a "tweaking" product that did this 
for you without your knowledge. If the latter, un-tweak.

On the other hand, if this behavior has occured since day one of your WiFi 
use, then you more than likely have a settings/configuration issue 
combined with either (1) a defective WiFi card or (2) a WiFi card that 
isn't built to support the settings you've chosen. After tightening 
security (if that applies to you), reduce your more demanding settings to 
their simplest settings. For example, if you have "Power Save Mode" set to 
on, turn it off, etc., and test some more. 

It sounds as if you've had this laptop for awhile, and just recently 
started using its WiFi capabilities. If that's the case, you may not be 
able to return it to the dealer with a complaint. However, if this laptop 
is brand new, take it back to the dealer and have them diagnose where the 
problem exists: a bad card or a setting that the card does not support. 
Perhaps an outdated driver in combination with an outdated BIOS.

And that would be my final suggestion; log onto the Toshiba web site, 
navigate to the support/download page for your laptop, and see if there 
are new versions of the BIOS available. If you've never upgraded a BIOS 
before, please READ AND FOLLOW the directions, including printing the web 
site page to paper so you have a reference while your machine is off and 
rebooting from the disc you'll have to burn. Shortcuts and "If I mess up, 
I'll just give it another go" approaches WILL NOT WORK when updating a 
BIOS. You either get it right the first time, or send your machine back to 
have the BIOS chips replaced; no second chances.


Cheers!
Frisco