BSOD starting Windows 64bit, error 0x0000001e


  1. Posts : 1
    Windows 7 Home Premium 64bit
       #1

    BSOD starting Windows 64bit, error 0x0000001e


    Hello,

    Sometimes when I start up my Windows 64bit Home Premium, I get a BSOD.
    At this moment, I have 50 crashes listed. The error messages are as following and pure randomly:

    - KMODE_EXCEPTION_NOT_HANDLED
    - SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
    - DRIVER_CORRUPTED_EXPOOL
    - IRQL_NOT_LESS_OR_EQUAL
    - ATTEMPTED_WRITE_TO_READONLY_MEMORY
    - PFN_LIST_CORRUPT
    - NTFS_FILE_SYSTEM

    I use the program bluescreenview to view the error messages, and when I click on one error message, I see always that the file called ntoskrnl.exe is involved. Always, in each crash report.

    I heard from a friend, that ntoskrnl.exe and intel network driver can cause problems..

    Soo, I hope someone is able to help me out, this really annoys me for quite a while. I am almost sure this is caused by ntoskrnl, but I'm not sure though..

    If you need any more info about those crashes, ask and I'll give!

    Thanks,
    Tankey
      My Computer


  2. JMH
    Posts : 7,952
    Win 7 Ultimate 64-bit. SP1.
       #2

    * I am a big fan of Nir Sofer's work, BUT blueScreenView more often than not, doesn't point out the correct causes. Similarly Who crashed is even worse.

    I prefer to use WinDbg (the Windows Debugging Tools) to read the memory dumps. It is the Gold standard for those of us that do this and often will give us the answer by itself. (we don't need the full jcgriff2 report each time).



    *
    We do need the DMP file as it contains the only record of the sequence of events leading up to the crash, what drivers were loaded, and what was responsible.

    Please attach the DMP files to your next post not to post one.


    If you are overclocking STOP


    You may be able to get the DMP files without crashing by booting into safe mode (F8) with networking.

    To enable us to assist you with your computer's BSOD symptoms, upload the contents of your "\Windows\Minidump" folder.

    The procedure:
    * Copy the contents of \Windows\Minidump to another (temporary) location somewhere on your machine.
    * Zip up the copy.
    * Attach the ZIP archive to your post using the "paperclip" (file attachments) button.
    *If the files are too large please upload them to a file sharing service like "Rapidshare" and put a link to them in your reply.
    To ensure minidumps are enabled:
    * Go to Start, in the Search Box type: sysdm.cpl, press Enter.
    * Under the Advanced tab, click on the Startup and Recovery Settings... button.
    * Ensure that Automatically restart is unchecked.
    * Under the Write Debugging Information header select Small memory dump (256 kB) in the dropdown box (the 256kb varies).
    * Ensure that the Small Dump Directory is listed as %systemroot%\Minidump.
    * OK your way out.
    * Reboot if changes have been made.


      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 23:49.
Find Us