BSOD ntoskrnl.exe


  1. Posts : 1
    Windows 7 64bit
       #1

    BSOD ntoskrnl.exe


    I looked at my minidumps and all I see are:
    hal.dll
    ntoskrnl.exe
    tcpip.sys
    ntoskrnl.exe
    ..... < dots mean same as above
    .....
    .....
    Unknown_Module_0000...
    ntoskrnl.exe
    .....
    .....
    dxgkrnl.sys
    ntoskrnl.exe
    .....

    So...Whats the next step...I see these minidumps, but I don't know what to do now.

    A little background information on my problems:
    When I boot up my computer in the morning normally it freezes and I have to restart the computer 5 times or so before it stops freezing. Then I get a bsod about 5 minutes after being on the desktop. After a while the BSODs become less frequent and finally stop at the end of the night. Then back to square one in the morning. Can anybody help me out?
      My Computer


  2. Posts : 28,845
    Win 8 Release candidate 8400
       #2

    Stuntabeck said:
    I looked at my minidumps and all I see are:
    hal.dll
    ntoskrnl.exe
    tcpip.sys
    ntoskrnl.exe
    ..... < dots mean same as above
    .....
    .....
    Unknown_Module_0000...
    ntoskrnl.exe
    .....
    .....
    dxgkrnl.sys
    ntoskrnl.exe
    .....

    So...Whats the next step...I see these minidumps, but I don't know what to do now.

    A little background information on my problems:
    When I boot up my computer in the morning normally it freezes and I have to restart the computer 5 times or so before it stops freezing. Then I get a bsod about 5 minutes after being on the desktop. After a while the BSODs become less frequent and finally stop at the end of the night. Then back to square one in the morning. Can anybody help me out?
    You have a few problems that need to be fixed

    1-Kaspersky and Norton both are known causes of BSOD's on some systems. I would remove them and replace with Microsoft Security essentials

    http://support.kaspersky.com/downloa...vremover10.zip

    http://us.norton.com/support/kb/web_...080710133834EN

    Virus, Spyware & Malware Protection | Microsoft Security Essentials


    2- Some of these (6 of 16) were blamed directly on memory management. Please run these two tests to verify your memory and determmine which driver is causing the problem


    ****-Memtest.

    *Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Memtest86+ - Advanced Memory Diagnostic Tool

    *Boot from the CD, and leave it running for at least 5 or 6 passes.

    Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot.

    Test the sticks individually, and if you find a good one, test it in all slots.

    RAM - Test with Memtest86+



    *****-Driver verifier

    I'd suggest that you first backup your data and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

    In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .

    Then, here's the procedure:
    - Go to Start and type in "verifier" (without the quotes) and press Enter
    - Select "Create custom settings (for code developers)" and click "Next"
    - Select "Select individual settings from a full list" and click "Next"
    - Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
    - Select "Select driver names from a list" and click "Next"
    Then select all drivers NOT provided by Microsoft and click "Next"
    - Select "Finish" on the next page.

    Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

    If you can't get into Windows because it crashes too soon, try it in Safe Mode.
    If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.
    Driver Verifier - Enable and Disable


    3-Several of these crashes were Related to Rt64win7.sys 8101E/8168/8169 NDIS 6.20 64-bit Driver from Realtek Corporation. I would re-install the newest version available.

    How To Find Drivers:
    - search Google for the name of the driver
    - compare the Google results with what's installed on your system to figure out which device/program it belongs to
    - visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
    - if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.
    - - The most common drivers are listed on this page: Driver Reference Driver Reference
    - - Driver manufacturer links are on this page: Drivers and Downloads
      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 03:29.
Find Us