BSOD ntoskrnl.exe Help

Page 1 of 4 123 ... LastLast

  1. Posts : 20
    Windows 7 64
       #1

    BSOD ntoskrnl.exe Help


    Hello,

    I keep getting a BSOD randomly and when I tried to debug the mini dump I get that ntoskrnl.exe may be the cause. I removed my keyboard which may be a resolution and this still didn't fix the issue as it has crashed again. I have also checked all forms of hardware. Crashes w/o graphics card. I have reformated OS, ran a memtest86 and also a hard drive check and it all checks out okay. I am under the impression after doing some research that it may be the boot.ini?, but I am also reading that windows 7 doesn't use this file...What else could I try anyone please?

    mini dump files included

    I have a....

    HP P6540Y
    1TB HD
    8 GB DD3
    AMD Phenom II 830 / 2.8 GHz
    Evga GTX 460 768MB
    Last edited by gstein7346; 02 Jan 2012 at 15:42. Reason: Attachments
      My Computer


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

    gstein7346 said:
    Hello,

    I keep getting a BSOD randomly and when I tried to debug the mini dump I get that ntoskrnl.exe may be the cause. I removed my keyboard which may be a resolution and this still didn't fix the issue as it has crashed again. I have also checked all forms of hardware. Crashes w/o graphics card. I have reformated OS, ran a memtest86 and also a hard drive check and it all checks out okay. I am under the impression after doing some research that it may be the boot.ini?, but I am also reading that windows 7 doesn't use this file...What else could I try anyone please?

    mini dump files included

    I have a....

    HP P6540Y
    1TB HD
    8 GB DD3
    AMD Phenom II 830 / 2.8 GHz
    Evga GTX 460 768MB
    Bet you used blue screen view or whocrashed.

    Ntoskrnl.exe is probably (almost certainly) not the cause. It isnt boot.ini either unless you are infected.



    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.

    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.
    Last edited by zigzag3143; 03 Jan 2012 at 00:02.
      My Computer


  3. Posts : 20
    Windows 7 64
    Thread Starter
       #3

    Crash Report Already Attached


    Hey Zigzag I used WinDbg, also I may not have identified it well in the OP but the crash report is attached as a ZIP title "Hotmail" do you see?

    Thanks in advance
      My Computer


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

    gstein7346 said:
    Hey Zigzag I used WinDbg, also I may not have identified it well in the OP but the crash report is attached as a ZIP title "Hotmail" do you see?

    Thanks in advance
    I open the zip/rar files and export the dmp files with a script, so I ddint notice. Happy to take a look.


    EDIT:


    Only thing in the zip is two DMP files, nothing else.





    In WIndbg There are two causes reported. The Net28.... Ralink driver seems to be the culprit in both.



    On another note. Your McAffee is often at least a contributing cause in BSOD's and might be here.




    I do notice McAffee which is a frequent cause of BSOD's. I would remove and replace it with Microsoft Security Essentials AT LEAST TO TEST!


    http://download.mcafee.com/products/...tches/MCPR.exe


    http://www.microsoft.com/security_essentials/
      My Computer


  5. Posts : 20
    Windows 7 64
    Thread Starter
       #5

    Will try


    Hello Zigzag,

    I will surely try that by replacing the Mcafee. However I was wondering what you thought about the fact that I have already reformatted this computer with a windows 7 and then had to manually reinstall mcafee again, and then this BSOD error continued. Also I have other machines with this copy of Mcafee and they work fine. Knowing this can we rule this out? Or should I ultimately try it anyway?

    Besides that, could you touch a little more on the Ralink concern please and was it just based on my dump report that you determined it to be one of the 2 issues you mentioned?


    Thank you again!
      My Computer


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

    gstein7346 said:
    Hello Zigzag,

    I will surely try that by replacing the Mcafee. However I was wondering what you thought about the fact that I have already reformatted this computer with a windows 7 and then had to manually reinstall mcafee again, and then this BSOD error continued. Also I have other machines with this copy of Mcafee and they work fine. Knowing this can we rule this out? Or should I ultimately try it anyway?

    Besides that, could you touch a little more on the Ralink concern please and was it just based on my dump report that you determined it to be one of the 2 issues you mentioned?


    Thank you again!
    McAffee is known to cause BSOD's on some systems.

    No definitive proof for or against it

    The ralink driver is definitive.

    Where?
      My Computer


  7. Posts : 20
    Windows 7 64
    Thread Starter
       #7

    Where?


    Hey Zigzag,

    You said "where?" what are you asking where to?

    Also how are you suggesting I resolve the Ralink issue? HP.com, re-install driver? I would prefer a free method where possible.

    Thanks!
      My Computer


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

    gstein7346 said:
    Hey Zigzag,

    You said "where?" what are you asking where to?

    Also how are you suggesting I resolve the Ralink issue? HP.com, re-install driver? I would prefer a free method where possible.

    Thanks!
    Sorry.

    Ralink was clearly pointed to in the crash log. Driver should be re-installed using the newest version available. Will be free of course.
      My Computer


  9. Posts : 20
    Windows 7 64
    Thread Starter
       #9

    Thanks


    Hey Zigzag,

    Thank you much, I have already implemented both and we'll just have to wait it out to see I guess if it didn't fix.

    If it's not too much trouble and not too extensive could you point out where the dump info indicates Ralink?


    Thanks
      My Computer


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

    gstein7346 said:
    Hey Zigzag,

    Thank you much, I have already implemented both and we'll just have to wait it out to see I guess if it didn't fix.

    If it's not too much trouble and not too extensive could you point out where the dump info indicates Ralink?


    Thanks
    Be happy to if you have the proper tools. DMP files are written in machine language using sets of symbols. Without the proper tools it looks like this.


    See pix
    Last edited by zigzag3143; 29 Feb 2012 at 00:41.
      My Computer


 
Page 1 of 4 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 01:24.
Find Us