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 )
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
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
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=????????????????
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.
