Intermittent BSOD ntoskrnl.exe (nt+7cc40)

[Davidc2]

The BSODs appear random - eg once during surfing with IE9, another time while using Photoshop. BSODs not regular or often - maybe once a fortnight - but seemingly completely unpredictable.

MemTest run (just for an hour) didn't show up any problems.

I'd be grateful for a steer on what can be causing the BSODs.

Thanks

 

[zigzag3143]

The BSODs appear random - eg once during surfing with IE9, another time while using Photoshop. BSODs not regular or often - maybe once a fortnight - but seemingly completely unpredictable.

MemTest run (just for an hour) didn't show up any problems.

I'd be grateful for a steer on what can be causing the BSODs.

Thanks

Easy, your Symantec is causing memory corruption. Remove and replace with Microsoft Security Essentials


ftp://ftp.symantec.com/public/english_us_canada/removal_tools/Norton_Removal_Tool.exe


Virus, Spyware & Malware Protection | Microsoft Security Essentials

 

[Davidc2]

Thanks. Could you tell that Norton is causing the problem from the mini dumps?

 

[zigzag3143]

Thanks. Could you tell that Norton is causing the problem from the mini dumps?

At least two absolutely are Related to BHDrvx64.sys BASH Driver from Symantec Corporation.

Most exhibit memory management issues (also possibly related to Symantec) so I would say "definitely", no. Probably YES.

 

[Davidc2]

Thanks. That's very helpful. Never had a problem with NIS 2012 before (it hasn't been out long of course and I upgraded to it over NIS 2011 - maybe a clean install would have been better) but I have now changed to F-Secure and will see if I get any more BSODs. I prefer this to MS Essentials. I'll see what happens.

 

[zigzag3143]

Thanks. That's very helpful. Never had a problem with NIS 2012 before (it hasn't been out long of course and I upgraded to it over NIS 2011 - maybe a clean install would have been better) but I have now changed to F-Secure and will see if I get any more BSODs. I prefer this to MS Essentials. I'll see what happens.

Of course and your call. good luck

 

[Davidc2]

Just when I thought it was safe to get back in the water...

I was browsing in IE9 and listening to a streamed radio programme using BBC I-Player just now and bang. No Norton on my system now so I'll be very interested to hear what the culprit is this time.

Thanks for any more help you can give me. I'm ready to go to Microsoft Essentials if that really will be the answer.

 

[zigzag3143]

I was browsing in IE9 and listening to a streamed radio programme using BBC I-Player just now and bang. No Norton on my system now so I'll be very interested to hear what the culprit is this time.

Thanks for any more help you can give me. I'm ready to go to Microsoft Essentials if that really will be the answer.

Still memory management. Either RAM or a dirver. One way to find out which is to run these two tests.


These were caused by a memory exception. Please run these two tests to verify your memory and find which driver is causing the problem.


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.

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



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

 

[Davidc2]

Thanks. I ran Driver Verifier and on the very first restart after setting up Verifier I got a BSOD. I attach the minidump - the relevant minidump report is the last one. I let Verifier run on for a while over a few more restarts and also while I worked with Photoshop for a while, but got no more BSODs.

I'd be grateful to know if the latest minidump points to a particular driver. Thanks.

 

[zigzag3143]

Thanks. I ran Driver Verifier and on the very first restart after setting up Verifier I got a BSOD. I attach the minidump - the relevant minidump report is the last one. I let Verifier run on for a while over a few more restarts and also while I worked with Photoshop for a while, but got no more BSODs.

I'd be grateful to know if the latest minidump points to a particular driver. Thanks.

David

Newest crash is still related to memory management and was verified but unfortunately verifier couldnt trap the offending driver. That does sometimes happen.

If you have not can you run a system file check to verify and repair system files?


Run a system file check to verify and repair your system files.
To do this type cmd in search, then right click to run as administrator, then
SFC /SCANNOW

Read here for more information http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html

Let us know the results from the report at the end.

 

[Davidc2]

No luck there. All the files seem to be fine. See the attached screenshot. Anything else I can try, please?

 

[Davidc2]

Here's an overnight Memtest screen. I can't see any errors reported but I don't know how to interpret the screen results. Any help?

 

[zigzag3143]

Here's an overnight Memtest screen. I can't see any errors reported but I don't know how to interpret the screen results. Any help?

That snip is basically useless. Corrupt data either from the RAM or from malware.


Can you re-run memtest and download and run malwarebytes?

 

[Davidc2]

I have run memtest twice (what I attached was a photo of the screenshot from the second go) and got the same output both times. It looked weird to me but I don't know what it should look like. Can you please give me a steer. What form of final output should I get/make from Memtest, please?

 

[Davidc2]

I ran a newer version of MemTest86 (4.20) and it behaved fine. No errors found in over 3 hours. See attached file.

I had done a full scan with F-Secure yesterday, and did one with Norton today. Not problems found.

Any other ideas, please?

PS another BSOD just now while listening to Audible audio book and working in Photoshop CS5. Another memory management. What can I do about this?

 

[zigzag3143]

I ran a newer version of MemTest86 (4.20) and it behaved fine. No errors found in over 3 hours. See attached file.

I had done a full scan with F-Secure yesterday, and did one with Norton today. Not problems found.

Any other ideas, please?

PS another BSOD just now while listening to Audible audio book and working in Photoshop CS5. Another memory management. What can I do about this?

The snip shows pass 1. You need to run 6-7 passes to stress the ram enough.

Malwarebytes will find things Norton and F-secure wont. Both F-secure and especially Norton have been known to cause BSOD's on some systems. If it were me I would remove them and replace with Micsrosoft security essentials

If you havent done a system file check please do so

Run a system file check to verify and repair your system files.
To do this type cmd in search, then right click to run as administrator, then
SFC /SCANNOW

Read here for more information http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html

Let us know the results from the report at the end.

 

[Davidc2]

solved - I think

Thanks. I gave up trying to track down the fault and re-installed everything. No problems after 16 hours. Thanks for all the help.

 

[zigzag3143]

Thanks. I gave up trying to track down the fault and re-installed everything. No problems after 16 hours. Thanks for all the help.

Good luck

 

[Davidc2]

Thanks. No BSODs yet but have had a "graphics driver stopped working but recovered" incident. May try a different vga card and driver.

 

[zigzag3143]

Thanks. No BSODs yet but have had a "graphics driver stopped working but recovered" incident. May try a different vga card and driver.

Good idea. Let us know.