BSOD on startup - Please help

Page 2 of 2 FirstFirst 12

  1. Posts : 12
    Windows 7 Ultimate 64-bit
    Thread Starter
       #11

    Ok, so I tried increasing the ram voltage to 1.6 and I thought I fixed it, but had another cold boot BSOD today.

    I've uploaded the most recent dump file if you guys could help me out again. Thanks
      My Computer


  2. Posts : 6,885
    Windows 7 Ultimate x64, Mint 9
       #12

    The dump doesn't tell us much. The stop code points to memory again.

    You might have a bad slot. Can you take out all but one stick and see if that helps?

    Code:
    Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [C:\Users\David\AppData\Local\Temp\Temp2_7-8-10mindumps.zip\7-8-10mindumps\070810-16156-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    
    Symbol search path is: SRV*c:\symbols*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.16539.amd64fre.win7_gdr.100226-1909
    Machine Name:
    Kernel base = 0xfffff800`02a1a000 PsLoadedModuleList = 0xfffff800`02c57e50
    Debug session time: Thu Jul  8 18:03:57.953 2010 (UTC - 7:00)
    System Uptime: 0 days 0:00:08.046
    Loading Kernel Symbols
    ...............................................................
    ....................................................
    Loading User Symbols
    Loading unloaded module list
    ....
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 1A, {41790, fffffa80036e8a40, ffff, 0}
    
    Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+33946 )
    
    Followup: MachineOwner
    ---------
    
    3: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    MEMORY_MANAGEMENT (1a)
        # Any other values for parameter 1 must be individually examined.
    Arguments:
    Arg1: 0000000000041790, The subtype of the bugcheck.
    Arg2: fffffa80036e8a40
    Arg3: 000000000000ffff
    Arg4: 0000000000000000
    
    Debugging Details:
    ------------------
    
    
    BUGCHECK_STR:  0x1a_41790
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    PROCESS_NAME:  smss.exe
    
    CURRENT_IRQL:  0
    
    LAST_CONTROL_TRANSFER:  from fffff80002afdede to fffff80002a8a600
    
    STACK_TEXT:  
    fffff880`03f5a828 fffff800`02afdede : 00000000`0000001a 00000000`00041790 fffffa80`036e8a40 00000000`0000ffff : nt!KeBugCheckEx
    fffff880`03f5a830 fffff800`02abdcc9 : 00000000`00000000 000007fe`fe650fff fffffa80`00000000 fffff683`ff7f3080 : nt! ?? ::FNODOBFM::`string'+0x33946
    fffff880`03f5a9f0 fffff800`02da4170 : fffffa80`051c1140 0007ffff`00000000 00000000`00000000 00000000`00000000 : nt!MiRemoveMappedView+0xd9
    fffff880`03f5ab10 fffff800`02da457b : 00000980`00000000 000007fe`fe450000 fffffa80`00000001 fffffa80`04f8c010 : nt!MiUnmapViewOfSection+0x1b0
    fffff880`03f5abd0 fffff800`02a89853 : 00000000`00000000 00000000`0032f580 fffffa80`050969d0 00000000`77239360 : nt!NtUnmapViewOfSection+0x5f
    fffff880`03f5ac20 00000000`7716fffa : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
    00000000`0032f398 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7716fffa
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    nt! ?? ::FNODOBFM::`string'+33946
    fffff800`02afdede cc              int     3
    
    SYMBOL_STACK_INDEX:  1
    
    SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+33946
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: nt
    
    IMAGE_NAME:  ntkrnlmp.exe
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4b88cfeb
    
    FAILURE_BUCKET_ID:  X64_0x1a_41790_nt!_??_::FNODOBFM::_string_+33946
    
    BUCKET_ID:  X64_0x1a_41790_nt!_??_::FNODOBFM::_string_+33946
    
    Followup: MachineOwner
    ---------
    ~Lordbob
      My Computer


  3. Posts : 12
    Windows 7 Ultimate 64-bit
    Thread Starter
       #13

    Hey guys, just thought I'd update this thread with my solution.

    It turns out that my memory was the problem even though I couldn't get memtest to show anything. Seems like others on the web have had a similar "cold boot" problem with the particular G Skill memory that I have. Anyway, I sent it back to G Skill under warranty and they sent me brand new memory - problem solved and no more booting/blue screen issues.

    Thanks to everyone that helped me troubleshoot this issue - you guys are great:)
      My Computer


  4. Posts : 13,354
    Windows 7 Professional x64
       #14

    Thanks for the report! I'm glad to hear the solution.
      My Computer


 
Page 2 of 2 FirstFirst 12

  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 09:00.
Find Us