New
#11
here's the shot of the command prompt thing. says it's clean.
so, i kinda crashed last night and forgot to let memtest run. so i'm gonna start it now and let it go for a few hours and then report back.
ok, so here's the report from memtest. no errors reported.
btw, sorry for double (triple) posting if there's a rule against that. i do that so if people are subscribed to the thread, they'll get the notification that there's been activity and check back. but i know some forums have problems with that, so sorry if i'm in violation of anything.
and here's a ZIP file of my BSOD dumps since i've been having this problem (pretty sure they're all from the same issue). by the way, if anybody would like to jump in and try to make sense of my last 4 posts, it'd be much obliged. i'd kind of like to get this fixed and considering how many people are out there on this forum, i'm sure one of you must be able to make heads or tails of this stuff.
/edit:
my computer just did it again. i won't bother to upload the dump file because i doubt it has anything different in it than the ones in that file.
mb
NotHIng you dont already know. This crash was caused by memory.
I would suggest. running memtestx86 for hours, or as one of my collegues says "until it bleeds"
I would also run a system file check by typeing cmd in search>right click and run as admin>
sfc /scannow
If you are overclocking stop.
Ken
quote by our most acidic one
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\K\Desktop\103109-24445-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*d:\symbols*Symbol information
Executable search path is:
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02a51000 PsLoadedModuleList = 0xfffff800`02c8ee50
Debug session time: Sat Oct 31 12:31:15.040 2009 (GMT-5)
System Uptime: 0 days 0:23:13.663
Loading Kernel Symbols
...............................................................
................................................................
.....................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 7F, {8, 80050031, 6f8, fffff80002ac89bc}
Probably caused by : ntkrnlmp.exe ( nt!KiDoubleFaultAbort+b2 )
Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
UNEXPECTED_KERNEL_MODE_TRAP (7f)
This means a trap occurred in kernel mode, and it's a trap of a kind
that the kernel isn't allowed to have/catch (bound trap) or that
is always instant death (double fault). The first number in the
bugcheck params is the number of the trap (8 = double fault, etc)
Consult an Intel x86 family manual to learn more about what these
traps are. Here is a *portion* of those codes:
If kv shows a taskGate
use .tss on the part before the colon, then kv.
Else if kv shows a trapframe
use .trap on that value
Else
.trap on the appropriate frame will show where the trap was taken
(on x86, this will be the ebp that goes with the procedure KiTrap)
Endif
kb will then show the corrected stack.
Arguments:
Arg1: 0000000000000008, EXCEPTION_DOUBLE_FAULT
Arg2: 0000000080050031
Arg3: 00000000000006f8
Arg4: fffff80002ac89bc
Debugging Details:
------------------
BUGCHECK_STR: 0x7f_8
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: 2
LAST_CONTROL_TRANSFER: from fffff80002ac2469 to fffff80002ac2f00
STACK_TEXT:
fffff880`009edc68 fffff800`02ac2469 : 00000000`0000007f 00000000`00000008 00000000`80050031 00000000`000006f8 : nt!KeBugCheckEx
fffff880`009edc70 fffff800`02ac0932 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`009eddb0 fffff800`02ac89bc : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDoubleFaultAbort+0xb2
fffff880`0761dfb0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!SepAccessCheck+0x1ac
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!KiDoubleFaultAbort+b2
fffff800`02ac0932 90 nop
SYMBOL_STACK_INDEX: 2
SYMBOL_NAME: nt!KiDoubleFaultAbort+b2
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc600
FAILURE_BUCKET_ID: X64_0x7f_8_nt!KiDoubleFaultAbort+b2
BUCKET_ID: X64_0x7f_8_nt!KiDoubleFaultAbort+b2
Followup: MachineOwner
ok, i really can't make sense of any of that. but it's caused by memory? would the fact that 2 out of my 3 memory sticks are ECC?
can't. i took out my 2 ECC ram sticks and i'm running the application to see if that was the problem at the suggestion of torrentg. seems to be working for now. i'm gonna leave it running and see how long it takes for it to crash (if it crashes at all).
it seems like that did it. i've had steam running for maybe an hour and a half now (with interspersed HL2) and it hasn't crashed yet. it usually would've crashed within that time frame. so i'm gonna see if this shop by me will take my 2 ECC sticks and let me buy 2 regular sticks for a discounted pricte (kinda like a trade in at gamestop).