BSOD ntoskrnl.exe Help

[gstein7346]

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

 

[zigzag3143]

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.

 

[gstein7346]

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

 

[zigzag3143]

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/licensed/cust_support_patches/MCPR.exe

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

 

[gstein7346]

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!

 

[zigzag3143]

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?

 

[gstein7346]

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!

 

[zigzag3143]

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.

 

[gstein7346]

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

 

[zigzag3143]

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

 

[gstein7346]

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

 

[zigzag3143]

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.

 

[gstein7346]

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

 

[zigzag3143]

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

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

 

[gstein7346]

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!

 

[zigzag3143]

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.

 

[gstein7346]

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

 

[zigzag3143]

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.

http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html



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.

http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html


Further Reading
Using Driver Verifier to identify issues with Windows drivers for advanced users

 

[gstein7346]

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!

 

[gstein7346]

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