Windows 7: BSOD playing LOL, system_service_exeption

NassiC · 08 Jan 2012

I am getting BSOD all the time when trying to play league of legends, i also got a few at other times...

Ive had some problems with Aero somthing crashing.(the desktop stuff)

I have reinstalled windows several times now, and up untill now that would buy me a month or two without BSOD, but today they came right away...

I have tryed 2 defrent grafic drivers, and ive tryed to run several diagnostic tools, all without any errors...

I dont know much about this, so really hope someone can help me...

I have read the BSOD "how to post" and that stuff should be in attached .rar file...

computer speccs:
Windows 7 Enterprice x64 installed, (before that windows 7 ultimate x64)
Its not OEM

My computer is just over a year old
and just reinstalled windows today...

If you need anything else, just tell me and ill be happy to find it for you...

writhziden · 08 Jan 2012

Code:


Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\NassiC\Windows_NT6_BSOD_jcgriff2\010812-18564-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\users\mike\documents\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`02e4f000 PsLoadedModuleList = 0xfffff800`03094670
Debug session time: Sun Jan  8 08:33:49.687 2012 (UTC - 7:00)
System Uptime: 0 days 1:11:39.249
Loading Kernel Symbols
.................................................
Loading User Symbols
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 7E, {ffffffffc0000005, fffff8800fd7dfe8, fffff88004330698, fffff8800432fef0}

Probably caused by : ntkrnlmp.exe ( nt!PoIdle+52a )

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

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

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (7e)
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: ffffffffc0000005, The exception code that was not handled
Arg2: fffff8800fd7dfe8, The address that the exception occurred at
Arg3: fffff88004330698, Exception Record Address
Arg4: fffff8800432fef0, 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: 
+3732313831663533
fffff880`0fd7dfe8 ??              ???

EXCEPTION_RECORD:  fffff88004330698 -- (.exr 0xfffff88004330698)
Cannot read Exception record @ fffff88004330698

CONTEXT:  fffff8800432fef0 -- (.cxr 0xfffff8800432fef0)
Unable to read context, Win32 error 0n30

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x7E

PROCESS_NAME:  System

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff80002ed54a9 to fffff8800456b7f2

STACK_TEXT:  
fffff800`00b9cc98 fffff800`02ed54a9 : 00000000`ffffffed fffffa80`04f965d8 fffff800`0304fcc0 00000000`00000001 : 0xfffff880`0456b7f2
fffff800`00b9cca0 fffff800`02ec393c : fffff800`03041e80 fffff800`00000000 00000000`00000000 fffff880`0f1140b0 : nt!PoIdle+0x52a
fffff800`00b9cd80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x2c


FOLLOWUP_IP: 
nt!PoIdle+52a
fffff800`02ed54a9 0fba25570e18000f bt      dword ptr [nt!PerfGlobalGroupMask+0x8 (fffff800`03056308)],0Fh

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!PoIdle+52a

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4e02aaa3

STACK_COMMAND:  .cxr 0xfffff8800432fef0 ; kb

FAILURE_BUCKET_ID:  X64_0x7E_nt!PoIdle+52a

BUCKET_ID:  X64_0x7E_nt!PoIdle+52a

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

Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\NassiC\Windows_NT6_BSOD_jcgriff2\010812-20872-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\users\mike\documents\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`02e17000 PsLoadedModuleList = 0xfffff800`0305c670
Debug session time: Sun Jan  8 13:45:13.647 2012 (UTC - 7:00)
System Uptime: 0 days 0:06:29.207
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 : hidusb.sys ( hidusb!HumReadReport+13f )

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

2: 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: 
+3838303532303231
00000000`00000000 ??              ???

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  0000000000000000

ERROR_CODE: (NTSTATUS) 0 - STATUS_WAIT_0

BUGCHECK_STR:  0x1E_0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  2

EXCEPTION_RECORD:  fffff88002f8b568 -- (.exr 0xfffff88002f8b568)
ExceptionAddress: fffff880019e8dd4 (usbccgp!UsbcAcquireRemoveLock+0x00000000000000bc)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

TRAP_FRAME:  fffff88002f8b610 -- (.trap 0xfffff88002f8b610)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=00fffa8005611d38 rbx=0000000000000000 rcx=fffffa800562fc40
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff880019e8dd4 rsp=fffff88002f8b7a0 rbp=fffffa8004cba760
 r8=fffff88002f8b7d0  r9=0000000000000000 r10=fffff88002f63b20
r11=fffffa80045df7b8 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe nc
usbccgp!UsbcAcquireRemoveLock+0xbc:
fffff880`019e8dd4 4c8918          mov     qword ptr [rax],r11 ds:0c70:00fffa80`05611d38=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002e8b5fe to fffff80002e93c10

STACK_TEXT:  
fffff880`02f8a648 fffff800`02e8b5fe : fffffa80`04cc91a0 fffff880`014d3569 fffff880`02f8adc0 fffff800`02ebf830 : nt!KeBugCheck
fffff880`02f8a650 fffff800`02ebf4fd : fffff800`0309d71c fffff800`02fdac30 fffff800`02e17000 fffff880`02f8b568 : nt!KiKernelCalloutExceptionHandler+0xe
fffff880`02f8a680 fffff800`02ebe2d5 : fffff800`02fde0fc fffff880`02f8a6f8 fffff880`02f8b568 fffff800`02e17000 : nt!RtlpExecuteHandlerForException+0xd
fffff880`02f8a6b0 fffff800`02ecf361 : fffff880`02f8b568 fffff880`02f8adc0 fffff880`00000000 fffffa80`00000003 : nt!RtlDispatchException+0x415
fffff880`02f8ad90 fffff800`02e932c2 : fffff880`02f8b568 00000000`00000000 fffff880`02f8b610 fffffa80`0562fb58 : nt!KiDispatchException+0x135
fffff880`02f8b430 fffff800`02e91bca : fffffa80`04fda000 fffffa80`04cba998 00000000`00000000 00000000`00000004 : nt!KiExceptionDispatch+0xc2
fffff880`02f8b610 fffff880`019e8dd4 : 00000000`00000324 00000000`00000000 fffffa80`0562fb58 00000000`000007ff : nt!KiGeneralProtectionFault+0x10a
fffff880`02f8b7a0 fffff880`019e350c : 00000000`0000000f fffffa80`05623b50 fffffa80`05623b58 fffffa80`04cba760 : usbccgp!UsbcAcquireRemoveLock+0xbc
fffff880`02f8b800 fffff880`0445e48f : fffffa80`05623a00 fffffa80`04cba701 00000000`00000000 00000000`000007ff : usbccgp!USBC_Dispatch+0xbc
fffff880`02f8b880 fffff880`0445df5b : fffffa80`04cba9e0 fffffa80`05636c01 fffff880`02f8b940 fffffa80`05636b30 : hidusb!HumReadReport+0x13f
fffff880`02f8b8d0 fffff880`05014555 : fffffa80`0562db01 fffffa80`0562dbb0 fffffa80`04cba760 00000000`00000008 : hidusb!HumInternalIoctl+0x137
fffff880`02f8b940 fffff880`05014d75 : fffffa80`0562dbb0 fffffa80`05636ca0 00000000`00000000 00000000`00000008 : HIDCLASS!HidpSubmitInterruptRead+0xdd
fffff880`02f8b9a0 fffff800`02e97021 : fffffa80`04cba9e3 00000000`00000000 fffffa80`05636b01 fffffa80`04cba700 : HIDCLASS!HidpInterruptReadComplete+0x37d
fffff880`02f8ba30 fffff880`04013631 : fffffa80`04ac0050 fffffa80`04749800 00000000`00000000 00000000`00000000 : nt!IopfCompleteRequest+0x341
fffff880`02f8bb20 fffff880`04013b0f : fffffa80`04759c02 fffffa80`04cba760 00000000`ffffffff fffffa80`04ac0eb0 : USBPORT!USBPORT_Core_iCompleteDoneTransfer+0xa15
fffff880`02f8bc00 fffff880`0401166f : fffffa80`04ac0eb0 fffffa80`04ac01a0 fffffa80`04ac1050 00000000`00000000 : USBPORT!USBPORT_Core_iIrpCsqCompleteDoneTransfer+0x3a7
fffff880`02f8bc60 fffff880`04002f89 : fffffa80`04ac0050 00000000`00000000 fffffa80`04ac0e02 fffffa80`04ac0eb0 : USBPORT!USBPORT_Core_UsbIocDpc_Worker+0xf3
fffff880`02f8bca0 fffff800`02e9f0ac : fffff880`02f63180 fffffa80`04ac0eb0 fffffa80`04ac0ec8 00000000`00000000 : USBPORT!USBPORT_Xdpc_Worker+0x1d9
fffff880`02f8bcd0 fffff800`02e8b96a : fffff880`02f63180 fffff880`02f6dfc0 00000000`00000000 fffff880`04002db0 : nt!KiRetireDpcList+0x1bc
fffff880`02f8bd80 00000000`00000000 : fffff880`02f8c000 fffff880`02f86000 fffff880`02f8bd40 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
hidusb!HumReadReport+13f
fffff880`0445e48f 488b4c2460      mov     rcx,qword ptr [rsp+60h]

SYMBOL_STACK_INDEX:  9

SYMBOL_NAME:  hidusb!HumReadReport+13f

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: hidusb

IMAGE_NAME:  hidusb.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4ce7a665

FAILURE_BUCKET_ID:  X64_0x1E_0_hidusb!HumReadReport+13f

BUCKET_ID:  X64_0x1E_0_hidusb!HumReadReport+13f

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

Update the following drivers. If you need help finding drivers, refer to Driver Reference for drivers and Drivers and Downloads for drivers' manufacturers. Also, Installing and updating drivers in 7 may be a helpful resource.

Code:

ASACPI	fffff880`04181000	fffff880`04189000	Sun Mar 27 20:30:36 2005 (42476c4c)	00003c77		ASACPI.sys
nvm62x64	fffff880`0446b000	fffff880`044ced80	Fri Oct 17 15:01:06 2008 (48f8fd12)	0006f977		nvm62x64.sys

Especially recommend updating ASACPI.SYS as it is a known BSOD problem on Windows 7. Update the driver by:
1. Going to the Asus motherboard support site
When you reach the website:
2. Scroll down the page and click Utilities
3. Hold Ctrl and press f (ctrl+f) to enter the browser's find feature
4. Search for "ATK0110 driver for WindowsXP/Vista/Windows 7 32&64-bit" (without quotes)
5. Download and install the driver.
6. After installation is complete, verify that it installed correctly.

a. Click Start Menu
b. Click My Computer
c. Go to C:\WIndows\System32\drivers\
d. Verify that the ASACPI.SYS file is dated 2009 or newer (2010,etc.)

Thanks to JMH and zigzag3143 for the above information.

NassiC · 08 Jan 2012

Okay thx so much for your awnser... I have tryed it, and will get back if it works or not...

NassiC · 09 Jan 2012

Damit got one again, just after going into league of legends and quiting again... It worked fine yesterday after i updated the driver above, but not no more

I have attatched a new dump file

writhziden · 09 Jan 2012

Code:

Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\NassiC\Windows_NT6_BSOD_jcgriff2\010912-18236-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\users\mike\documents\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`02e0f000 PsLoadedModuleList = 0xfffff800`03054670
Debug session time: Mon Jan  9 11:59:04.497 2012 (UTC - 7:00)
System Uptime: 0 days 6:08:21.058
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 : usbaudio.sys ( usbaudio!USBCaptureCompleteCallback+fa )

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: 
+3039623165666439
00000000`00000000 ??              ???

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  0000000000000000

ERROR_CODE: (NTSTATUS) 0 - STATUS_WAIT_0

BUGCHECK_STR:  0x1E_0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  2

EXCEPTION_RECORD:  fffff88002ffb798 -- (.exr 0xfffff88002ffb798)
ExceptionAddress: fffff880042032fe (usbaudio!USBCaptureCompleteCallback+0x00000000000000fa)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

TRAP_FRAME:  fffff88002ffb840 -- (.trap 0xfffff88002ffb840)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff88004209c10 rbx=0000000000000000 rcx=fffffa80049e7060
rdx=fffffa8003eb1510 rsi=0000000000000000 rdi=0000000000000000
rip=fffff880042032fe rsp=fffff88002ffb9d0 rbp=fffffa80049e7000
 r8=fffffa80049e71b0  r9=0000000000000000 r10=fffff80002e0f000
r11=fffff88002ffbb18 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
usbaudio!USBCaptureCompleteCallback+0xfa:
fffff880`042032fe 385f50          cmp     byte ptr [rdi+50h],bl ds:0002:00000000`00000050=??
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002e835fe to fffff80002e8bc10

STACK_TEXT:  
fffff880`02ffa878 fffff800`02e835fe : 00000000`00000001 fffff880`01711830 fffff880`02ffaff0 fffff800`02eb7830 : nt!KeBugCheck
fffff880`02ffa880 fffff800`02eb74fd : fffff800`0309571c fffff800`02fd2c30 fffff800`02e0f000 fffff880`02ffb798 : nt!KiKernelCalloutExceptionHandler+0xe
fffff880`02ffa8b0 fffff800`02eb62d5 : fffff800`02fd60fc fffff880`02ffa928 fffff880`02ffb798 fffff800`02e0f000 : nt!RtlpExecuteHandlerForException+0xd
fffff880`02ffa8e0 fffff800`02ec7361 : fffff880`02ffb798 fffff880`02ffaff0 fffff880`00000000 00fffa80`049e70a0 : nt!RtlDispatchException+0x415
fffff880`02ffafc0 fffff800`02e8b2c2 : fffff880`02ffb798 00000000`00000000 fffff880`02ffb840 fffffa80`049e7450 : nt!KiDispatchException+0x135
fffff880`02ffb660 fffff800`02e89bca : 00000000`00000000 fffffa80`05d30980 00000000`00000000 00000000`00000000 : nt!KiExceptionDispatch+0xc2
fffff880`02ffb840 fffff880`042032fe : fffffa80`049e7450 fffffa80`0395ca18 00fffa80`049e70a0 fffffa80`03eb1510 : nt!KiGeneralProtectionFault+0x10a
fffff880`02ffb9d0 fffff800`02e8f021 : fffffa80`03eb1793 fffff800`03424c02 00000000`00000000 00000000`00000000 : usbaudio!USBCaptureCompleteCallback+0xfa
fffff880`02ffba30 fffff880`045a0631 : fffffa80`0395c050 fffffa80`049e7400 00000000`00000000 00000000`00000000 : nt!IopfCompleteRequest+0x341
fffff880`02ffbb20 fffff880`045a0b0f : fffffa80`0637c902 fffffa80`03eb1510 00000000`ffffffff fffffa80`0395ceb0 : USBPORT!USBPORT_Core_iCompleteDoneTransfer+0xa15
fffff880`02ffbc00 fffff880`0459e66f : fffffa80`0395ceb0 fffffa80`0395c1a0 fffffa80`0395d050 00000000`00000000 : USBPORT!USBPORT_Core_iIrpCsqCompleteDoneTransfer+0x3a7
fffff880`02ffbc60 fffff880`0458ff89 : fffffa80`0395c050 00000000`00000000 fffffa80`0395ce02 fffffa80`0395ceb0 : USBPORT!USBPORT_Core_UsbIocDpc_Worker+0xf3
fffff880`02ffbca0 fffff800`02e970ac : fffff880`02fd3180 fffffa80`0395ceb0 fffffa80`0395cec8 00000000`00000000 : USBPORT!USBPORT_Xdpc_Worker+0x1d9
fffff880`02ffbcd0 fffff800`02e8396a : fffff880`02fd3180 fffff880`02fddfc0 00000000`00000000 fffff880`0458fdb0 : nt!KiRetireDpcList+0x1bc
fffff880`02ffbd80 00000000`00000000 : fffff880`02ffc000 fffff880`02ff6000 fffff880`02ffbd40 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
usbaudio!USBCaptureCompleteCallback+fa
fffff880`042032fe 385f50          cmp     byte ptr [rdi+50h],bl

SYMBOL_STACK_INDEX:  7

SYMBOL_NAME:  usbaudio!USBCaptureCompleteCallback+fa

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: usbaudio

IMAGE_NAME:  usbaudio.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4ce7a668

FAILURE_BUCKET_ID:  X64_0x1E_0_usbaudio!USBCaptureCompleteCallback+fa

BUCKET_ID:  X64_0x1E_0_usbaudio!USBCaptureCompleteCallback+fa

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

You received a second blue screen crash related to your USB devices. What USB devices do you have plugged in? Follow the steps in USB Driver - General Fix for Problems to see if they prevent your crashes.

NassiC · 09 Jan 2012

Thx for your awnser, i have my mouse and headset, and a usb charger for my E-cig... But i will try your link, thx for your help...

NassiC · 10 Jan 2012

After trying to fix the USB it kinda got worse, got a lot of BSOD this time, not only when in lol this time... i also had problems with my explore and firefox and internet explore crashing like all the time...

I really hope someone can help, cuz im getting really despret...

Ive attached a new dumpfile...

writhziden · 10 Jan 2012

Quote: Originally Posted by NassiC

After trying to fix the USB it kinda got worse, got a lot of BSOD this time, not only when in lol this time... i also had problems with my explore and firefox and internet explore crashing like all the time...

I really hope someone can help, cuz im getting really despret...

Ive attached a new dumpfile...

Taking a look now, post back shortly...

NassiC · 10 Jan 2012

Sounds good... And thx again soo much for all your help...

writhziden · 10 Jan 2012

Code:


Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\NassiC\Windows_NT6_BSOD_jcgriff2\011012-16317-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\users\mike\documents\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`02e03000 PsLoadedModuleList = 0xfffff800`03048670
Debug session time: Mon Jan  9 18:41:43.063 2012 (UTC - 7:00)
System Uptime: 0 days 0:09:16.249
Loading Kernel Symbols
...............................................................
................................................................
...................
Loading User Symbols
Loading unloaded module list
..........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 4E, {2, a3d60, 12ffff, 1}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+11718 )

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

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

PFN_LIST_CORRUPT (4e)
Typically caused by drivers passing bad memory descriptor lists (ie: calling
MmUnlockPages twice with the same list, etc).  If a kernel debugger is
available get the stack trace.
Arguments:
Arg1: 0000000000000002, A list entry was corrupt
Arg2: 00000000000a3d60, entry in list being removed
Arg3: 000000000012ffff, highest physical page number
Arg4: 0000000000000001, reference count of entry being removed

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


BUGCHECK_STR:  0x4E_2

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff80002e14488 to fffff80002e7fc40

STACK_TEXT:  
fffff880`0318c6c8 fffff800`02e14488 : 00000000`0000004e 00000000`00000002 00000000`000a3d60 00000000`0012ffff : nt!KeBugCheckEx
fffff880`0318c6d0 fffff800`02ec378b : fffff8a0`0c5da900 00000000`0006455f 00000000`0c5da900 fffff8a0`0c5da900 : nt! ?? ::FNODOBFM::`string'+0x11718
fffff880`0318c760 fffff800`02ec2188 : fffff8a0`0c5da800 fffff8a0`0c5db000 fffffa80`04111f90 fffffa80`04111f90 : nt!MiFlushSectionInternal+0x6bb
fffff880`0318c990 fffff800`02ec1669 : 00000000`00008b4a fffff880`0318cc58 00000000`00100000 fffffa80`043a2760 : nt!MmFlushSection+0xa4
fffff880`0318ca50 fffff800`02ec4f76 : fffffa80`040b0558 00000000`00000001 fffffa80`00000001 fffffa80`00100000 : nt!CcFlushCache+0x5e9
fffff880`0318cb50 fffff800`02ec5938 : fffff880`00000000 fffff880`0318cc58 fffffa80`03fb0c10 fffff880`042db734 : nt!CcWriteBehind+0x1c6
fffff880`0318cc00 fffff800`02e8a001 : fffffa80`03a48530 fffff800`03176901 fffff800`030818c0 00000000`00000002 : nt!CcWorkerThread+0x1c8
fffff880`0318ccb0 fffff800`0311afee : 00000000`00000000 fffffa80`03adb040 00000000`00000080 fffffa80`039ed040 : nt!ExpWorkerThread+0x111
fffff880`0318cd40 fffff800`02e715e6 : fffff880`02f63180 fffffa80`03adb040 fffff880`02f6dfc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`0318cd80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+11718
fffff800`02e14488 cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+11718

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4e02aaa3

FAILURE_BUCKET_ID:  X64_0x4E_2_nt!_??_::FNODOBFM::_string_+11718

BUCKET_ID:  X64_0x4E_2_nt!_??_::FNODOBFM::_string_+11718

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

Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\NassiC\Windows_NT6_BSOD_jcgriff2\011012-16879-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\users\mike\documents\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`02e4d000 PsLoadedModuleList = 0xfffff800`03092670
Debug session time: Mon Jan  9 18:44:25.092 2012 (UTC - 7:00)
System Uptime: 0 days 0:01:38.653
Loading Kernel Symbols
...............................................................
................................................................
....................
Loading User Symbols
Loading unloaded module list
.........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 24, {1904fb, fffff88008317758, fffff88008316fb0, fffff80002edc19a}

Probably caused by : Ntfs.sys ( Ntfs!NtfsTeardownFromLcb+fb )

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

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

NTFS_FILE_SYSTEM (24)
    If you see NtfsExceptionFilter on the stack then the 2nd and 3rd
    parameters are the exception record and context record. Do a .cxr
    on the 3rd parameter and then kb to obtain a more informative stack
    trace.
Arguments:
Arg1: 00000000001904fb
Arg2: fffff88008317758
Arg3: fffff88008316fb0
Arg4: fffff80002edc19a

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


EXCEPTION_RECORD:  fffff88008317758 -- (.exr 0xfffff88008317758)
ExceptionAddress: fffff80002edc19a (nt!ExAcquireFastMutex+0x000000000000001a)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000001
   Parameter[1]: 000000006bd59921
Attempt to write to address 000000006bd59921

CONTEXT:  fffff88008316fb0 -- (.cxr 0xfffff88008316fb0)
rax=0000000000000001 rbx=000000006bd59921 rcx=000000006bd59921
rdx=0000000000000001 rsi=fffff88008317b01 rdi=0000000000000000
rip=fffff80002edc19a rsp=fffff88008317990 rbp=fffff8000306a260
 r8=fffff8a007526480  r9=fffff8a0075268c0 r10=fffff880010ab5c0
r11=fffffa8003ca3510 r12=fffff8a007526480 r13=fffff8a001d07bc0
r14=fffff8a007526800 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010286
nt!ExAcquireFastMutex+0x1a:
fffff800`02edc19a f00fba3100      lock btr dword ptr [rcx],0 ds:002b:00000000`6bd59921=????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  1

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

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

EXCEPTION_PARAMETER1:  0000000000000001

EXCEPTION_PARAMETER2:  000000006bd59921

WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800030fc100
 000000006bd59921 

FOLLOWUP_IP: 
Ntfs!NtfsTeardownFromLcb+fb
fffff880`0123988b 83bfc000000000  cmp     dword ptr [rdi+0C0h],0

FAULTING_IP: 
nt!ExAcquireFastMutex+1a
fffff800`02edc19a f00fba3100      lock btr dword ptr [rcx],0

BUGCHECK_STR:  0x24

LAST_CONTROL_TRANSFER:  from fffff8800123988b to fffff80002edc19a

STACK_TEXT:  
fffff880`08317990 fffff880`0123988b : fffff8a0`07526480 fffffa80`03bc5c30 fffff8a0`075265b0 fffff880`012c1cc1 : nt!ExAcquireFastMutex+0x1a
fffff880`083179c0 fffff880`012bf63c : fffffa80`03bc5c30 fffffa80`04a39180 fffff8a0`07526480 fffff8a0`075268c0 : Ntfs!NtfsTeardownFromLcb+0xfb
fffff880`08317a50 fffff880`012410e2 : fffffa80`03bc5c30 fffffa80`03bc5c30 fffff8a0`07526480 fffff880`08317c00 : Ntfs!NtfsTeardownStructures+0xcc
fffff880`08317ad0 fffff880`012cf193 : fffffa80`03bc5c30 fffff800`0306a260 fffff8a0`4946744e 00000000`00000009 : Ntfs!NtfsDecrementCloseCounts+0xa2
fffff880`08317b10 fffff880`012be357 : fffffa80`03bc5c30 fffff8a0`075265b0 fffff8a0`07526480 fffffa80`04a39180 : Ntfs!NtfsCommonClose+0x353
fffff880`08317be0 fffff800`02ed4001 : 00000000`00000000 fffff800`031c0900 fffffa80`061c6001 00000000`00000003 : Ntfs!NtfsFspClose+0x15f
fffff880`08317cb0 fffff800`03164fee : 00000000`271f90ca fffffa80`061c6040 00000000`00000080 fffffa80`039ed040 : nt!ExpWorkerThread+0x111
fffff880`08317d40 fffff800`02ebb5e6 : fffff880`02fd4180 fffffa80`061c6040 fffffa80`0603f060 fffff880`01240a20 : nt!PspSystemThreadStartup+0x5a
fffff880`08317d80 00000000`00000000 : fffff880`08318000 fffff880`08312000 fffff880`083179e0 00000000`00000000 : nt!KxStartSystemThread+0x16


SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  Ntfs!NtfsTeardownFromLcb+fb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: Ntfs

IMAGE_NAME:  Ntfs.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4d79997b

STACK_COMMAND:  .cxr 0xfffff88008316fb0 ; kb

FAILURE_BUCKET_ID:  X64_0x24_Ntfs!NtfsTeardownFromLcb+fb

BUCKET_ID:  X64_0x24_Ntfs!NtfsTeardownFromLcb+fb

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

Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\NassiC\Windows_NT6_BSOD_jcgriff2\011012-18142-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\users\mike\documents\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`02e57000 PsLoadedModuleList = 0xfffff800`0309c670
Debug session time: Mon Jan  9 18:00:54.873 2012 (UTC - 7:00)
System Uptime: 0 days 4:17:05.434
Loading Kernel Symbols
...............................................................
................................................................
.....................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 24, {1904fb, fffff880074be288, fffff880074bdae0, fffff880012294d3}

Probably caused by : Ntfs.sys ( Ntfs!NtfsCommonRead+1ca7 )

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

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

NTFS_FILE_SYSTEM (24)
    If you see NtfsExceptionFilter on the stack then the 2nd and 3rd
    parameters are the exception record and context record. Do a .cxr
    on the 3rd parameter and then kb to obtain a more informative stack
    trace.
Arguments:
Arg1: 00000000001904fb
Arg2: fffff880074be288
Arg3: fffff880074bdae0
Arg4: fffff880012294d3

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


EXCEPTION_RECORD:  fffff880074be288 -- (.exr 0xfffff880074be288)
ExceptionAddress: fffff880012294d3 (Ntfs!NtfsCommonRead+0x0000000000001ca7)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

CONTEXT:  fffff880074bdae0 -- (.cxr 0xfffff880074bdae0)
rax=00fffa80048b6ec0 rbx=fffff8a0034c7790 rcx=fffff880074be5f8
rdx=fffffa8004a3e180 rsi=fffff8a0034c7980 rdi=fffff8a0034c7660
rip=fffff880012294d3 rsp=fffff880074be4c0 rbp=fffff880074be7f0
 r8=0000000000000000  r9=0000000000671c00 r10=fffffa8004789c00
r11=fffff880074be698 r12=0000000000060001 r13=0000000000000001
r14=fffff880074be708 r15=fffff880074be690
iopl=0         nv up ei pl zr na po nc
cs=0010  ss=0000  ds=002b  es=002b  fs=0053  gs=002b             efl=00010246
Ntfs!NtfsCommonRead+0x1ca7:
fffff880`012294d3 ff4008          inc     dword ptr [rax+8] ds:002b:00fffa80`048b6ec8=????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  League of Lege

CURRENT_IRQL:  0

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

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

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  ffffffffffffffff

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80003106100
 ffffffffffffffff 

FOLLOWUP_IP: 
Ntfs!NtfsCommonRead+1ca7
fffff880`012294d3 ff4008          inc     dword ptr [rax+8]

FAULTING_IP: 
Ntfs!NtfsCommonRead+1ca7
fffff880`012294d3 ff4008          inc     dword ptr [rax+8]

BUGCHECK_STR:  0x24

LAST_CONTROL_TRANSFER:  from fffff88001229a68 to fffff880012294d3

STACK_TEXT:  
fffff880`074be4c0 fffff880`01229a68 : fffff880`074be690 fffffa80`04789860 fffff880`074be701 fffffa80`03e3bb01 : Ntfs!NtfsCommonRead+0x1ca7
fffff880`074be660 fffff880`01142bcf : fffffa80`04789c00 fffffa80`04789860 fffffa80`03e3bb00 00000000`00000000 : Ntfs!NtfsFsdRead+0x1b8
fffff880`074be870 fffff880`011416df : fffffa80`048b8ca0 fffffa80`03ed7301 fffffa80`048b8c00 fffffa80`04789860 : fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x24f
fffff880`074be900 fffff800`02efbbc5 : fffffa80`04789880 fffffa80`03d9f7d0 fffffa80`03d21640 00000000`00a7355c : fltmgr!FltpDispatch+0xcf
fffff880`074be960 fffff800`02efb699 : 00000000`00000001 00000000`00000001 fffffa80`03d21580 fffffa80`03d21580 : nt!IoPageRead+0x255
fffff880`074be9f0 fffff800`02ee202a : 00000000`00000000 00000000`00000000 ffffffff`ffffffff 00000000`00000000 : nt!MiIssueHardFault+0x255
fffff880`074beac0 fffff800`02ed1d6e : 00000000`00000000 00000000`00a7355c fffffa80`03997a01 00000000`005006d4 : nt!MmAccessFault+0x146a
fffff880`074bec20 00000000`77aa6882 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e
00000000`0018e8b0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77aa6882


SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  Ntfs!NtfsCommonRead+1ca7

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: Ntfs

IMAGE_NAME:  Ntfs.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4d79997b

STACK_COMMAND:  .cxr 0xfffff880074bdae0 ; kb

FAILURE_BUCKET_ID:  X64_0x24_Ntfs!NtfsCommonRead+1ca7

BUCKET_ID:  X64_0x24_Ntfs!NtfsCommonRead+1ca7

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

Run Disk Check with both boxes checked for all HDDs and with Automatically fix file system errors checked for all SSDs.

Windows 7: BSOD playing LOL, system_service_exeption

BSOD playing LOL, system_service_exeption problems?