Solved BSOD Possibly After Connecting hdmi to TV/Happened While Browsing Net

[omgblank]

I've never had a BSOD before but recently I had two and the only thing that changed recently was that I decided to plug an hdmi between my TV and laptop to play a game. I haven't played any triple AAA games recently and nothing happens right after I play any indie games. I'm inclined to say that it was the cable because my brother got a new computer and he's been getting BSOD's. One of the first things he did was connect his computer to the TV. Maybe there's no connection.

The screen flashed blue and there was a lot of text. My computer restarted too quickly for me to read anything and when it booted up, it said Windows recovered from an unexpected shutdown. I'm scanning using MSE at the moment but I doubt that I will find anything.

Come to think of it, I updated something related to NVIDA recently and I may have stopped the update because I thought it was frozen. I'm not sure if it failed. Checking for new updates doesn't yield anything.

Sorry if this isn't enough information.

 

[Arc]

*** WARNING: Unable to verify timestamp for NETwNs64.sys
*** ERROR: Module load completed but symbols could not be loaded for NETwNs64.sys
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck DEADDEAD, {f000101, 1a700ac, 12a70000, 0}

Probably caused by : NETwNs64.sys ( NETwNs64+1f622b )

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

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

MANUALLY_INITIATED_CRASH1 (deaddead)
The user manually initiated this crash dump.
Arguments:
Arg1: 000000000f000101
Arg2: 0000000001a700ac
Arg3: 0000000012a70000
Arg4: 0000000000000000

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


OVERLAPPED_MODULE: Address regions for 'LMouFilt' and 'LHidFilt.Sys' overlap

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0xDEADDEAD

PROCESS_NAME:  System

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff88004dfb22b to fffff80003a86bc0

STACK_TEXT:  
fffff880`097ee598 fffff880`04dfb22b : 00000000`deaddead 00000000`0f000101 00000000`01a700ac 00000000`12a70000 : nt!KeBugCheckEx
fffff880`097ee5a0 00000000`deaddead : 00000000`0f000101 00000000`01a700ac 00000000`12a70000 00000000`00000000 : NETwNs64+0x1f622b
fffff880`097ee5a8 00000000`0f000101 : 00000000`01a700ac 00000000`12a70000 00000000`00000000 fffff880`04dfad3f : 0xdeaddead
fffff880`097ee5b0 00000000`01a700ac : 00000000`12a70000 00000000`00000000 fffff880`04dfad3f fffffa80`0e5398b0 : 0xf000101
fffff880`097ee5b8 00000000`12a70000 : 00000000`00000000 fffff880`04dfad3f fffffa80`0e5398b0 fffff880`056b8a80 : 0x1a700ac
fffff880`097ee5c0 00000000`00000000 : fffff880`04dfad3f fffffa80`0e5398b0 fffff880`056b8a80 00000000`00000cba : 0x12a70000


STACK_COMMAND:  kb

FOLLOWUP_IP: 
NETwNs64+1f622b
fffff880`04dfb22b ??              ???

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  NETwNs64+1f622b

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: NETwNs64

IMAGE_NAME:  NETwNs64.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4f0ab707

FAILURE_BUCKET_ID:  X64_0xDEADDEAD_NETwNs64+1f622b

BUCKET_ID:  X64_0xDEADDEAD_NETwNs64+1f622b

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

1: kd> lmvm NETwNs64
start             end                 module name
fffff880`04c05000 fffff880`0573b000   NETwNs64 T (no symbols)           
    Loaded symbol image file: NETwNs64.sys
    Image path: \SystemRoot\system32\DRIVERS\NETwNs64.sys
    Image name: NETwNs64.sys
    Timestamp:        Mon Jan 09 15:14:39 2012 (4F0AB707)
    CheckSum:         00AF00B8
    ImageSize:        00B36000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

The BSOD is caused by intel WiFi driver. It needs update.

If you want us to assist you in searching the driver, upload your MSINFO32.nfo file.

1. Click on the start button
2. Type "msinfo32" (without quotes) in the search bar of the start menu, click the resulting link. It will open the System Information window.
3. File>Save. In the "File Name" filed, put "MSINFO32" (without Quote), give the save location to desktop, and click the "save" button.
4. Give the time for processing, it will save a .nfo file on your desktop.
5. Zip it, and upload it following the instruction.

 

[omgblank]

Thanks, I went to the Intel website and there was a a detection tool for wireless drivers.

 

[Arc]

Good news
Let us know for any further issue.