Hello all, i'm not sure if this is in the right forum section but it seemed to be the most likely one... I've been having problems with my pc for about a week now and i've tried everything to fix it without succes... My Pc keeps giving me random BSODs when I leave it on for long periods of time... I've just done a clean install of windows 7 ultimate 64-bit and all my drivers are up to date... Here is the crash dump analysis; I was wondering if any of you had any ideas on how to fix this... Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Windows\Minidump\102709-19656-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7600 MP (4 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7600.16385.amd64fre.win7_rtm.090713-1255 Machine Name: Kernel base = 0xfffff800`0364b000 PsLoadedModuleList = 0xfffff800`03888e50 Debug session time: Tue Oct 27 16:34:41.101 2009 (GMT-4) System Uptime: 1 days 21:48:41.834 Loading Kernel Symbols ............................................................... ................................................................ .............................. Loading User Symbols Loading unloaded module list .............. ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck A, {fffffa80e904b9d0, 2, 1, fffff800036c3f4c} Probably caused by : ntkrnlmp.exe ( nt!KiCommitThreadWait+cc ) Followup: MachineOwner --------- 3: kd> !ANALYSE -V No export ANALYSE found 3: 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: fffffa80e904b9d0, 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: fffff800036c3f4c, address which referenced memory Debugging Details: ------------------ WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800038f30e0 fffffa80e904b9d0 CURRENT_IRQL: 2 FAULTING_IP: nt!KiCommitThreadWait+cc fffff800`036c3f4c 488910 mov qword ptr [rax],rdx CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0xA PROCESS_NAME: dwm.exe TRAP_FRAME: fffff88007de6960 -- (.trap 0xfffff88007de6960) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=fffffa80e904b9d0 rbx=0000000000000000 rcx=fffff88002fd9600 rdx=fffffa800a0ae100 rsi=0000000000000000 rdi=0000000000000000 rip=fffff800036c3f4c rsp=fffff88007de6af0 rbp=fffff88007de6c30 r8=0000000000000044 r9=fffff88007de6c30 r10=fffff800039b4900 r11=00000000002f6e94 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei pl nz na pe nc nt!KiCommitThreadWait+0xcc: fffff800`036c3f4c 488910 mov qword ptr [rax],rdx ds:fa40:fffffa80`e904b9d0=???????????????? Resetting default scope LAST_CONTROL_TRANSFER: from fffff800036bc469 to fffff800036bcf00 STACK_TEXT: fffff880`07de6818 fffff800`036bc469 : 00000000`0000000a fffffa80`e904b9d0 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx fffff880`07de6820 fffff800`036bb0e0 : 00000000`00000000 fffffa80`0a0ae060 fffff880`00000003 00001f80`00000000 : nt!KiBugCheckDispatch+0x69 fffff880`07de6960 fffff800`036c3f4c : fffffa80`096f5000 00000000`00000020 00000000`00000000 fffff880`04e9f333 : nt!KiPageFault+0x260 fffff880`07de6af0 fffff800`036c6756 : fffff880`00000001 00000000`00000000 00000000`00000044 00000000`003ad040 : nt!KiCommitThreadWait+0xcc fffff880`07de6b80 fffff800`039b49ee : fffffa80`0a0ae060 fffff880`07de6c28 00000000`00000000 00000000`00000044 : nt!KeDelayExecutionThread+0x186 fffff880`07de6bf0 fffff800`036bc153 : fffffa80`0a0ae060 fffffa80`06cc7ae0 ffffffff`ffffb1e0 fffffa80`06cc7ae0 : nt!NtDelayExecution+0x59 fffff880`07de6c20 00000000`778e01fa : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13 00000000`0383fb08 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x778e01fa STACK_COMMAND: kb FOLLOWUP_IP: nt!KiCommitThreadWait+cc fffff800`036c3f4c 488910 mov qword ptr [rax],rdx SYMBOL_STACK_INDEX: 3 SYMBOL_NAME: nt!KiCommitThreadWait+cc FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc600 FAILURE_BUCKET_ID: X64_0xA_nt!KiCommitThreadWait+cc BUCKET_ID: X64_0xA_nt!KiCommitThreadWait+cc Followup: MachineOwner --------- 3: kd> .trap 0xfffff88007de6960 NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=fffffa80e904b9d0 rbx=0000000000000000 rcx=fffff88002fd9600 rdx=fffffa800a0ae100 rsi=0000000000000000 rdi=0000000000000000 rip=fffff800036c3f4c rsp=fffff88007de6af0 rbp=fffff88007de6c30 r8=0000000000000044 r9=fffff88007de6c30 r10=fffff800039b4900 r11=00000000002f6e94 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei pl nz na pe nc nt!KiCommitThreadWait+0xcc: fffff800`036c3f4c 488910 mov qword ptr [rax],rdx ds:fa40:fffffa80`e904b9d0=???????????????? Thanks in advance for any help!
Could you run a Memtest overnight on the machine? I think win 7 comes with one built in. If you press f8 on the keyboard before you see the windows logo you should see some options and (I think) one should be memtest.
yeah.. it's a symptom of bad ram.. win7 like the other junk they make doesn't handle ram errors well.. a proper OS will slow down and apps will segfault and exit leaving traces in the logs. I have a couple of sticks that will drop from 256 to 32 as they get warm.. M$ stuff bsod's.. linux slows down and things exit without warning. firefox is usually the first thing that complains.. that's my experience anyway.. avidemux will show up overheat problems.. how cool is that?.. I can diagnose certain hardware problems by how a particular program works (or doesn't hehehehehe). plain and simple experience around recycled hardware over the years. There is a good ram test on ubcd.. (google it.. it's free!) dump the faulty M$ bloat 2 gigs for a desktop- before running app.. run the mem tests on the ubcd for a reliable assessment of the hardware status.. usually 2nd or 3rd pass it starts to throw errors. Also do a hdd integrity check.. sometimes bad sectors in the pagefile area will cause random crashes.
