BSOD Please Review Logs


  1. Posts : 1
    Windows 7 Home Premium 64bit
       #1

    BSOD Please Review Logs


    Windows 7 Home Premium
    x64
    the original installed OS on the system?
    OEM Version


    - What is the age of system (hardware)? All Brand new
    - What is the age of OS installation? I have not re-installed.


      My Computer


  2. Posts : 11,990
    Windows 7 Ultimate 32 bit
       #2

    HI, Cade, and welcome to the forum. You have several dumps with error code 124. This is a fatal hardware error. No specific cause is given. I You also have serveral dumps showing error code 1A. While I look further, read this article on your error 124: [2-Int] Stop 0x124 - what it means and what to try

    Do you get BSOD's in the Safe mode as well as in the normal mode? If you have not tried, boot into the Safe mode and see.

    Do the checks in in the article linked above. Then I suggest that you run Memtest86 to test your RAM. Follow the instructions in this tutorial:
    RAM - Test with Memtest86+. Run Memtest from a cold boot after your computer has been off for an hour or so. Let it run for at least 7 passes. This will take 6-8 hours. If you see errors, you can stop the test. Post back with your results.

    Code:
    Windows 7 Kernel Version 7600 MP (2 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS Personal
    Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
    Machine Name:
    Kernel base = 0xfffff800`02c03000 PsLoadedModuleList = 0xfffff800`02e40e50
    Debug session time: Mon Dec 27 10:11:11.622 2010 (GMT-5)
    System Uptime: 0 days 0:00:12.105
    Loading Kernel Symbols
    ................................................
    Loading User Symbols
    Mini Kernel Dump does not contain unloaded driver list
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 124, {0, fffffa8004dcb8f8, 0, 0}
    
    Probably caused by : hardware
    
    Followup: MachineOwner
    ---------
    
    Debug session time: Mon Dec 27 10:39:52.535 2010 (GMT-5)
    System Uptime: 0 days 0:15:24.017
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ..........................
    Loading User Symbols
    Loading unloaded module list
    .....
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 1A, {31, fffffa8003b47e10, fffff880029ef000, fffff8a002aafd7c}
    
    Probably caused by : ntkrnlmp.exe ( nt! ?? ::NNGAKEGL::`string'+6378 )
    
    Followup: MachineOwner
    ---------
    
    1: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    MEMORY_MANAGEMENT (1a)
        # Any other values for parameter 1 must be individually examined.
    Arguments:
    Arg1: 0000000000000031, The subtype of the bugcheck.
    Arg2: fffffa8003b47e10
    Arg3: fffff880029ef000
    Arg4: fffff8a002aafd7c
    
    Debugging Details:
    ------------------
    
    
    BUGCHECK_STR:  0x1a_31
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    PROCESS_NAME:  firefox.exe
    
    CURRENT_IRQL:  0
    
    LAST_CONTROL_TRANSFER:  from fffff80002fadb2d to fffff80002c7c600
    
    STACK_TEXT:  
    fffff880`07389078 fffff800`02fadb2d : 00000000`0000001a 00000000`00000031 fffffa80`03b47e10 fffff880`029ef000 : nt!KeBugCheckEx
    fffff880`07389080 fffff800`02f64f45 : fffff880`029ef000 00000000`038f0000 00000000`00733000 fffffa80`01530ea0 : nt! ?? ::NNGAKEGL::`string'+0x6378
    fffff880`073890d0 fffff800`02f5217c : 00000000`00000000 00000000`00000000 fffff6fc`40053f68 fffff800`00000000 : nt!MiPerformFixups+0x65
    fffff880`07389120 fffff800`02c5e57d : 00000000`0007104e 00000000`00000733 fffff8a0`0291f9e0 00000000`00000002 : nt!MiRelocateImagePfn+0x114
    fffff880`07389180 fffff800`02f64ea1 : fffffa80`03aea010 fffff6fc`40053f68 fffff8a0`00000002 00000000`00000000 : nt!MiValidateImagePages+0x2bd
    fffff880`07389220 fffff800`02f645b0 : ffffffff`ffffffff 00000000`00000001 fffff8a0`02a8f000 00000000`000000fe : nt!MiSwitchBaseAddress+0x61
    fffff880`07389250 fffff800`02f783ae : 00000000`00000004 00000000`01000000 00000000`00000000 00000000`00000000 : nt!MiRelocateImageAgain+0x100
    fffff880`073892a0 fffff800`02f6db83 : fffff880`07389500 00000000`00000000 fffff880`073895a8 fffff880`073894f8 : nt!MmCreateSection+0x302
    fffff880`073894b0 fffff800`030d8d75 : fffff8a0`00cd4268 00000000`00000000 00000000`00000001 00000002`00000000 : nt!NtCreateSection+0x162
    fffff880`07389530 fffff800`030d9127 : 00000000`00000010 fffff8a0`01bfc4e0 fffff880`073896c0 00000000`0000002c : nt!PfSnGetSectionObject+0x2d5
    fffff880`07389620 fffff800`030d9557 : fffff880`07389740 00000000`00000001 00000000`00000000 00000000`00000000 : nt!PfSnPrefetchSections+0x247
    fffff880`07389710 fffff800`030d997f : 00000006`5a6cacef fffffa80`0640e060 fffff8a0`01f78000 00000000`00000000 : nt!PfSnPrefetchScenario+0x187
    fffff880`07389980 fffff800`02ed211f : 00000000`00000000 00000000`18acfcff fffffa80`060df5f0 00000000`00000000 : nt!PfSnBeginAppLaunch+0x35f
    fffff880`07389a50 fffff800`02f4b130 : fffffa80`06355210 fffffa80`060df5f0 00000000`14050800 00000000`7efde000 : nt! ?? ::NNGAKEGL::`string'+0x503f0
    fffff880`07389a80 fffff800`02c5ac35 : fffff880`009e9180 00000000`00000000 fffff800`02f4b034 fffffa80`06355210 : nt!PspUserThreadStartup+0xfc
    fffff880`07389ae0 fffff800`02c5abb7 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartUserThread+0x16
    fffff880`07389c20 00000000`76cf3260 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartUserThreadReturn
    00000000`0017f548 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x76cf3260
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    nt! ?? ::NNGAKEGL::`string'+6378
    fffff800`02fadb2d cc              int     3
    
    SYMBOL_STACK_INDEX:  1
    
    SYMBOL_NAME:  nt! ?? ::NNGAKEGL::`string'+6378
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: nt
    
    IMAGE_NAME:  ntkrnlmp.exe
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4b88cfeb
    
    FAILURE_BUCKET_ID:  X64_0x1a_31_nt!_??_::NNGAKEGL::_string_+6378
    
    BUCKET_ID:  X64_0x1a_31_nt!_??_::NNGAKEGL::_string_+6378
    
    Followup: MachineOwner
    ---------



      My Computer


 

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