Solved

HELP! BSOD when booting up Windows 10

I am having an issue with my PC when booting it up. Every time I boot it up I get a different BSOD screen with a different error message, but then the PC shuts down. After it shuts down it then boots up without a problem and I don't know why. I reinstalled windows and I still get the same message. I have also tried updating my motherboard drivers and I still get the problem. Please help.
3 answers Last reply Best Answer
More about bsod booting windows
  1. System Information (local)
    --------------------------------------------------------------------------------
    Windows version: Windows 10 , 10.0, build: 10586
    Windows dir: C:\WINDOWS
    Hardware: ASUSTeK COMPUTER INC., H110M-K
    CPU: GenuineIntel Intel(R) Core(TM) i5-6600 CPU @ 3.30GHz Intel586, level: 6
    4 logical processors, active mask: 15
    RAM: 8508248064 bytes total


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

    Crash dump directory: C:\WINDOWS\Minidump

    Crash dumps are enabled on your computer.

    On Wed 13/07/2016 09:48:27 GMT your computer crashed
    crash dump file: C:\WINDOWS\Minidump\071316-4796-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x1427A0)
    Bugcheck code: 0x139 (0x3, 0xFFFFD00024390550, 0xFFFFD000243904A8, 0x0)
    Error: KERNEL_SECURITY_CHECK_FAILURE
    file path: C:\WINDOWS\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: The kernel has detected the corruption of a critical data structure.
    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 13/07/2016 09:48:27 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: 0x139 (0x3, 0xFFFFD00024390550, 0xFFFFD000243904A8, 0x0)
    Error: KERNEL_SECURITY_CHECK_FAILURE
    Bug check description: The kernel has detected the corruption of a critical data structure.
    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/07/2016 16:12:02 GMT your computer crashed
    crash dump file: C:\WINDOWS\Minidump\071316-4218-01.dmp
    This was probably caused by the following module: fltmgr.sys (0xFFFFF80190F0A712)
    Bugcheck code: 0x50 (0xFFFFA000B9421284, 0x2, 0xFFFFF80190F0A712, 0x2)
    Error: PAGE_FAULT_IN_NONPAGED_AREA
    file path: C:\WINDOWS\system32\drivers\fltmgr.sys
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: Microsoft Filesystem Filter Manager
    Bug check description: This indicates that invalid system memory has been referenced.
    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 Tue 12/07/2016 00:40:52 GMT your computer crashed
    crash dump file: C:\WINDOWS\Minidump\071216-4312-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x1427A0)
    Bugcheck code: 0x50 (0xFFFF80000FA50200, 0x0, 0xFFFFF802358B8852, 0x2)
    Error: PAGE_FAULT_IN_NONPAGED_AREA
    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 invalid system memory has been referenced.
    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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.


    On Mon 11/07/2016 16:24:58 GMT your computer crashed
    crash dump file: C:\WINDOWS\Minidump\071116-4468-01.dmp
    This was probably caused by the following module: ntfs.sys (NTFS+0xDDD57)
    Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF8018AD1DD57, 0xFFFFD0002474F408, 0xFFFFD0002474EC20)
    Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
    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 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 Mon 11/07/2016 15:02:46 GMT your computer crashed
    crash dump file: C:\WINDOWS\Minidump\071116-3750-01.dmp
    This was probably caused by the following module: ntfs.sys (0xFFFFF801935949FD)
    Bugcheck code: 0x50 (0xFFFF80005AD65928, 0x0, 0xFFFFF801935949FD, 0x2)
    Error: PAGE_FAULT_IN_NONPAGED_AREA
    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 that invalid system memory has been referenced.
    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 Sun 10/07/2016 17:37:35 GMT your computer crashed
    crash dump file: C:\WINDOWS\Minidump\071016-5062-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x1427A0)
    Bugcheck code: 0x50 (0xFFFF80019EAB2018, 0x0, 0xFFFFF802D20B9129, 0x2)
    Error: PAGE_FAULT_IN_NONPAGED_AREA
    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 invalid system memory has been referenced.
    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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.


    On Sun 10/07/2016 08:47:14 GMT your computer crashed
    crash dump file: C:\WINDOWS\Minidump\071016-5218-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x1427A0)
    Bugcheck code: 0xA (0xFFFFF79980021000, 0x2, 0x0, 0xFFFFF80122514DB0)
    Error: IRQL_NOT_LESS_OR_EQUAL
    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 Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
    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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.


    On Sat 09/07/2016 16:33:27 GMT your computer crashed
    crash dump file: C:\WINDOWS\Minidump\070916-4328-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x1427A0)
    Bugcheck code: 0x1A (0x61941, 0xFFFFC001FF9D6D98, 0x9, 0xFFFFD00141F87280)
    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 08/07/2016 21:21:05 GMT your computer crashed
    crash dump file: C:\WINDOWS\Minidump\070816-6296-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x142760)
    Bugcheck code: 0x1A (0x41792, 0xFFFFF6BFFF680E10, 0x800000000000, 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.
  2. Big thanks for posting this information.

    Looks like a critical system driver has failed. When this happens, you'll get a BSOD when booting up as these drivers are tied to the bootup process. This guide will show you how: http://www.techrepublic.com/article/rescue-an-ailing-system-launch-windows-10-startup-repair-from-the-recovery-drive/

    If the system drivers can't be repaired, the only other option is a full reformatting.

    Either way, once you're back up and running, start backing up your data! Either with a disk imager like Macrium Reflect Free or a snapshot tool like Comodo Time Machine or Rollback Rx.
  3. Best answer
    well, it looks like the system started getting bugchecks in virtual memory.

    - I would start by going to the motherboard vendors website and updating drivers, particularly any sata or storage driver.
    - i would turn off virtual memory, to delete your current hidden c:\pagefile.sys then I would turn it back on again to create a new one
    generally you want a size about 1.5 to 2 times the size of your physical RAM and make sure there is plenty of free space on your drive for the file to grow.
    - you might want to run crystaldiskinfo.exe and read the drives SMART error info to see if the drive is having problems.

    - you also had a bugcheck that had a 0xc0000005 error code, this is a bad memory address being passed to a driver.
    you will want to run memtest86 to confirm your memory timings are ok. (memory timing errors can cause any of these bugchecks)

    - since one of your bugchecks was in the file system you will want to run
    a malwarebytes scan and virus scan and run
    cmd.exe as an admin, (windows key +x, then type a)
    and run
    sfc.exe /scannow
    dism.exe /online /cleanup-image /restorehealth

    this often fixes cases where malware has infected storage drivers.

    try these and if you continue to get bugchecks, copy the actual memory dump files
    to a server like microsoft onedrive, share the files as public and post a link.
Ask a new question

Read More

windows 10 Blue Screen Boot