Help bsod

[suurtje]

Every few days i get a blu screen of dead.

My other computer whas 4 weeks old when that started.
Back to the shop got a new hard drive, back home same problems.

Gotten sick of it and in december i bought a new Acer Inspire.

After three weeks same problem.

Every few day a BSOD with the same message.

Microsoft-Windows-Kernel-Power
[ Guid] {331C3B3A-2005-44C2-AC5E-77220C37D6B4}
Logboeknaam: System
Bron: Microsoft-Windows-Kernel-Power
Datum: 1-2-2012 13:16:29
Gebeurtenis-id:41
Taakcategorie: (63)
Niveau: Kritiek
Trefwoorden: (2)
Gebruiker: SYSTEM
Computer: ria-PC
Beschrijving:
Het systeem is opnieuw opgestart zonder eerst correct te worden afgesloten. Deze fout is mogelijk veroorzaakt doordat het systeem niet meer reageert of is vastgelopen of doordat de stroom is uitgevallen.
Gebeurtenis-XML:
<Event xmlns="Error">
<System>
<Provider Name="Microsoft-Windows-Kernel-Power" Guid="{331C3B3A-2005-44C2-AC5E-77220C37D6B4}" />
<EventID>41</EventID>
<Version>2</Version>
<Level>1</Level>
<Task>63</Task>
<Opcode>0</Opcode>
<Keywords>0x8000000000000002</Keywords>
<TimeCreated SystemTime="2012-02-01T12:16:29.456014000Z" />
<EventRecordID>24895</EventRecordID>
<Correlation />
<Execution ProcessID="4" ThreadID="8" />
<Channel>System</Channel>
<Computer>ria-PC</Computer>
<Security UserID="S-1-5-18" />
</System>
<EventData>
<Data Name="BugcheckCode">209</Data>
<Data Name="BugcheckParameter1">0x1327310</Data>
<Data Name="BugcheckParameter2">0x2</Data>
<Data Name="BugcheckParameter3">0x0</Data>
<Data Name="BugcheckParameter4">0xfffff9600001992a</Data>
<Data Name="SleepInProgress">false</Data>
<Data Name="PowerButtonTimestamp">0</Data>
</EventData>
</Event>

Please help me. Don't know what to do anymore

 

[zigzag3143]

We do need the DMP file as it contains the only record of the sequence of events leading up to the crash, what drivers were loaded, and what was responsible.

If you are overclocking STOP

You may be able to get the DMP files without crashing by booting into safe mode (F8) with networking.

To enable us to assist you with your computer's BSOD symptoms, upload the contents of your "\Windows\Minidump" folder.

The procedure:

* Copy the contents of \Windows\Minidump to another (temporary) location somewhere on your machine.
* Zip up the copy.
* Attach the ZIP archive to your post using the "paperclip" (file attachments) button.
*If the files are too large please upload them to a file sharing service like "Rapidshare" and put a link to them in your reply.

To ensure minidumps are enabled:

* Go to Start, in the Search Box type: sysdm.cpl, press Enter.
* Under the Advanced tab, click on the Startup and Recovery Settings... button.
* Ensure that Automatically restart is unchecked.
* Under the Write Debugging Information header select Small memory dump (256 kB) in the dropdown box (the 256kb varies).
* Ensure that the Small Dump Directory is listed as %systemroot%\Minidump.
* OK your way out.
* Reboot if changes have been made.

 

[suurtje]

There you go.

Almost a year the same message.

 

[suurtje]

Somebody?

 

[zigzag3143]

It is much easier to find patterns, etc, when there are more than one crash.

We prefer you wait until you have at least two so that if one is corrupt the other probably wont be.

 

[suurtje]

More than one crash? This is going one for one year now.
Every week i have at least 2 or 3 crashes.
Al the same event.

 

[suurtje]

12, 17, 24, 25, 25 january. The last at 1 february.

On my other computer it is exactly the same.

 

[writhziden]

If you follow the http://www.sevenforums.com/crashes-debugging/96879-blue-screen-death-bsod-posting-instructions.html to upload all your crash reports, there would be more information to allow those of us helping to provide better troubleshooting.

 

[suurtje]

Hereby screen.

 

[suurtje]

and al the dumpfiles of the new computer

 

[suurtje]

On my old computer (8 months old) exact the same problem.

 

[writhziden]

[list=1]
[*]

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [G:\Kingston\BSODDmpFiles\suurtje\012612-15662-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 (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`02e0e000 PsLoadedModuleList = 0xfffff800`03053670
Debug session time: Thu Jan 26 13:50:34.784 2012 (GMT-7)
System Uptime: 0 days 14:38:25.658
Loading Kernel Symbols
...............................................................
................................................................
.......................
Loading User Symbols
Loading unloaded module list
..........................................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck C2, {7, 109b, e058, fffffa800878bc00}

GetPointerFromAddress: unable to read from fffff800030bd100
Probably caused by : ntkrnlmp.exe ( nt!ExDeleteResourceLite+1a2 )

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

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

BAD_POOL_CALLER (c2)
The current thread is making a bad pool request.  Typically this is at a bad IRQL level or double freeing the same allocation, etc.
Arguments:
Arg1: 0000000000000007, Attempt to free pool which was already freed
Arg2: 000000000000109b, (reserved)
Arg3: 000000000000e058, Memory contents of the pool block
Arg4: fffffa800878bc00, Address of the block of pool being deallocated

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


POOL_ADDRESS:  fffffa800878bc00 

FREED_POOL_TAG:  Vad 

BUGCHECK_STR:  0xc2_7_Vad 

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff80002fb8be9 to fffff80002e8ac40

STACK_TEXT:  
fffff880`0911efb8 fffff800`02fb8be9 : 00000000`000000c2 00000000`00000007 00000000`0000109b 00000000`0000e058 : nt!KeBugCheckEx
fffff880`0911efc0 fffff800`02e68b42 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!ExDeferredFreePool+0x1201
fffff880`0911f070 fffff800`02e9efea : 00000000`ffffffff fffff880`0911f1f8 00000000`00000001 fffff8a0`01a8e001 : nt!ExDeleteResourceLite+0x1a2
fffff880`0911f0d0 fffff800`02e7092f : fffffa80`07252410 fffff880`0911f1f8 00000000`00000000 fffffa80`07252410 : nt!CcUnpinFileDataEx+0x3fa
fffff880`0911f150 fffff800`02ecc6cb : fffffa80`0725dbe8 fffff880`0911f2d8 00000000`00001000 00000000`00000000 : nt!CcReleaseByteRangeFromWrite+0xa7
fffff880`0911f1a0 fffff880`012a06d4 : fffffa80`0725dbe8 00000000`00000000 fffff8a0`00000000 00000000`00001000 : nt!CcFlushCache+0x64b
fffff880`0911f2a0 fffff880`012964e3 : 00000000`00000000 fffff8a0`01a8c140 00000000`00000000 00000000`00000001 : Ntfs!NtfsFlushUserStream+0xb4
fffff880`0911f320 fffff880`0129efad : fffffa80`18a08d90 fffffa80`06df4180 00000000`00100001 00000000`00000000 : Ntfs!NtfsFlushVolume+0x2c7
fffff880`0911f450 fffff880`0129f6b4 : fffffa80`18a08d90 fffffa80`18dd2010 fffffa80`08e41b80 00000000`00000000 : Ntfs!NtfsCommonFlushBuffers+0x459
fffff880`0911f530 fffff880`01002bcf : fffffa80`18dd2368 fffffa80`18dd2010 fffffa80`18a08d90 fffff880`0911f558 : Ntfs!NtfsFsdFlushBuffers+0x104
fffff880`0911f5a0 fffff880`010016df : fffffa80`06646be0 00000000`00000000 fffffa80`06646b00 fffffa80`18dd2010 : fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x24f
fffff880`0911f630 fffff800`0319321b : 00000000`00000002 fffffa80`08e41b80 00000000`00000000 fffffa80`18dd2010 : fltmgr!FltpDispatch+0xcf
fffff880`0911f690 fffff800`03127b85 : fffffa80`18dd2010 fffffa80`18186660 fffffa80`08e41b80 fffff880`03165180 : nt!IopSynchronousServiceTail+0xfb
fffff880`0911f700 fffff800`02e89ed3 : fffffa80`18186660 fffffa80`03cc9040 fffffa80`06646be0 fffffa80`08e41b80 : nt!NtFlushBuffersFile+0x171
fffff880`0911f790 fffff800`02e86470 : fffff800`030cc89d 00000000`00000001 00000000`00000000 fffff8a0`045eaed8 : nt!KiSystemServiceCopyEnd+0x13
fffff880`0911f928 fffff800`030cc89d : 00000000`00000001 00000000`00000000 fffff8a0`045eaed8 fffffa80`0ae61af0 : nt!KiServiceLinkage
fffff880`0911f930 fffff800`03125fee : fffff880`06493550 fffffa80`18186660 00000000`00000080 00000000`00000001 : nt!PopFlushVolumeWorker+0x1bd
fffff880`0911fc00 fffff800`02e7c5e6 : fffff880`03165180 fffffa80`18186660 fffff880`0316ffc0 fffff880`01229cb0 : nt!PspSystemThreadStartup+0x5a
fffff880`0911fc40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!ExDeleteResourceLite+1a2
fffff800`02e68b42 33c0            xor     eax,eax

SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  nt!ExDeleteResourceLite+1a2

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4e02aaa3

FAILURE_BUCKET_ID:  X64_0xc2_7_Vad__nt!ExDeleteResourceLite+1a2

BUCKET_ID:  X64_0xc2_7_Vad__nt!ExDeleteResourceLite+1a2

Followup: MachineOwner
---------
[*]
Loading Dump File [G:\Kingston\BSODDmpFiles\suurtje\012512-13634-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 (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`02e16000 PsLoadedModuleList = 0xfffff800`0305b670
Debug session time: Wed Jan 25 11:58:08.126 2012 (GMT-7)
System Uptime: 0 days 12:50:53.001
Loading Kernel Symbols
...............................................................
................................................................
.......................
Loading User Symbols
Loading unloaded module list
..........................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck C2, {b, fffffa8015c97090, c8, fffffa8015c97f20}

Probably caused by : ntkrnlmp.exe ( nt!ExDeleteResourceLite+1a2 )

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

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

BAD_POOL_CALLER (c2)
The current thread is making a bad pool request.  Typically this is at a bad IRQL level or double freeing the same allocation, etc.
Arguments:
Arg1: 000000000000000b, type of pool violation the caller is guilty of.
Arg2: fffffa8015c97090
Arg3: 00000000000000c8
Arg4: fffffa8015c97f20

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


FAULTING_IP: 
nt!ExDeleteResourceLite+1a2
fffff800`02e70b42 33c0            xor     eax,eax

BUGCHECK_STR:  0xc2_b

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff80002fc0c93 to fffff80002e92c40

STACK_TEXT:  
fffff880`07ed5728 fffff800`02fc0c93 : 00000000`000000c2 00000000`0000000b fffffa80`15c97090 00000000`000000c8 : nt!KeBugCheckEx
fffff880`07ed5730 fffff800`02e70b42 : 00000000`00000000 00000000`00001000 00000000`00000000 00000000`00000015 : nt!ExDeferredFreePool+0x12bf
fffff880`07ed57e0 fffff800`02ea6fea : 00000000`ffffffff fffff880`07ed5968 00000000`00000001 fffff8a0`0035e0b0 : nt!ExDeleteResourceLite+0x1a2
fffff880`07ed5840 fffff800`02e7892f : fffffa80`064a9b20 fffff880`07ed5968 00000000`00000001 fffffa80`064a9b20 : nt!CcUnpinFileDataEx+0x3fa
fffff880`07ed58c0 fffff800`02ed46cb : 00000000`002d3dba fffff880`07ed5b18 00000000`00001000 00000000`00000000 : nt!CcReleaseByteRangeFromWrite+0xa7
fffff880`07ed5910 fffff800`02ed7f76 : fffffa80`066b4850 00000000`00000001 fffffa80`00000001 fffffa80`00001000 : nt!CcFlushCache+0x64b
fffff880`07ed5a10 fffff800`02ed8938 : fffffa80`00000000 fffff880`07ed5b18 fffffa80`06c78b50 fffff800`030948b8 : nt!CcWriteBehind+0x1c6
fffff880`07ed5ac0 fffff800`02e9d001 : fffffa80`03d427e0 fffff800`03189901 fffff800`030948c0 fffffa80`00000000 : nt!CcWorkerThread+0x1c8
fffff880`07ed5b70 fffff800`0312dfee : fffff880`0337dde8 fffffa80`11a6e3c0 00000000`00000080 fffffa80`03cc9040 : nt!ExpWorkerThread+0x111
fffff880`07ed5c00 fffff800`02e845e6 : fffff880`031d7180 fffffa80`11a6e3c0 fffffa80`03d42b60 fffff880`0125d384 : nt!PspSystemThreadStartup+0x5a
fffff880`07ed5c40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!ExDeleteResourceLite+1a2
fffff800`02e70b42 33c0            xor     eax,eax

SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  nt!ExDeleteResourceLite+1a2

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4e02aaa3

FAILURE_BUCKET_ID:  X64_0xc2_b_nt!ExDeleteResourceLite+1a2

BUCKET_ID:  X64_0xc2_b_nt!ExDeleteResourceLite+1a2

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

[*]
Loading Dump File [G:\Kingston\BSODDmpFiles\suurtje\012412-14289-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 (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`02e10000 PsLoadedModuleList = 0xfffff800`03055670
Debug session time: Tue Jan 24 13:19:39.245 2012 (GMT-7)
System Uptime: 0 days 14:12:07.119
Loading Kernel Symbols
...............................................................
................................................................
........................
Loading User Symbols
Loading unloaded module list
.............................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {0, 2, 1, fffff80002e6d3e3}

Probably caused by : ntkrnlmp.exe ( nt!KeSetEventBoostPriority+3f )

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

1: 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: 0000000000000001, 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: fffff80002e6d3e3, address which referenced memory

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


WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800030bf100
 0000000000000000 

CURRENT_IRQL:  2

FAULTING_IP: 
nt!KeSetEventBoostPriority+3f
fffff800`02e6d3e3 f00fba2907      lock bts dword ptr [rcx],7

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  iexplore.exe

TRAP_FRAME:  fffff8800a9aa3b0 -- (.trap 0xfffff8800a9aa3b0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000002 rbx=0000000000000000 rcx=0000000000000000
rdx=fffffa8018379a78 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002e6d3e3 rsp=fffff8800a9aa540 rbp=fffffa8018032b60
 r8=0000000000000000  r9=0000000000000000 r10=0000000000000000
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
nt!KeSetEventBoostPriority+0x3f:
fffff800`02e6d3e3 f00fba2907      lock bts dword ptr [rcx],7 ds:7000:00000000`00000000=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002e8c1e9 to fffff80002e8cc40

STACK_TEXT:  
fffff880`0a9aa268 fffff800`02e8c1e9 : 00000000`0000000a 00000000`00000000 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`0a9aa270 fffff800`02e8ae60 : 00000000`00000000 00000000`00000000 00000000`00000000 fffff880`009ea180 : nt!KiBugCheckDispatch+0x69
fffff880`0a9aa3b0 fffff800`02e6d3e3 : fffff980`1871b000 00000000`00001000 fffffa80`00000000 fffff800`03176fe1 : nt!KiPageFault+0x260
fffff880`0a9aa540 fffff800`02e8f23f : 00000000`00000197 00000000`00000000 00000000`00000000 fffff880`00da2132 : nt!KeSetEventBoostPriority+0x3f
fffff880`0a9aa5b0 fffff880`012a6db9 : fffff8a0`0aabb010 fffffa80`06490a01 fffff8a0`0aabb010 fffff8a0`0aabb140 : nt!ExpReleaseResourceForThreadLite+0x2bf
fffff880`0a9aa610 fffff880`00d9e31c : fffffa80`180b7190 fffff880`00da1401 00000000`146ae9d0 fffffa80`0b53c888 : Ntfs!NtfsFastQueryStdInfo+0x289
fffff880`0a9aa800 fffff880`00da18ba : fffff880`0a9aa8d0 fffffa80`0b53c888 00000000`00000000 00000000`146ae100 : fltmgr!FltpPerformFastIoCall+0x30c
fffff880`0a9aa860 fffff880`00dbfc72 : 00000000`146ae108 fffffa80`180b7190 fffff880`0a9aab60 00000000`146ae9d0 : fltmgr!FltpPassThroughFastIo+0xda
fffff880`0a9aa8a0 fffff800`0316b465 : fffffa80`180b7190 fffff800`00000000 fffffa80`03d1f7b0 fffffa80`18032b01 : fltmgr!FltpFastIoQueryStandardInfo+0x172
fffff880`0a9aa930 fffff800`02e8bed3 : 00000000`00001d3c 00000000`146ae108 00000000`146ae9d0 00000000`00000018 : nt!NtQueryInformationFile+0x670
fffff880`0a9aaa70 00000000`7771142a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`146ae0c8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7771142a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!KeSetEventBoostPriority+3f
fffff800`02e6d3e3 f00fba2907      lock bts dword ptr [rcx],7

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  nt!KeSetEventBoostPriority+3f

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4e02aaa3

FAILURE_BUCKET_ID:  X64_0xA_nt!KeSetEventBoostPriority+3f

BUCKET_ID:  X64_0xA_nt!KeSetEventBoostPriority+3f

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

[*]
Loading Dump File [G:\Kingston\BSODDmpFiles\suurtje\011712-12027-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 (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`02e52000 PsLoadedModuleList = 0xfffff800`03097670
Debug session time: Tue Jan 17 02:31:38.101 2012 (GMT-7)
System Uptime: 0 days 1:43:04.976
Loading Kernel Symbols
...............................................................
................................................................
.......................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {1a800000008, 2, 1, fffff80002eaca71}

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

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

2: 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: 000001a800000008, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, 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: fffff80002eaca71, address which referenced memory

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


WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80003101100
 000001a800000008 

CURRENT_IRQL:  2

FAULTING_IP: 
nt!ExDeleteResourceLite+d1
fffff800`02eaca71 48894108        mov     qword ptr [rcx+8],rax

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  NMIndexingServ

TRAP_FRAME:  fffff88008686dc0 -- (.trap 0xfffff88008686dc0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffa800000006c rbx=0000000000000000 rcx=000001a800000000
rdx=fffffa8007a52950 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002eaca71 rsp=fffff88008686f50 rbp=fffffa80082d6010
 r8=0000000000000000  r9=0000000000000000 r10=fffff80002e52000
r11=000000000000027d r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
nt!ExDeleteResourceLite+0xd1:
fffff800`02eaca71 48894108        mov     qword ptr [rcx+8],rax ds:e670:000001a8`00000008=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002ece1e9 to fffff80002ecec40

STACK_TEXT:  
fffff880`08686c78 fffff800`02ece1e9 : 00000000`0000000a 000001a8`00000008 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`08686c80 fffff800`02ecce60 : 00000000`00000000 00000000`00000000 00000000`00000001 fffffa80`0a210000 : nt!KiBugCheckDispatch+0x69
fffff880`08686dc0 fffff800`02eaca71 : 00000000`00000005 00000000`00000000 fffffa80`082ce670 00000000`00000048 : nt!KiPageFault+0x260
fffff880`08686f50 fffff880`064c8691 : fffffa80`0a5db120 fffffa80`082d6010 00000000`40310079 00000000`00000000 : nt!ExDeleteResourceLite+0xd1
fffff880`08686fb0 fffffa80`0a5db120 : fffffa80`082d6010 00000000`40310079 00000000`00000000 fffffa80`082d6010 : Sftfslh+0x49691
fffff880`08686fb8 fffffa80`082d6010 : 00000000`40310079 00000000`00000000 fffffa80`082d6010 fffff880`06497853 : 0xfffffa80`0a5db120
fffff880`08686fc0 00000000`40310079 : 00000000`00000000 fffffa80`082d6010 fffff880`06497853 fffffa80`0ab0d1a0 : 0xfffffa80`082d6010
fffff880`08686fc8 00000000`00000000 : fffffa80`082d6010 fffff880`06497853 fffffa80`0ab0d1a0 fffffa80`082d6010 : 0x40310079


STACK_COMMAND:  kb

FOLLOWUP_IP: 
Sftfslh+49691
fffff880`064c8691 ??              ???

SYMBOL_STACK_INDEX:  4

SYMBOL_NAME:  Sftfslh+49691

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: Sftfslh

IMAGE_NAME:  Sftfslh.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4c8e9fa2

FAILURE_BUCKET_ID:  X64_0xA_Sftfslh+49691

BUCKET_ID:  X64_0xA_Sftfslh+49691

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


[/list]

1. Appears to be due to your hard disk. Other possible causes are Memory problems... Drivers...
2. Possible causes are Memory problems... drivers...
3. Again, hard disk file system in the stack. Other possible causes are Memory problems... Corrupted hard disk file system... Corrupted System Files... Lack of Windows updates... Antivirus Software...
4. Same as last one, but due to Microsoft Application Virtualization (App-V) driver and Nero Indexing. Indexing can fail if you have a corrupt hard disk file system.

Thanks to Dave76 for help understanding possible causes.



We will start with the common problems first (see bold possible causes). Do the following steps and test after each to see if stability increases. Post back your results after each step, and if you get a blue screen crash, upload the files again and await further instructions after we are able to analyze the crash.

• If you are overclocking any hardware, please stop.
  
  
  
• Remove Nero from your sytems.
  
  
  
• Run Disk Check with both boxes checked for all HDDs and with Automatically fix file system errors checked for all SSDs. Post back your logs for the checks after finding them using http://www.sevenforums.com/tutorials/96938-check-disk-chkdsk-read-event-viewer-log.html
  
  
  
• Run http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html up to three times to fix all errors. Post back if it continues to show errors after a fourth run or if the first run comes back with no integrity violations.

 

[suurtje]

Fixed the problem. Seems it had to do with a old speakerset.
Hardwareproblem.
Running stabel for almost a week now.

 

[writhziden]

Good news. Nice job tracking it down, and we appreciate you posting back your solution.

 

[suurtje]

Of course. Thanks for the help.

 

[writhziden]

You're welcome.