Random BSOD's by ntoskrnl.exe

Page 1 of 3 123 LastLast

  1. Posts : 13
    windows 7 ultimate 64 bit
       #1

    Random BSOD's by ntoskrnl.exe


    Hi i'm new to this forum, so bare with me.
    Im getting BSOD's very randomly i tried everything that i can think of like update everything to the latest, tested the memory with memtest(no errors were found) ran chkdsk nothing is working and im getting a bit frustrated the dump files are attached to this thread all help would be highly appretiated
      My Computer

  2.    #2

    Code:
    BugCheck 1000007E, {ffffffffc0000005, fffff80002cc4281, fffff880031af0a8, fffff880031ae900}
    
    Probably caused by : memory_corruption ( nt!MiGetNextNode+15 )
    Code:
    Usual causes:  Insufficient disk space, Device driver, Video card, BIOS, Breakpoint with no debugger attached, Hardware incompatibility, Faulty system service, Memory, 3rd party remote control
    memory_corruption doesn't necessary mean that a RAM module is faulty, it can also point to a object which corrupted the RAM at the time of the crash, for instance a corrupted driver or program. Paging files and the CPU caches can also be causes.

    Follow these steps -

    Test for any corrupted drivers, by running Driver Verifier for least 24 hours, stop the test if a BSOD occurs before this time frame. Driver Verifier will place stress on the drivers within your system, which will cause corrupted drivers to crash and hopefully be pinpointed.

    Memory:

    Run Memtest86+ for least 7-8 passes, and preferrly overnight as it can take a while to fully complete.

    Test each RAM stick individually, if an error is found then move the same RAM stick into the next DIMM slot and test again, if errors are found for the same RAM stick in every available slot then you have a faulty RAM module. On the other hand, if no errors are found in the next slot or the other slots for the same RAM module, then you have a faulty DIMM slot.

    Test each RAM stick and every motherboard DIMM slot available.

    Upload a .NFO file:

    Start > Type: msinfo32 > File, Save

    Use this tutorial to upload the file:
      My Computer


  3. Posts : 13
    windows 7 ultimate 64 bit
    Thread Starter
       #3

    i ran verifier and restarted windows after windows booted and loaded programs i got a bsod AsIO.sys annd disabled driver verifier after restart.

    All msinfo32 is added as in the SF zip.

    i will run memtest during the night tonight.

    also i would like to add that when i play games like assassins creed and whatsoever i dont get bsod while playing.

    thanks for the fast reply
      My Computer

  4.    #4

    Code:
    BugCheck C4, {f6, 14c, fffffa8008029950, fffff88004566b03}
    
    *** WARNING: Unable to verify timestamp for AsIO.sys
    *** ERROR: Module load completed but symbols could not be loaded for AsIO.sys
    Probably caused by : AsIO.sys ( AsIO+1b03 )
    Remove ASUS:

    Code:
    Start Menu\Programs\ASUS
    The driver is related to ASUS, and therefore I recommend you remove any ASUS software from your system:

    Start > Computer > Uninstall/Change Program > Select ASUS > Uninstall
      My Computer


  5. Posts : 13
    windows 7 ultimate 64 bit
    Thread Starter
       #5

    ok i ran memtestx86 and no errors. i removed all asus programs and still bsod's happening
    im now running sfc /scannow will be back with results
      My Computer


  6. Posts : 13
    windows 7 ultimate 64 bit
    Thread Starter
       #6

    ok sfc is done now its telling me that there are some corrupted files that it wasnt able to fix. also i noticed that most of the time im watching a video on youtube it somehow speeds up thing and get bsods more frequently can it be a video card malfunction?

    EDIT: these are the files that sfc cannot fix because the source file is also corrupt
    MSOERES.dll
    NlsData0416.dll
    M1033DSK.CSD
    Last edited by Nikla; 12 Dec 2012 at 03:30. Reason: sfc results
      My Computer

  7.    #7

    Do you have a Windows 7 Installation DVD?
      My Computer


  8. Posts : 13
    windows 7 ultimate 64 bit
    Thread Starter
       #8

    yes i have one.
    i now tried removing one memory module and started the computer then after an hour or so i turned off the pc and changed the slot on the other empty one after 13 minutes i got a bsod saying :
    crash dump file: C:\Windows\Minidump\121212-19874-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)
    Bugcheck code: 0xBE (0xFFFFF8A00978FE30, 0x200000060, 0xFFFFF88008AEC530, 0xE)
    Error: ATTEMPTED_WRITE_TO_READONLY_MEMORY
    file path: C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: This is issued if a driver attempts to write to a read-only memory segment.
    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.
    plus i already got about 13 bsods today already
      My Computer

  9.    #9

    Upload the files and try to do a Repair Install, to repair or replace the corrupted Windows files:
      My Computer


  10. Posts : 13
    windows 7 ultimate 64 bit
    Thread Starter
       #10

    Here are the files. will start repair now
      My Computer


 
Page 1 of 3 123 LastLast

  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 06:55.
Find Us