New Computer, BSOD in windows 7

Page 2 of 3 FirstFirst 123 LastLast

  1. Posts : 94
    Windows 7 Professional 32-Bit
       #11

    here's the shot of the command prompt thing. says it's clean.

      My Computer


  2. Posts : 94
    Windows 7 Professional 32-Bit
       #12

    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.
      My Computer


  3. Posts : 94
    Windows 7 Professional 32-Bit
       #13

    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.
      My Computer


  4. Posts : 94
    Windows 7 Professional 32-Bit
       #14

    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.
      My Computer


  5. Posts : 28,845
    Win 8 Release candidate 8400
       #15

    Mirrorboy said:
    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
      My Computer


  6. Posts : 94
    Windows 7 Professional 32-Bit
       #16

    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?
      My Computer


  7. Posts : 1,360
    win7 ultimate / virtual box
       #17

    what is the exact spec of your memory sticks

    maybe use cpu-z for a readout
      My Computer


  8. Posts : 94
    Windows 7 Professional 32-Bit
       #18

    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).
      My Computer


  9. Posts : 1,360
    win7 ultimate / virtual box
       #19

    Mirrorboy said:
    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).
    well gl hope it gives you the cure

    If it is your ram can I suggest buy the same make of stick at the same time to ensure inter-compatibility
      My Computer


  10. Posts : 94
    Windows 7 Professional 32-Bit
       #20

    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).
      My Computer


 
Page 2 of 3 FirstFirst 123 LastLast

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 15:27.
Find Us