BSOD few minutes after bootup


  1. Posts : 2
    Windows 7 professional x64
       #1

    BSOD few minutes after bootup


    Recently built a pc using new parts and a few recycled ones.
    Downloaded win. 7, you can see the specs in my profile (only the mobo, processor, and video card are new)
    I have not yet installed any drivers for the gpu or the few mobo drivers
    After bootup, in like 5-10 minutes, it gives me BSOD
    (seems to run fine in safe mode with networking when I restart)
    Pls Help

    (i have the .dmp on a flash drive but dont know how to upload it)

    EDIT: I used osronline to analyze the dmp, this is what it gave me:

    Crash Dump Analysis provided by OSR Open Systems Resources, Inc. (OSR Homepage | OSR)
    Online Crash Dump Analysis Service
    See OSR Online - The Home Page for Windows Driver Developers for more information
    Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
    Machine Name:
    Kernel base = 0xfffff800`02865000 PsLoadedModuleList = 0xfffff800`02aaae90
    Debug session time: Sat Dec 26 09:18:12.648 2015 (UTC - 5:00)
    System Uptime: 0 days 0:06:07.507
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    WHEA_UNCORRECTABLE_ERROR (124)
    A fatal hardware error has occurred. Parameter 1 identifies the type of error
    source that reported the error. Parameter 2 holds the address of the
    WHEA_ERROR_RECORD structure that describes the error conditon.
    Arguments:
    Arg1: 0000000000000000, Machine Check Exception
    Arg2: fffffa80067b1038, Address of the WHEA_ERROR_RECORD structure.
    Arg3: 00000000bf800000, High order 32-bits of the MCi_STATUS value.
    Arg4: 0000000000000124, Low order 32-bits of the MCi_STATUS value.

    Debugging Details:
    ------------------

    TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2

    BUGCHECK_STR: 0x124_GenuineIntel

    CUSTOMER_CRASH_COUNT: 1

    DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT

    PROCESS_NAME: mscorsvw.exe

    CURRENT_IRQL: f

    STACK_TEXT:
    fffff800`03c06a98 fffff800`0282ea3b : 00000000`00000124 00000000`00000000 fffffa80`067b1038 00000000`bf800000 : nt!KeBugCheckEx
    fffff800`03c06aa0 fffff800`029f27d3 : 00000000`00000001 fffffa80`067b1ea0 00000000`00000000 fffffa80`067b1ef0 : hal!HalBugCheckSystem+0x1e3
    fffff800`03c06ae0 fffff800`0282e700 : 00000000`00000728 fffffa80`067b1ea0 fffff800`03c06e70 fffff800`03c06e00 : nt!WheaReportHwError+0x263
    fffff800`03c06b40 fffff800`0282e052 : fffffa80`067b1ea0 fffff800`03c06e70 fffffa80`067b1ea0 00000000`00000000 : hal!HalpMcaReportError+0x4c
    fffff800`03c06c90 fffff800`0282df0d : 00000000`00000002 00000000`00000001 fffff800`03c06ef0 00000000`00000000 : hal!HalpMceHandler+0x9e
    fffff800`03c06cd0 fffff800`02821e88 : fffff700`01080000 9f100000`6db9f867 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0x55
    fffff800`03c06d00 fffff800`028e3f2c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
    fffff800`03c06d30 fffff800`028e3d93 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
    fffff800`03c06e70 fffff800`02917905 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
    fffff880`04f67920 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!MiDeleteVirtualAddresses+0x6fd


    STACK_COMMAND: kb

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: GenuineIntel

    IMAGE_NAME: GenuineIntel

    DEBUG_FLR_IMAGE_TIMESTAMP: 0

    FAILURE_BUCKET_ID: X64_0x124_GenuineIntel_PROCESSOR_CACHE

    BUCKET_ID: X64_0x124_GenuineIntel_PROCESSOR_CACHE

    Followup: MachineOwner
    ---------
    Last edited by Bodya23; 26 Dec 2015 at 21:52. Reason: Found .dmp
      My Computer


  2. Posts : 19,383
    Windows 10 Pro x64 ; Xubuntu x64
       #2

    Additional information is required.

    1. Download the DM Log Collector application to your desktop by clicking the link below

    DM Log Collector.exe

    2. Run it by double-clicking the icon on your desktop, and follow the prompts.
    3. Locate the .ZIP file that is created on your desktop, and upload it here in your next reply.

      My Computer


  3. Posts : 2
    Windows 7 professional x64
    Thread Starter
       #3

    Some more info, but i will try to get dm log collector when i get home.
    The pc was running very cool when put my hand inside the case and felt the fans on the back, and in bios the cpu temp was at 40ish when overclocked

    I also tried removing the overclock and the video card, and just running through vga on the motherboard, and when i reinstalled windows, no blue screen and i was even able to download all the motherboard drivers before shutting it down for the night.

    One of my friends said it could be due to the power supply (some random psu that came with my old pc) 300w i think, not having enough power
      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 01:33.
Find Us