Solved BSOD on New Win7 x64 - ntoskrnl.exe+7f1c0 - random ~ every few days.

[abreingan]

Hi,
I built the Ivy Bridge machine described in my system specs a couple of weeks ago, and all went well except that I am getting BSOD’s every few days 5 in all.
Bluescreen view shows them as MEMORY_MANAGEMENT from ntoskrnl.exe+7f1c0 or Ntfs.sys+a4990 though there is one IRQL_NOT_LESS_OR_EQUAL also from ntoskrnl.exe+7f1c0.
No obvious causes that I can see though they often happen in Firefox.
I have:-
Run memtest - all shows as good.
Run sfc /verifyonly no problems
Run Crystal Disk Info which shows Good on all 3 drives
Run the Check Drive for errors (from the drive properties)
So I am throwing myself on your mercy, and hoping you can point me at any further tests I should try.
I attach the zip as described in your howto (I hope).
Thanks in advance for whatever help you can provide.

 

[zigzag3143]

These crashes were caused by memory management 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 a Raid update its Driver.



Memtest. If you havent run memtest for 6-8 passes please run it again, if you have start with driver verifier

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

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






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

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"IRP Logging and Force Pending I/O Requests. and click "Next"
NOTE: You can use Low Resource Simulation if you'd like.
From my limited experimentation it makes the BSOD's come faster.
- 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.

If you are using win 8 add these
- Concurrency Stress Test
- DDI compliance checking


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.

Thanks to JCGriff2 & Usasma.

Sysnative Forums

Driver Reference Table (DRT)

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

Driver Verifier

Using Driver Verifier (Windows Drivers)

 

[abreingan]

Thanks for that advice. I had previously run the Windows memory check, but have now run Memtest86+ and it reports errors between address 002249b8080 and 002249bbff8 error mask 000000ff Strangely it also shows errors in all of the 4 slots which doesn't sound right.

So i will now try various combinations of sticks and see how we go.

Thanks again.

 

[zigzag3143]

If it is memory it will move from slot to slot if it is the mobo slot it will not. Try a know good stick in each mobo slot.

 

[abreingan]

Thanks very much zigzag3143 for your patient and professional advice. The memory is definitely the cause as one stick always fails memtest86+ and the rest don't. Its being returned/replaced.

Thanks again

Alastair Breingan

 

[zigzag3143]

Thanks very much zigzag3143 for your patient and professional advice. The memory is definitely the cause as one stick always fails memtest86+ and the rest don't. Its being returned/replaced.

Thanks again

Alastair Breingan

My pleasure AB

Good job, and good luck. Dont forget to yell if you need help.

Ken