Windows 8 and 8.1 Forums


Multiple BSOD Bug Check Strings

  1. #1

    Multiple BSOD Bug Check Strings


    I have had at least 5 different bug check strings.

    This is the most recent one:

    A problem has been detected and Windows has been shut down to prevent damage
    to your computer.

    The problem seems to be caused by the following file: ntoskrnl.exe

    KERNEL_DATA_INPAGE_ERROR

    If this is the first time you've seen this stop error screen,
    restart your computer. If this screen appears again, follow
    these steps:

    Check to make sure any new hardware or software is properly installed.
    If this is a new installation, ask your hardware or software manufacturer
    for any Windows updates you might need.

    If problems continue, disable or remove any newly installed hardware
    or software. Disable BIOS memory options such as caching or shadowing.
    If you need to use safe mode to remove or disable components, restart
    your computer, press F8 to select Advanced Startup Options, and then
    select Safe Mode.

    Technical Information:

    *** STOP: 0x0000007a (0x0000000000000004, 0x0000000000000000, 0xfffffa801a344250,
    0x000007fe10581d3c)

    *** ntoskrnl.exe - Address 0xfffff802c2e9a340 base at 0xfffff802c2e1f000 DateStamp
    0x50ab0e64



    I've also had this:


    A problem has been detected and Windows has been shut down to prevent damage
    to your computer.

    The problem seems to be caused by the following file: ntoskrnl.exe

    MEMORY_MANAGEMENT

    If this is the first time you've seen this stop error screen,
    restart your computer. If this screen appears again, follow
    these steps:

    Check to make sure any new hardware or software is properly installed.
    If this is a new installation, ask your hardware or software manufacturer
    for any Windows updates you might need.

    If problems continue, disable or remove any newly installed hardware
    or software. Disable BIOS memory options such as caching or shadowing.
    If you need to use safe mode to remove or disable components, restart
    your computer, press F8 to select Advanced Startup Options, and then
    select Safe Mode.

    Technical Information:

    *** STOP: 0x0000001a (0x0000000000041793, 0xfffff68007258080, 0x0000000000000001,
    0x0000000000000000)

    *** ntoskrnl.exe - Address 0xfffff8019ee94340 base at 0xfffff8019ee19000 DateStamp
    0x50ab0e64


    And this...

    A problem has been detected and Windows has been shut down to prevent damage
    to your computer.

    The problem seems to be caused by the following file: ntoskrnl.exe

    DRIVER_CORRUPTED_EXPOOL

    If this is the first time you've seen this stop error screen,
    restart your computer. If this screen appears again, follow
    these steps:

    Check to make sure any new hardware or software is properly installed.
    If this is a new installation, ask your hardware or software manufacturer
    for any Windows updates you might need.

    If problems continue, disable or remove any newly installed hardware
    or software. Disable BIOS memory options such as caching or shadowing.
    If you need to use safe mode to remove or disable components, restart
    your computer, press F8 to select Advanced Startup Options, and then
    select Safe Mode.

    Technical Information:

    *** STOP: 0x000000c5 (0x0000000000000008, 0x0000000000000002, 0x0000000000000000,
    0xfffff801efaf747a)

    *** ntoskrnl.exe - Address 0xfffff801ef903340 base at 0xfffff801ef888000 DateStamp
    0x50ab0e64

    And this...

    A problem has been detected and Windows has been shut down to prevent damage
    to your computer.

    The problem seems to be caused by the following file: ntoskrnl.exe

    PAGE_FAULT_IN_NONPAGED_AREA

    If this is the first time you've seen this stop error screen,
    restart your computer. If this screen appears again, follow
    these steps:

    Check to make sure any new hardware or software is properly installed.
    If this is a new installation, ask your hardware or software manufacturer
    for any Windows updates you might need.

    If problems continue, disable or remove any newly installed hardware
    or software. Disable BIOS memory options such as caching or shadowing.
    If you need to use safe mode to remove or disable components, restart
    your computer, press F8 to select Advanced Startup Options, and then
    select Safe Mode.

    Technical Information:

    *** STOP: 0x00000050 (0xfffff88001f04004, 0x0000000000000000, 0xfffff80309329654,
    0x0000000000000000)

    *** ntoskrnl.exe - Address 0xfffff80308efa340 base at 0xfffff80308e7f000 DateStamp
    0x50ab0e64



    And I've also had this, which was not caused by the same file, but I had a feeling that the same file was involved in some way or form.

    A problem has been detected and Windows has been shut down to prevent damage
    to your computer.

    The problem seems to be caused by the following file: rdyboost.sys

    CRITICAL_PROCESS_DIED

    If this is the first time you've seen this stop error screen,
    restart your computer. If this screen appears again, follow
    these steps:

    Check to make sure any new hardware or software is properly installed.
    If this is a new installation, ask your hardware or software manufacturer
    for any Windows updates you might need.

    If problems continue, disable or remove any newly installed hardware
    or software. Disable BIOS memory options such as caching or shadowing.
    If you need to use safe mode to remove or disable components, restart
    your computer, press F8 to select Advanced Startup Options, and then
    select Safe Mode.

    Technical Information:

    *** STOP: 0x000000ef (0xfffffa8005315940, 0x0000000000000000, 0x0000000000000000,
    0x0000000000000000)

    *** rdyboost.sys - Address 0xfffffa8003cdeac0 base at 0xfffff88002109000 DateStamp
    0x5010ab52

    So my question is: How do I fix this? Do I have to reinstall Windows 8 (my computer did not come with a restore disc)? What should I do?

      My System SpecsSystem Spec

  2. #2


    I haven't had any crashes since I fixed my computer, but now I have another problem which doesn't relate to this topic, and I'll post it in another thread.
      My System SpecsSystem Spec

Multiple BSOD Bug Check Strings
Related Threads
Solved BSOD Kernel Security Check Failure in BSOD Crashes and Debugging
Hi, BSOD comes out lately very often with kernel security check failure. İt's come out i guess when watching youtube video in fullscreen and paused video and away from keyboard and screen goes off (power managment). Then i come and saw BSOD with kernel security check.
Dear Sir/Madam I am having trouble with my new notebook (Windows 8.1, 64bit), on which I keep getting BSOD errors. I tried solving the problem myself but I can't find any solution that eliminates the BSOD. Today I got a BSOD on startup saying: BSOD SYSTEM_SERVICE_EXCEPTION. BlueScreenView...
I built a computer recently. Since day one I get BSODs but the drivers, and Bug/Checks listed are never the same. I was thinking it couldn't be a single device or driver so I've: Replaced the MOBO. Repair Installed the OS. Replaced the RAM. It BSOD'd multiple times between each change. ...
BSOD every day. Kernel System Check Failure. in BSOD Crashes and Debugging
So a few nights ago I was on my computer. The power randomly went out in my neighborhood without warning despite the fact a storm wasn't present. I restart the computer and continue. Later that night I receive a BSOD Kernel System Check Failure and have to restart again. Now 3 days later, it does...
Solved BSOD kernel security check failure in BSOD Crashes and Debugging
Recently I started getting BSOD when the PC is restarting saying kernel security check failure. I have to hard reset 3-4 times in order for it to boot normally. I have no clue why, hope someone can help me :/
BSoD Kernel Check in BSOD Crashes and Debugging
I haven't blue screened in the longest of times but once again I have Blue Screened. I recently re-installed AVG, however it is the 2014 version which says it supports Windows 8.1 Below is a log I gathered for you guys. The only thing I was doing when it happened was talking on TeamSpeak
Eight Forums Android App Eight Forums IOS App Follow us on Facebook