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

[StripyHorse]

Hi,

My laptop is around 9 months old, and first showed a few BSODs about 6 months ago. It is still within warranty, and I sent it back to the manufacturer, who apparently did a RAM burn-in or test, found nothing, factory reset it and sent it back. This solved the problem for a few months before it started again, and it has continued for the past month or so. The error codes are in the title in abbreviated form. The BSODs tend to occur when either loading the desktop or launching a program, but they aren't reliably caused by anything and I think they have sometimes happened when doing basic word processing/web surfing etc.
I have run the windows memcheck for a total of 4 passes (2 on standard setting, and 2 on extended) and dskchk at least twice, both with no joy. I updated drivers, and finally the BIOS about a week ago. Since the BIOS update I have had no BSODs, but they are really sporadic (occurring sometimes every day, sometimes once a fortnight), so it's hard to know whether the problem is actually solved.
I tried looking at the minidumps (attached) with BlueScreenView, which shows a problem every time with ntoskrnl.exe, and sometimes fbfmon.sys, fltmgr.sys, hal.dll, and fileinfo.sys additionally, but none of these other files are consistently flagged as problems.
I would really appreciate any help in tracking down the problem as far as possible, as my warranty expires in about 3 months, and if the problem was not fixed by the BIOS update, it would be useful to have some ammunition when I send it back so maybe it will actually get fixed this time. Basically I'd like to know if there is a chance that my BIOS update fixed the problem or not based on what the minidumps show, because I don't have the knowledge to verify this.
The OS listed in my specs is the original one, and I'm not overclocking anything.
Apologies for the mammoth post, but I've tried to be as comprehensive as possible.

Thanks.

 

[Tekno Venus]

Hi and welcome to Seven Forums,

If you are overclocking your system, please return all overclocked components to their stock speeds. If the BSOD's are found not to be caused by the overclock, you can re-overclock the components once we have finished the diagnostics


I have noticed you have 2 anti-virus programs installed, Zone Alarm and AVG. Please correct me if I'm wrong though! Two real time anti-virus programs can cause conflicts so I would recommend uninstalling them both and replacing them with Microsoft Security Essentials. This will offer better protection and is less likely to contribute to a BSOD. If you want on demand malware protection I recommend Malwarebytes' Anti-Malware. How to use Malwarebytes' Anti-Malware to scan and remove malware from your computer.


The BSOD dumps you gave me do not give a definitive cause for your BSOD's. They pointed at ntkrnlmp.exe which is a system file and very unlikely to cause a BSOD.

As a result I recommend you check your hardware for issues. Please run Memtest86+ to check your RAM. Let it run for 6-8 passes overnight as described in the tutorial. Pay particular attention to parts 2 and 3.

Also check your HDD for errors using Seatools and chkdsk.. Download and create a bootable version of the Seatools for DOS program as described here. For check disk, follow this tutorial: http://www.sevenforums.com/tutorials/433-disk-check.html

If you have any questions, feel free to ask
Stephen

 

[writhziden]

In addition to the excellent steps Stephen has suggested: Crashes primarily point to hardware. They may be related to your processor, your hard disk (run Stephen's checks for the hard disks and memory), or your motherboard (those are my prime suspects, but it still may be something else entirely). Run some hardware checks.

• If you are overclocking any hardware, please stop.
  
  
• Monitor temperatures during the following tests.
  
  Use the following programs to monitor the temperatures.​
  • Real Temp is a good CPU temperature monitor.
  • Speccy - System Information - Free Download will monitor all hardware temperatures.
  • HWiNFO, HWiNFO32 & HWiNFO64 - Hardware Information and Analysis Tools can be inaccurate for CPU temperatures, but is a good program for GPU temperature monitoring.
  • Use FurMark: VGA Stress Test, Graphics Card and GPU Stability Test, Burn-in Test, OpenGL Benchmark and GPU Temperature | oZone3D.Net to test the graphics card GPU. Let it run until the GPU temperatures even out or until the GPU temperatures reach a dangerous level (you can find the max temperature for your card on either the nVidia or AMD sites; if you are not sure, ask us). The goal is to get a steady temperature, find out if the GPU is overheating, or to see if there are any artifacts present in the test itself: look for strange pixelated patterns on the screen or colors that do not look like they belong. Then use the |MG| Video Memory Stress Test 1.7.116 Download to test your graphics card memory. Let the memory test run for at least seven passes; the more the better.
    
    
  • Run http://www.sevenforums.com/tutorials/100352-hardware-stress-test-prime95.html to determine any hardware problems. Run all three tests for a few hours each. If you get errors, stop the test and post back here.
    
    
  • Follow the steps for doing CPU stress test using IntelBurnTest

 

[Tekno Venus]

• Use FurMark: VGA Stress Test, Graphics Card and GPU Stability Test, Burn-in Test, OpenGL Benchmark and GPU Temperature | oZone3D.Net to test the graphics card GPU. Let it run until the GPU temperatures even out or until the GPU temperatures reach a dangerous level (you can find the max temperature for your card on either the nVidia or AMD sites; if you are not sure, ask us). The goal is to get a steady temperature, find out if the GPU is overheating, or to see if there are any artifacts present in the test itself: look for strange pixelated patterns on the screen or colors that do not look like they belong. Then use the |MG| Video Memory Stress Test 1.7.116 Download to test your graphics card memory. Let the memory test run for at least seven passes; the more the better.
• Run http://www.sevenforums.com/tutorials/100352-hardware-stress-test-prime95.html to determine any hardware problems. Run all three tests for a few hours each. If you get errors, stop the test and post back here.
• Follow the steps for doing CPU stress test using IntelBurnTest

These were going my next steps after RAM and HDD checks!

 

[StripyHorse]

Hi Stephen and writhziden, thanks very much for your advice.

AVG and ZoneAlarm were an antivirus and firewall respectively. I installed them following someone's advice, but I've uninstalled them and switched to MSE and Windows Firewall, which seem to be a much cleaner and better regarded combo!

I'll run those various tests over the course of the next couple of days and see if anything crops up. I've already run chkdsk (which I called dskchk in the OP, my bad) with no results, but I'll give the Seatools one a try as well.

Cheers,
Tom

 

[Tekno Venus]

Replacing zone alarm and AVG with the Windows firewall and MSE is a good move. Run through the tests at your own pace and report back the results.

Stephen

 

[StripyHorse]

Hi,

I've only run Memtest86+ so far, which ran for 11 passes with no errors. I ran chkdsk before with no results as a I said, but when I tried to run Seatools it showed the message "no hard drives found". I read somewhere that you need to configure your hard drive to IDE instead of AHCI, but I don't know what that means or if it's safe to mess about with those settings in BIOS. Any idea why it isn't working?

Also, my computer does not have a discrete GPU, but runs on the integrated Intel hd 3000 graphics that come with the i series CPUs. Should I just run the CPU stress test, or should I run the FurMark GPU test? And are the stress tests likely to invalidate my warranty?

Thanks,
Tom

EDIT: I ran the Seatools for Windows tests (long generic, short drive self test, SMART check) instead, all with no errors. Can I write the HDD off as the culprit now?

I also forgot to mention that I had another BSOD 2 days ago, so the BIOS update didn't fix the problem. I've run the BSOD Dump & System File Collection app again and attached the results (only the most recent dump from 20/06/12 is new).

 

[StripyHorse]

Just an apologetic bump as this has slipped way down the boards - I would have contacted the members concerned but I can't seem to private message as a new member.

 

[Tekno Venus]

Apologies for the delay. For once a bump has been used in a good way as I'd completely forgotten about this thread! My apologies again.

Ok, your latest dumps are still indicating hardware issues. As you couldn't get seatools for DOS to work, try using chkdsk - follow this tutorial: http://www.sevenforums.com/tutorials/433-disk-check.html. Just to be sure there are no HDD issues.

Now, I would say to run some stress tests but I recommend not doing so on a laptop as the cooling is not always sufficient to deal with the heat of the CPU and graphics card. So, lets try this:

• An underlying driver may be incompatible\conflicting with your system. Run Driver Verifier to find any issues. To run Driver Verifier, do the following:
  a. Backup your system and user files
  b. Create a system restore point
  c. If you do not have a Windows 7 DVD, Create a system repair disc
  d. In Windows 7:
  

  • Click the Start Menu
  • Type verifier in Search programs and files (do not hit enter)
  • Right click verifier and click Run as administrator
  • Put a tick in Create custom settings (for code developers) and click next
  • Put a tick in Select individual settings from a full list and click next
  • Set up the individual settings as in the image and click next
    
    
  • Put a tick in Select driver names from a list
  • Put a tick next to all non-Microsoft drivers.
  • Click Finish.
  • Restart your computer.

  
  If Windows cannot start in normal mode with driver verifier running, start in safe mode. If it cannot start in safe mode or normal mode, restore the system restore point using http://www.sevenforums.com/tutorials/700-system-restore.html OPTION TWO.
  
  If you are unable to start Windows with all drivers being verified or if the blue screen crashes fail to create .dmp files, run them in groups of 5 or 10 until you find a group that causes blue screen crashes and stores the blue screen .dmp files.​
  The idea with Verifier is to cause the system to crash, so do the things you normally do that cause crashes. After you have a few crashes, upload the crash reports for us to take a look and try to find patterns.
  
  When you are ready to disable Verifier: Start Menu -> All Programs -> Accessories -> Right click Command Prompt -> Run as administrator -> Type the following command and then Enter:
  verifier /reset​
  -> Restart your computer.

Thanks to Writhziden for providing the Driver Verifier steps.


Oh, and to contact me in the future if I've forgotten you again (I'll try not to ) you can either send me a Private Message of Visitor Message. Any member should be able to do them. Go to my profile page and click "Send Message" underneath my profile picture. Choose either PM or VM. I prefer PM as I get an email but a VM is absolutely fine.

Stephen

 

[StripyHorse]

No worries . I can't see any private messaging options on my CP or when I view your profile, and I read on another thread that new members can't send PMs until they lose their 'new member' status, as a spam-protection measure. Guess I'll just have to post some more...

Chkdsk reported no faults when I ran it. I tried Driver Verifier for about half an hour, doing all the things I usually do like watching video, using a word processor, surfing the web, and playing light games, which produced no crashes. The only abnormality I noticed (aside from the computer running a bit slowly) was that sound lagged occasionally, by which I mean that it slowed down and stuttered. Does that sound like any indication of a driver fault?

 

[karlsnooks]

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

If not, then please do.

Then use this procedure:

# 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 timecreated, id, message |
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

 

[Tekno Venus]

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

 

[StripyHorse]

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

 

[karlsnooks]

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.

 

[karlsnooks]

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.

# ************************************************************
# 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
#
# ************************************************************

 

[StripyHorse]

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.

 

[Tekno Venus]

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.

 

[StripyHorse]

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

 

[karlsnooks]

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.

 

[Tekno Venus]

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/mobiles/in2aud47ww5.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