Webcam/Microphone BSOD

[zisforz]

Hello All,

I have a Dell XPS 16 with Windows 7 64-bit. It's been running fine lately, but after a major MS update, anytime I enable my built-in webcam and microphone the PC freezes. Nothing is operational just frozen. Every now and then I'll get a BSOD but as of lately it just locks up my entire laptop.

Anyone else experience this with the same system?

 

[zigzag3143]

Hello All,

I have a Dell XPS 16 with Windows 7 64-bit. It's been running fine lately, but after a major MS update, anytime I enable my built-in webcam and microphone the PC freezes. Nothing is operational just frozen. Every now and then I'll get a BSOD but as of lately it just locks up my entire laptop.

Anyone else experience this with the same system?

To enable us to assist you with your computer's BSOD symptoms, upload the contents of your "\Windows\Minidump" folder.

The procedure:

* Copy the contents of \Windows\Minidump to another (temporary) location somewhere on your machine.
* Zip up the copy.
* Attach the ZIP archive to your post using the "paperclip" (file attachments) button.



To ensure minidumps are enabled:

Go to Start, in the Search Box type: sysdm.cpl, press Enter.
Under the Advanced tab, click on the Startup and Recovery Settings... button.
Ensure that Automatically restart is unchecked.
Under the Write Debugging Information header select Small memory dump (256 kB) in the dropdown box (the 256kb varies).
Ensure that the Small Dump Directory is listed as %systemroot%\Minidump.
OK your way out.
Reboot if changes have been made.

 

[zisforz]

Attached

 

[zigzag3143]

Attached

Three problems


1-your Macaffee. Remove and replace with Microsoft security essentials

How to uninstall or reinstall supported McAfee consumer products using the McAfee Consumer Products Removal tool (MCPR.exe)

http://www.microsoft.com/security_essentials/




2- your network driver (netw5v64.sys) Re-install it with newest version.

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\K\Desktop\110110-88062-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\Symbols*http://msdl.microsoft.com/download/symbols;srv*e:\symbols
*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`0325a000 PsLoadedModuleList = 0xfffff800`03497e50
Debug session time: Mon Nov  1 19:12:30.012 2010 (GMT-4)
System Uptime: 4 days 23:47:24.459
Loading Kernel Symbols
...............................................................
................................................................
...........................................................
Loading User Symbols
Loading unloaded module list
..................................................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {64, 2, 0, fffff88004727bbe}

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

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

1: 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: 0000000000000064, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff88004727bbe, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800035020e0
 0000000000000064 

CURRENT_IRQL:  2

FAULTING_IP: 
netw5v64+aabbe
fffff880`04727bbe 807f6400        cmp     byte ptr [rdi+64h],0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xD1

PROCESS_NAME:  FAService.exe

TRAP_FRAME:  fffff88002d21fe0 -- (.trap 0xfffff88002d21fe0)
Unable to read trap frame at fffff880`02d21fe0

LAST_CONTROL_TRANSFER:  from fffff800032c9ca9 to fffff800032ca740

STACK_TEXT:  
fffff880`02d21e98 fffff800`032c9ca9 : 00000000`0000000a 00000000`00000064 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`02d21ea0 fffff800`032c8920 : fffffa80`0531e000 fffffa80`06563430 00000000`40030003 fffffa80`052cc010 : nt!KiBugCheckDispatch+0x69
fffff880`02d21fe0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x260


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
netw5v64+aabbe
fffff880`04727bbe 807f6400        cmp     byte ptr [rdi+64h],0

SYMBOL_NAME:  netw5v64+aabbe

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: netw5v64

IMAGE_NAME:  netw5v64.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  49cbab84

FAILURE_BUCKET_ID:  X64_0xD1_netw5v64+aabbe

BUCKET_ID:  X64_0xD1_netw5v64+aabbe

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

3- Old drivers

rimmpx64.sys    11/17/2006 09:49:50 PM    fffff880`04bfe000    0x00013000    0x455e66be    fffff880`04beb000                            
rixdpx64.sys    11/18/2006 12:07:46 AM    fffff300`04ee3000    0xfffffa8000057000    0x455e8712    fffff880`04e8c000                            
PxHlpa64.sys    10/17/2007 02:25:02 PM    fffff880`01187700    0x0000b700    0x4716537e    fffff880`0117c000                            
k57nd60a.sys    2/24/2008 05:40:03 AM    fffff300`0463f000    0xfffffa800003f000    0x47c13b73    fffff880`04600000                            
OA001Ufd.sys    6/3/2008 05:30:37 AM    fffff880`0915d3a0    0x000293a0    0x48450f3d    fffff880`09134000                            
atikmdag.sys    7/3/2008 11:53:28 PM    fffff880`042dc000    0x00652000    0x486d9eb8    fffff880`03c8a000                            
stwrt64.sys    7/18/2008 03:54:08 PM    fffff880`08f5c000    0x00074000    0x4880f4e0    fffff880`08ee8000                            
OA001Vid.sys    9/19/2008 05:30:16 AM    fffff880`091331c0    0x0004d1c0    0x48d37128    fffff880`090e6000                            
facap.sys    9/24/2008 10:34:31 PM    002ff8f4`093f4000    0x0030007400039000    0x48daf8b7    fffff880`093bb000                            
SynTP.sys    9/25/2008 10:00:10 PM    fffff880`04fbd000    0x00046000    0x48dc422a    fffff880`04f77000                            
000.fcl    9/26/2008 09:11:22 AM    fffff300`023eb000    0xfffffa800002b000    0x48dcdf7a    fffff880`023c0000                            
RimSerial_AMD64.sys    11/24/2008 01:01:01 PM    644d65f3`05551c00    0x644d6d7300007c00    0x492addcd    fffff880`0554a000                            
itecir.sys    3/9/2009 04:58:47 AM    fffff880`04f3f000    0x0005c000    0x49b4da47    fffff880`04ee3000                            
netw5v64.sys    3/26/2009 12:21:24 PM    002ff8f4`04bb8000    0x003000740053b000    0x49cbab84    fffff880`0467d000                            
spldr.sys    5/11/2009 12:56:27 PM    fffff880`01454000    0x00008000    0x4a0858bb    fffff880`0144c000                            
GEARAspiWDM.sys    5/18/2009 08:17:04 AM    fffff880`04fdb000    0x0000d000    0x4a1151c0    fffff880`04fce000                            
amdxata.sys    5/19/2009 01:56:59 PM    fffff880`00df4000    0x0000b000    0x4a12f2eb    fffff880`00de9000                            
rimspx64.sys    6/25/2009 03:13:43 AM    fffff300`043e7000    0xfffffa8000017000    0x4a4323a7    fffff880`043d0000

How To Find Drivers:

- search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
- if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.

- - The most common drivers are listed on this page: Driver Reference Driver Reference
- - Driver manufacturer links are on this page: Drivers and Downloads