BSOD after installing pci wireless adapter

Hi shyboy78758

Install Service pack 1 and all other windows updates. Otherwise the system will remain vulnerable to threats.

Code:

Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.17273.amd64fre.win7_gdr.130318-1532

Learn how to install Windows 7 Service Pack 1 (SP1)
Service Pack Center - Microsoft Windows

You are highly overclocked.

Code:

 Processor Version             AMD Athlon(tm) 64 X2 Dual Core Processor 6000+
  Processor Voltage             8dh - 1.3V
  Max Speed                     2400MHz
  Current Speed                 3000MHz

As you are getting BSODs, you should stop overclocking and run all the hardware components like CPU, GPU and RAM to their default settings. Also set the BIOS to default, too.
How To Clear CMOS (Reset BIOS)

Your BIOS is too old, too,

Code:

BiosVersion = 6.00 PG
BiosReleaseDate = 12/08/2008
SystemManufacturer = Shuttle Inc
SystemProductName = SK22V10

You may search for updates in Shuttle Europe: Drivers / BIOS

So this PC is old. Let us check some more things ..... Upload a snapshot Using Speccy.

• Download and install Speccy.
• File> Save snapshot.
• Save it on desktop.
• Zip it and upload it following following Screenshots and Files - Upload and Post in Seven Forums .

And, as it started occurring after installing the new adapter, check the situation if it is running OK without that adapter. Update the device driver too.

Let us know the results.
___________________________________________________________
BSOD ANALYSIS:

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa80054f2038, b2000010, 10c0f}

Probably caused by : AuthenticAMD

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

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

WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: fffffa80054f2038, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000b2000010, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000010c0f, Low order 32-bits of the MCi_STATUS value.

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


BUGCHECK_STR:  0x124_AuthenticAMD

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  f

STACK_TEXT:  
fffff800`047f0ac8 fffff800`02a2a903 : 00000000`00000124 00000000`00000000 fffffa80`054f2038 00000000`b2000010 : nt!KeBugCheckEx
fffff800`047f0ad0 fffff800`02be6543 : 00000000`00000001 fffffa80`054f2ea0 00000000`00000000 fffffa80`054f2ef0 : hal!HalBugCheckSystem+0x1e3
fffff800`047f0b10 fffff800`02a2a5c8 : 00000000`00000728 fffffa80`054f2ea0 fffff800`047f0e70 fffff800`02c4ae00 : nt!WheaReportHwError+0x263
fffff800`047f0b70 fffff800`02a29f1a : fffffa80`054f2ea0 fffff800`047f0e70 fffffa80`054f2ea0 00000000`00000000 : hal!HalpMcaReportError+0x4c
fffff800`047f0cc0 fffff800`02a1de8f : 00000000`00000000 00000000`00000001 fffff800`047f0ef0 00000000`00000000 : hal!HalpMceHandler+0x9e
fffff800`047f0d00 fffff800`02acf12c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x47
fffff800`047f0d30 fffff800`02acef93 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
fffff800`047f0e70 fffff880`0438d1f2 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
fffff800`047e4c98 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : amdk8!C1Halt+0x2


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: AuthenticAMD

IMAGE_NAME:  AuthenticAMD

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_BUS

BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_BUS

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

Well, use that driver that worked good there .... ok? :)