Intermittent BSODs, errors 0x0c2, 0x019, 0x05c, 0x00a

Page 2 of 3 FirstFirst 123 LastLast

  1. Posts : 10,200
    MS Windows 7 Ultimate SP1 64-bit
       #11

    StripyHorse,
    Did you run ChkDSK over ALL of your drives?

    If not, then please do.

    Then use this procedure:

    Script:
    # Start copying with first line that does NOT start with a #
    # Copy thru 2nd EXIT; 
    # Paste into PowerShell using right-click

    $events get-winevent -filterhashtable @{logname='application';id=1001,26212,26214} -verbose:$false -ea:silentlycontinue |
    sort-object -property timecreated -desc 
    where {($_.providername -ne 'Microsoft-Windows-LoadPerf') -and ($_.providername -ne 'Windows Error Reporting')}

    If (
    $events -eq $Null) {"No check disk logs exist." OUT-FILE $env:userprofile\desktop\CHKDSKLOGS.TXT} ELSE
    {
    $events SELECT timecreatedidmessage |
    format-table -auto -wrap OUT-FILE $env:userprofile\desktop\CHKDSKLOGS.TXT
    }

    EXIT
    EXIT

    # ************************************************************
    # Places CHKDSKLOGS.txt on your DESKTOP
    #
    # Results of running chkdsk (check disk) are in ChkDskLogs.txt
    # **********************INSTRUCTIONS**************************
    # STEP 1 *****************************************************
    # RUN PowerShell as administrator
    # START ORB | type POWERSHELL | CTRL+SHIFT+ENTER key combo | YES
    # ************************************************************
    # STEP 2 *****************************************************
    # COPY, using CTRL + C, every line down thru both EXIT statements 
    # PASTE into Powershell by right-clicking at the PowerShell Prompt
    #  (Ctrl V does not work)
    # ************************************************************
    # ***************** NOTE - POWERSHELL VERSION*****************
    # if you receive this error msg:
    #  Get-WinEvent: The system can not find the path specified
    # you need to update your PowerShell
    # you must be using Powershell 2.0 or later.
    #
    # To determine your Powershell version:
    #   Run PowerShell
    #   enter following $host.version
    #   you should see at least:
    # Major  Minor  Build  Revision
    # -----  -----  -----  --------
    # 2      0      -1     -1
    #
    # If you do not see the above, update your Vista/Win 7.
    # ************************************************************
    # *************** NOTE - EXECUTION POLICY*********************
    # If you haven't set the execution policy, you may need to:
    #   Run PowerShell
    #   enter following without the #
    #   Set-ExecutionPolicy -executionpolicy remotesigned
    #
    # ************************************************************ 
    Upload the chkdsk.txt file that this puts on your desktop.
    thanks,
    karl
      My Computer


  2. Posts : 719
    Windows 7 Home Premium 64bit (O.E.M)
       #12

    Ok, in addition to Karl's advice, could you re-enable verifier and keep it running until you get 2-4 crashes or until it has been running for 6 hours. It often takes time to work. The program will make your computer laggy and slow so don't worry about that.

    Stephen
      My Computer


  3. Posts : 15
    Windows 7 Home Premium 64bit
    Thread Starter
       #13

    Hi Karl,

    Here is the chkdsk file. I ran it before this thread started on all disks, but after the BSODs began.

    Driver Verifier has bee running for a while now (over 6 hours, but I've been using the computer for maybe 3 of those), and still no crashes... I'll let it run for at least another 3 hours of use and keep you posted.

    Thanks,
    Tom
      My Computer


  4. Posts : 10,200
    MS Windows 7 Ultimate SP1 64-bit
       #14

    StripyHorse,
    Chkdsk logs look good. Your disk is ok.
    Sounds real good that DriverVerifier is running without crashing. Be sure and run some of the same programs on your computer that crashed before.
      My Computer


  5. Posts : 10,200
    MS Windows 7 Ultimate SP1 64-bit
       #15

    Now if you would llke to empty out all of your event logs so that finding things in the Event Viewer is easier, then here is a very short PowerShell script to empty them out.

    The writeup is nearly all explanation and the actual script very short.

    Script:
    # ************************************************************
    # Clear the EVENT LOGS
    #
    # **********************INSTRUCTIONS**************************
    # STEP 1 *****************************************************
    # RUN PowerShell as ADMINISTRATOR
    # START ORB | type POWERSHELL | CTRL+SHIFT+ENTER key combo | ALT+Y keycombo
    # ************************************************************
    # STEP 2 *****************************************************
    # COPY, starting with the first line that does NOT start with a #
    # COPY, using CTRL+C, every line thru both EXIT statements 
    # PASTE into Powershell
    # You PASTE by Right-clicking at the PowerShell Prompt
    #  (Ctrl+V does not work)
    # ************************************************************

    Get-WinEvent -ListLog * -Force 
    % { 
    $_.logname;Wevtutil.exe cl $_.logname };
    Wevtutil.exe cl system

    EXIT
    EXIT

    # ***************** NOTE - POWERSHELL VERSION*****************
    # if you receive this error msg:
    #  Get-WinEvent: The system can not find the path specified
    # you need to update your PowerShell
    # you must be using Powershell 2.0 or later.
    #
    # To determine your Powershell version:
    #   Run PowerShell
    #   enter $host.version
    #   you should see at least:
    # Major  Minor  Build  Revision
    # -----  -----  -----  --------
    # 2      0      -1     -1
    #
    # If you do not see the above, update your Vista/Win 7.
    # ************************************************************
    # *************** NOTE - EXECUTION POLICY*********************
    # If you haven't set the execution policy, you may need to:
    #   Run PowerShell
    #   enter Set-ExecutionPolicy -executionpolicy remotesigned
    #
    # ************************************************************ 
      My Computer


  6. Posts : 15
    Windows 7 Home Premium 64bit
    Thread Starter
       #16

    Why is it advisable to empty the event logs? In event viewer I think I can only see event logs from the last 7 days anyway. Is that correct? Also, I might hold fire because I've just had a driver_verifier_detected_violation bsod on bringing the computer out of sleep and the event logs could be helpful (?). I'm going to try to replicate it then I'll write back.
      My Computer


  7. Posts : 719
    Windows 7 Home Premium 64bit (O.E.M)
       #17

    Don't forget to follow the posting instructions to upload the new dumps. And yes, don't delete the event viewer logs at the moment as you've just had a BSOD.
      My Computer


  8. Posts : 15
    Windows 7 Home Premium 64bit
    Thread Starter
       #18

    Sorry for the delay, I had to go out. I managed to replicate the crash, which occurred when sending the laptop to sleep with a game running (Half-Life on Steam). When I opened it, both times, it had switched itself off and came up with the "Windows did not shut down successfully" screen. The crashes started before I had either Steam or Half Life installed, but I think I have had crashes when bringing the laptop out of sleep.

    The two most recent BSOD dumps (dated today) are the relevant ones.

    Tom
      My Computer


  9. Posts : 10,200
    MS Windows 7 Ultimate SP1 64-bit
       #19

    Since you are still having BSODS, then as Tekno Venus advised:
    Do NOT delete the logs at this time.
    My mistake in that I thought that the bsod problems were gone.
      My Computer


  10. Posts : 719
    Windows 7 Home Premium 64bit (O.E.M)
       #20

    Now we're getting somewhere :)

    Those new dumps are blaming CHDRD64.sys - a driver for your "Conexant High Definition SmartAudio" device. You need to uninstall the driver then update it. It's quite hard to find so here is the download link direct from Lenovo - http://download.lenovo.com/consumer/...n2aud47ww5.exe

    To fully re-install a driver, use the following steps.

    1. First, download the latest driver. Then do the next steps.
    2. Click Start Menu
    3. Right Click My Computer/Computer
    4. Click Manage
    5. Click Device Manager from the list on the left
    6. Find the device you are trying to uninstall by expanding the appropriate set of devices
    7. Right click the device
    8. Click Uninstall (do not click OK in the dialog box that pops up after hitting Uninstall)
    9. Put a tick in Delete driver software for this device (if this option is available, otherwise just hit OK) and hit OK
    10. Restart your computer only if Windows asks you to.
    11. Install the latest driver for the device.

    Alternatively:

    1. Login as an administrative user.
    2. First, download the latest driver. Then do the next steps.
    3. Click Start Menu
    4. Click Control Panel
    5. Click Hardware and Sound
    6. Click Device Manager (the last link under Devices and Printers)
    7. Find the device you are trying to uninstall by expanding the appropriate set of devices
    8. Right click the device
    9. Click Uninstall (do not click OK in the dialog box that pops up after hitting Uninstall)
    10. Put a tick in Delete driver software for this device (if this option is available, otherwise just hit OK) and hit OK
    11. Restart your computer only if Windows asks you to.
    12. Install the latest driver for the device.

    Thanks to Writhziden for these steps!

    This should solve it, or at least help slightly.

    Stephen
      My Computer


 
Page 2 of 3 FirstFirst 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 06:46.
Find Us