BSOD on custom build. Happens daily


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

    BSOD on custom build. Happens daily


    Hello,

    I apologize in advance for being new but I will follow instruction if someone can just help point me in the right direction :)

    I have a custom built computer that has been getting random BSOD. They happen everyday. I can boot my computer, then randomly in the first hour it will usually crash. After the crash, the computer works just fine until after I turn it off. I can run it for days without another BSOD but as soon as I turn it off and boot back up, I will inevitably get another BSOD at a random time soon after. I've included my specs and ran the DM Log (which is included as well). I also have a crash dump analysis from WhoCrashed which I will copy/paste here also. Please let me know if there is anything else I need to include and what I can do to resolve this issue.

    Thanks in advance!!

    Additionally, I have no idea why WhoCrashed is showing my Windows version as Windows XP Service Pack 3, 5.1, build: 2600. I most definitely have Windows 7 Home Edition 64-bit.

    System Information (local)
    --------------------------------------------------------------------------------

    Computer name: GAMING-PC
    Windows version: Windows XP Service Pack 3, 5.1, build: 2600
    Windows dir: C:\Windows
    Hardware: Z97X-Gaming 7, Gigabyte Technology Co., Ltd.
    CPU: GenuineIntel Intel(R) Core(TM) i7-4790K CPU @ 4.00GHz Intel586, level: 6
    8 logical processors, active mask: 255
    RAM: 17018142720 bytes total




    --------------------------------------------------------------------------------
    Crash Dump Analysis
    --------------------------------------------------------------------------------

    Crash dump directory: C:\Windows\Minidump

    Crash dumps are enabled on your computer.

    On Wed 12/16/2015 4:47:21 PM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\121615-13478-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x73C40)
    Bugcheck code: 0x1A (0x41790, 0xFFFFFA80050F7270, 0xFFFF, 0x0)
    Error: MEMORY_MANAGEMENT
    file path: C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: This indicates that a severe memory management error occurred.
    This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



    On Wed 12/16/2015 4:47:21 PM GMT your computer crashed
    crash dump file: C:\Windows\memory.dmp
    This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
    Bugcheck code: 0x1A (0x41790, 0xFFFFFA80050F7270, 0xFFFF, 0x0)
    Error: MEMORY_MANAGEMENT
    Bug check description: This indicates that a severe memory management error occurred.
    This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



    On Tue 12/15/2015 3:42:48 PM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\121515-5163-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x73C40)
    Bugcheck code: 0x1A (0x41790, 0xFFFFFA8008CC5F50, 0xFFFF, 0x0)
    Error: MEMORY_MANAGEMENT
    file path: C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: This indicates that a severe memory management error occurred.
    This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



    On Mon 12/14/2015 11:13:01 PM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\121415-5366-01.dmp
    This was probably caused by the following module: cdd.dll (cdd+0x200DD)
    Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF960007A00DD, 0xFFFFF88009E0DEA8, 0xFFFFF88009E0D700)
    Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
    file path: C:\Windows\system32\cdd.dll
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: Canonical Display Driver
    Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
    The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



    On Thu 12/10/2015 8:08:31 PM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\121015-5335-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x73C40)
    Bugcheck code: 0x1A (0x41790, 0xFFFFFA8004FA2EF0, 0xFFFF, 0x0)
    Error: MEMORY_MANAGEMENT
    file path: C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: This indicates that a severe memory management error occurred.
    This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



    On Sat 12/5/2015 9:49:38 PM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\120515-5116-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x73C40)
    Bugcheck code: 0x1A (0x41790, 0xFFFFFA8005038950, 0xFFFF, 0x0)
    Error: MEMORY_MANAGEMENT
    file path: C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: This indicates that a severe memory management error occurred.
    This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



    On Thu 12/3/2015 10:07:05 PM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\120315-5304-01.dmp
    This was probably caused by the following module: ntfs.sys (Ntfs+0x4688)
    Bugcheck code: 0x24 (0x1904FB, 0xFFFFF88003745C78, 0xFFFFF880037454D0, 0xFFFFF800032A1F10)
    Error: NTFS_FILE_SYSTEM
    file path: C:\Windows\system32\drivers\ntfs.sys
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT File System Driver
    Bug check description: This indicates a problem occurred in the NTFS file system.
    The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



    On Sat 11/28/2015 8:19:09 PM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\112815-5288-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x73C40)
    Bugcheck code: 0x1A (0x41790, 0xFFFFFA8008BF9F20, 0xFFFF, 0x0)
    Error: MEMORY_MANAGEMENT
    file path: C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: This indicates that a severe memory management error occurred.
    This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



    On Fri 11/27/2015 2:47:25 AM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\112615-5038-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x73C40)
    Bugcheck code: 0x1A (0x41790, 0xFFFFFA8008C5F920, 0xFFFF, 0x0)
    Error: MEMORY_MANAGEMENT
    file path: C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: This indicates that a severe memory management error occurred.
    This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



    On Sun 11/22/2015 8:05:51 PM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\112215-5506-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x73C40)
    Bugcheck code: 0x1A (0x41790, 0xFFFFFA8008C4B760, 0xFFFF, 0x0)
    Error: MEMORY_MANAGEMENT
    file path: C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: This indicates that a severe memory management error occurred.
    This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.





    --------------------------------------------------------------------------------
    Conclusion
    --------------------------------------------------------------------------------

    24 crash dumps have been found and analyzed. Only 10 are included in this report. No offending third party drivers have been found. Connsider using WhoCrashed Professional which offers more detailed analysis using symbol resolution. Also configuring your system to produce a full memory dump may help you.
      My Computer


  2. Posts : 2
    Windows 7 Home Premium 64-bit
    Thread Starter
       #2

    any help is appreciated please :)
      My Computer


  3. Posts : 1,851
    Windows 7 pro
       #3

    Start by testing your ram. RAM - Test with Memtest86+
      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 00:13.
Find Us