BSOD ntoskrnl.exe Help

Page 2 of 4 FirstFirst 1234 LastLast

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

    Ugh again


    Hi Again Zigzag,

    New dump files uploaded. I am having BSOD issues again. I installed windows essentials instead of Mcafee, as well I went to HP.com and downloaded the drivers for the Ralink. Could you please help again.


    Thanks
      My Computer


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

    gstein7346 said:
    Hi Again Zigzag,

    New dump files uploaded. I am having BSOD issues again. I installed windows essentials instead of Mcafee, as well I went to HP.com and downloaded the drivers for the Ralink. Could you please help again.


    Thanks
    No NEW dmp files included in upload the most recent is from 1.5 days ago and still blames on Ralink.
      My Computer


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

    Title mini-dump


    Hey Zigzag,

    They are titled mini-dump.zip and they were from today. They were included in the post I just sent prior to this one can you please check again. Just in case they are again included in this post. Title mini-dump.zip

    Thanks
      My Computer


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

    gstein7346 said:
    Hey Zigzag,

    They are titled mini-dump.zip and they were from today. They were included in the post I just sent prior to this one can you please check again. Just in case they are again included in this post. Title mini-dump.zip

    Thanks

    My apologies, you're correct.

    Still the same cause (network driver)



    Some old drivers needing updating
    Code:
    lmimirr.sys    4/10/2007 5:32:45 PM    fffff880`077e1000    d88407ac`077e8000        0xd8840f2c00007000    0x461c108d                        
    RaInfo.sys    1/4/2008 1:57:14 PM    fffff880`06824000    fffff880`0682b000        0x00007000    0x477e818a                        
    LMIRfsDriver.sys    7/14/2008 11:26:56 AM    fffff880`0682b000    fffff300`0683e000        0xfffffa8000013000    0x487b7e50
    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


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

    Logmein?


    Hello Zigzag,

    If it is true that these 3 drivers are referring to Logmein, I can uninstall the driver and then reinstall it from the Logmein.com site. Please correct me if I am wrong with these being a Logmein issue. However, as I mentioned in my OP I have reformatted my computer and reinstalled windows 7...I had to reinstall Logmein from scratch as well. How could this still be the problem? Also Logmein is working on other machines that I have in the house with no problem.


    Thanks!
      My Computer


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

    gstein7346 said:
    Hello Zigzag,

    If it is true that these 3 drivers are referring to Logmein, I can uninstall the driver and then reinstall it from the Logmein.com site. Please correct me if I am wrong with these being a Logmein issue. However, as I mentioned in my OP I have reformatted my computer and reinstalled windows 7...I had to reinstall Logmein from scratch as well. How could this still be the problem? Also Logmein is working on other machines that I have in the house with no problem.


    Thanks!
    All three are logmein and it could be the issue.
      My Computer


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

    Again


    Hey Zigzag,

    Ugh I got a new report new BSOD attached to this post. Could you please assist?

    Zip is titled again.zip

    Thanks
      My Computer


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

    gstein7346 said:
    Hey Zigzag,

    Ugh I got a new report new BSOD attached to this post. Could you please assist?

    Zip is titled again.zip

    Thanks
    Again this was caused by memory corruption.

    If you havent already please run these two tests.



    These crashes were caused by memory corruption (probably a driver). Please run these two tests to verify your memory and find which driver is causing the problem.

    If you are overclocking anything reset to default before running these tests.
    In other words STOP!!!



    1-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.

    Any errors are indicative of a memory problem.

    If a known good stick fails in a motherboard slot it is probably the slot.

    RAM - Test with Memtest86+



    2-Driver verifier

    Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable 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


    Further Reading
    Using Driver Verifier to identify issues with Windows drivers for advanced users
    Last edited by zigzag3143; 10 Jan 2012 at 15:10.
      My Computer


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

    Still continuous


    Hey Zigzag,

    As mentioned in OP I have already ran memtest86 and all checks out. As far as I know I am not overclocking. I am sorry I am a little baffled still as to the understanding. But I did the driver verifier utility, and as normal behavior may 6 hours after it crashed. I was never having a immediate crash problem from the boot of the computer. So in other words I just notice the BSOD's occurring as the same way they've always done.

    Same mini-dump message as the again.zip.


    Please help!
      My Computer


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

    I know this hasn't been 36 hours but its been at least 24 and you said only 36 really if you dont notice a bsod in that span in your last post
      My Computer


 
Page 2 of 4 FirstFirst 1234 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 10:21.
Find Us