Random BSODs-Out of the Blue

caerroil · Oct 18, 2010

Hi all,
I started having these BSODs ever since I got this computer a couple of months ago. All components are new and I had the OS reinstalled about a week ago or so, after one of the BSODs occurred again. According to the error description (3b) I updated the video driver but to no avail. Why out of the blue-simply because it happens for no apparent reason. I am not a gamer and do not use any other graphics card but the one integrated. I also run 2 passes of Memtest (before I read here that at least 7-8 are required) which showed 0 errors. About a month ago 2 hours of Prime also showed no errors. Last night I had this BSOD, but with a new error-1e. I would take the computer to the shop and have them service it but I am working on something important and have no time to wait for them for days. I hope you will be able to help me. Thanks!

Ultimate x64-OEM
Athlon x4 630
Asus M4A785TD-V
4 GB HyperX 1600

CarlTR6 · Oct 18, 2010

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:

[FONT=&quot]- 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.[/FONT]

- - 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.

caerroil · Oct 19, 2010

Thanks a lot for the quick answer. Will sure do what you told me, although I`ve got a lot of homework to do with those drivers.

CarlTR6 · Oct 19, 2010

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

caerroil · Oct 23, 2010

I have had no BSODs since I followed your advice. I removed the Vimicro drivers, updated all Realtek ones and also uninstalled the pcouffin driver. According to the VSO forum, it is known to crash Windows 7 x64. Their solution is to use VSO Clean to remove it because it is not that necessary with the latest versions of their software. Again, I had no success in finding new drivers for the webcam which is, BTW, some pretty old Canyon one (don`t know the model) that worked with Vimicro drivers. It is the same thing with a modem driver, which I cannot find any more recent than the one I already have. I need to ask for your help again cause I am not that experienced in the field of old hardware. It is pretty easy to work with the new one

http://forums.vso-software.fr/patin-couffin-driver-t9764.html
http://forums.vso-software.fr/pcouffin-sys-and-missing-dvd-drives-t10319.html

CarlTR6 · Oct 23, 2010

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.

caerroil · Oct 23, 2010

If I understand correctly-there is no driver solution to this? I do not actually use the modem, but kind of would like to keep it for backup. But, if that is not possible... The same goes for the webcam? Can I simply delete the drivers from C:\Windows\System32\Drivers, reboot and then use some registry cleaner afterwards? Thanks

CarlTR6 · Oct 23, 2010

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.

caerroil · Oct 24, 2010

OK, will do so. Thanks for all the help.

CarlTR6 · Oct 24, 2010

You are welcome; it is my pleasure.

caerroil · Dec 1, 2010

I am sorry too that I have to resurrect this thread but the creature I thought was dead showed its ugly face again. I have run 7 passes of Memtest on both RAM sticks today (one at a time), also run MSE and Malwarebytes full scan at least twice a week and current DriverGenius reports that all drivers are up to date. Again. could some expert help me with this? Thanks!

CarlTR6 · Dec 1, 2010

I looked at both dumps.

Error code 3D, INTERRUPT_EXCEPTION_NOT_HANDLED. BSOD Index.

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

Code:

Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02e50000 PsLoadedModuleList = 0xfffff800`0308de50
Debug session time: Wed Dec  1 05:52:34.382 2010 (GMT-5)
System Uptime: 0 days 0:42:29.145
Loading Kernel Symbols
...............................................................
................................................................
......................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3D, {fffff88002ffaac0, 0, 0, fffff880040a413b}

Probably caused by : ntkrnlmp.exe ( nt!KiInterruptHandler+29 )

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

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

INTERRUPT_EXCEPTION_NOT_HANDLED (3d)
Arguments:
Arg1: fffff88002ffaac0
Arg2: 0000000000000000
Arg3: 0000000000000000
Arg4: fffff880040a413b

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


CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x3D

PROCESS_NAME:  System

CURRENT_IRQL:  b

EXCEPTION_RECORD:  fffff88002ffb258 -- (.exr 0xfffff88002ffb258)
Cannot read Exception record @ fffff88002ffb258

TRAP_FRAME:  fffff88002ffb300 -- (.trap 0xfffff88002ffb300)
Unable to read trap frame at fffff880`02ffb300

LAST_CONTROL_TRANSFER:  from fffff80002ebfca9 to fffff80002ec0740

STACK_TEXT:  
fffff880`02ffa208 fffff800`02ebfca9 : 00000000`0000003d fffff880`02ffaac0 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
fffff880`02ffa210 fffff800`02ebbfe9 : fffffa80`05a83130 00000000`00000000 fffff880`02ffaac0 fffff800`02eed668 : nt!KiBugCheckDispatch+0x69
fffff880`02ffa350 fffff800`02ee640d : fffff880`03fd7150 fffff880`03fb9058 fffff880`03f93000 fffff880`02ffb258 : nt!KiInterruptHandler+0x29
fffff880`02ffa380 fffff800`02eeda90 : fffff800`0300f91c fffff880`02ffa3f8 fffff880`02ffb258 fffff800`02e50000 : nt!RtlpExecuteHandlerForException+0xd
fffff880`02ffa3b0 fffff800`02efa9ef : fffff880`02ffb258 fffff880`02ffaac0 fffff880`00000000 fffff880`02ffb510 : nt!RtlDispatchException+0x410
fffff880`02ffaa90 fffff800`02ebfd82 : fffff880`02ffb258 fffffa80`04a5e040 fffff880`02ffb300 00000000`00000001 : nt!KiDispatchException+0x16f
fffff880`02ffb120 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiExceptionDispatch+0xc2


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!KiInterruptHandler+29
fffff800`02ebbfe9 90              nop

SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  nt!KiInterruptHandler+29

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4c1c44a9

FAILURE_BUCKET_ID:  X64_0x3D_nt!KiInterruptHandler+29

BUCKET_ID:  X64_0x3D_nt!KiInterruptHandler+29

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

Debug session time: Wed Dec  1 06:09:37.451 2010 (GMT-5)
System Uptime: 0 days 0:15:50.840
Loading Kernel Symbols
...............................................................
................................................................
......................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff80002e797b4, fffff88009a97180, 0}

Probably caused by : ntkrnlmp.exe ( nt!KeSetEvent+124 )

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

0: 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: fffff80002e797b4, Address of the exception record for the exception that caused the bugcheck
Arg3: fffff88009a97180, 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: 
nt!KeSetEvent+124
fffff800`02e797b4 48894108        mov     qword ptr [rcx+8],rax

CONTEXT:  fffff88009a97180 -- (.cxr 0xfffff88009a97180)
rax=fffffa80061c9a68 rbx=fffffa80061c9a60 rcx=ff7ffa80061c9a68
rdx=fffffa8003b36918 rsi=0000000000000000 rdi=fffff80002fefe80
rip=fffff80002e797b4 rsp=fffff88009a97b50 rbp=0000000000000000
 r8=0000000000000000  r9=0000000000000008 r10=fffffa800370d570
r11=00000000001f0003 r12=000000007efdb001 r13=000000000014fd20
r14=000000000014e750 r15=00000000747f2450
iopl=0         nv up ei ng nz na pe cy
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010283
nt!KeSetEvent+0x124:
fffff800`02e797b4 48894108        mov     qword ptr [rcx+8],rax ds:002b:ff7ffa80`061c9a70=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x3B

PROCESS_NAME:  opera.exe

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff80003192154 to fffff80002e797b4

STACK_TEXT:  
fffff880`09a97b50 fffff800`03192154 : 00000000`00000000 fffff800`00000001 fffffa80`0370d500 ff7ffa80`061c9a68 : nt!KeSetEvent+0x124
fffff880`09a97bc0 fffff800`02e74993 : fffffa80`05b23660 fffffa80`061b8be0 00000000`00000000 fffffa80`061c9a60 : nt!NtSetEvent+0x90
fffff880`09a97c20 00000000`747f2dd9 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0014e6d8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x747f2dd9


FOLLOWUP_IP: 
nt!KeSetEvent+124
fffff800`02e797b4 48894108        mov     qword ptr [rcx+8],rax

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nt!KeSetEvent+124

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4c1c44a9

STACK_COMMAND:  .cxr 0xfffff88009a97180 ; kb

FAILURE_BUCKET_ID:  X64_0x3B_nt!KeSetEvent+124

BUCKET_ID:  X64_0x3B_nt!KeSetEvent+124

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

0: kd> lmtsmn
start             end                 module name
fffff880`0400c000 fffff880`0404a000   1394ohci 1394ohci.sys Mon Jul 13 20:07:12 2009 (4A5BCC30)
fffff880`00e4d000 fffff880`00ea4000   ACPI     ACPI.sys     Mon Jul 13 19:19:34 2009 (4A5BC106)
fffff880`02a00000 fffff880`02a8a000   afd      afd.sys      Mon Jul 13 19:21:40 2009 (4A5BC184)
fffff880`04063000 fffff880`04079000   AgileVpn AgileVpn.sys Mon Jul 13 20:10:24 2009 (4A5BCCF0)
fffff880`03c26000 fffff880`03c3b000   amdppm   amdppm.sys   Mon Jul 13 19:19:25 2009 (4A5BC0FD)
fffff880`00fe1000 fffff880`00fec000   amdxata  amdxata.sys  Tue May 19 13:56:59 2009 (4A12F2EB)
fffff880`041c0000 fffff880`041c8000   ASACPI   ASACPI.sys   Wed Jul 15 23:31:29 2009 (4A5E9F11)
fffff880`00fae000 fffff880`00fb7000   atapi    atapi.sys    Mon Jul 13 19:19:47 2009 (4A5BC113)
fffff880`00fb7000 fffff880`00fe1000   ataport  ataport.SYS  Mon Jul 13 19:19:52 2009 (4A5BC118)
fffff880`04609000 fffff880`04dfe000   atikmdag atikmdag.sys Tue Oct 26 22:29:53 2010 (4CC78EA1)
fffff880`03eaf000 fffff880`03efa000   atikmpag atikmpag.sys Tue Oct 26 22:14:23 2010 (4CC78AFF)
fffff880`015f4000 fffff880`015fc000   AtiPcie64 AtiPcie64.sys Wed Mar 10 09:33:45 2010 (4B97ADC9)
fffff880`02b54000 fffff880`02b5b000   Beep     Beep.SYS     Mon Jul 13 20:00:13 2009 (4A5BCA8D)
fffff880`03ddb000 fffff880`03dec000   blbdrive blbdrive.sys Mon Jul 13 19:35:59 2009 (4A5BC4DF)
fffff880`024c8000 fffff880`024e6000   bowser   bowser.sys   Mon Jul 13 19:23:50 2009 (4A5BC206)
fffff960`00650000 fffff960`00677000   cdd      cdd.dll      Wed May 19 15:48:26 2010 (4BF4408A)
fffff880`02af4000 fffff880`02b1e000   cdrom    cdrom.sys    Mon Jul 13 19:19:54 2009 (4A5BC11A)
fffff880`00c9b000 fffff880`00d5b000   CI       CI.dll       Mon Jul 13 21:32:13 2009 (4A5BE01D)
fffff880`013cc000 fffff880`013fc000   CLASSPNP CLASSPNP.SYS Mon Jul 13 19:19:58 2009 (4A5BC11E)
fffff880`00c3d000 fffff880`00c9b000   CLFS     CLFS.SYS     Mon Jul 13 19:19:57 2009 (4A5BC11D)
fffff880`012f2000 fffff880`01365000   cng      cng.sys      Mon Jul 13 19:49:40 2009 (4A5BC814)
fffff880`04053000 fffff880`04063000   CompositeBus CompositeBus.sys Mon Jul 13 20:00:33 2009 (4A5BCAA1)
fffff880`072f9000 fffff880`07302000   cpuz134_x64 cpuz134_x64.sys Fri Jul 09 07:16:58 2010 (4C37052A)
fffff880`065e5000 fffff880`065f3000   crashdmp crashdmp.sys Mon Jul 13 20:01:01 2009 (4A5BCABD)
fffff880`03d3a000 fffff880`03dbd000   csc      csc.sys      Mon Jul 13 19:24:26 2009 (4A5BC22A)
fffff880`03dbd000 fffff880`03ddb000   dfsc     dfsc.sys     Mon Jul 13 19:23:44 2009 (4A5BC200)
fffff880`03d2b000 fffff880`03d3a000   discache discache.sys Mon Jul 13 19:37:18 2009 (4A5BC52E)
fffff880`0124c000 fffff880`01262000   disk     disk.sys     Mon Jul 13 19:19:57 2009 (4A5BC11D)
fffff880`04e3d000 fffff880`04e5f000   drmk     drmk.sys     Mon Jul 13 21:01:25 2009 (4A5BD8E5)
fffff880`04ed7000 fffff880`04ee2000   dsnpfd   dsnpfd.sys   Mon Aug 31 13:03:21 2009 (4A9C0259)
fffff880`06400000 fffff880`06409000   dump_atapi dump_atapi.sys Mon Jul 13 19:19:47 2009 (4A5BC113)
fffff880`065f3000 fffff880`065ff000   dump_dumpata dump_dumpata.sys Mon Jul 13 19:19:47 2009 (4A5BC113)
fffff880`04e65000 fffff880`04e78000   dump_dumpfve dump_dumpfve.sys Mon Jul 13 19:21:51 2009 (4A5BC18F)
fffff880`065d9000 fffff880`065e5000   Dxapi    Dxapi.sys    Mon Jul 13 19:38:28 2009 (4A5BC574)
fffff880`03efa000 fffff880`03fee000   dxgkrnl  dxgkrnl.sys  Thu Oct 01 21:00:14 2009 (4AC5509E)
fffff880`03e00000 fffff880`03e46000   dxgmms1  dxgmms1.sys  Mon Jul 13 19:38:32 2009 (4A5BC578)
fffff880`00fec000 fffff880`01000000   fileinfo fileinfo.sys Mon Jul 13 19:34:25 2009 (4A5BC481)
fffff880`00e00000 fffff880`00e4c000   fltmgr   fltmgr.sys   Mon Jul 13 19:19:59 2009 (4A5BC11F)
fffff880`01376000 fffff880`01380000   Fs_Rec   Fs_Rec.sys   Mon Jul 13 19:19:45 2009 (4A5BC111)
fffff880`011ba000 fffff880`011f4000   fvevol   fvevol.sys   Fri Sep 25 22:34:26 2009 (4ABD7DB2)
fffff880`015aa000 fffff880`015f4000   fwpkclnt fwpkclnt.sys Mon Jul 13 19:21:08 2009 (4A5BC164)
fffff800`033e1000 fffff800`0342a000   hal      hal.dll      Mon Jul 13 21:27:36 2009 (4A5BDF08)
fffff880`03e46000 fffff880`03e6a000   HDAudBus HDAudBus.sys Mon Jul 13 20:06:13 2009 (4A5BCBF5)
fffff880`024e9000 fffff880`02502000   HIDCLASS HIDCLASS.SYS Mon Jul 13 20:06:21 2009 (4A5BCBFD)
fffff880`02502000 fffff880`0250a080   HIDPARSE HIDPARSE.SYS Mon Jul 13 20:06:17 2009 (4A5BCBF9)
fffff880`04e86000 fffff880`04e94000   hidusb   hidusb.sys   Mon Jul 13 20:06:22 2009 (4A5BCBFE)
fffff880`02400000 fffff880`024c8000   HTTP     HTTP.sys     Mon Jul 13 19:22:16 2009 (4A5BC1A8)
fffff880`014aa000 fffff880`014b3000   hwpolicy hwpolicy.sys Mon Jul 13 19:19:22 2009 (4A5BC0FA)
fffff880`041c8000 fffff880`041e6000   i8042prt i8042prt.sys Mon Jul 13 19:19:57 2009 (4A5BC11D)
fffff880`041e6000 fffff880`041f5000   kbdclass kbdclass.sys Mon Jul 13 19:19:50 2009 (4A5BC116)
fffff800`00b9f000 fffff800`00ba9000   kdcom    kdcom.dll    Mon Jul 13 21:31:07 2009 (4A5BDFDB)
fffff880`04efe000 fffff880`04f41000   ks       ks.sys       Wed Mar 03 23:32:25 2010 (4B8F37D9)
fffff880`012d8000 fffff880`012f2000   ksecdd   ksecdd.sys   Mon Jul 13 19:20:54 2009 (4A5BC156)
fffff880`01460000 fffff880`0148b000   ksecpkg  ksecpkg.sys  Fri Dec 11 01:03:32 2009 (4B21E0B4)
fffff880`04e5f000 fffff880`04e64200   ksthunk  ksthunk.sys  Mon Jul 13 20:00:19 2009 (4A5BCA93)
fffff880`0255c000 fffff880`02571000   lltdio   lltdio.sys   Mon Jul 13 20:08:50 2009 (4A5BCC92)
fffff880`02518000 fffff880`0253b000   luafv    luafv.sys    Mon Jul 13 19:26:13 2009 (4A5BC295)
fffff880`00c1c000 fffff880`00c29000   mcupdate_AuthenticAMD mcupdate_AuthenticAMD.dll Mon Jul 13 21:29:09 2009 (4A5BDF65)
fffff880`07302000 fffff880`07306280   mdmxsdk  mdmxsdk.sys  Mon Jun 19 17:27:26 2006 (449716BE)
fffff880`04e78000 fffff880`04e86000   monitor  monitor.sys  Mon Jul 13 19:38:52 2009 (4A5BC58C)
fffff880`04eed000 fffff880`04efc000   mouclass mouclass.sys Mon Jul 13 19:19:50 2009 (4A5BC116)
fffff880`0250b000 fffff880`02518000   mouhid   mouhid.sys   Mon Jul 13 20:00:20 2009 (4A5BCA94)
fffff880`00f94000 fffff880`00fae000   mountmgr mountmgr.sys Mon Jul 13 19:19:54 2009 (4A5BC11A)
fffff880`02b1e000 fffff880`02b4b000   MpFilter MpFilter.sys Sat Mar 20 01:58:08 2010 (4BA463F0)
fffff880`07926000 fffff880`07936000   MpNWMon  MpNWMon.sys  Sat Mar 20 01:58:00 2010 (4BA463E8)
fffff880`02589000 fffff880`025a1000   mpsdrv   mpsdrv.sys   Mon Jul 13 20:08:25 2009 (4A5BCC79)
fffff880`025a1000 fffff880`025ce000   mrxsmb   mrxsmb.sys   Sat Feb 27 02:52:19 2010 (4B88CF33)
fffff880`07288000 fffff880`072d6000   mrxsmb10 mrxsmb10.sys Sat Feb 27 02:52:28 2010 (4B88CF3C)
fffff880`072d6000 fffff880`072f9000   mrxsmb20 mrxsmb20.sys Sat Feb 27 02:52:26 2010 (4B88CF3A)
fffff880`02bb9000 fffff880`02bc4000   Msfs     Msfs.SYS     Mon Jul 13 19:19:47 2009 (4A5BC113)
fffff880`00ead000 fffff880`00eb7000   msisadrv msisadrv.sys Mon Jul 13 19:19:26 2009 (4A5BC0FE)
fffff880`0127a000 fffff880`012d8000   msrpc    msrpc.sys    Mon Jul 13 19:21:32 2009 (4A5BC17C)
fffff880`03d20000 fffff880`03d2b000   mssmbios mssmbios.sys Mon Jul 13 19:31:10 2009 (4A5BC3BE)
fffff880`0123a000 fffff880`0124c000   mup      mup.sys      Mon Jul 13 19:23:45 2009 (4A5BC201)
fffff880`014b8000 fffff880`015aa000   ndis     ndis.sys     Mon Jul 13 19:21:40 2009 (4A5BC184)
fffff880`0409d000 fffff880`040a9000   ndistapi ndistapi.sys Mon Jul 13 20:10:00 2009 (4A5BCCD8)
fffff880`03e6a000 fffff880`03e99000   ndiswan  ndiswan.sys  Mon Jul 13 20:10:11 2009 (4A5BCCE3)
fffff880`04fad000 fffff880`04fc2000   NDProxy  NDProxy.SYS  Mon Jul 13 20:10:05 2009 (4A5BCCDD)
fffff880`03c68000 fffff880`03c77000   netbios  netbios.sys  Mon Jul 13 20:09:26 2009 (4A5BCCB6)
fffff880`02a8a000 fffff880`02acf000   netbt    netbt.sys    Mon Jul 13 19:21:28 2009 (4A5BC178)
fffff880`01400000 fffff880`01460000   NETIO    NETIO.SYS    Mon Jul 13 19:21:46 2009 (4A5BC18A)
fffff880`02bc4000 fffff880`02bd5000   Npfs     Npfs.SYS     Mon Jul 13 19:19:48 2009 (4A5BC114)
fffff880`03d14000 fffff880`03d20000   nsiproxy nsiproxy.sys Mon Jul 13 19:21:02 2009 (4A5BC15E)
fffff800`02e05000 fffff800`033e1000   nt       ntkrnlmp.exe Sat Jun 19 00:16:41 2010 (4C1C44A9)
fffff880`01017000 fffff880`011ba000   Ntfs     Ntfs.sys     Mon Jul 13 19:20:47 2009 (4A5BC14F)
fffff880`02b4b000 fffff880`02b54000   Null     Null.SYS     Mon Jul 13 19:19:37 2009 (4A5BC109)
fffff880`03c42000 fffff880`03c68000   pacer    pacer.sys    Mon Jul 13 20:09:41 2009 (4A5BCCC5)
fffff880`041a3000 fffff880`041c0000   parport  parport.sys  Mon Jul 13 20:00:40 2009 (4A5BCAA8)
fffff880`00ef7000 fffff880`00f0c000   partmgr  partmgr.sys  Mon Jul 13 19:19:58 2009 (4A5BC11E)
fffff880`00eb7000 fffff880`00eea000   pci      pci.sys      Mon Jul 13 19:19:51 2009 (4A5BC117)
fffff880`00f7d000 fffff880`00f84000   pciide   pciide.sys   Mon Jul 13 19:19:49 2009 (4A5BC115)
fffff880`00f84000 fffff880`00f94000   PCIIDEX  PCIIDEX.SYS  Mon Jul 13 19:19:48 2009 (4A5BC114)
fffff880`01365000 fffff880`01376000   pcw      pcw.sys      Mon Jul 13 19:19:27 2009 (4A5BC0FF)
fffff880`07307000 fffff880`073ad000   peauth   peauth.sys   Mon Jul 13 21:01:19 2009 (4A5BD8DF)
fffff880`04e00000 fffff880`04e3d000   portcls  portcls.sys  Mon Jul 13 20:06:27 2009 (4A5BCC03)
fffff880`00c29000 fffff880`00c3d000   PSHED    PSHED.dll    Mon Jul 13 21:32:23 2009 (4A5BE027)
fffff880`04079000 fffff880`0409d000   rasl2tp  rasl2tp.sys  Mon Jul 13 20:10:11 2009 (4A5BCCE3)
fffff880`02ad8000 fffff880`02af3000   raspppoe raspppoe.sys Mon Jul 13 20:10:17 2009 (4A5BCCE9)
fffff880`04e9c000 fffff880`04ebd000   raspptp  raspptp.sys  Mon Jul 13 20:10:18 2009 (4A5BCCEA)
fffff880`04ebd000 fffff880`04ed7000   rassstp  rassstp.sys  Mon Jul 13 20:10:25 2009 (4A5BCCF1)
fffff880`03cc3000 fffff880`03d14000   rdbss    rdbss.sys    Mon Jul 13 19:24:09 2009 (4A5BC219)
fffff880`04ee2000 fffff880`04eed000   rdpbus   rdpbus.sys   Mon Jul 13 20:17:46 2009 (4A5BCEAA)
fffff880`02b9e000 fffff880`02ba7000   RDPCDD   RDPCDD.sys   Mon Jul 13 20:16:34 2009 (4A5BCE62)
fffff880`02ba7000 fffff880`02bb0000   rdpencdd rdpencdd.sys Mon Jul 13 20:16:34 2009 (4A5BCE62)
fffff880`02bb0000 fffff880`02bb9000   rdprefmp rdprefmp.sys Mon Jul 13 20:16:35 2009 (4A5BCE63)
fffff880`01200000 fffff880`0123a000   rdyboost rdyboost.sys Mon Jul 13 19:34:34 2009 (4A5BC48A)
fffff880`02571000 fffff880`02589000   rspndr   rspndr.sys   Mon Jul 13 20:08:50 2009 (4A5BCC92)
fffff880`040bd000 fffff880`04122000   Rt64win7 Rt64win7.sys Wed Oct 06 05:55:03 2010 (4CAC4777)
fffff880`04fc2000 fffff880`04ffe500   RtHDMIVX RtHDMIVX.sys Mon May 24 08:07:55 2010 (4BFA6C1B)
fffff880`073ad000 fffff880`073b8000   secdrv   secdrv.SYS   Wed Sep 13 09:18:38 2006 (4508052E)
fffff880`04000000 fffff880`0400c000   serenum  serenum.sys  Mon Jul 13 20:00:33 2009 (4A5BCAA1)
fffff880`03c77000 fffff880`03c94000   serial   serial.sys   Mon Jul 13 20:00:40 2009 (4A5BCAA8)
fffff880`014a3000 fffff880`014aa000   speedfan speedfan.sys Sun Sep 24 09:26:48 2006 (45168798)
fffff880`0149b000 fffff880`014a3000   spldr    spldr.sys    Mon May 11 12:56:27 2009 (4A0858BB)
fffff880`0781f000 fffff880`078b5000   srv      srv.sys      Thu Aug 26 23:38:00 2010 (4C773318)
fffff880`07200000 fffff880`07267000   srv2     srv2.sys     Thu Aug 26 23:37:46 2010 (4C77330A)
fffff880`073b8000 fffff880`073e5000   srvnet   srvnet.sys   Thu Aug 26 23:37:24 2010 (4C7732F4)
fffff880`04efc000 fffff880`04efd480   swenum   swenum.sys   Mon Jul 13 20:00:18 2009 (4A5BCA92)
fffff880`01602000 fffff880`017ff000   tcpip    tcpip.sys    Sun Jun 13 23:39:04 2010 (4C15A458)
fffff880`073e5000 fffff880`073f7000   tcpipreg tcpipreg.sys Mon Jul 13 20:09:49 2009 (4A5BCCCD)
fffff880`02bf3000 fffff880`02c00000   TDI      TDI.SYS      Mon Jul 13 19:21:18 2009 (4A5BC16E)
fffff880`02bd5000 fffff880`02bf3000   tdx      tdx.sys      Mon Jul 13 19:21:15 2009 (4A5BC16B)
fffff880`03caf000 fffff880`03cc3000   termdd   termdd.sys   Mon Jul 13 20:16:36 2009 (4A5BCE64)
fffff960`00490000 fffff960`0049a000   TSDDD    TSDDD.dll    unavailable (00000000)
fffff880`03c00000 fffff880`03c26000   tunnel   tunnel.sys   Mon Jul 13 20:09:37 2009 (4A5BCCC1)
fffff880`04f41000 fffff880`04f53000   umbus    umbus.sys    Mon Jul 13 20:06:56 2009 (4A5BCC20)
fffff880`06415000 fffff880`06416f00   USBD     USBD.SYS     Mon Jul 13 20:06:23 2009 (4A5BCBFF)
fffff880`04192000 fffff880`041a3000   usbehci  usbehci.sys  Mon Jul 13 20:06:30 2009 (4A5BCC06)
fffff880`04183000 fffff880`04192000   usbfilter usbfilter.sys Thu Sep 30 02:49:36 2010 (4CA43300)
fffff880`04f53000 fffff880`04fad000   usbhub   usbhub.sys   Mon Jul 13 20:07:09 2009 (4A5BCC2D)
fffff880`04122000 fffff880`0412d000   usbohci  usbohci.sys  Mon Jul 13 20:06:30 2009 (4A5BCC06)
fffff880`0412d000 fffff880`04183000   USBPORT  USBPORT.SYS  Mon Jul 13 20:06:31 2009 (4A5BCC07)
fffff880`06409000 fffff880`06415000   usbprint usbprint.sys Mon Jul 13 20:38:18 2009 (4A5BD37A)
fffff880`00eea000 fffff880`00ef7000   vdrvroot vdrvroot.sys Mon Jul 13 20:01:31 2009 (4A5BCADB)
fffff880`02b5b000 fffff880`02b69000   vga      vga.sys      Mon Jul 13 19:38:47 2009 (4A5BC587)
fffff880`06418000 fffff880`065d9000   viahduaa viahduaa.sys Wed Aug 04 03:51:53 2010 (4C591C19)
fffff880`02b69000 fffff880`02b8e000   VIDEOPRT VIDEOPRT.SYS Mon Jul 13 19:38:51 2009 (4A5BC58B)
fffff880`0148b000 fffff880`0149b000   vmstorfl vmstorfl.sys Mon Jul 13 19:42:54 2009 (4A5BC67E)
fffff880`00f0c000 fffff880`00f21000   volmgr   volmgr.sys   Mon Jul 13 19:19:57 2009 (4A5BC11D)
fffff880`00f21000 fffff880`00f7d000   volmgrx  volmgrx.sys  Mon Jul 13 19:20:33 2009 (4A5BC141)
fffff880`01380000 fffff880`013cc000   volsnap  volsnap.sys  Mon Jul 13 19:20:08 2009 (4A5BC128)
fffff880`03c94000 fffff880`03caf000   wanarp   wanarp.sys   Mon Jul 13 20:10:21 2009 (4A5BCCED)
fffff880`02b8e000 fffff880`02b9e000   watchdog watchdog.sys Mon Jul 13 19:37:35 2009 (4A5BC53F)
fffff880`00d5b000 fffff880`00dff000   Wdf01000 Wdf01000.sys Mon Jul 13 19:22:07 2009 (4A5BC19F)
fffff880`00c00000 fffff880`00c0f000   WDFLDR   WDFLDR.SYS   Mon Jul 13 19:19:54 2009 (4A5BC11A)
fffff880`02acf000 fffff880`02ad8000   wfplwf   wfplwf.sys   Mon Jul 13 20:09:26 2009 (4A5BCCB6)
fffff960`000b0000 fffff960`003bf000   win32k   win32k.sys   Tue Aug 31 22:58:04 2010 (4C7DC13C)
fffff880`0404a000 fffff880`04053000   wmiacpi  wmiacpi.sys  Mon Jul 13 19:31:02 2009 (4A5BC3B6)
fffff880`00ea4000 fffff880`00ead000   WMILIB   WMILIB.SYS   Mon Jul 13 19:19:51 2009 (4A5BC117)
fffff880`0253b000 fffff880`0255c000   WudfPf   WudfPf.sys   Mon Jul 13 20:05:37 2009 (4A5BCBD1)

Unloaded modules:
fffff880`078b5000 fffff880`07926000   spsys.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
fffff880`01262000 fffff880`01270000   crashdmp.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
fffff880`011f4000 fffff880`01200000   dump_ataport
    Timestamp: unavailable (00000000)
    Checksum:  00000000
fffff880`01270000 fffff880`01279000   dump_atapi.s
    Timestamp: unavailable (00000000)
    Checksum:  00000000
fffff880`01000000 fffff880`01013000   dump_dumpfve
    Timestamp: unavailable (00000000)
    Checksum:  00000000

The only thing that jumps out at me is one very obsolete driver. It is an XP driver.

mdmxsdk.sys Mon Jun 19 17:27:26 2006 - Conexant Modem Diagnostic Interface x86 Driver. Conexant: Support.

Update this driver. If there is no update, using Windows Explorer, navigate to C:\Windows\System32\Drivers, locate the driver and rename it from .sys to .old. The will break the modem. But if there is no update, the modem is obsolete. Reboot and run your system. Let's see how it does. Update us and let us know. If you get another BSOD, upload it and we will go from there.

caerroil · Dec 2, 2010

OK, did the driver magic(turned it into .old). However, after that first incident I had, I physically removed the modem and the webcam (according to your advice). That was before these last 2 BSODs. Also, I do not know if you spotted it, but perfmon says some XAudio is reporting "tv_ConfigMgrErr24". This XAudio is reportedly linked with the modem and I would have removed it if I could find it (I already have one XAudio64 turned into.bak). Dunno if that is good idea...?

CarlTR6 · Dec 2, 2010

The Xaudio drivers are related to to the modem. Physically removing the modem does uninstall it from Windows. You uninstall from Windows through Device Manager. If that does not delete all of the drivers, you have to rename them or delete them. Do a search of your C: drive for xaudio*.* and see if you can locate the drivers that way.

Great job of working on this problem.

caerroil · Dec 2, 2010

OK, I have searched the disk and here is the screenshot of what I have found. I am a bit puzzled with these .dll files in WOW64 and DriverStore. Also, have no idea what this .cab is? I am not sure if I can rename them to .old or .bak without affecting the registry or something else. Please advise

The attached .rar is actually .cab, but I had to change the extension to upload it. For the sake of security, I scanned it using Malwarebytes and MSE, so no worries

If there is something you do not understand, have no fear, it is just my English.

Random BSODs-Out of the Blue

New member

My Computer My Computer

At a glance

Antique Senior Member

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

Antique Senior Member

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

Antique Senior Member

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

Antique Senior Member

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

Antique Senior Member

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

Antique Senior Member

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

Antique Senior Member

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

Similar threads

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer