[Løst] Maskina 'restarter' seg etter 35 min idle (blåskjerm før, men ikke nå lenger)

Hareide · 29. desember 2013

Når maskina min ikke har vært i bruk på (ca) nøyaktig 35 minutter, kommer det en blåskjerm. Dumpfil blir generert:

IRQL_NOT_LESS_OR_EQUAL 0x0000000a

00000000`00000000 00000000`00000002 00000000`00000000 fffff800`030XXXXX ntoskrnl.exe+75bc0

Kjørte memtest86+ i et døgn tidligere, men fikk ikke på skjermen når jeg skulle sjekke resultatet. (Har hatt litt problemer med dette lenge, har en teori om at det er relatert til bruk av displayport. Oppstått kun utenfor 'Windows', slik som memtest og spinrite).

Har et veldig godt eksempel fra at maskina stod på over natta i forrigårs (event viewer):

Level:		Date and Time:	Source:		EvtID:	TaskGr:	Time between:
Information	12.28.13 10:46	Kernel-General	12	None	00:35
Information	12.28.13 10:10	Kernel-General	12	None	00:35
Information	12.28.13 9:35	Kernel-General	12	None	00:35
Information	12.28.13 8:59	Kernel-General	12	None	00:35
Information	12.28.13 8:23	Kernel-General	12	None	00:35
Information	12.28.13 7:48	Kernel-General	12	None	00:37
Information	12.28.13 7:10	Kernel-General	12	None	00:35
Information	12.28.13 6:35	Kernel-General	12	None	00:35
Information	12.28.13 5:59	Kernel-General	12	None	00:35
Information	12.28.13 5:24	Kernel-General	12	None	00:35
Information	12.28.13 4:48	Kernel-General	12	None	00:35
Information	12.28.13 4:12	Kernel-General	12	None	00:35
Information	12.28.13 3:37	Kernel-General	12	None	00:35
Information	12.28.13 3:01	Kernel-General	12	None	00:35
Information	12.28.13 2:25	Kernel-General	12	None	00:35
Information	12.28.13 1:50	Kernel-General	12	None	00:35
Information	12.28.13 1:14	Kernel-General	12	None

(Finner ingen spor av hva som skjer før restarten, kun spor av at windows bootes på nytt)

Har nylig spillt gjennom et lass med spill, ingen problemer da (eller når maskina brukes).

Hardware:
CPU: Intel i5 2500k
HK: P8Z77-V LE PLUS (Bios version 0905)
PSU: Newton R3 600W (kjøpt for 2 mnd siden, semi passiv vifte)
GPU: Sapphire HD 5870 1GB
RAM: 2x 4GB 
SSD: Corsair Force Series GT 120GB (OS, ca 1 år gammel)
HD: Hitachi 2TB (HDS722020ALA330)
(alt er over 2 år gammelt, med unntak av SSD og PSU)

OS: Windows 7 64bit

Ser at jeg oppdaterte GPU driver 01.12.2013:

Driver Packaging Version		13.152.1.8-131008a-163824C-ATI
Catalyst Version			13.9
Provider				Advanced Micro Devices, Inc.
2D Driver Version			8.01.01.1331
Direct3D Version			9.14.10.0984
OpenGL Version				6.14.10.12430
AMD Catalyst Control Center Version	2013.1008.932.15229

Windbg

Minidump:

Microsoft ® Windows Debugger Version 6.12.0002.633 AMD64
Copyright © Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Users\PKH\Desktop\Blåskjerm\121813-15818-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: srv*c:\symboler*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.18247.amd64fre.win7sp1_gdr.130828-1532
Machine Name:
Kernel base = 0xfffff800`03012000 PsLoadedModuleList = 0xfffff800`032556d0
Debug session time: Wed Dec 18 08:55:09.533 2013 (UTC + 1:00)
System Uptime: 0 days 0:24:50.735
Loading Kernel Symbols
...............................................................
................................................................
..........................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {0, 2, 0, fffff8000309ca55}

Probably caused by : CLFS.SYS ( CLFS!CClfsLogFcbPhysical::MapCacheData+105 )

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: 0000000000000000, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, 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: fffff8000309ca55, address which referenced memory

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

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800032bf100
0000000000000000

CURRENT_IRQL: 2

FAULTING_IP:
nt!IopCompleteRequest+ae5
fffff800`0309ca55 488b09 mov rcx,qword ptr [rcx]

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0xA

PROCESS_NAME: TrustedInstall

IRP_ADDRESS: ffffffffffffff89

TRAP_FRAME: fffff880042f85b0 -- (.trap 0xfffff880042f85b0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=000000000000000f rbx=0000000000000000 rcx=000000000000003f
rdx=fffff980450c0000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80003384c07 rsp=fffff880042f8740 rbp=fffffa80148be9b8
r8=000000000000000f r9=fffffa8006663540 r10=fffffa8006663008
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na po nc
nt!CcMapData+0x117:
fffff800`03384c07 0fb602 movzx eax,byte ptr [rdx] ds:fffff980`450c0000=??
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff80003087169 to fffff80003087bc0

STACK_TEXT:
fffff880`042f7ff8 fffff800`03087169 : 00000000`0000000a 00000000`00000000 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`042f8000 fffff800`03085de0 : fffff880`0cb04000 00000000`00000000 fffffa80`06fe6990 fffffa80`0a8c3260 : nt!KiBugCheckDispatch+0x69
fffff880`042f8140 fffff800`0309ca55 : 00000000`00000001 fffff800`030b6687 fffffa80`20206f49 fffffa80`010f1460 : nt!KiPageFault+0x260
fffff880`042f82d0 fffff800`0307a5f7 : 00000000`00000001 fffffa80`1367b2f0 fffff880`042f8300 fffff800`00000000 : nt!IopCompleteRequest+0xae5
fffff880`042f83a0 fffff800`03035ec9 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDeliverApc+0x1c7
fffff880`042f8420 fffff800`0309585c : 00000000`00000000 00000000`00000000 ffffffff`ffffffff 00000000`00000000 : nt!KiCheckForKernelApcDelivery+0x25
fffff880`042f8450 fffff800`03085cee : 00000000`00000000 fffff980`450c0000 00000000`00000000 00000000`0000000e : nt!MmAccessFault+0x1a3c
fffff880`042f85b0 fffff800`03384c07 : 00000000`00000000 00000000`00000000 fffff880`042f8808 fffff880`042f8800 : nt!KiPageFault+0x16e
fffff880`042f8740 fffff880`00d1db19 : 00000000`00040000 fffffa80`144be010 fffffa80`148be9b8 00000000`0000000e : nt!CcMapData+0x117
fffff880`042f8800 fffff880`00d4bd1f : fffffa80`0c146000 fffffa80`148be9b8 fffff880`042f8970 fffff8a0`00040000 : CLFS!CClfsLogFcbPhysical::MapCacheData+0x105
fffff880`042f88b0 fffff880`00d17454 : fffffa80`0c146000 fffffa80`072a64f0 fffff880`00000100 00000000`00000000 : CLFS!CClfsLogFcbPhysical::FindEndOfLog+0x257
fffff880`042f89e0 fffff880`00d3cd9e : fffffa80`0c146000 fffffa80`148be9b8 fffffa80`148be820 00000000`0012019f : CLFS!CClfsLogFcbPhysical::Initialize+0xa4c
fffff880`042f8b30 fffff880`00d3c4e6 : fffffa80`0a8a6680 fffff880`042f8d01 00000000`00000007 fffffa80`06750100 : CLFS!CClfsRequest::Create+0x406
fffff880`042f8c70 fffff880`00d58657 : fffffa80`0a8a6680 fffffa80`06a09000 00000000`00000000 00000000`000007ff : CLFS!CClfsRequest::Dispatch+0x12a
fffff880`042f8ce0 fffff880`00d30a09 : fffffa80`133d2930 fffffa80`0c135a60 fffffa80`133d2930 fffffa80`1396e230 : CLFS!ClfsDispatchIoRequest+0x1cb
fffff880`042f8d30 fffff800`0338743c : 00000000`00000004 fffffa80`148be9b8 fffffa80`0c135a60 fffffa80`0c135af8 : CLFS!CClfsDriver::LogIoDispatch+0x21
fffff880`042f8d60 fffff800`03382db8 : fffffa80`06a09060 fffff800`00000000 fffffa80`148be800 fffff8a0`00000000 : nt!IopParseDevice+0x14d3
fffff880`042f8ec0 fffff800`03383fd6 : 00000000`00000000 fffffa80`148be800 fffffa80`00000060 fffffa80`067543f0 : nt!ObpLookupObjectName+0x588
fffff880`042f8fb0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!ObOpenObjectByName+0x306

STACK_COMMAND: kb

FOLLOWUP_IP:
CLFS!CClfsLogFcbPhysical::MapCacheData+105
fffff880`00d1db19 448ae8 mov r13b,al

SYMBOL_STACK_INDEX: 9

SYMBOL_NAME: CLFS!CClfsLogFcbPhysical::MapCacheData+105

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: CLFS

IMAGE_NAME: CLFS.SYS

DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc11d

FAILURE_BUCKET_ID: X64_0xA_CLFS!CClfsLogFcbPhysical::MapCacheData+105

BUCKET_ID: X64_0xA_CLFS!CClfsLogFcbPhysical::MapCacheData+105

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: 0000000000000000, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, 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: fffff8000309ca55, address which referenced memory

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

READ_ADDRESS: 0000000000000000

CURRENT_IRQL: 2

FAULTING_IP:
nt!IopCompleteRequest+ae5
fffff800`0309ca55 488b09 mov rcx,qword ptr [rcx]

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0xA

PROCESS_NAME: TrustedInstall

IRP_ADDRESS: ffffffffffffff89

TRAP_FRAME: fffff880042f85b0 -- (.trap 0xfffff880042f85b0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=000000000000000f rbx=0000000000000000 rcx=000000000000003f
rdx=fffff980450c0000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80003384c07 rsp=fffff880042f8740 rbp=fffffa80148be9b8
r8=000000000000000f r9=fffffa8006663540 r10=fffffa8006663008
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na po nc
nt!CcMapData+0x117:
fffff800`03384c07 0fb602 movzx eax,byte ptr [rdx] ds:fffff980`450c0000=??
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff80003087169 to fffff80003087bc0

STACK_TEXT:
fffff880`042f7ff8 fffff800`03087169 : 00000000`0000000a 00000000`00000000 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`042f8000 fffff800`03085de0 : fffff880`0cb04000 00000000`00000000 fffffa80`06fe6990 fffffa80`0a8c3260 : nt!KiBugCheckDispatch+0x69
fffff880`042f8140 fffff800`0309ca55 : 00000000`00000001 fffff800`030b6687 fffffa80`20206f49 fffffa80`010f1460 : nt!KiPageFault+0x260
fffff880`042f82d0 fffff800`0307a5f7 : 00000000`00000001 fffffa80`1367b2f0 fffff880`042f8300 fffff800`00000000 : nt!IopCompleteRequest+0xae5
fffff880`042f83a0 fffff800`03035ec9 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDeliverApc+0x1c7
fffff880`042f8420 fffff800`0309585c : 00000000`00000000 00000000`00000000 ffffffff`ffffffff 00000000`00000000 : nt!KiCheckForKernelApcDelivery+0x25
fffff880`042f8450 fffff800`03085cee : 00000000`00000000 fffff980`450c0000 00000000`00000000 00000000`0000000e : nt!MmAccessFault+0x1a3c
fffff880`042f85b0 fffff800`03384c07 : 00000000`00000000 00000000`00000000 fffff880`042f8808 fffff880`042f8800 : nt!KiPageFault+0x16e
fffff880`042f8740 fffff880`00d1db19 : 00000000`00040000 fffffa80`144be010 fffffa80`148be9b8 00000000`0000000e : nt!CcMapData+0x117
fffff880`042f8800 fffff880`00d4bd1f : fffffa80`0c146000 fffffa80`148be9b8 fffff880`042f8970 fffff8a0`00040000 : CLFS!CClfsLogFcbPhysical::MapCacheData+0x105
fffff880`042f88b0 fffff880`00d17454 : fffffa80`0c146000 fffffa80`072a64f0 fffff880`00000100 00000000`00000000 : CLFS!CClfsLogFcbPhysical::FindEndOfLog+0x257
fffff880`042f89e0 fffff880`00d3cd9e : fffffa80`0c146000 fffffa80`148be9b8 fffffa80`148be820 00000000`0012019f : CLFS!CClfsLogFcbPhysical::Initialize+0xa4c
fffff880`042f8b30 fffff880`00d3c4e6 : fffffa80`0a8a6680 fffff880`042f8d01 00000000`00000007 fffffa80`06750100 : CLFS!CClfsRequest::Create+0x406
fffff880`042f8c70 fffff880`00d58657 : fffffa80`0a8a6680 fffffa80`06a09000 00000000`00000000 00000000`000007ff : CLFS!CClfsRequest::Dispatch+0x12a
fffff880`042f8ce0 fffff880`00d30a09 : fffffa80`133d2930 fffffa80`0c135a60 fffffa80`133d2930 fffffa80`1396e230 : CLFS!ClfsDispatchIoRequest+0x1cb
fffff880`042f8d30 fffff800`0338743c : 00000000`00000004 fffffa80`148be9b8 fffffa80`0c135a60 fffffa80`0c135af8 : CLFS!CClfsDriver::LogIoDispatch+0x21
fffff880`042f8d60 fffff800`03382db8 : fffffa80`06a09060 fffff800`00000000 fffffa80`148be800 fffff8a0`00000000 : nt!IopParseDevice+0x14d3
fffff880`042f8ec0 fffff800`03383fd6 : 00000000`00000000 fffffa80`148be800 fffffa80`00000060 fffffa80`067543f0 : nt!ObpLookupObjectName+0x588
fffff880`042f8fb0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!ObOpenObjectByName+0x306

STACK_COMMAND: kb

FOLLOWUP_IP:
CLFS!CClfsLogFcbPhysical::MapCacheData+105
fffff880`00d1db19 448ae8 mov r13b,al

SYMBOL_STACK_INDEX: 9

SYMBOL_NAME: CLFS!CClfsLogFcbPhysical::MapCacheData+105

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: CLFS

IMAGE_NAME: CLFS.SYS

DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc11d

FAILURE_BUCKET_ID: X64_0xA_CLFS!CClfsLogFcbPhysical::MapCacheData+105

BUCKET_ID: X64_0xA_CLFS!CClfsLogFcbPhysical::MapCacheData+105

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

Fulldump:

Microsoft ® Windows Debugger Version 6.12.0002.633 AMD64
Copyright © Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Users\PKH\Desktop\Blåskjerm\MEMORY.DMP]
Kernel Summary Dump File: Only kernel address space is available

Symbol search path is: srv*c:\symboler*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.18247.amd64fre.win7sp1_gdr.130828-1532
Machine Name:
Kernel base = 0xfffff800`03012000 PsLoadedModuleList = 0xfffff800`032556d0
Debug session time: Wed Dec 18 08:55:09.533 2013 (UTC + 1:00)
System Uptime: 0 days 0:24:50.735
Loading Kernel Symbols
...............................................................
................................................................
..........................................
Loading User Symbols
PEB is paged out (Peb.Ldr = 000007ff`fffd5018). Type ".hh dbgerr001" for details
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {0, 2, 0, fffff8000309ca55}

Probably caused by : CLFS.SYS ( CLFS!CClfsLogFcbPhysical::MapCacheData+105 )

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: 0000000000000000, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, 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: fffff8000309ca55, address which referenced memory

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

READ_ADDRESS: 0000000000000000

CURRENT_IRQL: 2

FAULTING_IP:
nt!IopCompleteRequest+ae5
fffff800`0309ca55 488b09 mov rcx,qword ptr [rcx]

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0xA

PROCESS_NAME: TrustedInstall

IRP_ADDRESS: ffffffffffffff89

TRAP_FRAME: fffff880042f85b0 -- (.trap 0xfffff880042f85b0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=000000000000000f rbx=0000000000000000 rcx=000000000000003f
rdx=fffff980450c0000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80003384c07 rsp=fffff880042f8740 rbp=fffffa80148be9b8
r8=000000000000000f r9=fffffa8006663540 r10=fffffa8006663008
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na po nc
nt!CcMapData+0x117:
Page 5e2b3 not present in the dump file. Type ".hh dbgerr004" for details
fffff800`03384c07 0fb602 movzx eax,byte ptr [rdx] ds:fffff980`450c0000=??
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff80003087169 to fffff80003087bc0

STACK_TEXT:
fffff880`042f7ff8 fffff800`03087169 : 00000000`0000000a 00000000`00000000 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`042f8000 fffff800`03085de0 : fffff880`0cb04000 00000000`00000000 fffffa80`06fe6990 fffffa80`0a8c3260 : nt!KiBugCheckDispatch+0x69
fffff880`042f8140 fffff800`0309ca55 : 00000000`00000001 fffff800`030b6687 fffffa80`20206f49 fffffa80`010f1460 : nt!KiPageFault+0x260
fffff880`042f82d0 fffff800`0307a5f7 : 00000000`00000001 fffffa80`1367b2f0 fffff880`042f8300 fffff800`00000000 : nt!IopCompleteRequest+0xae5
fffff880`042f83a0 fffff800`03035ec9 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDeliverApc+0x1c7
fffff880`042f8420 fffff800`0309585c : 00000000`00000000 00000000`00000000 ffffffff`ffffffff 00000000`00000000 : nt!KiCheckForKernelApcDelivery+0x25
fffff880`042f8450 fffff800`03085cee : 00000000`00000000 fffff980`450c0000 00000000`00000000 00000000`0000000e : nt!MmAccessFault+0x1a3c
fffff880`042f85b0 fffff800`03384c07 : 00000000`00000000 00000000`00000000 fffff880`042f8808 fffff880`042f8800 : nt!KiPageFault+0x16e
fffff880`042f8740 fffff880`00d1db19 : 00000000`00040000 fffffa80`144be010 fffffa80`148be9b8 00000000`0000000e : nt!CcMapData+0x117
fffff880`042f8800 fffff880`00d4bd1f : fffffa80`0c146000 fffffa80`148be9b8 fffff880`042f8970 fffff8a0`00040000 : CLFS!CClfsLogFcbPhysical::MapCacheData+0x105
fffff880`042f88b0 fffff880`00d17454 : fffffa80`0c146000 fffffa80`072a64f0 fffff880`00000100 00000000`00000000 : CLFS!CClfsLogFcbPhysical::FindEndOfLog+0x257
fffff880`042f89e0 fffff880`00d3cd9e : fffffa80`0c146000 fffffa80`148be9b8 fffffa80`148be820 00000000`0012019f : CLFS!CClfsLogFcbPhysical::Initialize+0xa4c
fffff880`042f8b30 fffff880`00d3c4e6 : fffffa80`0a8a6680 fffff880`042f8d01 00000000`00000007 fffffa80`06750100 : CLFS!CClfsRequest::Create+0x406
fffff880`042f8c70 fffff880`00d58657 : fffffa80`0a8a6680 fffffa80`06a09000 00000000`00000000 00000000`000007ff : CLFS!CClfsRequest::Dispatch+0x12a
fffff880`042f8ce0 fffff880`00d30a09 : fffffa80`133d2930 fffffa80`0c135a60 fffffa80`133d2930 fffffa80`1396e230 : CLFS!ClfsDispatchIoRequest+0x1cb
fffff880`042f8d30 fffff800`0338743c : 00000000`00000004 fffffa80`148be9b8 fffffa80`0c135a60 fffffa80`0c135af8 : CLFS!CClfsDriver::LogIoDispatch+0x21
fffff880`042f8d60 fffff800`03382db8 : fffffa80`06a09060 fffff800`00000000 fffffa80`148be800 fffff8a0`00000000 : nt!IopParseDevice+0x14d3
fffff880`042f8ec0 fffff800`03383fd6 : 00000000`00000000 fffffa80`148be800 fffffa80`00000060 fffffa80`067543f0 : nt!ObpLookupObjectName+0x588
fffff880`042f8fb0 fffff800`033858dc : fffffa80`135be900 00000000`00000000 fffff8a0`052aea00 00000000`000007ff : nt!ObOpenObjectByName+0x306
fffff880`042f9080 fffff800`0332dcab : fffff880`042f9308 00000000`c0000000 fffff880`042f9390 fffff880`042f9370 : nt!IopCreateFile+0x2bc
fffff880`042f9120 fffff800`033058d5 : fffff880`042f9370 fffff880`042f9308 00000000`c0000000 fffff880`042f9390 : nt!IoCreateFileEx+0xfb
fffff880`042f91c0 fffff880`00d58fcd : 00000000`00000000 00000000`00000010 fffff880`00d64ee0 00000000`00000001 : nt!IoCreateFileSpecifyDeviceObjectHint+0xe5
fffff880`042f9270 fffff800`03304622 : fffff880`042f9500 00000000`00000074 00000000`00000010 fffff8a0`1983b250 : CLFS!ClfsCreateLogFile+0x901
fffff880`042f9460 fffff800`0330548a : 00000000`00000000 fffff8a0`2144b010 00000000`00000001 fffff800`0328e5e0 : nt!CmpInitCmRM+0x372
fffff880`042f9640 fffff800`03304f17 : fffff8a0`00000020 fffff880`042f9960 00000000`00000000 00000000`00000021 : nt!CmLoadKey+0x452
fffff880`042f9830 fffff800`03305a60 : 0000007f`fffffff8 00000000`00d7de00 00000000`00000000 00000000`00000000 : nt!NtLoadKeyEx+0x4c5
fffff880`042f9a90 fffff800`03086e53 : 00000000`00000008 00000000`76fd46bb 00000000`00000001 00000000`00000000 : nt!NtLoadKey+0x24
fffff880`042f9ae0 00000000`770020ba : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`00d7dda8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x770020ba

STACK_COMMAND: kb

FOLLOWUP_IP:
CLFS!CClfsLogFcbPhysical::MapCacheData+105
fffff880`00d1db19 448ae8 mov r13b,al

SYMBOL_STACK_INDEX: 9

SYMBOL_NAME: CLFS!CClfsLogFcbPhysical::MapCacheData+105

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: CLFS

IMAGE_NAME: CLFS.SYS

DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc11d

FAILURE_BUCKET_ID: X64_0xA_CLFS!CClfsLogFcbPhysical::MapCacheData+105

BUCKET_ID: X64_0xA_CLFS!CClfsLogFcbPhysical::MapCacheData+105

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

Har litt problemer med hvor en bør starte feilsøking (driver > 1xRAM > PSU > memtest > test idle i BIOS ..).

Noen som har et godt tips?

Forsøkt:

Kjørt maskina med kun 1 rambrikke (prøvd begge 2, i forskjellige slotter)
Sleep/hibernate/screen saver/display off/hd shutdown = deaktivert
Idle i BIOS (får da ikke blåskjem)
Resatt bios

Edit:

Ser nå at jeg har endra fra minidump til fulldump ved blåskjerm. Derfor det ikke kom fram i bluescreenview 'plutselig'. Har dermed trolig fått blåskjerm hele tiden, har endra på posten til å gjenspeile dette.

Endret 30. desember 2013 av Hareide

SteinarN · 29. desember 2013

Ser det går 35 min mellom hver gang. Hva har du i tidsinnstillinger for sleep/dvale osv? Jeg har vært borti noe lignende hvor maskinen gikk ut av sleep nesten med en gang pga noe som jeg aldri fant ordentlig ut av. Kanskje prøve å slå av sleep/dvale og se om maskinen restarter da når den får stå for seg selv ubrukt.

Hareide · 29. desember 2013

Ser det går 35 min mellom hver gang. Hva har du i tidsinnstillinger for sleep/dvale osv? Jeg har vært borti noe lignende hvor maskinen gikk ut av sleep nesten med en gang pga noe som jeg aldri fant ordentlig ut av. Kanskje prøve å slå av sleep/dvale og se om maskinen restarter da når den får stå for seg selv ubrukt.

Takk for tipset, men jeg sjekka dette tidligere i dag. Har dobbelsjekka det nå, og alt slikt er deaktivert.

Gjorde noen små endringer inni der nå, men har ikke store håpet om bedringer:

'Allow hybrid sleep: On -> Off'

'Turn off hard disk after: 20 min => Never'

'Turn off display after: 1 min => Never'

Hareide · 30. desember 2013

Googla litt etter infoen i Windbg, kom fram til at jeg opplever det samme som i denne tråden om: ("windbg clfs TrustedInstall IRQL_NOT_LESS_OR_EQUAL")

IRQ_NOT_LESS_OR_EQUAL (a)

Der skyldes det på 'Software Certification Toolkit' versjon 3.5.0.0 (eller bare 'Certification Tool'), som jeg "tilfeldigvis" installerte dette 11.12.2013.

Skal nå prøve å avinstallere certification tool og gjøre følgende endring i regedit:

"

I would suggest to stop the Systrace.sys driver from loading by doing the following:

Open regedit and navigate to the following registry key:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\SysTrace

At that key in the right window double-click Start and change the Value data to 4 which should disable Systrace.

Create a System Restore Point beforehand and restart the computer afterward.

Hopefully that should prevent any further BSODs.

"

Endret 30. desember 2013 av Hareide

Hareide · 30. desember 2013

Uninstall av MS 'Software Certification Toolkit' var ikke nok, måtte inn i regedit å gjøre endringen ovenfor.

Men nå har maskina vært påslått uten reboot i over 10 timer, IDLE.

Da er vel denne løst.

Mye takk til: Hvordan DU kan feilsøke Windows! (Guider)

Endret 30. desember 2013 av Hareide

Logg inn

[Løst] Maskina 'restarter' seg etter 35 min idle (blåskjerm før, men ikke nå lenger)

Anbefalte innlegg

Hareide

Lenke til kommentar

Videoannonse

SteinarN

Lenke til kommentar

Hareide

Lenke til kommentar

Hareide

Lenke til kommentar

Hareide

Lenke til kommentar

Opprett en konto eller logg inn for å kommentere

Opprett konto

Logg inn

Populær nå

Nei til pride 2024! 1 2 3 4 14

Woke i moderne underholdningsindustri 1 2 3 4 161

Hvem er aktive 0 medlemmer