Bluesceen Error

https://www.sevenforums.com/bsod-help-support/

Yeah, I posted the wrong link too.Blue Screen of Death (BSOD) Posting Instructions

First thing that's showing is your 802.11 USB Network Adaptor driver.

Code:

fffff880`01fb2900  00000000`00000410
fffff880`01fb2908  fffff800`02ea36fa nt!MiQueryAddressSpan+0xaa
fffff880`01fb2910  fffffa80`09f74300
fffff880`01fb2918  fffffa80`09c3b330
fffff880`01fb2920  fffffa80`09c3b330
fffff880`01fb2928  00000000`004d7000
fffff880`01fb2930  fffff880`01fb2988 <Unloaded_bcmwlhigh664>+0x11c988
fffff880`01fb2938  00000000`00000001
fffff880`01fb2940  00000000`00000000
fffff880`01fb2948  00000000`00000000
fffff880`01fb2950  fffffa80`09c3b548
fffff880`01fb2958  00000000`06a3e718
fffff880`01fb2960  00000000`00000410
fffff880`01fb2968  fffffa80`08eceb50
fffff880`01fb2970  fffff880`01fb2b60 <Unloaded_bcmwlhigh664>+0x11cb60
fffff880`01fb2978  fffff800`031b0db4 nt!NtQueryVirtualMemory+0x382
fffff880`01fb2980  fffff880`00000004
fffff880`01fb2988  00000000`004d8000
fffff880`01fb2990  fffffa80`09f74300
fffff880`01fb2998  fffff880`00000000
fffff880`01fb29a0  fffff880`01fb29d8 <Unloaded_bcmwlhigh664>+0x11c9d8

The driver is old and needs updating, check here for an updated version.

Code:

BCMH43XX     Broadcom 802.11 USB Ne Broadcom 802.11 USB Ne 
4/19/2011 3:13:08 AM   C:\Windows\system32\DRIVERS\bcmwlhigh664.sys

Could you also run MemTest86+ to test your RAM (detailed below), it may be a driver causing the following BSOD but none are showing. Let's rule out the RAM and if all is good there we'll look at stressing the drivers to see if anything gives.

Code:

BugCheck 1E, {ffffffffc0000005, fffff80002ef2ad0, 0, ffffffffffffffff}

Probably caused by : memory_corruption ( nt!MiReplenishPageSlist+c0 )

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

1: 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: ffffffffc0000005, The exception code that was not handled
Arg2: fffff80002ef2ad0, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: ffffffffffffffff, Parameter 1 of the exception

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80003109100
GetUlongFromAddress: unable to read from fffff800031091c0
 0000000000000000 Nonpaged pool

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

Download and run MemTest86+ to test your RAM. RAM - Test with Memtest86+

   Note

Run MemTest86+ for at least 8 passes. Ideally set it off before you go to bed and leave it overnight, we're looking for zero errors here. A single error will show something's going bad with your RAM.

OK, good stuff. It's a possibility that the 0x1E was down to the network adapter driver, can you just use the PC as normal and if you receive any more BSODs upload the new logs. Keep us posted either way, if you do get receive more BSODs we'll take it from there.