Computer cashes every once in a while.

Ryashon · Aug 20, 2012

Recently my Computer has been crashing every once in a while and i'm still trying to figure out whats causing it. I came across this website from a microsoft answers page and i was hoping someone here could help me.

OS - Windows 7
x64 bit
What was original installed OS on system? Windows 7
Is the OS an OEM version or full retail version? OEM (Custom Built With an OEM Key.)
Age of system: Don't know exactly but less than a year
Age of OS installation? Less than a year.
[*]CPU: AMD FX 6100 3.30Ghz
[*]Video Card: AMD Radeon HD 7860

[*]MotherBoard: Gigabyte GA-790FXTA-UD5

[*]Power Supply: BITWIN 620W

Tj Belfiore · Aug 20, 2012

Hello, welcome to Sysnative.

What are you doing before it crashes? Are you surfing the net? Playing a game?

Ryashon · Aug 20, 2012

Undocked_Windy said:
Hello, welcome to Sysnative.

What are you doing before it crashes? Are you surfing the net? Playing a game?

Hello, thanks!

Actually the funny thing is the last time my computer crashed it was in the process of shutting down.

When I used NirSoft BlueScreenView this was the last entry:

Code:

ntoskrnl.exe ntoskrnl.exe+25a30 fffff800`03850000 fffff800`03e38000 0x005e8000 0x4fa390f3 5/4/2012 1:18:59 AM Microsoft® Windows® Operating System NT Kernel & System 6.1.7601.17835 (win7sp1_gdr.120503-2030) Microsoft Corporation C:\Windows\system32\ntoskrnl.exe

My computer has sporadically been doing this, sometimes im not doing anything and my computer is idle when it crashes and sometimes im surfing, playing a game or listening to music.

Tj Belfiore · Aug 20, 2012

Could you please follow the instructions on this link here: https://www.sysnative.com/forums/showthread.php/29-Driver-Verifier-BSOD-related And attach output please?

jcgriff2 · Aug 20, 2012

Ryashon said:

When I used NirSoft BlueScreenView this was the last entry:

Code:

ntoskrnl.exe ntoskrnl.exe+25a30 fffff800`03850000 fffff800`03e38000 0x005e8000 0x4fa390f3 5/4/2012 1:18:59 AM Microsoft® Windows® Operating System NT Kernel & System 6.1.7601.17835 (win7sp1_gdr.120503-2030) Microsoft Corporation C:\Windows\system32\ntoskrnl.exe

Hi -

ntoskrnl.exe = The Windows NT Kernel and is listed as the probable cause as a default. Very common to see.

Please remove Elby for now -

http://www.sysnative.com/drivers/driver.php?id=ElbyCDIO.sys

Please see the quote below for these 2 -
http://www.sysnative.com/drivers/driver.php?id=AODDriver2.sys
http://www.sysnative.com/drivers/driver.php?id=AppleCharger.sys

Courtesy of usasma, John Carrona, MS MVP -

AMD OverDrive (AODDriver2.sys) is either a stand-alone application, or a component of the AMD VISION Engine Control Center. This driver is known to cause BSOD's on some Win7 systems.

Please un-install all AMD/ATI video stuff from Control Panel...Programs...Un-install a program
Then, download (but DO NOT install) a fresh copy of the ATI drivers from http://ati.amd.com (in the upper right corner of the page)
Use this procedure to install the DRIVER ONLY: https://www.sysnative.com/forums/sh...ideo-cards-DRIVER-ONLY-installation-procedure

If the device (AODDriver or AODDriver4.01) remains a problem, open Device Manager, select the "View" item. (YOU have this problem, so follow the steps here)
Then select "Show hidden devices" and scroll down to the Non-Plug and Play Drivers section.
Locate the AODDriver entry, right click on it and select "Uninstall". Reboot for changes to take affect.

Click to expand...

Sometimes the driver remains and continues to cause BSOD's. If this is the case for you, post back and we'll give further instructions for safely removing it.

If overclocking, please stop. Remove the overclock and return the system to stock/standard values while we're troubleshooting. Once the system is stable again, feel free to resume the overclocking.

Gigabyte's EasyTune6 (ET6) has been known to cause BSOD's on some Win7 systems - please uninstall it. If Easy Saver is also installed, please uninstall it also.

Please uninstall Apple Charger - it's recently been implicated in a number of BSOD's on Win7 systems.

Then run Driver Verifier

Regards. . .

jcgriff2

BSOD SUMMARY

Code:


Debug session time: Mon Aug 20 02:51:41.045 2012 (GMT-4)
Loading Dump File [C:\Users\PalmDesert\SysnativeBSODApps\081912-16458-01.dmp]
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
System Uptime: 0 days 9:03:05.409
BugCheck A, {fffffa001323ee60, 2, 0, fffff8000390f993}
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : ntkrnlmp.exe ( nt!CcFlushCache+103 )
Bugcheck code 0000000A
Arguments fffffa00`1323ee60 00000000`00000002 00000000`00000000 fffff800`0390f993
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xA_nt!CcFlushCache+103
BiosVersion = F5
BiosReleaseDate = 03/29/2012
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = GA-970A-UD3
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

writhziden · Aug 20, 2012

In addition to the excellent suggestions by Undocked_Windy and jcgriff2, I noticed the following:

One of your modules may be corrupted or damaged. We should verify that it is intact. To do so:

Please download sigcheck.
Copy and paste sigcheck.exe to your desktop.
Open up a command prompt:
1. Click Start Menu
2. Click All Programs
3. Click Accessories
4. Click Command Prompt

In the command prompt, type the following:

Code:

cd Desktop
sigcheck -i c:\windows\system32\win32k.sys > sigcheck.txt

Compress (zip) the sigcheck.txt file and attach it to your next post.

Ryashon · Aug 22, 2012

Undocked_Windy said:
Could you please follow the instructions on this link here: https://www.sysnative.com/forums/showthread.php/29-Driver-Verifier-BSOD-related And attach output please?

I did run driver verifier though I forgot to save the output, on all drivers non-microsoft related, and I had no BSOD's. I'll run it again with all drivers being verified.

jcgriff2 said:
Hi -

ntoskrnl.exe = The Windows NT Kernel and is listed as the probable cause as a default. Very common to see.

Please remove Elby for now -

http://www.sysnative.com/drivers/driver.php?id=ElbyCDIO.sys

Please see the quote below for these 2 -
http://www.sysnative.com/drivers/driver.php?id=AODDriver2.sys
http://www.sysnative.com/drivers/driver.php?id=AppleCharger.sys

Then run Driver Verifier

Regards. . .

jcgriff2

Hello, thanks for the reply. When you say remove Elby you want me to uninstall AnyDVD and CloneDVD correct? and for the AODDriver should i remove easy tuner and my ATI Catalyst manager?

Thanks!

writhziden said:
In addition to the excellent suggestions by Undocked_Windy and jcgriff2, I noticed the following:

One of your modules may be corrupted or damaged. We should verify that it is intact. To do so:

Please download sigcheck.

Copy and paste sigcheck.exe to your desktop.

Open up a command prompt:

Click Start Menu

Click All Programs

Click Accessories

Click Command Prompt

In the command prompt, type the following:

Code:

cd Desktop sigcheck -i c:\windows\system32\win32k.sys > sigcheck.txt

Compress (zip) the sigcheck.txt file and attach it to your next post.

Thanks for the reply I will come back soon with information.

Best Regards

Ryashon.

jcgriff2 · Aug 22, 2012

Ryashon said:
When you say remove Elby you want me to uninstall AnyDVD and CloneDVD correct? and for the AODDriver should i remove easy tuner and my ATI Catalyst manager?

Yes.. please remove Elby & any other virtual devices for now. You can always reinstall them after the BSOD epidemic ceases.

Yes also on ET & CCC.

Also, please run sigcheck requested by writhziden. Thank you.

Rergards. . .

jcgriff2

Ryashon · Aug 22, 2012

So i ran driver verifier on all my drivers including all microsoft drivers, and what do you know, my computer crashed on reboot.

Sig check is in the sigcheck.zip, and i uploaded a mini dump from my last bsod.

New reading from BlueScreenView

Code:

ntoskrnl.exe    ntoskrnl.exe+5053dc    fffff800`0384e000    fffff800`03e36000    0x005e8000    0x4fa390f3    5/4/2012 1:18:59 AM    Microsoft® Windows® Operating System    NT Kernel & System    6.1.7601.17835 (win7sp1_gdr.120503-2030)    Microsoft Corporation    C:\Windows\system32\ntoskrnl.exe

tcpipreg.sys    tcpipreg.sys+35a5    fffff880`0897d000    fffff880`0898f000    0x00012000    0x4ce7a844    11/20/2010 3:51:48 AM

writhziden · Aug 22, 2012

Having Verifier enabled on Microsoft drivers often causes false positives in crashes. Sigcheck checks out.

Please run Verifier with all non-Microsoft drivers enabled. Do so for at least 36 hours and see if you get a crash. If you do, upload it here. If not, post back for further troubleshooting steps.

Ryashon · Aug 22, 2012

I had previously ran driver verifier on all non Microsoft drivers and my computer had no crashes, it was only when I verified microsofts drivers that my computer crashed.

writhziden · Aug 23, 2012

How long did you run verifier for?

If you ran it for more than 36 hours, I would recommend checking Windows for file corruption.

Run a system file check to check Windows for corruption:

Click Start Menu
Click All Programs
Click Accessories
Right click Command Prompt
Click Run as administrator
Type
Code:
```
sfc /scannow
```
and press Enter
Once it is complete, make note of the message. If it says Windows Resource Protection did not find any integrity violations., restart your computer and post back
If the message does not say Windows Resource Protection did not find any integrity violations., restart your computer and do steps 1-6 again.
You may need to do steps 1-6 up to three times to resolve all corrupted files.
If you still have corrupted files after a fourth run, post back here with the following:
- Click Start Menu
- Click Computer
- Open your C: drive
- Open Windows
- Open Logs
- Open CBS
- Copy and paste CBS.log or CBS (it may not have the log extension) to a location you will remember.
- Compress (zip) the CBS file and attach the .zip file to your next post.

Ryashon · Aug 23, 2012

I don't recall how long it was running, SFC came up with no integrity violations.

jcgriff2 · Aug 24, 2012

Please run Driver Verifier again; 3rd party drivers only; 36 hours minimum or BSOD.

https://www.sysnative.com/forums/showthread.php/29-Driver-Verifier-BSOD-related

Regards. . .

jcgriff2

Search

Search

Computer cashes every once in a while.

Ryashon

Member

Attachments

Tj Belfiore

Well-known member

Ryashon

Member

Tj Belfiore

Well-known member

jcgriff2

Co-Founder / Admin
BSOD Instructor/Expert
Microsoft MVP (Ret.)

writhziden

Administrator, .NET/UWP Developer

Ryashon

Member

jcgriff2

Co-Founder / Admin
BSOD Instructor/Expert
Microsoft MVP (Ret.)

Ryashon

Member

Attachments

writhziden

Administrator, .NET/UWP Developer

Ryashon

Member

writhziden

Administrator, .NET/UWP Developer

Ryashon

Member

jcgriff2

Co-Founder / Admin
BSOD Instructor/Expert
Microsoft MVP (Ret.)

Computer cashes every once in a while.

Member

Attachments

Well-known member

Member

Well-known member

Co-Founder / AdminBSOD Instructor/ExpertMicrosoft MVP (Ret.)

Administrator, .NET/UWP Developer

Member

Co-Founder / AdminBSOD Instructor/ExpertMicrosoft MVP (Ret.)

Member

Attachments

Administrator, .NET/UWP Developer

Member

Administrator, .NET/UWP Developer

Member

Co-Founder / AdminBSOD Instructor/ExpertMicrosoft MVP (Ret.)

Co-Founder / Admin
BSOD Instructor/Expert
Microsoft MVP (Ret.)

Co-Founder / Admin
BSOD Instructor/Expert
Microsoft MVP (Ret.)

Co-Founder / Admin
BSOD Instructor/Expert
Microsoft MVP (Ret.)