Windows 8 and 8.1 Forums


getting random BSOD. now cannot boot at all

  1. #1


    Posts : 3
    Windows 8

    getting random BSOD. now cannot boot at all


    getting all kinds of BSOD since a few days ago. the first time it happened was when i was installing a AMD GPU driver half way. after that i rolled back to a stable driver thinking that was the one causing it but it only kept happening again. i started getting errors like memory management, pagefault in nonpaged area, system service exception, critical structure and a few others. with files like ntoskrnl.exe suddenly going missing and most recently Windows\system32\config\system. It could either be my HDD or RAM but im not sure. i did change my RAM about a month ago but didnt have any kind of problems.


    I did chkdsk for my C drive via CD recovery and the result was 0 problems other than getting "failed to transfer logged messages to the event log with status 50" at the end. I tried doing a refresh but got the message saying my hard drive is locked ("The drive where windows is installed is locked. Unlock drive and try again"). I never locked my drive before but Acer might have.



    the BSOD thing is on and off as well. sometimes my PC works fine for hours and other times it just doesn't. this has happened for the past few days. I will try to post the crash logs if i manage to turn on my PC again.

    is there a way to find out what is causing this? what should i do?


    edit: logs

    On Fri 20/09/2013 12:04:24 PM GMT your computer crashed
    crash dump file: C:\WINDOWS\Minidump\092013-33265-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x5A440)
    Bugcheck code: 0x1A (0x41284, 0x4F28CE8001, 0x276E, 0xFFFFF70001080000)
    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 20/09/2013 12:04:24 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 (0x41284, 0x4F28CE8001, 0x276E, 0xFFFFF70001080000)
    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 Fri 20/09/2013 10:46:20 AM GMT your computer crashed
    crash dump file: C:\WINDOWS\Minidump\092013-61640-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x5A440)
    Bugcheck code: 0x21 (0xFFFFFA800F41F3C0, 0x3, 0x9163, 0x6315)
    Error: QUOTA_UNDERFLOW
    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 quota charges have been mishandled by returning more quota to a particular block than was previously charged.
    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 19/09/2013 11:52:00 AM GMT your computer crashed
    crash dump file: C:\WINDOWS\Minidump\091913-48234-01.dmp
    This was probably caused by the following module: Unknown ()
    Bugcheck code: 0x0 (0x0, 0x0, 0x0, 0x0)
    Error: CUSTOM_ERROR
    A third party driver was identified as the probable root cause of this system error.
    Google query: CUSTOM_ERROR



    On Thu 19/09/2013 11:49:47 AM GMT your computer crashed
    crash dump file: C:\WINDOWS\Minidump\091913-44296-01.dmp
    This was probably caused by the following module: Unknown ()
    Bugcheck code: 0x0 (0x0, 0x0, 0x0, 0x0)
    Error: CUSTOM_ERROR
    A third party driver was identified as the probable root cause of this system error.
    Google query: CUSTOM_ERROR



    On Thu 19/09/2013 10:51:02 AM GMT your computer crashed
    crash dump file: C:\WINDOWS\Minidump\091913-50453-01.dmp
    This was probably caused by the following module: win32k.sys (win32k+0x62386)
    Bugcheck code: 0x3B (0xC0000005, 0xFFFFF960001C3386, 0xFFFFF8800DB580A0, 0x0)
    Error: SYSTEM_SERVICE_EXCEPTION
    file path: C:\WINDOWS\system32\win32k.sys
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: Multi-User Win32 Driver
    Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
    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 Wed 18/09/2013 11:30:44 AM GMT your computer crashed
    crash dump file: C:\WINDOWS\Minidump\091813-52421-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x5A440)
    Bugcheck code: 0x109 (0xA3A039D8A35D792B, 0x0, 0xED1E2A5CA832889E, 0x101)
    Error: CRITICAL_STRUCTURE_CORRUPTION
    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 the kernel has detected critical kernel code or data corruption.
    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 18/09/2013 11:07:52 AM GMT your computer crashed
    crash dump file: C:\WINDOWS\Minidump\091813-72437-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x5A440)
    Bugcheck code: 0x18 (0xFFFFFA800853E750, 0xFFFFFA8012C1C640, 0x1, 0x800000000000)
    Error: REFERENCE_BY_POINTER
    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 the reference count of an object is illegal for the current state of the object.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 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.



    edit 2: did a windows memory diagnostic and did not have any issues. however the computer got seizures after that ( screen kept flickering) and then said windows/system32/winload.exe could not be loaded

      My System SpecsSystem Spec

  2. #2


    Posts : 5,139
    Win8.1Pro - Finally!!!


    For starters:
    At work we start all repairs with a set of diagnostics. Often they find problems that weren't even expected. It's a waste of time to try to fix software on a system that has hardware problems.
    Please try these free diagnostics for starters: Initial Hardware Diagnostics
    Also, please ensure that you have ALL available Windows Updates (it may take several trips to get them all).
    As soon as you get it to boot into Windows - run the report collection tool
    That'll provide us with the best info.
      My System SpecsSystem Spec

  3. #3


    Posts : 3
    Windows 8


    Quote Originally Posted by usasma View Post
    For starters:
    At work we start all repairs with a set of diagnostics. Often they find problems that weren't even expected. It's a waste of time to try to fix software on a system that has hardware problems.
    Please try these free diagnostics for starters: Initial Hardware Diagnostics
    Also, please ensure that you have ALL available Windows Updates (it may take several trips to get them all).
    As soon as you get it to boot into Windows - run the report collection tool
    That'll provide us with the best info.
    and how do i get that collection tool?

    edit: ran a seagate DOS ram test. no problems detected after running for 6+ hours. running memtest86 now
    Last edited by kudoboi; 22 Sep 2013 at 00:36.
      My System SpecsSystem Spec

  4. #4


    Posts : 3
    Windows 8


    they found 33 errors. am i supposed to be worried about this? edit: now 100

    Attachment 28149
    Last edited by kudoboi; 22 Sep 2013 at 03:23.
      My System SpecsSystem Spec

  5. #5


    Posts : 5,139
    Win8.1Pro - Finally!!!


    Please provide this information so we can provide a complete analysis (this is the data/report collection tool link): Blue Screen of Death (BSOD) Posting Instructions

    RAM errors like that mean bad RAM.
    Try the steps at this link for figuring out which stick/slot it is: Memory Diagnostics
    The steps start around Step 6 or 7

    You must fix the RAM errors before we move on - as it's very difficult trying to fix software errors that are masked by hardware problems.

    Good luck!
      My System SpecsSystem Spec

getting random BSOD. now cannot boot at all
Related Threads
Random BSOD at random times in BSOD Crashes and Debugging
Hello, Im new here so bare with me :think: I built my custom pc a year ago now. Since day one iv been experiencing BSOD. At first it happened during or just after the first boot up of that day and was always Memory Management error. Soon after, i upgraded my ram from 4gb to 8 gb. After doing this...
I have been getting a ton of bsods I have re installed video drivers, updated and reinstalled windows 8. Did countless hardware test(Video ram, check memory, Cpu test) all passed temperatures stay around 25-35 c. Recently uninstalled all video drivers and re installed. The bsods sometimes go away...
BSOD at Random Times for Random Reasons in BSOD Crashes and Debugging
DCP Watchdog, Memory Management, Kernel Security Failure and several others at random times - especially during large file transfers between drives. I did a memory test and it stated there was an issue but I removed the culprit and the random BSOD continues. Thanks for your help
Hi all, I get a random BSOD when I boot my HP Pavilion 15-e073sa notebook. It's only on boot up, and only every 2 or 3 boots it gives me a REFERENCE_BY_POINTER and reboots, usually with no problem. Any help would be appreciated, thanks!
Hey guys, so I am in a bit of a pickle. I have an HP m6-k015dx laptop and it is giving me hell. I will get random BSOD's, usually at or a short while after login. They usually happen consecutively and then stop. I was able to enable driver verifier in order to see what was wrong. After it was...
Hi, i'm new to this forum and i hope you guy can help me :) So my laptop is relatively new, it's not even a month old. I guess i've been downloading a lot of stuff that caused this error. Now, i'm not a computer expert or any type of expert, so please bear with me :D Before i go on, here are...
Random BSOD on Windows 8 boot in BSOD Crashes and Debugging
Hello, I am running Windows 8 installed on a corsair SSD but I also have a PCIe RAID controler (Raidcore RC5252-08). My BSOD only happens when Windows is starting after the pc was powered off. After a BSOD, the system restart itself and windows boot normally. I suspect the Raid controler...
Eight Forums Android App Eight Forums IOS App Follow us on Facebook