Blue screen of death - reports posted

helenlouise · 22 Mar 2012

thank you so much for all your help have just run that and it says Windows Resource Protection did not find any integrity violations

think i am going to give up now, it is frying my head, again many thanks for your help, will post if it blue screens again

just curious as to where the links i posted no good? or could nothing be seen?

writhziden · 22 Mar 2012

The links were good. Here is the analysis:

Possible out of date drivers:

Code:

btnetdrv	95822000	958249e0	Tue Sep 21 04:15:32 2004 (414fff44)	0000a019		btnetdrv.sys
vbtenum	95b31000	95b33d00	Tue Sep 21 04:18:01 2004 (414fffd9)	0000924b		vbtenum.sys
blueletaudio	95b34000	95b38e80	Mon Oct 18 21:39:23 2004 (41748c6b)	00008497		blueletaudio.sys
VComm	95825000	9582c040	Mon Oct 18 23:37:37 2004 (4174a821)	000148fd		VComm.sys
BTHidMgr	8c29a000	8c2a0de0	Mon Oct 18 23:40:54 2004 (4174a8e6)	0000f78e		BTHidMgr.sys
VcommMgr	95b1a000	95b23560	Thu Nov 04 21:39:07 2004 (418af5db)	0001acf5		VcommMgr.sys
SABI	929f2000	929fa000	Thu May 28 00:38:10 2009 (4a1e3152)	00010f81		SABI.sys

btnetdrv.sys
vbtenum.sys
blueletaudio.sys May not be compatible with Windows 7
VComm.sys May not be compatible with Windows 7
BTHidMgr.sys May not be compatible with Windows 7
VcommMgr.sys May not be compatible with Windows 7
SABI.sys

Code:

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


Loading Dump File [D:\Kingston\BSODDmpFiles\helenlouise\Windows_NT6_BSOD_jcgriff2\032212-19110-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17727.x86fre.win7sp1_gdr.111118-2330
Machine Name:
Kernel base = 0x83045000 PsLoadedModuleList = 0x83185230
Debug session time: Thu Mar 22 03:54:06.574 2012 (UTC - 6:00)
System Uptime: 0 days 0:52:52.322
Loading Kernel Symbols
...............................................................
................................................................
............................
Loading User Symbols
Loading unloaded module list
..........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {cccccccc, 2, 1, 8309b4e6}

Unable to load image \SystemRoot\system32\DRIVERS\igdkmd32.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for igdkmd32.sys
*** ERROR: Module load completed but symbols could not be loaded for igdkmd32.sys
Probably caused by : dxgmms1.sys ( dxgmms1!VidSchiProcessDpcCompletedPacket+3d6 )

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

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

IRQL_NOT_LESS_OR_EQUAL (a)
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 a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: cccccccc, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000001, bitfield :
	bit 0 : value 0 = read operation, 1 = write operation
	bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: 8309b4e6, address which referenced memory

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


WRITE_ADDRESS: GetPointerFromAddress: unable to read from 831a4828
Unable to read MiSystemVaType memory at 83184d80
 cccccccc 

CURRENT_IRQL:  2

FAULTING_IP: 
nt!KiSignalSynchronizationObject+1c
8309b4e6 8901            mov     dword ptr [ecx],eax

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  csrss.exe

TRAP_FRAME:  80d8ac64 -- (.trap 0xffffffff80d8ac64)
ErrCode = 00000002
eax=0004c25d ebx=aef3ab78 ecx=cccccccc edx=00000000 esi=0004c25d edi=9420c2a7
eip=8309b4e6 esp=80d8acd8 ebp=80d8ace8 iopl=0         nv up ei ng nz ac po cy
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010293
nt!KiSignalSynchronizationObject+0x1c:
8309b4e6 8901            mov     dword ptr [ecx],eax  ds:0023:cccccccc=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from 8309b4e6 to 8307dc0b

STACK_TEXT:  
80d8ac64 8309b4e6 badb0d00 00000000 80d8ac84 nt!KiTrap0E+0x2cf
80d8ace8 83099ce3 83167d20 aef3ab70 86feb008 nt!KiSignalSynchronizationObject+0x1c
80d8ad10 9420234e aef3ab70 00000000 00000000 nt!KeSetEvent+0x8e
80d8ad5c 94202451 86feb008 87d259d0 00000000 dxgmms1!VidSchiProcessDpcCompletedPacket+0x3d6
80d8ad78 9420251e 86feb008 88330000 86feb008 dxgmms1!VidSchiProcessDpcDmaPacket+0xc5
80d8ad90 94202832 88330000 00000001 87276e90 dxgmms1!VidSchDdiNotifyDpcWorker+0xb2
80d8adb4 9413ff28 85653920 80d8add4 9413fe88 dxgmms1!VidSchDdiNotifyDpc+0x78
80d8adc0 9413fe88 871b6098 85653920 9413fe2b dxgkrnl!VIDSCH_EXPORT::VidSchDdiNotifyDpc+0x11
80d8add4 938a6784 85653920 9413fe2b 80d8ae18 dxgkrnl!DxgNotifyDpcCB+0x5d
WARNING: Stack unwind information not available. Following frames may be wrong.
80d8ade4 938a63dc 8724a000 00000000 87bbcea4 igdkmd32+0x88784
80d8ae18 93832641 8724a000 00000000 00000000 igdkmd32+0x883dc
80d8af28 9413fb45 8724a000 85653d10 87ea86ec igdkmd32+0x14641
80d8af48 8309a955 85653d10 85653920 00000000 dxgkrnl!DpiFdoDpcForIsr+0x28
80d8afa4 8309a7b8 83167d20 87ea8668 00000000 nt!KiExecuteAllDpcs+0xf9
80d8aff4 83099f7c 9778e780 00000000 00000000 nt!KiRetireDpcList+0xd5
80d8aff8 9778e780 00000000 00000000 00000000 nt!KiDispatchInterrupt+0x2c
83099f7c 00000000 0000001a 00d6850f bb830000 0x9778e780


STACK_COMMAND:  kb

FOLLOWUP_IP: 
dxgmms1!VidSchiProcessDpcCompletedPacket+3d6
9420234e 807dff00        cmp     byte ptr [ebp-1],0

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  dxgmms1!VidSchiProcessDpcCompletedPacket+3d6

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: dxgmms1

IMAGE_NAME:  dxgmms1.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4d4a24c1

FAILURE_BUCKET_ID:  0xA_dxgmms1!VidSchiProcessDpcCompletedPacket+3d6

BUCKET_ID:  0xA_dxgmms1!VidSchiProcessDpcCompletedPacket+3d6

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

The crashes were related to your DirectX/Graphics card.

Try re-installing DirectX using the Download: DirectX Redist (June 2010) - Microsoft Download Center - Download Details and see how the system responds.

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.
1. Download the latest drivers for your display card(s)
2. Click Start Menu
3. Right Click My Computer/Computer
4. Click Manage
5. Click Device Manager from the list on the left
6. Expand Display adapters
7. 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
8. Restart your computer after uninstalling drivers for all display cards
9. Install the latest driver for the display cards once Windows starts
Alternatively:
1. Login as an adminstrative user
2. Download the latest drivers for your display card(s)
3. Click Start Menu
4. Click Control Panel
5. Click Hardware and Sound
6. Click Device Manager (the last link under Devices and Printers)
7. Expand Display adapters
8. 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
9. Restart your computer after uninstalling drivers for all display cards
10. Install the latest driver for the display cards once Windows starts

helenlouise · 22 Mar 2012

looking at older thread it was 4 weeks ago that it blue screened and that was the driver you have said above, and thought i had sorted that, its sounding like something is on the way out, for it to be the same again, 4 weeks later

writhziden · 22 Mar 2012

Do you want to run hardware tests to find out?

helenlouise · 23 Mar 2012

writhziden said:

Do you want to run hardware tests to find out?

depends how difficult that is, as you know i am not to techie minded

writhziden · 23 Mar 2012

I think we should wait to see if the crashes re-occur first. Your crashes do not seem to be too frequent, so it may not be a real issue.

helenlouise · 23 Mar 2012

just been to device manager and right clicked on rapportbuka and uninstall was now there, have uninstalled it and it gone, there are other rapport things things there but nothing showing a yellow triangle thing (sorry not tech words lol) also removed rapport from control panel. Anything i can now do to check everything else or should i leave well alone?

writhziden · 23 Mar 2012

Recommend leaving it be for now. It does not seem to be causing any problems from your descriptions.

Do your normal routine for a few days and post back how the system is responding at that time.

helenlouise · 23 Mar 2012

ok, will do, same as was said in other thread, thank you so very much for all your time and help, will post back if any problems