BSOD Very Frequently While Using PC

[Zoren]

Hello,

I've been having BSODs ever since i bought this new PC but recently the BSODs have become very frequent.
I've had this PC for about 8 months now but during this time BSODs HAVE occurred, but only once every couple days or weeks. Now it BSODs very frequently, about once every 20mins-2hr. I have also noticed that BSODs occur more frequently when gaming but still do happen when using the PC normally, such as watching movies, browsing, etc. I dont really know much about BSOD trouble-shooting so any help would be greatly appreciated.

Thanks in advance!

 

[Saurabh A]

Hi Zoren,

For a better understanding about the issue with the system, would like to have a look at the 'Mini Dump' (Files saved on the computer when Blue screen errors occur). Please follow the instructions in the following tutorial to capture the relevant details: http://www.sevenforums.com/bsod-help-support/96879-blue-screen-death-bsod-posting-instructions.html

This tool also allows you to capture other important information like 'Event Logs, Update Logs & System Information' that may be instrumental in getting closer to the root cause.

Also share if you made any 'hardware/software change' to the computer immediately before the BSOD first occurred.

Do reply with the details; would be glad to assist.

 

[Zoren]

View attachment 256117

Thanks for the reply Saurabh. I attached all the minidump files from BSODs that occured on the day I started this thread.

 

[Saurabh A]

Hi Zoren,

Please perform a test on the 'system memory': http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html
Note: The goal is to test all the RAM sticks and all the motherboard slots. (Please refer to the tutorial and follow the steps listed in detail)

If the test passes, please check 'Windows Update' history to see if any misses/corruption is observed since the day you first experienced the 'Blue screen'. Would also like to look at the 'Event logs' to see what else may have happened during that time. Please follow the steps shared in this tutorial to capture the related information (except mini-dump files): http://www.sevenforums.com/bsod-help-support/96879-blue-screen-death-bsod-posting-instructions.html

The 'Mini-dump' points at the following errors:

Bug Check String: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
Bug Check Code: 0x1000007e
Caused By Driver: dxgmms1.sys

Bug Check String: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
Bug Check Code: 0x1000007e
Caused By Driver: nvlddmkm.sys

Bug Check String: KMODE_EXCEPTION_NOT_HANDLED
Bug Check Code: 0x0000001e
Caused By Driver: ntoskrnl.exe

The information from 'Mini-dump' does not look very conclusive. You may try to roll-back 'nVidia drivers' and see if that helps. Also perform 'Windows Updates'; should take care of the 'nVidia drivers & DirectX'. You may also try re-installing the 'display drivers' to see if that makes any difference.

Hope this helps. Do reply with the findings.

 

[Northernsoul55]

Hi Zoren,

All the information required for the minidumps is not in the logs you posted.

In order to accurately analyse your BSOD , we need also:

Driver list
dxdiag
EventApp
EventSys
Hosts
MSInfo32
Systeminfo
Windowsupdate

Please run the SF Tool again and select "Grab All" and wait for each window open and click ok,
and repost new log.

:ar: http://www.sevenforums.com/bsod-help-support/96879-blue-screen-death-bsod-posting-instructions.html

Cheers

Dave

 

[Zoren]

View attachment 256230
Ok i have attached the the missing files. Currently running Memtest.

Thanks for the help!

 

[Saurabh A]

Hi Zoren,

Thank you for sharing the complete information.

The recent event logs indicate issues with a few games (PlanetSide2.exe, team fortress 2) crashing. 'DMP files' also point at the 'nVidia drivers'; was wondering if you've tried re-installing the 'nVidia drivers'.

Would recommend you to check for the latest available drivers from Drivers | GeForce. Please ensure that you clean up the currently installed drivers. To remove the drivers, you may follow these steps:
- Open 'Device Manager' > Expand 'Display Adapters' > Right click and uninstall the 'nVidia related' device listed > Also choose to remove the 'utility/software' if prompted > Follow through with the uninstall to finish > Restart the computer > Install a fresh set of drivers and check performance.

Looks like the system is overclocked; please remove the overclocking to see if that helps.

Log Name: System
Source: Service Control Manager
Event ID: 7036
The Superfetch service entered the running state.

Would also suggest you to run 'Chkdsk from Command Prompt': http://www.sevenforums.com/tutorials/433-disk-check.html to find and fix errors on the disk.

http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html should also be useful to check the integrity of 'Windows files'; and share its results. (Refer to option 3 in the tutorial to capture the CGS logs).

Also update the 'Network drivers' ATHEROS drivers for Microsoft Windows (Atheros?????) to see if that helps. Appears that CCleaner is in use; would also recommend to remove it and check results.

Hope this helps. Do reply with the findings.

 

[Zoren]

View attachment 256584
I ran SFC three times and eveytime it said 'Windows Resource Protection found corrupt files but was unale to fix some of them. I followed the guide and attached the CBS.log. Also i noticed that the BSOD have been ocurring less frequently after i updated my Nvidia drivers. About the overclock, i never overcloked my system, or at least do not remember doing so?

 

[Saurabh A]

Hi Zoren,

The logs report too many 'file errors' and most of them point at the 'printer driver corruption':

2013-02-19 22:15:11, Info                  CSI    00000023 [SR] Cannot repair member file [l:24{12}]"dot4.inf_loc" of dot4.inf.Resources, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture = [l:10{5}]"en-US", VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, file is missing
2013-02-19 22:15:11, Info                  CSI    00000024 [SR] Cannot repair member file [l:24{12}]"dot4.inf_loc" of dot4.inf.Resources, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture = [l:10{5}]"en-US", VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, file is missing
2013-02-19 22:16:41, Info                  CSI    000001ee [SR] Cannot repair member file [l:36{18}]"Amd64\CNBIC4_3.DLL" of prnca00z.inf, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type = [l:24{12}]"driverUpdate", TypeName neutral, PublicKey neutral in the store, file is missing
2013-02-19 22:16:41, Info                  CSI    000001f4 [SR] Cannot repair member file [l:32{16}]"Amd64\CNBEI4.DLL" of prnca00z.inf, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type = [l:24{12}]"driverUpdate", TypeName neutral, PublicKey neutral in the store, file is missing
2013-02-19 22:16:42, Info                  CSI    00000225 [SR] This component was referenced by [l:186{93}]"Microsoft-Windows-Printer-Drivers-Package~31bf3856ad364e35~amd64~~6.1.7601.17514.INF_prnep003"
2013-02-19 22:16:42, Info                  CSI    00000226 [SR] Cannot repair member file [l:36{18}]"Amd64\EP0LB030.INI" of prnep003.inf, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type = [l:24{12}]"driverUpdate", TypeName neutral, PublicKey neutral in the store, file is missing
2013-02-19 22:16:42, Info                  CSI    00000230 [SR] Cannot repair member file [l:36{18}]"Amd64\CNBIC4_3.DLL" of prnca00z.inf, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type = [l:24{12}]"driverUpdate", TypeName neutral, PublicKey neutral in the store, file is missing
2013-02-19 22:16:42, Info                  CSI    00000231 [SR] This component was referenced by [l:186{93}]"Microsoft-Windows-Printer-Drivers-Package~31bf3856ad364e35~amd64~~6.1.7601.17514.INF_prnca00z"

Errors with 'Realtek Audio Drivers'

 Cannot repair member file [l:30{15}]"portcls.sys.mui" of wdmaudio.inf.Resources, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture = [l:10{5}]"en-US", VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, file is missing
2013-02-19 22:16:47, Info                  CSI    000002ad [SR] This component was referenced by [l:194{97}]"Microsoft-Windows-Client-Drivers-Package~31bf3856ad364e35~amd64~en-US~6.1.7601.17514.INF_wdmaudio"

Error related to 'Microsoft Live Cam' drivers:

a0 [SR] Cannot repair member file [l:32{16}]"wiafbdrv.dll.mui" of sti.inf.Resources, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture = [l:10{5}]"en-US", VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, file is missing
2013-02-19 22:16:46, Info                  CSI    000002a1 [SR] Cannot repair member file [l:30{15}]"serscan.sys.mui" of sti.inf.Resources, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture = [l:10{5}]"en-US", VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, file is missing
2013-02-19 22:16:46, Info                  CSI    000002a2 [SR] Cannot repair member file [l:32{16}]"wiafbdrv.dll.mui" of sti.inf.Resources, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture = [l:10{5}]"en-US", VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, file is missing
2013-02-19 22:16:46, Info                  CSI    000002a3 [SR] This component was referenced by [l:184{92}]"Microsoft-Windows-Client-Drivers-Package~31bf3856ad364e35~amd64~en-US~6.1.7601.17514.INF_sti"
2013-02-19 22:16:46, Info                  CSI    000002a4 [SR] Cannot repair member file [l:30{15}]"serscan.sys.mui" of sti.inf.Resources, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture = [l:10{5}]"en-US", VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, file is missing
2013-02-19 22:16:46, Info                  CSI    000002a5 [SR] This component was referenced by [l:184{92}]"Microsoft-Windows-Client-Drivers-Package~31bf3856ad364e35~amd64~en-US~6.1.7601.17514.INF_sti"

Other Windows 'file errors / corruptions' also reported:

http://ecomm.dell.com/myaccount/login.aspx?at=ga,remote&c=us&ct=2%2f25%2f2013+1%3a14%3a17+PM&fs=0&id=100&l=en&ru=https%3a%2f%2fecomm.dell.com%2fmyaccount%2fmain.aspx%3fc%3dus%26l%3den%26s%3ddhs%26~ck%3dpn&s=dhs&tw=7200

Please share if you performed http://www.sevenforums.com/tutorials/433-disk-check.html as I suggested in my previous post.

Also follow the steps listed below to see if they help:
Note: Please follow the steps in this tutorial to create a system restore point; may help in future: http://www.sevenforums.com/tutorials/697-system-restore-point-create.html

1. Uninstall the 'Anti-virus' from the system to check performance. You may allow 'Windows' to install 'Microsoft Security Essentials'; is known to bring stability to 'Windows'

2. Unplug the printer from the computer and remove the printer drivers completely. You may want to use http://www.sevenforums.com/tutorials/83814-drivers-clean-left-over-files-after-uninstalling.html if using an HP Printer. (Also share the make/model of the printer in use)
Alternatively, you may also uninstall the 'driver' from 'Device Manager'; also check 'Programs and Feature' to remove all residual components. Check if the system performance gets better.

3. Try re-installing the 'Realtek Audio' drivers and check the difference.

4. Also remove the 'Microsoft Live Cam' from the 'Device Manager' and check results.

If the issue persists, you may try to 'Reset Windows Update Components' and see if that helps: How do I reset Windows Update components?

Hope this helps. Do reply with the findings; would be glad to assist.