Randomly Getting BSOD's... :(

borgqueenx · 17 Apr 2010

So, i got a MSI GX740 notebook last week, but im getting random BSOD's all over.
i posted here because i seriously need help. this notebook is superb awesome - until it crashes, and that is more then terrible

Im getting these BSOD's while doing normal system operations.
Here are 2 dump logs:

first one:

Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Windows\Minidump\041610-22339-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: *** Invalid ***
****************************************************************************
* Symbol loading may be unreliable without a symbol search path. *
* Use .symfix to have the debugger choose a symbol path. *
* After setting your symbol path, use .reload to refresh symbol locations. *
****************************************************************************
Executable search path is:
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`03810000 PsLoadedModuleList = 0xfffff800`03a4de50
Debug session time: Fri Apr 16 22:59:27.314 2010 (UTC + 2:00)
System Uptime: 0 days 0:25:57.501
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Loading Kernel Symbols
....................................... ........................
....................................... .........................
....................................... ...
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck C2, {7, 1097, 210013, fffffa800418d590}

Unable to load image \SystemRoot\system32\DRIVERS\NETw5s64.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for NETw5s64.sys
*** ERROR: Module load completed but symbols could not be loaded for NETw5s64.sys
***** Kernel symbols are WRONG. Please fix symbols to do analysis.

*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!PVOID ***
*** ***
*************************************************************************
unable to get nt!MmSpecialPoolStart
unable to get nt!MmSpecialPoolEnd
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_POOL_HEADER ***
*** ***
*************************************************************************
unable to get nt!MmPoolCodeStart
unable to get nt!MmPoolCodeEnd
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_POOL_HEADER ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_POOL_TRACKER_BIG_PAGES ***
*** ***
*************************************************************************
Cannot get _POOL_TRACKER_BIG_PAGES type size
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
Probably caused by : NETw5s64.sys ( NETw5s64+e805 )

Followup: MachineOwner

So i googled NETw5s64.sys and found out it had somethign to do with the intel wifi chip. i upgraded the driver this morning, i hope i wont hear errors with NETw5s64.sys again.

second BSOD error log:

Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Windows\Minidump\041710-21684-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: *** Invalid ***
****************************************************************************
* Symbol loading may be unreliable without a symbol search path. *
* Use .symfix to have the debugger choose a symbol path. *
* After setting your symbol path, use .reload to refresh symbol locations. *
****************************************************************************
Executable search path is:
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`03857000 PsLoadedModuleList = 0xfffff800`03a94e50
Debug session time: Sat Apr 17 13:47:21.859 2010 (UTC + 2:00)
System Uptime: 0 days 1:16:40.435
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Loading Kernel Symbols
....................................... ........................
....................................... .........................
....................................... ..
Loading User Symbols
Loading unloaded module list
............
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck C2, {7, 1097, f4cf00c1, fffff88003f2c0d4}

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
Probably caused by : ntoskrnl.exe ( nt+70600 )

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

The blue screen of death in the BSOD above said: BAD_POOL_CALLER.
Here are 2 photos, made with my iphone of the BSOD(i had to make them fast)
Imageshack - img2776q.jpg
Imageshack - img2775o.jpg

Help is greatly, REALLY GREATLY appriciated.

ickymay · 17 Apr 2010

please zip up and attach your .dmp files in a post for further analysis

borgqueenx · 17 Apr 2010

attached all dump files from the beginning i got the notebook.
I dont own this thing for a week yet!

the newest dump file is from 5 minutes ago

windows debugger says the newest BSOD had something to do with NETw5s64.sys again...

****...

here is a photo of the newest BSOD from 5 minutes ago:
http://img413.imageshack.us/img413/1399/img2780y.jpg

Crispy · 17 Apr 2010

Code:

POOL_ADDRESS:  fffffa8009963e00 

FREED_POOL_TAG:  W3Rx

BUGCHECK_STR:  0xc2_7_W3Rx

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  uTorrent.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff800037f760e to fffff800036c5f00

STACK_TEXT:  
fffff880`0b78ff48 fffff800`037f760e : 00000000`000000c2 00000000`00000007 00000000`00001097 00000000`04210005 : nt!KeBugCheckEx
fffff880`0b78ff50 fffff880`016dbad2 : fffffa80`09cf7fb0 fffff880`0584c198 00000000`00000100 fffffa80`09963e20 : nt!ExFreePool+0xccb
fffff880`0b790000 fffff880`059f1d75 : fffff880`059f1cb0 fffffa80`0749ba80 fffffa80`09cf7fe0 fffff880`0584c198 : ndis!NdisFreeNetBufferList+0x112
fffff880`0b790030 fffff880`059f1cb0 : fffffa80`0749ba80 fffffa80`09cf7fe0 fffff880`0584c198 00000000`00000000 : NETw5s64+0x1b6d75
fffff880`0b790038 fffffa80`0749ba80 : fffffa80`09cf7fe0 fffff880`0584c198 00000000`00000000 fffffa80`091ab7b0 : NETw5s64+0x1b6cb0
fffff880`0b790040 fffffa80`09cf7fe0 : fffff880`0584c198 00000000`00000000 fffffa80`091ab7b0 fffffa80`0749ba80 : 0xfffffa80`0749ba80
fffff880`0b790048 fffff880`0584c198 : 00000000`00000000 fffffa80`091ab7b0 fffffa80`0749ba80 fffff880`05849805 : 0xfffffa80`09cf7fe0
fffff880`0b790050 00000000`00000000 : fffffa80`091ab7b0 fffffa80`0749ba80 fffff880`05849805 00000000`00000000 : NETw5s64+0x11198


STACK_COMMAND:  kb

FOLLOWUP_IP: 
NETw5s64+1b6d75
fffff880`059f1d75 ??              ???

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  NETw5s64+1b6d75

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: NETw5s64

IMAGE_NAME:  NETw5s64.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4aafedb7

FAILURE_BUCKET_ID:  X64_0xc2_7_W3Rx_NETw5s64+1b6d75

BUCKET_ID:  X64_0xc2_7_W3Rx_NETw5s64+1b6d75

Followup: MachineOwner

netw5s64.sys indicates that Intel® Wireless WiFi Link Adapter is the cause for the crash. Visit the manufacturer’s (Intel) website and download and install the latest wireless network adapter drivers and check if that fixes the issue.

Code:

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x3B

PROCESS_NAME:  FEAR2SETUP.EXE

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from 0000000000000000 to 0000000000000000

STACK_TEXT:  
fffff880`0bc76ec8 fffff800`0367f469 : 00000000`0000003b 00000000`c0000005 00000000`00000000 fffff880`0bc77790 : nt!KeBugCheckEx
fffff880`0bc76ed0 fffff800`0367edbc : fffff880`0bc77f38 fffff880`0bc77790 00000000`00000000 fffff800`036ae450 : nt!KiBugCheckDispatch+0x69
fffff880`0bc77010 fffff800`036a5bed : fffff800`038a1828 fffff800`037c6814 fffff800`0360e000 fffff880`0bc77f38 : nt!KiSystemServiceHandler+0x7c
fffff880`0bc77050 fffff800`036ad250 : fffff800`037ce1e8 fffff880`0bc770c8 fffff880`0bc77f38 fffff800`0360e000 : nt!RtlpExecuteHandlerForException+0xd
fffff880`0bc77080 fffff800`036ba1b5 : fffff880`0bc77f38 fffff880`0bc77790 fffff880`00000000 00000000`00000000 : nt!RtlDispatchException+0x410
fffff880`0bc77760 fffff800`0367f542 : fffff880`0bc77f38 fffffa80`09c74b30 fffff880`0bc77fe0 00000000`00000000 : nt!KiDispatchException+0x135
fffff880`0bc77e00 fffff800`0367e0ba : 00000000`00000008 fffffa80`09c74b30 fffff880`0bc78000 fffff800`038235f8 : nt!KiExceptionDispatch+0xc2
fffff880`0bc77fe0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x23a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!KiSystemServiceHandler+7c
fffff800`0367edbc b801000000      mov     eax,1

SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  nt!KiSystemServiceHandler+7c

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc600

FAILURE_BUCKET_ID:  X64_0x3B_nt!KiSystemServiceHandler+7c

BUCKET_ID:  X64_0x3B_nt!KiSystemServiceHandler+7c

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

This one is from a corrupt exe file named "FEAR2SETUP.EXE" I would uninstall it and reinstall to see if it fixes it or the ISO you have is corrupt

Code:

FAULTING_IP: 
dxgmms1!DXGFASTMUTEX::`scalar deleting destructor'+b6
fffff880`05180aaa 488bc3          mov     rax,rbx

BUGCHECK_STR:  0xc2_b

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  AssassinsCreed

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff800037bf6b8 to fffff8000368df00

STACK_TEXT:  
fffff880`08d09558 fffff800`037bf6b8 : 00000000`000000c2 00000000`0000000b fffffa80`09e84700 00000000`9c4e46dd : nt!KeBugCheckEx
fffff880`08d09560 fffff880`05180aaa : fffff8a0`0fccbff0 fffffa80`09e85010 fffffa80`08459000 00000000`00000001 : nt!ExFreePool+0xd89
fffff880`08d09610 fffff880`05195c97 : fffff8a0`14df8e50 fffff880`ffffffb2 fffff8a0`6d4d6956 fffff880`00000174 : dxgmms1!DXGFASTMUTEX::`scalar deleting destructor'+0xb6
fffff880`08d09640 fffff880`0517c98f : fffffa80`087d6b00 fffff8a0`12aaa0e0 fffffa80`08459000 00000000`00000000 : dxgmms1!VIDMM_GLOBAL::DestroyOneAllocation+0x2bf
fffff880`08d09720 fffff880`050befb3 : 00000000`00000000 00000000`00000000 fffff8a0`02ab4000 00000000`00000174 : dxgmms1!VidMmDestroyAllocation+0x4f
fffff880`08d09750 00000000`00000000 : 00000000`00000000 fffff8a0`02ab4000 00000000`00000174 7fffffff`00000001 : dxgkrnl+0x37fb3


STACK_COMMAND:  kb

FOLLOWUP_IP: 
dxgmms1!DXGFASTMUTEX::`scalar deleting destructor'+b6
fffff880`05180aaa 488bc3          mov     rax,rbx

SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  dxgmms1!DXGFASTMUTEX::`scalar deleting destructor'+b6

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: dxgmms1

IMAGE_NAME:  dxgmms1.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc578

FAILURE_BUCKET_ID:  X64_0xc2_b_dxgmms1!DXGFASTMUTEX::_scalar_deleting_destructor_+b6

BUCKET_ID:  X64_0xc2_b_dxgmms1!DXGFASTMUTEX::_scalar_deleting_destructor_+b6

Followup: MachineOwner

Make sure your DirectX is up to date here is the link for the latest version: DirectX

As for all the other dumps you might have virus so I would do a virus scan and download and run Ccleaner: CCleaner - Optimization and Cleaning - Free Download

borgqueenx · 17 Apr 2010

Crispy said:

netw5s64.sys indicates that Intel® Wireless WiFi Link Adapter is the cause for the crash. Visit the manufacturer’s (Intel) website and download and install the latest wireless network adapter drivers and check if that fixes the issue.

yeah, like i told in the first post i did.
but it didnt work because i got a BSOD about it 10 minutes ago.

Crispy · 17 Apr 2010

Also try uninstalling utorrent and reinstall and see if that works.

borgqueenx · 17 Apr 2010

Fear2setup? Is that loaded into memory/ram?
Whats the date of the crash with fear2setup?

Il try to reinstall utorrent, installed from original website though.
Directx errors seems strange as well, but il try to update.

I have mccaffee, and it doesnt give me errors or virusses. Il try ccleaner.

Any more info or hints please?

EDIT: i cannot update directx, already got the newest version, according to the version downloaded from your link.
Utorrent removed, i dont want any app thats causing BSOD's.
i wont install a torrent client until the BSOD's are gone.

installed ccleaner, what should i do with it?

Mccaffee is running a full sweep ATM.

EDIT2: assassins creed? wtf seriously? i never got a BSOD while i was playing a game yet.
Is assassins creed still in ram when you quit it? or when windows starts?

Crispy · 17 Apr 2010

Another common cause of blue screens is anti-virus programs but I don't think it is causing it, if you want to try uninstalling your ant-virus and reinstalling a different one.

ickymay · 18 Apr 2010

Crispy said:

Another common cause of blue screens is anti-virus programs but I don't think it is causing it, if you want to try uninstalling your ant-virus and reinstalling a different one.

I think you have likely hit one or both possible causes for the crashes here , and I agree with you the o/p needs to completely unninstall Mcafee using this tool, and replace with MSE and also completely unninstall Utorrent and replace with Bittorent then monitor for crashes

let us know how it goes :)

borgqueenx · 19 Apr 2010

No more bsods:) utorrent was the cause. I did some research about bsods with utorrent, and some people started to have them after version 1.8.
Im now using 1.7 and no bsods anymore. Yay!

Thanks for all the help everyone. I really appriciate it, and hope you can help people who have desame problems as i had.
So remember intel wifi+utorrent 1.8 and above is trouble