Unexpected Shutdown...what!

Okay, so I locked my computer and went upstairs for dinner, after watching some tv shows I came back 2 hours later to find the computer had restarted!

So after logging in a message comes up saying:

Quote:

---

Windows has recovered from an unexpected shutdown

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.0.6001.2.1.0.768.3
Locale ID: 5129

Additional information about the problem:
BCCode: a
BCP1: 88801000
BCP2: 00000002
BCP3: 00000001
BCP4: 828F3693
OS Version: 6_0_6001
Service Pack: 1_0
Product: 768_1

Files that help describe the problem:
C:\WINDOWS\Minidump\Mini031509-01.dmp
C:\Users\André\AppData\Local\Temp\WER-6620776-0.sysdata.xml
C:\Users\André\AppData\Local\Temp\WER4AD6.tmp.vers ion.txt

Read our privacy statement:
http://go.microsoft.com/fwlink/?link...3&clcid=0x0409

---

Is this bad :S If so what actions should I take to prevent it happening again.

Thanks,
Ver.

It can't be good, it could either be a one off or it could be a bad problem with your hardware or drivers. What you should do is download WinDBG from http://www.microsoft.com/whdc/devtoo...g/default.mspx

Then install it and goto File > Open Crash Dump > Browse to and open "C:\WINDOWS\Minidump\Mini031509-01.dmp" then post it here.

So much easier to find out why a BSOD happened unlike on a Mac. JOKE. JESUS. DON'T FLAME ME LOL.

Here is what is came up with:

Quote:

---

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\WINDOWS\Minidump\Mini031509-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: *** Invalid ***
************************************************** **************************
* Symbol loading may be unreliable without a symbol search path. *
* Use .symfix to have the debugger choose a symbol path. *
* After setting your symbol path, use .reload to refresh symbol locations. *
************************************************** **************************
Executable search path is:
************************************************** *******************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
************************************************** *******************
Unable to load image \SystemRoot\system32\ntkrnlpa.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Windows Server 2008/Windows Vista Kernel Version 6001 (Service Pack 1) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Machine Name:
Kernel base = 0x8283e000 PsLoadedModuleList = 0x82955c70
Debug session time: Sun Mar 15 20:41:22.341 2009 (GMT+13)
System Uptime: 0 days 11:10:07.221
************************************************** *******************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
************************************************** *******************
Unable to load image \SystemRoot\system32\ntkrnlpa.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Loading Kernel Symbols
.................................................. .............
.................................................. ..............
.....................
Loading User Symbols
Loading unloaded module list
..................................................
************************************************** *****************************
* *
* Bugcheck Analysis *
* *
************************************************** *****************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {88801000, 2, 1, 828f3693}

*** WARNING: Unable to verify timestamp for mssmbios.sys
*** ERROR: Module load completed but symbols could not be loaded for mssmbios.sys
*** WARNING: Unable to verify timestamp for Wdf01000.sys
*** ERROR: Module load completed but symbols could not be loaded for Wdf01000.sys
*** WARNING: Unable to verify timestamp for USBPORT.SYS
*** ERROR: Module load completed but symbols could not be loaded for USBPORT.SYS
*** WARNING: Unable to verify timestamp for spck.sys
*** ERROR: Module load completed but symbols could not be loaded for spck.sys
***** Kernel symbols are WRONG. Please fix symbols to do analysis.

************************************************** ***********************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
************************************************** ***********************
************************************************** ***********************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
************************************************** ***********************
************************************************** ***********************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
************************************************** ***********************
************************************************** *******************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
************************************************** *******************
************************************************** *******************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
************************************************** *******************
Probably caused by : athrusb.sys ( athrusb+7ef96 )

Followup: MachineOwner
---------

---

Quote:

---

Probably caused by : athrusb.sys ( athrusb+7ef96 )

Followup: MachineOwner
---------

---

Tells me that your Wireless driver is fubared. I would go and check for a driver update from the manufacturer's website if I was you.

Hur?

http://img14.imageshack.us/img14/9452/hmml.jpg

http://www.tp-link.com/support/downl...=1&m=TL-WN620G Use those, never rely on what Windows can find.

That's where I downloaded them from, went into Device Manager and clicked update drivers from selected location.

Ahh ok, you'll have to wait until they release some new updates then... it may have just been a one of though.

Should I uninstall the current ones and install these?

Can not edit post.

To make matters worse, I go to turn on my computer today, it starts and then a screen comes up saying windows failed to start, so I did the repairs and restarted, same thing. So I removed the TP-Link wifi adapter and rebooted, sure enough it booted fine. So what's wrong with the adapter? Is it corrupt or something...

I would get a new one, to be fair I have never heard of the company that makes it before LOL

Quote:

---

Originally Posted by *****

I would get a new one, to be fair I have never heard of the company that makes it before LOL

---

same, I'd also recommend the Belkin ;D, it was the first (for me) that worked flawlessly on Vista xD

Yeah my friend is always nagging me to get a belkin One lol. Thanks.