Intermittent computer crashes with BSOD - Please help

[tal valler]

Hi,
For the past few weeks my computer has been crashing every couple of hours for some obscure reason.

I've tried doing a system restore but as soon as win 7 completes it's updates after the restore the problem persists.

I've also tried doing a repair, but the windows installation CD supplied by the store with the computer doesn't have the repair option for some reason when booting from it.

attached is the following support data in a zip file:
the contents of my Windows_NT6_BSOD_jcgriff2 folder
the performance manager report
an Everest report of my system stats
A bluescreenview report of the crashes (it claims the culprit is the ntoskrnl driver).

Please HELP... what can I do?

 

[zigzag3143]

Memory management probably caused by your Symantec. I would remove and replace it at least to test.

Symantec is a frequent cause of BSOD's. I would remove and replace it with Microsoft Security Essentials AT LEAST TO TEST


http://us.norton.com/support/kb/web_view.jsp?wv_type=public_web&docurl=20080710133834EN

Microsoft Security Essentials - Free Antivirus for Windows

 

[tal valler]

Thanks,
I had a hunch that that might be the cause...

I'll uninstall and see how it goes.

As far as you know btw, is Microsoft security essentials a satisfactory protection system? or should I install AVG or something similar?

 

[zigzag3143]

Thanks,
I had a hunch that that might be the cause...

I'll uninstall and see how it goes.

As far as you know btw, is Microsoft security essentials a satisfactory protection system? or should I install AVG or something similar?

MSE is a good lightweight app to use in the interim.

Personally I like a malware app that has a firewall built in.

 

[tal valler]

Computer just went blue screen again, so I guess that wasn't it...
Any other ideas?

I'm kinda stuck

 

[zigzag3143]

Computer just went blue screen again, so I guess that wasn't it...
Any other ideas?

I'm kinda stuck

Would have more of an idea if you uploaded the DMP file.

 

[tal valler]

oops... I was sure I uploaded them through the zipped folder.

Here they are, attached.

thanks in advance for the help. I'm really at a loss on how to resolve this.

btw. there are several dmp files attached and it seems that more then one driver might be the cause.

on bluescreenview it gives 3 different drivers as the cause (a different one in the each of the last 3 crashes):

nvlddmkm.sys
SYMEFA64.SYS
ntoskrnl.exe

 

[zigzag3143]

Still memory management lets try checking the ram and drivers




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.

*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" 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 JGriff2 & Usasma.

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

Driver Verifier

Using Driver Verifier (Windows Drivers)

 

[tal valler]

hi...
weird, but after new automatic updates the system sort of fixed itself.
haven't had crashes for over a week now.
I'll try your suggestions if the problem reemerges.
thank's for the help.