Sat Dec 10 12:04:05.313 2011
STOP 0x0000003B: SYSTEM_SERVICE_EXCEPTION
Usual causes: System service, Device driver, graphics driver, ?memory.
Bugcheck Analysis:
Code:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 3B, {c0000005, fffff880010bf039, fffff8800a552990, 0}
Probably caused by : [B]fileinfo.sys [/B]( fileinfo!FIStreamGet+52 )
Followup: MachineOwner
---------
2: 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: fffff880010bf039, Address of the instruction which caused the bugcheck
Arg3: fffff8800a552990, 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:
fltmgr!GetContextFromStreamList+99
fffff880`010bf039 488b4820 mov rcx,qword ptr [rax+20h]
CONTEXT: fffff8800a552990 -- (.cxr 0xfffff8800a552990)
rax=f7fff8a00c0c4f68 rbx=0000000000000000 rcx=fffffa8007b4a6d0
rdx=fffffa80075b7bb0 rsi=fffffa8007b4a720 rdi=fffffa8007b4a6d0
rip=fffff880010bf039 rsp=fffff8800a553370 rbp=fffff8800a5534b0
r8=0000000000000000 r9=fffff8800a5534a8 r10=fffffa8007b4a6d8
r11=0000000000000011 r12=fffff8800a5534a8 r13=fffffa8008ecccf0
r14=0000000000000000 r15=fffffa80075b7bb0
iopl=0 nv up ei ng nz na pe nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010282
fltmgr!GetContextFromStreamList+0x99:
fffff880`010bf039 488b4820 mov rcx,qword ptr [rax+20h] ds:002b:f7fff8a0`0c0c4f88=????????????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x3B
PROCESS_NAME: [B] APB.exe[/B]
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from fffff880010c9dbe to fffff880010bf039
FOLLOWUP_IP:
fileinfo!FIStreamGet+52
fffff880`0110f052 8bd8 mov ebx,eax
SYMBOL_STACK_INDEX: 2
SYMBOL_NAME: fileinfo!FIStreamGet+52
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: fileinfo
IMAGE_NAME: fileinfo.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc481
STACK_COMMAND: .cxr 0xfffff8800a552990 ; kb
FAILURE_BUCKET_ID: X64_0x3B_fileinfo!FIStreamGet+52
BUCKET_ID: X64_0x3B_fileinfo!FIStreamGet+52
Sat Dec 10 13:21:16.956 2011
STOP 0x0000001E: KMODE_EXCEPTION_NOT_HANDLED
Usual causes: Device driver, hardware, System service, compatibility, Remote control programs, memory, BIOS.
Bugcheck Analysis:
Code:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1E, {0, 0, 0, 0}
Probably caused by :[B] ntkrnlmp.exe[/B] ( nt!KiKernelCalloutExceptionHandler+e )
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:
+3038383932623437
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: [B] APB.exe[/B]
CURRENT_IRQL: 2
EXCEPTION_RECORD: fffff880009b05d8 -- (.exr 0xfffff880009b05d8)
ExceptionAddress: fffff800032e14f9 (nt!KiProcessExpiredTimerList+0x0000000000000129)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff
TRAP_FRAME: fffff880009b0680 -- (.trap 0xfffff880009b0680)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffa80086343e8 rbx=0000000000000000 rcx=f7fffa80086343e8
rdx=0000000000000102 rsi=0000000000000000 rdi=0000000000000000
rip=fffff800032e14f9 rsp=fffff880009b0810 rbp=fffffa8007de5688
r8=fffff88002fd7301 r9=0000000000000002 r10=000000000000009b
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
nt!KiProcessExpiredTimerList+0x129:
fffff800`032e14f9 48894108 mov qword ptr [rcx+8],rax ds:f7fffa80`086343f0=????????????????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff800032cd5fe to fffff800032d5c10
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!KiKernelCalloutExceptionHandler+e
fffff800`032cd5fe 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: 4e02aaa3
FAILURE_BUCKET_ID: X64_0x1E_0_nt!KiKernelCalloutExceptionHandler+e
BUCKET_ID: X64_0x1E_0_nt!KiKernelCalloutExceptionHandler+e
There's nothing jumping out at me in your latest dump files. APB.exe is mentioned in both dump files though. As hard as it may be, can you steer clear of cleaning up the streets for a while to see if you still get a blue screen? Say, give it a miss for 8 hours. Then try to play and see what happens.
After about 4 hours of no play you may want to enable driver verifier so that if there is a rogue driver, we can flush it out.
To start Driver Verifier:
- Create a restore point!!
- GoTo Start and in the Search or a Run... Window type
verifier and press
Enter.
- Select
Create custom settings (for code developers) and click
Next.
- Select
Select individual settings from a full list and click
Next.
- Select every option
EXCEPT for
Low Resource Simulation and click
Next.
- Select
Select driver names from a list and click
Next.
- Select all drivers listed that are
NOT provided by Microsoft and click
Next.
- Select
Finish on the next page.
Reboot the system and
wait for it to crash to the Blue Screen. If this happens as soon as Windows tries to start then try it in Safe Mode. Continue to use your system normally, if you know what causes the crash, do that repeatedly. The objective is to get the system to crash because Driver Verifier is stressing the drivers out and hopefully create a pattern.
On the extremely rare occasion that you can't get into Safe Mode, use System Restore from your installation DVD / Restore Disc to set the system back to the previous restore point that you created.
To turn off Driver Verifier when finished, Open a
Command Prompt or
Run... window and type
verifier /reset and press Enter/OK.
or
GoTo Start and in the Search or a Run... Window type
verifier. Select
Delete existing settings and press "Finish".
