BOSD while doing anything on the computer, gaming or browsing the web

KayEffCee · 26 Dec 2011

I recently got an Alienware Aurora and a few weeks in it begins to BSOD. It doesn't seem to matter if I'm gaming or browsing the web, it will BSOD at what feels like random times.

The crash info:

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 1033

Additional information about the problem:
BCCode: 1e
BCP1: 0000000000000000
BCP2: 0000000000000000
BCP3: 0000000000000000
BCP4: 0000000000000000
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1

Files that help describe the problem:
C:\WINDOWS\Minidump\122611-14383-01.dmp
C:\Users\Tuan\AppData\Local\Temp\WER-258150-0.sysdata.xml

My system specs are:

Alienware Aurora
Intel(R) Core(TM) i7 CPU 960
RAM: 5.99GB
Windows 7 Home Premium 64bit
AMD Radeon HD 6800 series

writhziden · 26 Dec 2011

You have both of these errors (the links provide fixes, as well):

Event ID 10 is logged in the Application log after you install Service Pack 1 for Windows 7 or Windows Server 2008 R2
Event ID 4107 or Event ID 11 is logged in the Application log in Windows and in Windows Server

Code:


Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\KayEffCee\Windows_NT6_BSOD_jcgriff2\122511-24850-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\users\mike\documents\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`02c62000 PsLoadedModuleList = 0xfffff800`02ea7670
Debug session time: Sun Dec 25 01:13:08.876 2011 (UTC - 7:00)
System Uptime: 0 days 6:54:56.860
Loading Kernel Symbols
...............................................................
................................................................
................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1E, {0, 0, 0, 0}

Unable to load image \SystemRoot\system32\DRIVERS\athrxu6.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for athrxu6.sys
*** ERROR: Module load completed but symbols could not be loaded for athrxu6.sys
Probably caused by : nwifi.sys ( nwifi!Pt6RepackRecvNBL+103 )

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

6: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: 0000000000000000, The exception code that was not handled
Arg2: 0000000000000000, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception

Debugging Details:
------------------


EXCEPTION_CODE: (Win32) 0 (0) - The operation completed successfully.

FAULTING_IP: 
+3731623830316234
00000000`00000000 ??              ???

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  0000000000000000

ERROR_CODE: (NTSTATUS) 0 - STATUS_WAIT_0

BUGCHECK_STR:  0x1E_0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  2

EXCEPTION_RECORD:  fffff8800353d4a8 -- (.exr 0xfffff8800353d4a8)
ExceptionAddress: fffff88005208767 (nwifi!Pt6RepackRecvNBL+0x0000000000000103)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

TRAP_FRAME:  fffff8800353d550 -- (.trap 0xfffff8800353d550)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffa800998a0c0 rbx=0000000000000000 rcx=fffff880052406e0
rdx=fffffa8009a10f40 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88005208767 rsp=fffff8800353d6e0 rbp=0000000000000000
 r8=0000000000000000  r9=1f07d0c2c7116392 r10=fffff8800523e110
r11=0000000000000006 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na pe nc
nwifi!Pt6RepackRecvNBL+0x103:
fffff880`05208767 450fb701        movzx   r8d,word ptr [r9] ds:fe9b:1f07d0c2`c7116392=????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002cd65fe to fffff80002cdec10

STACK_TEXT:  
fffff880`0353c588 fffff800`02cd65fe : fffffa80`063e3890 fffffa80`063dcfd0 fffff880`0353cd00 fffff800`02d0a830 : nt!KeBugCheck
fffff880`0353c590 fffff800`02d0a4fd : fffff800`02ee871c fffff800`02e25c30 fffff800`02c62000 fffff880`0353d4a8 : nt!KiKernelCalloutExceptionHandler+0xe
fffff880`0353c5c0 fffff800`02d092d5 : fffff800`02e290fc fffff880`0353c638 fffff880`0353d4a8 fffff800`02c62000 : nt!RtlpExecuteHandlerForException+0xd
fffff880`0353c5f0 fffff800`02d1a361 : fffff880`0353d4a8 fffff880`0353cd00 fffff880`00000000 fffffa80`09993a90 : nt!RtlDispatchException+0x415
fffff880`0353ccd0 fffff800`02cde2c2 : fffff880`0353d4a8 00000000`00000000 fffff880`0353d550 fffffa80`09bcc010 : nt!KiDispatchException+0x135
fffff880`0353d370 fffff800`02cdcbca : fffffa80`0998a1b0 fffff800`02ce4fda fffff800`02e54e00 fffff880`06d10524 : nt!KiExceptionDispatch+0xc2
fffff880`0353d550 fffff880`05208767 : 00000000`00000000 00000000`00000000 fffffa80`09bcc010 fffffa80`00000f76 : nt!KiGeneralProtectionFault+0x10a
fffff880`0353d6e0 fffff880`052096c8 : fffffa80`0999c030 fffffa80`09990578 fffffa80`00000578 fffffa80`09bcc010 : nwifi!Pt6RepackRecvNBL+0x103
fffff880`0353d7e0 fffff880`018ce4e7 : fffffa80`0998e1a0 fffffa80`09993a90 00000000`00000001 fffffa80`099a3468 : nwifi!Pt6Receive+0x170
fffff880`0353d840 fffff880`06cd8e92 : fffffa80`096efe9b 00000000`00000000 00000000`00000000 fffffa80`09955c00 : ndis! ?? ::FNODOBFM::`string'+0xcf1f
fffff880`0353d890 fffffa80`096efe9b : 00000000`00000000 00000000`00000000 fffffa80`09955c00 00000000`00000001 : athrxu6+0x10e92
fffff880`0353d898 00000000`00000000 : 00000000`00000000 fffffa80`09955c00 00000000`00000001 00000000`00000000 : 0xfffffa80`096efe9b


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nwifi!Pt6RepackRecvNBL+103
fffff880`05208767 450fb701        movzx   r8d,word ptr [r9]

SYMBOL_STACK_INDEX:  7

SYMBOL_NAME:  nwifi!Pt6RepackRecvNBL+103

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nwifi

IMAGE_NAME:  nwifi.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bcc3b

FAILURE_BUCKET_ID:  X64_0x1E_0_nwifi!Pt6RepackRecvNBL+103

BUCKET_ID:  X64_0x1E_0_nwifi!Pt6RepackRecvNBL+103

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

Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\KayEffCee\Windows_NT6_BSOD_jcgriff2\122611-16442-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\users\mike\documents\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`02c1b000 PsLoadedModuleList = 0xfffff800`02e60670
Debug session time: Mon Dec 26 15:47:29.959 2011 (UTC - 7:00)
System Uptime: 1 days 5:54:24.943
Loading Kernel Symbols
...............................................................
................................................................
...............
Loading User Symbols
Loading unloaded module list
..........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1E, {0, 0, 0, 0}

Unable to load image \SystemRoot\system32\DRIVERS\athrxu6.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for athrxu6.sys
*** ERROR: Module load completed but symbols could not be loaded for athrxu6.sys
Probably caused by : nwifi.sys ( nwifi!Pt6RepackRecvNBL+58d )

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

6: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: 0000000000000000, The exception code that was not handled
Arg2: 0000000000000000, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception

Debugging Details:
------------------


EXCEPTION_CODE: (Win32) 0 (0) - The operation completed successfully.

FAULTING_IP: 
+3731623830316234
00000000`00000000 ??              ???

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  0000000000000000

ERROR_CODE: (NTSTATUS) 0 - STATUS_WAIT_0

BUGCHECK_STR:  0x1E_0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  chrome.exe

CURRENT_IRQL:  2

EXCEPTION_RECORD:  fffff88003344538 -- (.exr 0xfffff88003344538)
ExceptionAddress: fffff88003a08bf1 (nwifi!Pt6RepackRecvNBL+0x000000000000058d)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

TRAP_FRAME:  fffff880033445e0 -- (.trap 0xfffff880033445e0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=cb9e037fb0c1acf1 rbx=0000000000000000 rcx=0000000000000f36
rdx=fffff880033447e0 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88003a08bf1 rsp=fffff88003344770 rbp=fffffa8005eeb018
 r8=0000000000000000  r9=0000000000000000 r10=fffff88003a3e110
r11=0000000000000006 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe nc
nwifi!Pt6RepackRecvNBL+0x58d:
fffff880`03a08bf1 488b00          mov     rax,qword ptr [rax] ds:f480:cb9e037f`b0c1acf1=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002c8f5fe to fffff80002c97c10

STACK_TEXT:  
fffff880`03343618 fffff800`02c8f5fe : 00000000`00000000 00000000`00000000 fffff880`03343d90 fffff800`02cc3830 : nt!KeBugCheck
fffff880`03343620 fffff800`02cc34fd : fffff800`02ea171c fffff800`02ddec30 fffff800`02c1b000 fffff880`03344538 : nt!KiKernelCalloutExceptionHandler+0xe
fffff880`03343650 fffff800`02cc22d5 : fffff800`02de2028 fffff880`033436c8 fffff880`03344538 fffff800`02c1b000 : nt!RtlpExecuteHandlerForException+0xd
fffff880`03343680 fffff800`02cd3361 : fffff880`03344538 fffff880`03343d90 fffff880`00000000 fffffa80`00000005 : nt!RtlDispatchException+0x415
fffff880`03343d60 fffff800`02c972c2 : fffff880`03344538 cb9e037f`b0c1acf1 fffff880`033445e0 fffff880`033447e0 : nt!KiDispatchException+0x135
fffff880`03344400 fffff800`02c95bca : fffffa80`0abaa150 fffff800`02dc61de 00000000`00000001 00000000`00011021 : nt!KiExceptionDispatch+0xc2
fffff880`033445e0 fffff880`03a08bf1 : fffff880`03315180 00000000`00000001 fffffa80`05e62200 fffff800`02c9dfda : nt!KiGeneralProtectionFault+0x10a
fffff880`03344770 fffff880`03a09021 : fffffa80`058b1030 00000000`00000000 00000000`00000000 fffffa80`06027010 : nwifi!Pt6RepackRecvNBL+0x58d
fffff880`033447c0 fffff880`03a096fc : fffffa80`06027010 fffffa80`060f6cfd fffffa80`00000cfd fffffa80`06027010 : nwifi!Pt6RepackRecvNBL+0x9bd
fffff880`03344a10 fffff880`010a54e7 : fffffa80`098d41a0 fffffa80`05707340 00000000`00000001 fffffa80`06011db8 : nwifi!Pt6Receive+0x1a4
fffff880`03344a70 fffff880`082ede92 : fffffa80`05825e0b 00000000`00000000 00000000`00000000 fffffa80`0b0a9200 : ndis! ?? ::FNODOBFM::`string'+0xcf1f
fffff880`03344ac0 fffffa80`05825e0b : 00000000`00000000 00000000`00000000 fffffa80`0b0a9200 00000000`00000001 : athrxu6+0x10e92
fffff880`03344ac8 00000000`00000000 : 00000000`00000000 fffffa80`0b0a9200 00000000`00000001 00000000`00000000 : 0xfffffa80`05825e0b


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nwifi!Pt6RepackRecvNBL+58d
fffff880`03a08bf1 488b00          mov     rax,qword ptr [rax]

SYMBOL_STACK_INDEX:  7

SYMBOL_NAME:  nwifi!Pt6RepackRecvNBL+58d

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nwifi

IMAGE_NAME:  nwifi.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bcc3b

FAILURE_BUCKET_ID:  X64_0x1E_0_nwifi!Pt6RepackRecvNBL+58d

BUCKET_ID:  X64_0x1E_0_nwifi!Pt6RepackRecvNBL+58d

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

Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\KayEffCee\Windows_NT6_BSOD_jcgriff2\122611-14383-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\users\mike\documents\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`02c04000 PsLoadedModuleList = 0xfffff800`02e49670
Debug session time: Mon Dec 26 16:33:09.899 2011 (UTC - 7:00)
System Uptime: 0 days 0:22:32.883
Loading Kernel Symbols
...............................................................
................................................................
..............
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1E, {0, 0, 0, 0}

Unable to load image \SystemRoot\system32\DRIVERS\athrxu6.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for athrxu6.sys
*** ERROR: Module load completed but symbols could not be loaded for athrxu6.sys
Probably caused by : nwifi.sys ( nwifi!Pt6RepackRecvNBL+103 )

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

6: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: 0000000000000000, The exception code that was not handled
Arg2: 0000000000000000, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception

Debugging Details:
------------------


EXCEPTION_CODE: (Win32) 0 (0) - The operation completed successfully.

FAULTING_IP: 
+3731623830316234
00000000`00000000 ??              ???

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  0000000000000000

ERROR_CODE: (NTSTATUS) 0 - STATUS_WAIT_0

BUGCHECK_STR:  0x1E_0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  2

EXCEPTION_RECORD:  fffff8800333d4a8 -- (.exr 0xfffff8800333d4a8)
ExceptionAddress: fffff88004378767 (nwifi!Pt6RepackRecvNBL+0x0000000000000103)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

TRAP_FRAME:  fffff8800333d550 -- (.trap 0xfffff8800333d550)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffa80097e8590 rbx=0000000000000000 rcx=fffff880043b06e0
rdx=fffffa80098c1f40 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88004378767 rsp=fffff8800333d6e0 rbp=0000000000000000
 r8=0000000000000000  r9=75e6e56c684b7aff r10=fffff880043ae110
r11=0000000000000006 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na po nc
nwifi!Pt6RepackRecvNBL+0x103:
fffff880`04378767 450fb701        movzx   r8d,word ptr [r9] ds:9aeb:75e6e56c`684b7aff=????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002c785fe to fffff80002c80c10

STACK_TEXT:  
fffff880`0333c588 fffff800`02c785fe : fffffa80`05c2fc40 00000000`00000000 fffff880`0333cd00 fffff800`02cac830 : nt!KeBugCheck
fffff880`0333c590 fffff800`02cac4fd : fffff800`02e8a71c fffff800`02dc7c30 fffff800`02c04000 fffff880`0333d4a8 : nt!KiKernelCalloutExceptionHandler+0xe
fffff880`0333c5c0 fffff800`02cab2d5 : fffff800`02dcb0fc fffff880`0333c638 fffff880`0333d4a8 fffff800`02c04000 : nt!RtlpExecuteHandlerForException+0xd
fffff880`0333c5f0 fffff800`02cbc361 : fffff880`0333d4a8 fffff880`0333cd00 fffff880`00000000 fffffa80`09891e50 : nt!RtlDispatchException+0x415
fffff880`0333ccd0 fffff800`02c802c2 : fffff880`0333d4a8 00000000`00000000 fffff880`0333d550 fffffa80`09a03010 : nt!KiDispatchException+0x135
fffff880`0333d370 fffff800`02c7ebca : fffffa80`097e8680 fffff800`02c86fda fffffa80`08e92000 fffff880`0425d524 : nt!KiExceptionDispatch+0xc2
fffff880`0333d550 fffff880`04378767 : 00000000`00000000 00000000`00000000 fffffa80`09a03010 fffffa80`000005fc : nt!KiGeneralProtectionFault+0x10a
fffff880`0333d6e0 fffff880`043796c8 : fffffa80`09812030 fffffa80`098bc834 fffffa80`00000834 fffffa80`09a03010 : nwifi!Pt6RepackRecvNBL+0x103
fffff880`0333d7e0 fffff880`016c24e7 : fffffa80`097c71a0 fffffa80`09891e50 00000000`00000001 fffffa80`098bf120 : nwifi!Pt6Receive+0x170
fffff880`0333d840 fffff880`04225e92 : fffffa80`097a9aeb 00000000`00000000 00000000`00000000 fffffa80`09734900 : ndis! ?? ::FNODOBFM::`string'+0xcf1f
fffff880`0333d890 fffffa80`097a9aeb : 00000000`00000000 00000000`00000000 fffffa80`09734900 00000000`00000001 : athrxu6+0x10e92
fffff880`0333d898 00000000`00000000 : 00000000`00000000 fffffa80`09734900 00000000`00000001 00000000`00000000 : 0xfffffa80`097a9aeb


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nwifi!Pt6RepackRecvNBL+103
fffff880`04378767 450fb701        movzx   r8d,word ptr [r9]

SYMBOL_STACK_INDEX:  7

SYMBOL_NAME:  nwifi!Pt6RepackRecvNBL+103

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nwifi

IMAGE_NAME:  nwifi.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bcc3b

FAILURE_BUCKET_ID:  X64_0x1E_0_nwifi!Pt6RepackRecvNBL+103

BUCKET_ID:  X64_0x1E_0_nwifi!Pt6RepackRecvNBL+103

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

All three are probably caused by nwifi.sys which is the NativeWiFi Miniport Driver for Windows. It appears to be related to your athrxu6.sys driver for your outdated Atheros wireless device. The device is not supported by Windows 7. Recommend removing it/disabling it and physically installing a new wireless device, perhaps a USB wireless device if you cannot replace the device in the motherboard.

KayEffCee · 26 Dec 2011

I do have an old wireless internet adapter that I use windows vista drivers for it to work. I will go obtain a Wnidows 7 compatible wireless internet as quickly as possible and report back.

writhziden · 16 Jan 2012

Did you get a new wireless network device for your computer? How is it running? Please keep us updated. :)

KayEffCee · 16 Jan 2012

Ah! I'm sorry! I got a new wireless adapter and it is working great with no blue screens or crashes. I've been enjoying my crashless computer too much and forgot to report back :P

writhziden · 16 Jan 2012

No problem. Thanks for getting back to us now. You can mark the thread as solved by clicking the green button at the bottom of the thread next to Post Reply. :)