Hi,
My BSOD has happened now 3 days in a row and I can't ignore it any longer! I can't identify a trigger for it. It happened once when I was using IE9, and twice when the computer was idle.
Any help greatly appreciated!
Thanks!
Please upload your msinfo32.nfo file. To get this: Start Menu -> Type msinfo32 into the Search programs and files box -> When it opens, go to File, Save -> Save as msinfo32.nfo and save in a place you will remember -> Let it finish the process of gathering and saving the system info -> Right click the .nfo file, click send to compressed (zipped) folder -> Upload the .zip file here.
Please upload your msinfo32.txt file. To get this: Start Menu -> Type msinfo32 into the Search programs and files box -> When it opens, go to File, Export -> Save as msinfo32.txt and save in a place you will remember -> Let it finish the process of gathering and saving the system info -> Right click the .txt file, click send to compressed (zipped) folder -> Upload the .zip file here.
Network errors:
Code:ffff880`074f17b8 fffff880`016211a7 ndis!NdisFreeNetBufferList+0x87 fffff880`074f17d8 fffff880`03fee110 vwififlt!WPP_GLOBAL_Control fffff880`074f17e8 fffff880`01ee0010 lltdio!_NULL_IMPORT_DESCRIPTOR+0xe54 fffff880`074f1800 fffff880`01f23280 nwifi!Dot11Mem+0x100 fffff880`074f1818 fffff880`01eeb630 nwifi!WPP_SF_dll+0x420 fffff880`074f18e8 fffff880`03c8c092 tcpip!FlReceiveNetBufferListChain+0xb2 fffff880`074f18f0 fffff880`03c8b8f0 tcpip!FlReceiveNetBufferListChainCalloutRoutine fffff880`074f1958 fffff880`01713872 NETIO!NetioDereferenceNetBufferListChain+0x132 fffff880`074f1b00 fffff880`03da39a0 tcpip!Ipv4Global fffff880`074f1b08 fffff880`03c8cfd2 tcpip!IpFlcReceivePackets+0x6e2 fffff880`074f1b20 fffff880`03da39a0 tcpip!Ipv4Global fffff880`074f1c68 fffff880`0143d284 Ntfs!NtfsCommonWrite+0x375c fffff880`074f1c88 fffff800`02cd4530 nt!ExpWorkerThread fffff880`074f1c90 fffff880`04e7f8f9 bcmwl664+0x7f8f9 fffff880`074f1c98 fffff880`04e00000 bcmwl664 fffff880`074f1ca0 fffff880`051f3944 bcmwl664+0x3f3944 fffff880`074f1ca8 fffff880`04e00000 bcmwl664 fffff880`074f1cb0 fffff880`051f3938 bcmwl664+0x3f3938 fffff880`074f1cb8 fffff880`04e00000 bcmwl664 fffff880`074f1cc0 fffff880`051f392c bcmwl664+0x3f392c fffff880`074f1cc8 fffff880`04e00000 bcmwl664 fffff880`074f1cd0 fffff880`051f4d30 bcmwl664+0x3f4d30 fffff880`074f1cd8 fffff880`04e00000 bcmwl664 fffff880`074f1ce0 fffff880`051f4d3c bcmwl664+0x3f4d3c fffff880`074f1ce8 fffff880`04e00000 bcmwl664 fffff880`074f1cf0 fffff880`051f28dc bcmwl664+0x3f28dc fffff880`074f1cf8 fffff880`04e00000 bcmwl664 fffff880`074f1d00 fffff880`051f30ec bcmwl664+0x3f30ec fffff880`074f1d08 fffff800`02c4c000 nt!KiSelectNextThread <PERF> (nt+0x0) fffff880`074f1d10 fffff800`02ee5684 nt!BBTBuffer <PERF> (nt+0x299684) fffff880`074f1d18 fffff800`02c4c000 nt!KiSelectNextThread <PERF> (nt+0x0) fffff880`074f1d20 fffff800`02ed1614 nt!BBTBuffer <PERF> (nt+0x285614) fffff880`074f1d28 fffff800`02c4c000 nt!KiSelectNextThread <PERF> (nt+0x0) fffff880`074f1d30 fffff800`02ee21d4 nt!BBTBuffer <PERF> (nt+0x2961d4) fffff880`074f1d40 fffff880`04e4eed6 bcmwl664+0x4eed6 fffff880`074f1d48 fffff880`04e4eed9 bcmwl664+0x4eed9 fffff880`074f1de8 fffff880`03c8b9ca tcpip!FlReceiveNetBufferListChainCalloutRoutine+0xda fffff880`074f1f18 fffff880`03c8c092 tcpip!FlReceiveNetBufferListChain+0xb2 fffff880`074f1f20 fffff880`03c8b8f0 tcpip!FlReceiveNetBufferListChainCalloutRoutine You can also see NTFS errors along with the network which is often caused by stubborn antivirus apps, one like McAfee.I'd recommend removing McAfee, it is a frequent cause of BSOD-s, consider uninstalling it with the McAfee Removal Tool and replace with Microsoft Security Essentials (To test)Code:Start Menu\Programs\McAfee Public:Start Menu\Programs\McAfee Public
Microsoft Security Essentials.
Recommended from a strict BSOD perspective, compatibility & stability compared to other antiviruses/internet security software. It is free and lightweight:-
WarningDo not start the free trial of Malware Bytes; remember to deselect that option when prompted.
Run a full scan with both (separately) once downloaded, installed and updated.
After that, update the Broadcom 802.11g Network Adapter - Dell Wireless 1390 WLAN Mini-Card to the latest driver version possible.
Here's a method you could follow:
Click on the Start► Control Panel ► Programs ► Uninstall a program ► Uninstall everything related to "Broadcom 802.11g Network Adapter - Dell Wireless 1390 WLAN Mini-Card" and reboot the system. Delete remnants of its drivers/older drivers using Driver Sweeper.
Link to tutorial:
Perform a System File Check:
- Click on the start
- Type CMD on Search
- Left click and Run as Administrator
- Type SFC /scannow
Full tutorial here:
Disk Check on your hard drive for file system errors and bad sectors on it:
Reduce items at start-up. Nothing except anti-virus is required:
You should also clean up some factory bloatware IMO:
BUG CHECK SUMMARY
Code:ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии`` *** WARNING: Unable to verify timestamp for bcmwl664.sys *** ERROR: Module load completed but symbols could not be loaded for bcmwl664.sys ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 1000007E, {ffffffffc0000005, fffff88004e4eed6, fffff880074f2588, fffff880074f1de0} Probably caused by : bcmwl664.sys ( bcmwl664+4eed6 ) Followup: MachineOwner --------- 0: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e) 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. Some common problems are exception code 0x80000003. This means a hard coded breakpoint or assertion was hit, but this system was booted /NODEBUG. This is not supposed to happen as developers should never have hardcoded breakpoints in retail code, but ... If this happens, make sure a debugger gets connected, and the system is booted /DEBUG. This will let us see why this breakpoint is happening. Arguments: Arg1: ffffffffc0000005, The exception code that was not handled Arg2: fffff88004e4eed6, The address that the exception occurred at Arg3: fffff880074f2588, Exception Record Address Arg4: fffff880074f1de0, Context Record Address Debugging Details: ------------------ EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s. FAULTING_IP: bcmwl664+4eed6 fffff880`04e4eed6 410fb744240c movzx eax,word ptr [r12+0Ch] EXCEPTION_RECORD: fffff880074f2588 -- (.exr 0xfffff880074f2588) ExceptionAddress: fffff88004e4eed6 (bcmwl664+0x000000000004eed6) ExceptionCode: c0000005 (Access violation) ExceptionFlags: 00000000 NumberParameters: 2 Parameter[0]: 0000000000000000 Parameter[1]: ffffffffffffffff Attempt to read from address ffffffffffffffff CONTEXT: fffff880074f1de0 -- (.cxr 0xfffff880074f1de0) rax=fffffa80057fc410 rbx=fffffa8005804010 rcx=0000000000015aac rdx=0000000000000002 rsi=fffffa8005805a60 rdi=fffffa8005868f80 rip=fffff88004e4eed6 rsp=fffff880074f27c0 rbp=fffffa8006fca010 r8=fffffa80057fc410 r9=fffff880074f2920 r10=fffff88004e00000 r11=0000000000000004 r12=000600000002ffff r13=0000000000000001 r14=fffffa8005805a60 r15=0000000000000000 iopl=0 nv up ei pl zr na po nc cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010246 bcmwl664+0x4eed6: fffff880`04e4eed6 410fb744240c movzx eax,word ptr [r12+0Ch] ds:002b:00060000`0003000b=???? Resetting default scope CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT PROCESS_NAME: System CURRENT_IRQL: 0 ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s. EXCEPTION_PARAMETER1: 0000000000000000 EXCEPTION_PARAMETER2: ffffffffffffffff READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002efa100 GetUlongFromAddress: unable to read from fffff80002efa1c0 ffffffffffffffff FOLLOWUP_IP: bcmwl664+4eed6 fffff880`04e4eed6 410fb744240c movzx eax,word ptr [r12+0Ch] BUGCHECK_STR: 0x7E LAST_CONTROL_TRANSFER: from fffff880074f27e4 to fffff88004e4eed6 STACK_TEXT: fffff880`074f27c0 fffff880`074f27e4 : fffff880`074f27e8 00000000`00000000 fffffa80`047e4ae0 5362dabd`02533502 : bcmwl664+0x4eed6 fffff880`074f27c8 fffff880`074f27e8 : 00000000`00000000 fffffa80`047e4ae0 5362dabd`02533502 0000006d`3a988033 : 0xfffff880`074f27e4 fffff880`074f27d0 00000000`00000000 : fffffa80`047e4ae0 5362dabd`02533502 0000006d`3a988033 00000000`0000359f : 0xfffff880`074f27e8 SYMBOL_STACK_INDEX: 0 SYMBOL_NAME: bcmwl664+4eed6 FOLLOWUP_NAME: MachineOwner MODULE_NAME: bcmwl664 IMAGE_NAME: bcmwl664.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4c08019d STACK_COMMAND: .cxr 0xfffff880074f1de0 ; kb FAILURE_BUCKET_ID: X64_0x7E_bcmwl664+4eed6 BUCKET_ID: X64_0x7E_bcmwl664+4eed6 Followup: MachineOwner --------- 0: kd> lmvm bcmwl664 start end module name fffff880`04e00000 fffff880`051ff000 bcmwl664 T (no symbols) Loaded symbol image file: bcmwl664.sys Image path: \SystemRoot\system32\DRIVERS\bcmwl664.sys Image name: bcmwl664.sys Timestamp: Fri Jun 04 01:25:17 2010 (4C08019D) CheckSum: 003FB521 ImageSize: 003FF000 Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4 ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Quote