Problem Devices:
Code:
Mass Storage Controller PCI\VEN_1217&DEV_7130&SUBSYS_02731028&REV_01\4&280AAD99&0&2BF0 The drivers for this device are not installed.
Antivirus Software:
Code:
avp.exe c:\program files\kaspersky lab\kaspersky internet security 2012\avp.exe 648 8 200 1380 2/26/2012 12:55 AM 12.0.0.374 197.55 KB (202,296 bytes) 4/25/2011 12:15 AM
avp.exe c:\program files\kaspersky lab\kaspersky internet security 2012\avp.exe 2924 8 200 1380 2/26/2012 12:56 AM 12.0.0.374 197.55 KB (202,296 bytes) 4/25/2011 12:15 AM
Possible outdated drivers:
Code:
ElbyDelay 911d6000 911d6f80 Thu Feb 12 10:11:28 2004 (402bb3c0) 0000be7f ElbyDelay.sys
ElbyCDIO 971d6000 971d8680 Wed Jul 21 15:45:25 2004 (40fee3f5) 0000329f ElbyCDIO.sys
VClone 835d9000 835de880 Thu Sep 02 07:45:13 2004 (413723e9) 00008356 VClone.sys
Rt86win7 9112d000 91152000 Thu Feb 26 02:04:22 2009 (49a65b16) 0002bdef Rt86win7.sys
bcmwl6 9100b000 91123000 Thu Mar 26 18:58:48 2009 (49cc24c8) 0011a306 bcmwl6.sys
amdxata 835f2000 835fb000 Tue May 19 11:57:35 2009 (4a12f30f) 0000636d amdxata.sys
ElbyDelay.sys
ElbyCDIO.sys
VClone.sys
Rt86win7.sys
bcmwl6.sys
amdxata.sys
Please remove the CD/DVD Clone software from your system. It may cause conflicts due to the age of the drivers. Update the rest of the drivers listed above and install all Windows updates.
Code:
-
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [D:\Kingston\BSODDmpFiles\slugeng\Seven Forums\022612-28017-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
Executable search path is:
Windows 7 Kernel Version 7600 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.x86fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0x82807000 PsLoadedModuleList = 0x8294f810
Debug session time: Sat Feb 25 14:24:16.479 2012 (UTC - 7:00)
System Uptime: 0 days 23:39:31.305
Loading Kernel Symbols
...............................................................
................................................................
................................
Loading User Symbols
Loading unloaded module list
............................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000007E, {c0000005, 9141b501, 92057ba0, 92057780}
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::ProcessDeferredCommand+443 )
Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
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.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: 9141b501, The address that the exception occurred at
Arg3: 92057ba0, Exception Record Address
Arg4: 92057780, Context Record Address
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
FAULTING_IP:
dxgmms1!VIDMM_GLOBAL::ProcessDeferredCommand+443
9141b501 8b00 mov eax,dword ptr [eax]
EXCEPTION_RECORD: 92057ba0 -- (.exr 0xffffffff92057ba0)
ExceptionAddress: 9141b501 (dxgmms1!VIDMM_GLOBAL::ProcessDeferredCommand+0x00000443)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 00000000
Parameter[1]: 00000000
Attempt to read from address 00000000
CONTEXT: 92057780 -- (.cxr 0xffffffff92057780)
eax=00000000 ebx=00000000 ecx=ffffffd8 edx=ae1937c8 esi=8ca82a00 edi=87e18438
eip=9141b501 esp=92057c68 ebp=92057cc4 iopl=0 nv up ei pl nz na po cy
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010203
dxgmms1!VIDMM_GLOBAL::ProcessDeferredCommand+0x443:
9141b501 8b00 mov eax,dword ptr [eax] ds:0023:00000000=????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: NULL_DEREFERENCE
PROCESS_NAME: System
CURRENT_IRQL: 0
ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
EXCEPTION_PARAMETER1: 00000000
EXCEPTION_PARAMETER2: 00000000
READ_ADDRESS: GetPointerFromAddress: unable to read from 8296f718
Unable to read MiSystemVaType memory at 8294f160
00000000
FOLLOWUP_IP:
dxgmms1!VIDMM_GLOBAL::ProcessDeferredCommand+443
9141b501 8b00 mov eax,dword ptr [eax]
BUGCHECK_STR: 0x7E
LAST_CONTROL_TRANSFER: from 9141be66 to 9141b501
STACK_TEXT:
92057cc4 9141be66 01057ce0 00000000 92057cf8 dxgmms1!VIDMM_GLOBAL::ProcessDeferredCommand+0x443
92057cf0 9141d4c8 00000000 92057d18 914312cd dxgmms1!VIDMM_GLOBAL::ProcessTerminationCommand+0x40
92057cfc 914312cd 8797e850 87a48428 87a48428 dxgmms1!VidMmiProcessTerminationCommand+0x10
92057d18 9143227d 87a48760 87a48528 92057d3c dxgmms1!VidSchiSubmitDeviceCommand+0x33
92057d28 914324cc 87a48428 828433f1 87523008 dxgmms1!VidSchiSubmitQueueCommand+0xaf
92057d3c 91432573 87523008 00000000 875f8558 dxgmms1!VidSchiRun_PriorityTable+0x24
92057d50 82a1566d 87523008 b950c6dc 00000000 dxgmms1!VidSchiWorkerThread+0x7f
92057d90 828c70d9 914324f4 87523008 00000000 nt!PspSystemThreadStartup+0x9e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: dxgmms1!VIDMM_GLOBAL::ProcessDeferredCommand+443
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: dxgmms1
IMAGE_NAME: dxgmms1.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc265
STACK_COMMAND: .cxr 0xffffffff92057780 ; kb
FAILURE_BUCKET_ID: 0x7E_dxgmms1!VIDMM_GLOBAL::ProcessDeferredCommand+443
BUCKET_ID: 0x7E_dxgmms1!VIDMM_GLOBAL::ProcessDeferredCommand+443
Followup: MachineOwner
---------
-
Loading Dump File [D:\Kingston\BSODDmpFiles\slugeng\Seven Forums\022512-21028-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
Executable search path is:
Windows 7 Kernel Version 7600 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.x86fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0x8280b000 PsLoadedModuleList = 0x82953810
Debug session time: Fri Feb 24 14:35:22.838 2012 (UTC - 7:00)
System Uptime: 1 days 1:03:47.664
Loading Kernel Symbols
...............................................................
................................................................
...............................
Loading User Symbols
Loading unloaded module list
......................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000008E, {c0000005, 9264a6bc, b28f3b00, 0}
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::CloseOneAllocation+116 )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
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.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: 9264a6bc, The address that the exception occurred at
Arg3: b28f3b00, Trap Frame
Arg4: 00000000
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
FAULTING_IP:
dxgmms1!VIDMM_GLOBAL::CloseOneAllocation+116
9264a6bc 894804 mov dword ptr [eax+4],ecx
TRAP_FRAME: b28f3b00 -- (.trap 0xffffffffb28f3b00)
ErrCode = 00000002
eax=00000000 ebx=87a61000 ecx=b5061b18 edx=00000001 esi=87e42830 edi=b9e322b8
eip=9264a6bc esp=b28f3b74 ebp=b28f3ba8 iopl=0 nv up ei pl zr na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246
dxgmms1!VIDMM_GLOBAL::CloseOneAllocation+0x116:
9264a6bc 894804 mov dword ptr [eax+4],ecx ds:0023:00000004=????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x8E
PROCESS_NAME: firefox.exe
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from 9264af53 to 9264a6bc
STACK_TEXT:
b28f3ba8 9264af53 00000000 00000000 c62db5b0 dxgmms1!VIDMM_GLOBAL::CloseOneAllocation+0x116
b28f3bc8 9262e32b bb90cea0 00000000 b28f3c54 dxgmms1!VIDMM_GLOBAL::CloseAllocation+0x37
b28f3bd8 9253f4aa 87a61000 bb90cea0 00000000 dxgmms1!VidMmCloseAllocation+0x13
b28f3c54 9253d481 00000000 00000000 997e4168 dxgkrnl!DXGDEVICE::DestroyAllocations+0x19a
b28f3c7c 92542ee8 00000001 00000000 00000000 dxgkrnl!DXGDEVICE::ProcessTerminationList+0x89
b28f3d28 8284e42a 002fb3c8 002fb36c 779464f4 dxgkrnl!DxgkCreateAllocation+0x28c
b28f3d28 779464f4 002fb3c8 002fb36c 779464f4 nt!KiFastCallEntry+0x12a
WARNING: Frame IP not in any known module. Following frames may be wrong.
002fb36c 00000000 00000000 00000000 00000000 0x779464f4
STACK_COMMAND: kb
FOLLOWUP_IP:
dxgmms1!VIDMM_GLOBAL::CloseOneAllocation+116
9264a6bc 894804 mov dword ptr [eax+4],ecx
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: dxgmms1!VIDMM_GLOBAL::CloseOneAllocation+116
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: dxgmms1
IMAGE_NAME: dxgmms1.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc265
FAILURE_BUCKET_ID: 0x8E_dxgmms1!VIDMM_GLOBAL::CloseOneAllocation+116
BUCKET_ID: 0x8E_dxgmms1!VIDMM_GLOBAL::CloseOneAllocation+116
Followup: MachineOwner
---------
- Caused by DirectX/graphics card/graphics card drivers. Other possible causes are Memory problems... BIOS... Corrupted hard disk file system... Corrupted System Files... Lack of Windows updates... Drivers...
- Caused by DirectX/graphics card/graphics card drivers. Other possible causes are Memory problems... Viruses... Corrupted hard disk file system... Corrupted System Files... Lack of Windows updates... Drivers...
Follow the steps for Diagnosing basic problems with DirectX. To re-install your display card drivers as outlined in the DirectX link, use the following steps.
- Download the latest drivers for your display card(s)
- Click Start Menu
- Right Click My Computer/Computer
- Click Manage
- Click Device Manager from the list on the left
- Expand Display adapters
- Do the following for each adapter (in case you have multiple display cards)
- Right click the adapter
- Click Uninstall (do not click OK in the dialog box that pops up after hitting Uninstall)
- Put a tick in Delete driver software for this device (if this option is available, otherwise just hit OK) and hit OK
- Restart your computer after uninstalling drivers for all display cards
- Install the latest driver for the display cards once Windows starts
Alternatively:
- Login as an adminstrative user
- Download the latest drivers for your display card(s)
- Click Start Menu
- Click Control Panel
- Click Hardware and Sound
- Click Device Manager (the last link under Devices and Printers)
- Expand Display adapters
- Do the following for each adapter (in case you have multiple display cards)
- Right click the adapter
- Click Uninstall (do not click OK in the dialog box that pops up after hitting Uninstall)
- Put a tick in Delete driver software for this device (if this option is available, otherwise just hit OK) and hit OK
- Restart your computer after uninstalling drivers for all display cards
- Install the latest driver for the display cards once Windows starts
Update to Service Pack 1 (SP1)
Links to Service Pack 1 (SP1) and preparation for SP1 courtesy of JMH