Blue Screen crash -- bccode:a


  1. Posts : 8
    Windows 7 Ultimate x64
       #1

    Blue Screen crash -- bccode:a


    Basic information:

    Windows 7 x64
    original installed OS on the system
    full retail version

    I bought the hardware in 2009. and had my win7 installed about the same time.

    My problem:

    frequently crash, with all kinds of bccode.

    I'v attached necessary files to this post, which is created "by the book".

    Need help! thanks in advance!.
    Last edited by digbug; 14 Nov 2010 at 10:21.
      My Computer


  2. Posts : 8,383
    Windows 10 Pro x64, Arch Linux
       #2

    Update your Realtek drivers Realtek

    If you are overclocking, reset the overclocks
      My Computer


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

    thanks, Dr House. Will that be all?
      My Computer


  4. Posts : 507
    Windows 7 Ultimate x64 SP1
       #4

    Hi digbug,
    Sorry for my bad, I mean you don't need to create new thread but just follow the instructions to collect more data.

    Anyway your most of dump files indicated hardware failure.
    But before we move to the next step, you need to do the advice as suggested before.
    I still see old drivers that need to be update because outdate drivers can cause BSOD in win7.

    Start troubleshooting your problem by removing Avira and replace it with MSE.
    You may go back to Avira after your Windows have stabled.
    http://www.microsoft.com/security_essentials/

    Uninstall your Acronis software because it's the outdate version.

    Then these drivers need to be update:
    Code:
    wacommousefilter.sys Fri Feb 16 10:12:17 2007 --> Wacom(tablet) Mouse Filter
    snapman.sys  Fri Oct 06 06:43:53 2006 --> Acronis True Image Snapshot
    LVUSBS64.sys Fri May 11 17:01:20 2007 --> Logitech Camera driver
    lvuvc64.sys  Fri May 11 16:59:12 2007  --> Logitech USB Video Class Driver
    lvpopf64.sys Fri Nov 10 19:08:05 2006 --> also part your Logitech device
    CertClient.dat Wed Aug 27 00:23:55 2008  --> unknown 
    CMBProtector.dat Tue Mar 11 19:41:13 2008 --> unknown
    Make sure to do the suggestion above then if you get another BSOD, it'll create new dmp files. Then run jcgriff2.exe again to collect the new data and attach here. (don't need to create new thread)
      My Computer


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

    Let's see if i'm doing it right.
    I'v manually deleted snapman.sys from /system32/drivers. because I find out that It seems i'v already made a uninstallation long time ago and it's not listed in control panel anymore.
    I'v updated other drivers.
    And I'v unintalled Avira and installed MSE to take place.

    Thanks for your patient. These nasty crashes have bothored me for a long long time. Considering I'm a CG artist and independed programmer who need to work with computer for long hours everyday, I'm even surprised that I got this far in one peice, without freaking out and format the hard driver. which will certainly be a long, painful journy because I will have to backup tons of personal presets .....

    Now you might have some idea about how grateful I'm.You guys are like angels to me.

    English is not my first language, excuse me if I somehow get it wrong.

    Seems all set now. Finger is crossed!
      My Computer


  6. Posts : 507
    Windows 7 Ultimate x64 SP1
       #6

    That's good, then we'll see how is it goes.
    Because troubleshooting BSOD is step by step
      My Computer


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

    After several very very happy days...........I'm back -_-!


    BCCode: 3b
    BCP1: 00000000C000001D
    BCP2: FFFFF8000516E145
    BCP3: FFFFF8800897BAC0
    BCP4: 0000000000000000
    OS Version: 6_1_7600
    Service Pack: 0_0
    Product: 256_1
      My Computer


  8. Posts : 11,840
    64-bit Windows 8.1 Pro
       #8

    The dmp(s) point to ntkrplmp.exe or ntoskrnl.exe as the probable cause. We know this is not the case, as these are core OS files, and will definitely not cause a BSOD. They are just the default files the debuggers blame when they can't see a better cause. We need to enable driver verifier to help pinpoint the faulting driver..

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

    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 3B, {c000001d, fffff8000516e145, fffff8800897bac0, 0}
    
    Probably caused by : ntkrnlmp.exe ( nt!ObpWaitForMultipleObjects+ea )
    
    Followup: MachineOwner
    ---------
    The following drivers are outdated and should be updated ...

    Code:
    wacommousefilter.sys Fri Feb 16 13:12:17 2007 (45D5F401) ... Wacom(tablet) Mouse Filter ... Wacom Hardware Drivers
      My Computer


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

    I'v make change according to your instruction. But when i reboot my computer and reenter Win7, It failed. said: driver error. I managed successful reboot using latest correct configration. Does that has something to do with the "verifier"?
      My Computer


 

  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 03:44.
Find Us