Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.



Windows 7: BSOD error code system service exception (attached mini dump)

13 Feb 2012   #1

windows 7 home premium x64
 
 
BSOD error code system service exception (attached mini dump)

i have windows 7 home premium x64. i installed from disk 2 days ago. my pc is about 3 days old i built it myself. i am getting BSOD at least twice a day i got the error message 'system service exception' i have attached the mini dump files. thanks scott

My System SpecsSystem Spec
13 Feb 2012   #2

windows 7 home premium x64
 
 
another BSOD error code driver-irql-not-less-or-equal

i have just had another BSOD with error code 'driver-irql-not-less-or-equal. dump files attached
My System SpecsSystem Spec
14 Feb 2012   #3

Windows 7 Home Premium 64 Bit
 
 

Code:
Loading Dump File [F:\BSODDmpFiles\flashflash55\Windows_NT6_BSOD_jcgriff2\021312-40295-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 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Machine Name:
Kernel base = 0xfffff800`02e57000 PsLoadedModuleList = 0xfffff800`03094e70
Debug session time: Mon Feb 13 18:05:18.660 2012 (GMT-7)
System Uptime: 0 days 0:54:54.330
Loading Kernel Symbols
...............................................................
................................................................
.........................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {58, 2, 0, fffff88007ba9db4}

Probably caused by : dxgmms1.sys ( dxgmms1!VidSchiProfilePerformanceTick+628 )

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

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

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: 0000000000000058, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff88007ba9db4, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800030ff0e0
 0000000000000058 

CURRENT_IRQL:  2

FAULTING_IP: 
dxgmms1!VidSchiProfilePerformanceTick+628
fffff880`07ba9db4 49634558        movsxd  rax,dword ptr [r13+58h]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xD1

PROCESS_NAME:  System

TRAP_FRAME:  fffff8800650d930 -- (.trap 0xfffff8800650d930)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffa800a4d3850 rbx=0000000000000000 rcx=0000000000000001
rdx=fffffa8008a1f410 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88007ba9db4 rsp=fffff8800650dac0 rbp=0000000000000000
 r8=0000000000000000  r9=0000000000000000 r10=fffffa8008a1fbe0
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
dxgmms1!VidSchiProfilePerformanceTick+0x628:
fffff880`07ba9db4 49634558        movsxd  rax,dword ptr [r13+58h] ds:00000000`00000058=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002ec6b29 to fffff80002ec75c0

STACK_TEXT:  
fffff880`0650d7e8 fffff800`02ec6b29 : 00000000`0000000a 00000000`00000058 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`0650d7f0 fffff800`02ec57a0 : 00000000`00160171 00000000`00000000 fffffa80`0978f700 00000000`00000003 : nt!KiBugCheckDispatch+0x69
fffff880`0650d930 fffff880`07ba9db4 : 00000000`00000000 fffff880`02dd9f40 fffffa80`08a1f410 fffff880`07bd6d3c : nt!KiPageFault+0x260
fffff880`0650dac0 fffff880`07ba9590 : fffffa80`08ad5000 00000000`00000001 fffffa80`0a4d3850 00000000`00000001 : dxgmms1!VidSchiProfilePerformanceTick+0x628
fffff880`0650db80 fffff880`07ba9177 : fffffa80`08a1f410 00000000`00000000 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiSelectContext+0x120
fffff880`0650dbf0 fffff880`07bd5e7a : 00000000`00000000 fffffa80`0a4d3850 00000000`00000080 fffffa80`08a1f410 : dxgmms1!VidSchiScheduleCommandToRun+0x8b
fffff880`0650dd00 fffff800`031676fa : 00000000`057d2395 fffffa80`08985620 fffffa80`06a25040 fffffa80`08985620 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`0650dd40 fffff800`02ea5b46 : fffff880`02dd5180 fffffa80`08985620 fffff880`02ddffc0 fffff880`012542b4 : nt!PspSystemThreadStartup+0x5a
fffff880`0650dd80 00000000`00000000 : fffff880`0650e000 fffff880`06508000 fffff880`0650d690 00000000`00000000 : nt!KiStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_IP: 
dxgmms1!VidSchiProfilePerformanceTick+628
fffff880`07ba9db4 49634558        movsxd  rax,dword ptr [r13+58h]

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  dxgmms1!VidSchiProfilePerformanceTick+628

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: dxgmms1

IMAGE_NAME:  dxgmms1.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4d3fa174

FAILURE_BUCKET_ID:  X64_0xD1_dxgmms1!VidSchiProfilePerformanceTick+628

BUCKET_ID:  X64_0xD1_dxgmms1!VidSchiProfilePerformanceTick+628

Followup: MachineOwner
---------
Caused by DirectX, your graphics card, or your graphics card driver. 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



Update to Service Pack 1 (SP1)
Download Details - Microsoft Download Center - System Update Readiness Tool for Windows 7 (KB947821) [August 2011]

Download Details - Microsoft Download Center - System Update Readiness Tool for Windows 7 for x64-based Systems (KB947821) [August 2011]

Steps to follow before you install Windows 7 Service Pack 1 from the Microsoft Download Center

Service Pack 1 Download site
Links to Service Pack 1 (SP1) and preparation for SP1 courtesy of JMH
My System SpecsSystem Spec
.


Reply

 BSOD error code system service exception (attached mini dump)





Thread Tools



Similar help and support threads for2: BSOD error code system service exception (attached mini dump)
Thread Forum
BSOD without code, system service exception, played BF3 BSOD Help and Support
BSOD error messages : system service exception and irql less not equal BSOD Help and Support
BSOD: system service exception. windows not doing memory dump BSOD Help and Support
BSOD again.....attached mini dump this time BSOD Help and Support
BSOD, Mini Dump Attached. Help? BSOD Help and Support
Windows 7 BSOD (Mini Dump attached) BSOD Help and Support
BSOD upon start-up, mini-dump attached BSOD Help and Support

Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 10:43 PM.
Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App
  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33