Random BSODs-Out of the Blue

Hi caerroil; welcome to the forum. I will take a look and see what I can find.

Error code 1E (2X), KMODE_EXCEPTION_NOT_HANDLED. Usual causes: Device driver, hardware, System service, compatibility, Remote control programs, memory, BIOS.

Error code 3B, SYSTEM_SERVICE_EXCEPTION. Usual causes: System service, Device driver, graphics driver, ?memory.

Two of the three dumps indicate memory corruption.

Code:

Kernel base = 0xfffff800`02e4a000 PsLoadedModuleList = 0xfffff800`03087e50
Debug session time: Mon Oct 18 09:42:39.479 2010 (GMT-4)
System Uptime: 0 days 0:24:32.242
Loading Kernel Symbols
...............................................................
................................................................
..................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1E, {0, 0, 0, 0}

Probably caused by : USBPORT.SYS ( USBPORT!USBPORT_Core_iCompleteDoneTransfer+45f )

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

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

KMODE_EXCEPTION_NOT_HANDLED (1e)
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.
Arguments:
Arg1: 0000000000000000, The exception code that was not handled
Arg2: 0000000000000000, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception

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


EXCEPTION_CODE: (Win32) 0 (0) - The operation completed successfully.

FAULTING_IP: 
+529b952f00d2dde8
00000000`00000000 ??              ???

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  0000000000000000

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x1E

PROCESS_NAME:  System

CURRENT_IRQL:  2

EXCEPTION_RECORD:  fffff88002ffb888 -- (.exr 0xfffff88002ffb888)
ExceptionAddress: fffff80002e0579c (hal!HalPutScatterGatherList+0x000000000000004c)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

TRAP_FRAME:  fffff88002ffb930 -- (.trap 0xfffff88002ffb930)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffa80042ea360 rbx=0000000000000000 rcx=fffffa800528b520
rdx=fffffa80042ea360 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002e0579c rsp=fffff88002ffbac0 rbp=fffffa800510e630
 r8=0000000000000000  r9=0000000000000002 r10=00000000ffffffff
r11=0000000000000002 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz ac pe nc
hal!HalPutScatterGatherList+0x4c:
fffff800`02e0579c 8b772c          mov     esi,dword ptr [rdi+2Ch] ds:0013:00000000`0000002c=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002eb246e to fffff80002eba710

STACK_TEXT:  
fffff880`02ffa978 fffff800`02eb246e : fffffa80`0457e898 00000000`00000000 fffff880`02ffb0f0 fffff800`02ee7668 : nt!KeBugCheck
fffff880`02ffa980 fffff800`02ee040d : fffff800`030c8b7c fffff800`03002e84 fffff800`02e4a000 fffff880`02ffb888 : nt!KiKernelCalloutExceptionHandler+0xe
fffff880`02ffa9b0 fffff800`02ee7a90 : fffff800`03009b14 fffff880`02ffaa28 fffff880`02ffb888 fffff800`02e4a000 : nt!RtlpExecuteHandlerForException+0xd
fffff880`02ffa9e0 fffff800`02ef49ef : fffff880`02ffb888 fffff880`02ffb0f0 fffff880`00000000 ff7ffa80`06aacc20 : nt!RtlDispatchException+0x410
fffff880`02ffb0c0 fffff800`02eb9d82 : fffff880`02ffb888 fffffa80`042ea330 fffff880`02ffb930 fffffa80`04a51050 : nt!KiDispatchException+0x16f
fffff880`02ffb750 fffff800`02eb868a : fffffa80`056a09f0 fffff880`048a7638 00000000`00000000 fffffa80`056a09f0 : nt!KiExceptionDispatch+0xc2
fffff880`02ffb930 fffff800`02e0579c : fffffa80`04a511a0 00000000`000003d8 00000000`00000000 fffffa80`05649c30 : nt!KiGeneralProtectionFault+0x10a
fffff880`02ffbac0 fffff880`03f9b023 : fffffa80`04a511a0 fffffa80`03dcfa20 fffffa80`04a51050 fffffa80`04a511a0 : hal!HalPutScatterGatherList+0x4c
fffff880`02ffbb20 fffff880`03f9bab7 : fffffa80`03dcf602 fffffa80`03dbc500 00000000`ffffffff fffffa80`04a51ea8 : USBPORT!USBPORT_Core_iCompleteDoneTransfer+0x45f
fffff880`02ffbc00 fffff880`03f9964f : fffffa80`04a51ea8 fffffa80`04a511a0 fffffa80`04a52040 00000000`00000000 : USBPORT!USBPORT_Core_iIrpCsqCompleteDoneTransfer+0x3a7
fffff880`02ffbc60 fffff880`03f8af89 : fffffa80`04a51050 00000000`00000000 fffffa80`04a51e02 fffffa80`04a51ea8 : USBPORT!USBPORT_Core_UsbIocDpc_Worker+0xf3
fffff880`02ffbca0 fffff800`02ec5bfc : fffff880`02fd3180 fffffa80`04a51ea8 fffffa80`04a51ec0 00000000`00000000 : USBPORT!USBPORT_Xdpc_Worker+0x1d9
fffff880`02ffbcd0 fffff800`02ec2eea : fffff880`02fd3180 fffff880`02fddfc0 00000000`00000000 fffff880`03f8adb0 : nt!KiRetireDpcList+0x1bc
fffff880`02ffbd80 00000000`00000000 : fffff880`02ffc000 fffff880`02ff6000 fffff880`02ffbd40 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
USBPORT!USBPORT_Core_iCompleteDoneTransfer+45f
fffff880`03f9b023 4533c0          xor     r8d,r8d

SYMBOL_STACK_INDEX:  8

SYMBOL_NAME:  USBPORT!USBPORT_Core_iCompleteDoneTransfer+45f

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: USBPORT

IMAGE_NAME:  USBPORT.SYS

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bcc07

FAILURE_BUCKET_ID:  X64_0x1E_USBPORT!USBPORT_Core_iCompleteDoneTransfer+45f

BUCKET_ID:  X64_0x1E_USBPORT!USBPORT_Core_iCompleteDoneTransfer+45f

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

Kernel base = 0xfffff800`02e06000 PsLoadedModuleList = 0xfffff800`03043e50
Debug session time: Sun Oct 17 19:22:47.017 2010 (GMT-4)
System Uptime: 0 days 5:04:54.407
Loading Kernel Symbols
...............................................................
................................................................
..................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1E, {0, 0, 0, 0}

Probably caused by : ntkrnlmp.exe ( nt!KiKernelCalloutExceptionHandler+e )

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

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

KMODE_EXCEPTION_NOT_HANDLED (1e)
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.
Arguments:
Arg1: 0000000000000000, The exception code that was not handled
Arg2: 0000000000000000, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception

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


EXCEPTION_CODE: (Win32) 0 (0) - The operation completed successfully.

FAULTING_IP: 
+529b952f00cddce4
00000000`00000000 ??              ???

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  0000000000000000

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x1E

PROCESS_NAME:  System

CURRENT_IRQL:  2

EXCEPTION_RECORD:  fffff800043aa2a8 -- (.exr 0xfffff800043aa2a8)
ExceptionAddress: fffffa8005e5e2c3
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

TRAP_FRAME:  fffff800043aa350 -- (.trap 0xfffff800043aa350)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ff7ffa800412f388 rbx=0000000000000000 rcx=fffffa8004b4c4e8
rdx=fffffa800692a858 rsi=0000000000000000 rdi=0000000000000000
rip=fffffa8005e5e2c3 rsp=fffff800043aa4e0 rbp=fffffa8005e927b8
 r8=0000000001172679  r9=0000000001cb6e52 r10=fffff800043aa4e8
r11=0000002a984ee126 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
fffffa80`05e5e2c3 ??              ???
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002e6e46e to fffff80002e76710

STACK_TEXT:  
fffff800`043a9398 fffff800`02e6e46e : 00000000`00000000 fffff800`043a9900 fffff800`043a9b10 fffff800`02ea3668 : nt!KeBugCheck
fffff800`043a93a0 fffff800`02e9c40d : fffff800`03084b7c fffff800`02fbee84 fffff800`02e06000 fffff800`043aa2a8 : nt!KiKernelCalloutExceptionHandler+0xe
fffff800`043a93d0 fffff800`02ea3a90 : fffff800`02fc5b14 fffff800`043a9448 fffff800`043aa2a8 fffff800`02e06000 : nt!RtlpExecuteHandlerForException+0xd
fffff800`043a9400 fffff800`02eb09ef : fffff800`043aa2a8 fffff800`043a9b10 fffff800`00000000 fffffa80`04b4c4e8 : nt!RtlDispatchException+0x410
fffff800`043a9ae0 fffff800`02e75d82 : fffff800`043aa2a8 ff7ffa80`0412f388 fffff800`043aa350 00000000`01172679 : nt!KiDispatchException+0x16f
fffff800`043aa170 fffff800`02e7468a : fffffa80`05135010 fffffa80`04e179b0 00000000`0000000e fffffa80`04e17fe6 : nt!KiExceptionDispatch+0xc2
fffff800`043aa350 fffffa80`05e5e2c3 : 00000000`000003e8 fffff800`043aa540 fffff800`043aa508 00000000`01cb6e52 : nt!KiGeneralProtectionFault+0x10a
fffff800`043aa4e0 00000000`000003e8 : fffff800`043aa540 fffff800`043aa508 00000000`01cb6e52 fffffa80`05e927b8 : 0xfffffa80`05e5e2c3
fffff800`043aa4e8 fffff800`043aa540 : fffff800`043aa508 00000000`01cb6e52 fffffa80`05e927b8 00000000`00000000 : 0x3e8
fffff800`043aa4f0 fffff800`043aa508 : 00000000`01cb6e52 fffffa80`05e927b8 00000000`00000000 fffffa80`04b4c538 : 0xfffff800`043aa540
fffff800`043aa4f8 00000000`01cb6e52 : fffffa80`05e927b8 00000000`00000000 fffffa80`04b4c538 00000000`00000002 : 0xfffff800`043aa508
fffff800`043aa500 fffffa80`05e927b8 : 00000000`00000000 fffffa80`04b4c538 00000000`00000002 00000000`00000001 : 0x1cb6e52
fffff800`043aa508 00000000`00000000 : fffffa80`04b4c538 00000000`00000002 00000000`00000001 fffffa80`04b4c538 : 0xfffffa80`05e927b8


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!KiKernelCalloutExceptionHandler+e
fffff800`02e6e46e 90              nop

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!KiKernelCalloutExceptionHandler+e

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4c1c44a9

FAILURE_BUCKET_ID:  X64_0x1E_nt!KiKernelCalloutExceptionHandler+e

BUCKET_ID:  X64_0x1E_nt!KiKernelCalloutExceptionHandler+e

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

Kernel base = 0xfffff800`02c4a000 PsLoadedModuleList = 0xfffff800`02e87e50
Debug session time: Thu Oct 14 08:16:31.399 2010 (GMT-4)
System Uptime: 0 days 2:10:28.162
Loading Kernel Symbols
...............................................................
................................................................
..................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff880040dfca0, fffff880055029a0, 0}

Probably caused by : dxgkrnl.sys ( dxgkrnl!DXGCONTEXT::Render+25c )

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

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

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff880040dfca0, Address of the exception record for the exception that caused the bugcheck
Arg3: fffff880055029a0, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

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


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

FAULTING_IP: 
dxgkrnl!DXGCONTEXT::Render+25c
fffff880`040dfca0 41ff90c0010000  call    qword ptr [r8+1C0h]

CONTEXT:  fffff880055029a0 -- (.cxr 0xfffff880055029a0)
rax=fffffa8004671c10 rbx=0000000000000200 rcx=fffffa8006176500
rdx=fffff880055033d0 rsi=0000000000000000 rdi=fffff8a00257d900
rip=fffff880040dfca0 rsp=fffff88005503370 rbp=fffff88005503a40
 r8=ff7ff880041758d0  r9=0000000000000000 r10=0000000000000021
r11=fffff8a0022c0000 r12=0000000000000002 r13=0000000000000001
r14=ffffffffc000000d r15=0000000000000001
iopl=0         nv up ei ng nz na po cy
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010287
dxgkrnl!DXGCONTEXT::Render+0x25c:
fffff880`040dfca0 41ff90c0010000  call    qword ptr [r8+1C0h] ds:002b:ff7ff880`04175a90=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x3B

PROCESS_NAME:  dwm.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff880040dfca0

STACK_TEXT:  
fffff880`05503370 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : dxgkrnl!DXGCONTEXT::Render+0x25c


FOLLOWUP_IP: 
dxgkrnl!DXGCONTEXT::Render+25c
fffff880`040dfca0 41ff90c0010000  call    qword ptr [r8+1C0h]

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  dxgkrnl!DXGCONTEXT::Render+25c

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: dxgkrnl

IMAGE_NAME:  dxgkrnl.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4ac5509e

STACK_COMMAND:  .cxr 0xfffff880055029a0 ; kb

FAILURE_BUCKET_ID:  X64_0x3B_dxgkrnl!DXGCONTEXT::Render+25c

BUCKET_ID:  X64_0x3B_dxgkrnl!DXGCONTEXT::Render+25c

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

To begin your troubleshooting, I suggest you uninstall Eset NOD32 using this uninstall tool: Tool. Eset has been known to cause BSOD's on some Win 7 systems. Plus your version of Eset is old and the drivers are not up to date for Win 7. After you get your system stable you can try an updated version; but I do not recommend doing so. Download and install Microsoft Security Essentials in its place. Make sure Windows firewall is turned on.

I find some obsolete drivers on your system. Older drivers can and do cause memory corruption and crashes. Update these drivers, especailly those in red font.

CAX_CNXT.sys Tue Jun 30 15:59:52 2009 - Conexant Modem Conexant: Support

CAX_DPV.sys Tue Jun 30 16:05:11 2009 -Conexant Modem Conexant: Support

CAXHWBS2.sys Tue Jun 30 16:01:38 2009 - Conexant Modem Conexant: Support

eamon.sys Fri Feb 06 08:14:25 2009 - Eset NOD32

ehdrv.sys Fri Feb 06 08:15:07 2009 - ESET Smart Security

epfw.sys Fri Feb 06 08:07:05 2009 - EPFW Filter Driver, a part of ESET NOD32

Epfwndis.sys Fri Feb 06 08:07:01 2009 - ESET Personal Firewall NDIS filter

epfwwfp.sys Fri Feb 06 08:07:04 2009 - ESET Smart Security

pcouffin.sys Tue Dec 05 09:39:30 2006 - low level access layer for CD devices (A part of many different CD/DVD burning programs) http://www.vso-software.fr
or
rename to pcouffin.BAK and see what CD/DVD program it breaks.

RtHDMIVX.sys Wed Jun 24 06:23:22 2009 - Realtek Semiconductor Corp. High Definition Audio System, Realtek

usbVM303.sys Sun Mar 25 00:26:25 2007 - This driver appears to have played a role in one of your crashes. Video streaming and Capture Device Driver is from Vimicro Corporation. Uninstall this software and upgrade to software certified compatible with Win 7.

vvftav303.sys Sun Mar 18 04:43:28 2007 - Vimicro capture driver from Vimicro Corporation. Uninstall this software.

XAudio64.sys Wed Apr 29 14:21:07 2009 - Conexant Modem Audio Conexant: Support

How to update drivers:

- I have listed links to most of the drivers in the code box below. Please use the links there to see what info I've found about those 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 manufacturer links are on this page: Drivers and Downloads
- - To remove any left over driver remnants, especially from graphics cards, use driver sweeper Guru3D - Driver Sweeper

Uninstall Eset, update the drivers above or uninstall the software, reboot and let's see how your system does. If you get another BSOD, please upload it and we will go from there. If you do not get another crash, post back in two or three days and let us know.

You are welcome. If you need help with the drivers, don't hesitate to ask.

That is great news and thank your for reporting back. I appreciate the tip about VSO clean. I was not aware of that. As far as the hardware is concerned, you need to uninstall the webcam; it is obsolete. Purchase a new webcam that is certified compatible with Win 7. The same goes for the modem. Do you use a dialup connection? If not, you do not need the modem. You can disable it in Device manager and navigate to C:\Windows\System32\Drivers and rename the four drivers from.sys to .bak, reboot and they will not load. If you are using a dialup connection you will have to upgrade to a modem compatible with Win 7.

If the manufacturer does not offer an updated driver for Win 7, there is no solution; the hardware is obsolete - planned obsolescence. It is a choice by the software and hardware manufacturers as to whether they make their products compatible with Win 7. Sometime they opt to sell new software or hardware versions rather than spend the money to upgrade existing versions for which they get no monetary return.

The best way - just in case - is to rename the drivers from .sys to .bak or to .old, whichever you prefer. That way, they won't load and you can rename back should the need arise. If you ever need a modem, I suggest you buy a new one. Outdated modem and webcam drivers can bite you - and often do.

You are welcome; it is my pleasure. :)