BSOD while watching youtube.

[boredomez]

So the most recent bsod i had was when i was watching youtube, but I forgot to note down the error.

Before this, i had many different bsods and so I formatted my laptop, ran chkdsk and SFC, where the sfc found corrupted files but unable to fix them. I also ran Windows Defender Offline which found no malware, and also antiviruses which found no viruses. After the formatting, many of the bsods didn't appear anymore other than the youtube eror.

I also did a boot-log recently and showed some files which failed to load, as attached just in case.

Edit : My laptop also restarted suddenly (no bluescreens just sudden restart) while playing Dota2, happened a few mins ago.

 

[Arc]

Hello boredomez.

It is crashed by Trend Micro Internet Security.

fffff880`0a2708d0  fffff880`097f3a38Unable to load image \SystemRoot\system32\DRIVERS\tmevtmgr.sys, Win32 error 0n2
[COLOR=Red]*** WARNING: Unable to verify timestamp for tmevtmgr.sys
*** ERROR: Module load completed but symbols could not be loaded for tmevtmgr.sys
 tmevtmgr+0xea38[/COLOR]

Description here: Driver Reference Table - tmevtmgr.sys

fffff880`0a270858  fffff880`097c2bceUnable to load image \SystemRoot\system32\DRIVERS\tmcomm.sys, Win32 error 0n2
[COLOR=Red]*** WARNING: Unable to verify timestamp for tmcomm.sys
*** ERROR: Module load completed but symbols could not be loaded for tmcomm.sys
 tmcomm+0x4bce[/COLOR]

Description here: Driver Reference Table - tmcomm.sys

fffff880`0a270808  fffff880`09678bc3Unable to load image \SystemRoot\system32\DRIVERS\tmactmon.sys, Win32 error 0n2
[COLOR=Red]*** WARNING: Unable to verify timestamp for tmactmon.sys
*** ERROR: Module load completed but symbols could not be loaded for tmactmon.sys
 tmactmon+0x6bc3[/COLOR]

Description here: Driver Reference Table - tmactmon.sys

Uninstall Trend Micro.
Use Microsoft Security Essentials as your antivirus with windows inbuilt firewall, and free MBAM as the on demand scanner.

Download and install those, and then run full system scans with both of them, one by one.

Also, get rid of intel rapid storage.

1. Right click on "my computer" icon and click "manage" on the context menu.
2. It will open the "computer management" window.
3. Select "Device Manager" in the left pane, It will list all the existing devices up.
4. Expand "Disc Drives" by clicking on the triangle in front of it.
5. Select one item under it, right click, uninstall.
6. Continue the process for all items under "Disc Drives"
7. Now restart the computer. At restart, windows will auto configure the appropriate system driver, msahci.sys.

Let us know the results.

 

[boredomez]

Thanks Arc, did what youu said although I only had one driver to uninstall :O. Anyway will post if I encounter any more BSOD or sudden-restarts ^^

 

[boredomez]

It didn't work . I had a flash of bluescreen while watching youtube, follow by another while restarting up, it was too fast so I couldnt see whether any dump-files was recorded or what the error was.

 

[boredomez]

Sorry for multi-posting, didn't know how to attach files while editting older posts x.x

More BSODs at starting up, not sure if there were any new dump files created, but attaching the most recent just in case.

 

[Arc]

Intel(R) Wireless WiFi Link 5000 Series Adapter Driver for Windows 7

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

Use !analyze -v to get detailed debugging information.

BugCheck D1, {8e60cb34, 2, 1, fffff8800580e0cd}

Unable to load image NETwNs64.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for NETwNs64.sys
*** ERROR: Module load completed but symbols could not be loaded for NETwNs64.sys
[COLOR=Red]Probably caused by : NETwNs64.sys[/COLOR] ( NETwNs64+70cd )

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

Which is somehow old.

lmvm NETwNs64
start             end                 module name
fffff880`05807000 fffff880`0608d000   NETwNs64 T (no symbols)           
    Loaded symbol image file: NETwNs64.sys
    Image path: NETwNs64.sys
   [COLOR=Red] Image name: NETwNs64.sys
    Timestamp:        Thu Aug 04 05:58:26 2011[/COLOR] (4E39E7AA)
    CheckSum:         0083C028
    ImageSize:        00886000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Update it from Intel Download Center.

 

[boredomez]

Thanks Arc, updated three drivers/software, will post if I encounter anymore BSODs or sudden-restarts ^^

 

[boredomez]

So there were no BSODs for awhile, but I encountered one after alt-tabbing from a game,but was a flash of bluescreen so not sure whether any dump files was saved, uploading the most recent just in case.
Also, I think the BSOD was an DRIVER_IRQL_NOT_LESS_OR_EQUAL

 

[Arc]

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

Use !analyze -v to get detailed debugging information.

BugCheck D1, {a8, 2, 0, fffff880059061c3}

Unable to load image Netwsw00.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for Netwsw00.sys
*** ERROR: Module load completed but symbols could not be loaded for Netwsw00.sys
Probably caused by : Netwsw00.sys ( Netwsw00+e51c3 )

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

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

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: 00000000000000a8, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff880059061c3, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80003cc4100
 00000000000000a8 

CURRENT_IRQL:  2

FAULTING_IP: 
Netwsw00+e51c3
fffff880`059061c3 0fb64166        movzx   eax,byte ptr [rcx+66h]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xD1

PROCESS_NAME:  SuperStarLive.

TRAP_FRAME:  fffff80000ba1ee0 -- (.trap 0xfffff80000ba1ee0)
Unable to read trap frame at fffff800`00ba1ee0

LAST_CONTROL_TRANSFER:  from fffff80003a94569 to fffff80003a94fc0

STACK_TEXT:  
fffff800`00ba1d98 fffff800`03a94569 : 00000000`0000000a 00000000`000000a8 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff800`00ba1da0 fffff800`03a931e0 : fffffa80`0a2f0cf0 fffff880`0584a906 fffff880`05c2df00 00000000`0000c20a : nt!KiBugCheckDispatch+0x69
fffff800`00ba1ee0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x260


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
Netwsw00+e51c3
fffff880`059061c3 0fb64166        movzx   eax,byte ptr [rcx+66h]

SYMBOL_NAME:  Netwsw00+e51c3

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: Netwsw00

IMAGE_NAME:  Netwsw00.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  50688e44

FAILURE_BUCKET_ID:  X64_0xD1_Netwsw00+e51c3

BUCKET_ID:  X64_0xD1_Netwsw00+e51c3

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

0: kd> lmvm Netwsw00
start             end                 module name
fffff880`05821000 fffff880`06371000   Netwsw00 T (no symbols)           
    Loaded symbol image file: Netwsw00.sys
    Image path: Netwsw00.sys
    Image name: Netwsw00.sys
    Timestamp:        Sun Sep 30 23:54:04 2012 (50688E44)
    CheckSum:         00B02BC1
    ImageSize:        00B50000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
0: kd> !thread

The latest Intel® Wireless WiFi Link Adapter driver is also in problem. In such a situation, I think I should consult with some other more knowledgeable persons. Please give some time.

You should stop hardware acceleration in your browser too.

 

[boredomez]

Okayys :3

 

[boredomez]

Had multiple different BSODs, SF file attached .__.

 

[Arc]

As I am seeing, it is a bloatware caused issue.

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

Use !analyze -v to get detailed debugging information.

BugCheck A, {34efa, 2, 1, fffff80003ad7066}

Unable to load image assd.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for assd.sys
*** ERROR: Module load completed but symbols could not be loaded for assd.sys
[COLOR=Red]Probably caused by : assd.sys[/COLOR] ( assd+2667 )

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

Description here: Driver Reference Table - assd.sys.

Again, another one....

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


[B][COLOR=Red]OVERLAPPED_MODULE: Address regions for 'ASMMAP64' and 'WinUsb.sys' overlap[/COLOR][/B]

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

FAULTING_IP: 
nt!CmpDereferenceNameControlBlockWithLock+22
fffff800`03d73072 448b06          mov     r8d,dword ptr [rsi]

EXCEPTION_RECORD:  fffff880033af848 -- (.exr 0xfffff880033af848)
ExceptionAddress: fffff80003d73072 (nt!CmpDereferenceNameControlBlockWithLock+0x0000000000000022)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

Description here: Driver Reference Table - ASMMAP64.sys

All those are causing the problems there.

I would suggest you follow the guide http://www.sevenforums.com/tutorials/219576-clean-up-factory-bloatware.html with a special reference to point #13.

13. Consider a Clean Reinstall - Factory OEM Windows 7 which is often better than getting a new computer considering how pre-installed bloatware can corrupt Windows 7 even if it's completely cleaned up.

Have a try.

 

[boredomez]

Okays done and also did a chkdsk repair since there was a registry error, but will post if any more BSODs showed up ^^. Thanks Arc

 

[Arc]

Good news.

Now observe it, see how it works. For any further issues, let us know.

 

[boredomez]

So its was fine for quite a long time, until is BSOD with CACHE_MANAGER and an error-less bsod at recover-bootup which happened while i was installing a game.

 

[boredomez]

More BSODs popping up while playing games x.x

 

[Arc]

Four crash dumps, four different causes.

Display driver.

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

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffff880808df064, 8, fffff880808df064, 5}

Unable to load image \SystemRoot\system32\DRIVERS\igdkmd64.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for igdkmd64.sys
*** ERROR: Module load completed but symbols could not be loaded for igdkmd64.sys

Could not read faulting driver name
[COLOR=Red]Probably caused by : igdkmd64.sys [/COLOR]( igdkmd64+8904e )

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

I'd suggest you to uninstall the existing display driver, using |MG| Driver Fusion (Driver Sweeper) 1.2.0 Download. Then download it again from Intel Download Center, preferable a release earlier than that of 27th September, that is you using.

File System.

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

Use !analyze -v to get detailed debugging information.

BugCheck 24, {1904fb, fffff8800a623f48, fffff8800a6237a0, fffff8800125d146}

[COLOR=Red]Probably caused by : Ntfs.sys[/COLOR] ( Ntfs!NtfsMultipleAsync+26 )

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

1. Update your SSD's Firmware (Skip it, if it is not a SSD)
2. Re-seat the sata and power.
3. Run chkdsk /f/r, following the option two of the tutorial Disk Check
4. Seatool for dos: SeaTools | Seagate download
   Burn it in a blank cd. boot from the CD, click on "Accept", wait for it to finish detecting the drives, then in the upper left corner select "Basic Tests", then select "Long Test" and let it run.

Memory Corruption.

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

Use !analyze -v to get detailed debugging information.

BugCheck 34, {50853, fffff8800338c518, fffff8800338bd70, fffff80002b4ca7c}

[COLOR=Red]Probably caused by : memory_corruption[/COLOR] ( nt!MiRemoveLowestPriorityStandbyPage+1bc )

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

Again, with a different bugcheck

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

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffffc0000005, fffff80002a9895e, fffff8800330f758, fffff8800330efb0}

[COLOR=Red]Probably caused by : memory_corruption[/COLOR] ( nt!MiUnlinkPageFromLockedList+36e )

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

Test your RAM modules for possible errors.
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 passes, preferably overnight, per RAM module per slot.

Moreover, you should do two more things .....

Scan the system for possible virus infection.

• Anti-rootkit utility TDSSKiller
• Windows Defender Offline

Stress test the CPU.
Hardware - Stress Test With Prime95

Let us know the results.

 

[boredomez]

So, chkdsk fixed an error. SeaTools, memtest86+, anti-rootkit, Windows defender offline, microsoft security essentials, anti malwarebyte and Prime95 all gave no errors. Im not sure memtest86+ did 8 passes since I ran it for 6 to 7 hours and I only had 1 ram module to test.

 

[Arc]

Good! Very good news. Let us know how the computer is performing now.

 

[boredomez]

Multiple BSODs still happening x.x