Intermittent BSOD ntoskrnl.exe (nt+7cc40)

Page 1 of 3 123 LastLast

  1. Posts : 37
    Windows 7 Ultimate x64
       #1

    Intermittent BSOD ntoskrnl.exe (nt+7cc40)


    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
      My Computer


  2. Posts : 28,845
    Win 8 Release candidate 8400
       #2

    Davidc2 said:
    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/englis...moval_Tool.exe


    Virus, Spyware & Malware Protection | Microsoft Security Essentials
      My Computer


  3. Posts : 37
    Windows 7 Ultimate x64
    Thread Starter
       #3

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


  4. Posts : 28,845
    Win 8 Release candidate 8400
       #4

    Davidc2 said:
    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.
      My Computer


  5. Posts : 37
    Windows 7 Ultimate x64
    Thread Starter
       #5

    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.
      My Computer


  6. Posts : 28,845
    Win 8 Release candidate 8400
       #6

    Davidc2 said:
    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
      My Computer


  7. Posts : 37
    Windows 7 Ultimate x64
    Thread Starter
       #7

    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.
      My Computer


  8. Posts : 28,845
    Win 8 Release candidate 8400
       #8

    Davidc2 said:
    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.

    RAM - Test with Memtest86+



    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.
    Driver Verifier - Enable and Disable
      My Computer


  9. Posts : 37
    Windows 7 Ultimate x64
    Thread Starter
       #9

    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.
      My Computer


  10. Posts : 28,845
    Win 8 Release candidate 8400
       #10

    Davidc2 said:
    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 SFC /SCANNOW Command - System File Checker

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


 
Page 1 of 3 123 LastLast

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 19:58.
Find Us