Random BSOD, multiple codes - ntoskrnl.exe, fltmgr.sys, Ntfs.sys

Hello,

A couple weeks ago i bought a brand new notebook (a Lenovo G470, running Windows 7 Home Premium x64 ) and a few days ago, it started BSOD'ing, to the point that it was impossible to use the computer because the BSOD happened almost every time.
The BSOD all had random error codes and almost always were because of ntoskrnl.exe, one time fltmgr.sys and another time fileinfo.sys (i think), according to bluescreenview.

I ran memtest for 2 passes and it right on the beginning it found like 400.000 errors.

I called Lenovo support and they told me to format the computer using Lenovo's system partiton. After the format, i just left the pc running idle and, after a while, it BSOD again.

Booting in safe mode did not give BSOD. I also ran Ubuntu 10.04 via Live USB and did not have any crashes. In Ubuntu, i left the computer running multiple 1080p mkv movies in loop for half a day and also opened dozens of programs at once to try and stress the system, and no crashes. Temperature was normal.

After that, i ran:
Memtest - No errors (the 400k errors found before dont appear anymore)
Prime95 for a few hours - No errors/crashes
Furmark - No errors/crashes, temperatures ok
Seatools (Seagate HD Diagnostics) - No errors/crashes
Lenovo's LSC Lite HD and Memory diagnostics - No errors/crashes

Even with all those tests, i still got a few BSOD later.
So, i was thinking that maybe the Lenovo's recovery system had a corrupted windows installation (or there was a conflict with the pre-installed softwares/drivers) and decided to try another windows version. I formatted again/deleted the partitions and installed Windows 7 Ultimate x64.

After the second format (now with Windows 7 Ultimate x64), i left the pc running completely clean of drivers and applications for a few hours and no crashes. So, i installed a few drivers and a few applications. I went to sleep and left Windows downloading updates. All seemed well. But this morning, when installing the Windows' updates, the system BSOD again. (The dump file is attached)

I really want to make sure that i have a hardware problem before sending it to the repair shop, which can take up to 30 days to get the computer back.

So, any help will be greatly appreciated! And sorry for the really long text,i wanted to give the max number of informations as possible.

The system specs are:
Model: Lenovo G470
Processor: Intel Core I5 2410m
Ram Memory: 4 GB, 1 stick
Graphics: Intel HD 3000
OS: Windows 7 Home Premium x64 OEM
(After 2nd format, Windows 7 Ultimate x64 retail, installed yesterday)

Almost impossible to diagnose a problem from a single DMP. There is no way to spot trends, etc. If this DMP is from the final re-install, and is supposed clean there are BT drivers, etc.

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



This crash was related to a memory exception (probably a driver). You need to run memtest for 6-8 continuous passes.

Also run verifier as indicated below.



These crashes were caused by memory corruption/exception (Cx05) 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!!!

* If you have raid update its Driver.



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-7 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+



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.

So, I'd suggest that you first backup your stuff 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).

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 "Special Pool", "Force Pending I/O Requests" and "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.

Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.

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. You did create a restore point didnt you?

Using Driver Verifier (Windows Drivers)

ShadowKyuzo said:

Thanks for the reply. I had like 20 dump files from the previous blue screens, but unfortunately i did not save them before formatting. (damn...)

I'm gonna ran memtest again for more passes and also use Driver Verifier.

If more BSOD occur, i will update this thread with the new dump files.

Thanks again.

Our pleasure and let us know if you need help.

ken

Three of 4 DMPS were corrupt and unreadable. The 4th still a memory exception, not verified.

One thing of note is you may want to update to SP-1. Probably cant hurt.

Please run the System Update Readiness Tool (SURT) and then update to SP-1


32 Bit

Download: System Update Readiness Tool for Windows 7 (KB947821) [February 2012] - Microsoft Download Center - Download Details

64 Bit

Download: System Update Readiness Tool for Windows 7 for x64-based Systems (KB947821) [February 2012] - Microsoft Download Center - Download Details


Now update to SP-1

Learn how to install Windows 7 Service Pack 1 (SP1)

zigzag3143 said:

Three of 4 DMPS were corrupt and unreadable. The 4th still a memory exception, not verified.

One thing of note is you may want to update to SP-1. Probably cant hurt.

Please run the System Update Readiness Tool (SURT) and then update to SP-1


32 Bit

Download: System Update Readiness Tool for Windows 7 (KB947821) [February 2012] - Microsoft Download Center - Download Details

64 Bit

Download: System Update Readiness Tool for Windows 7 for x64-based Systems (KB947821) [February 2012] - Microsoft Download Center - Download Details


Now update to SP-1

Learn how to install Windows 7 Service Pack 1 (SP1)

Thanks again for replying.

Sorry for sending corrupted dumps. Do you have any idea why even the dumps were corrupted? In one of the BSOD, the system hanged when "copying dump contents to disc" (or something like that), what could cause this?

I'm gonna run the SURT tool and update to SP1, but i think tomorrow i will call Lenovo and get a service order.

Any resolution on this? I'm having almost identical problems with the same stop errors/driver files. Just started happening a few days ago.

tmaculate1 said:

Any resolution on this? I'm having almost identical problems with the same stop errors/driver files. Just started happening a few days ago.

I gave up trying to fix it and sent it to the repair shop. They told me it was a problem with the hard drive and they are going to replace it, but i haven't received it from the repair shop yet.

When i get the computer back i wll update this thread to say if switching the hard drive really fixed the problem.