Solved BSOD playing games, browsing the web, programming, doing nothing

[Techtony96]

Hello, and thanks for taking your time to read this.

I built my new computer last weekend, installed Windows 7 Home Premium x64 on it, installed all my motherboard drivers (latest from the website) and the graphics card driver (tried latest stable and latest beta). I then installed all Windows Updates. At this point BSOD starting happening. I have been using my computer to try to pinpoint the BSOD cause, but no luck. I tried using my computer in safemode but it will BSOD there too. Computer hardware info is below, and the debug tool files are attached as well.


Intel Core i5-4670K, Gigabyte GeForce GTX 770, BitFenix Prodigy M Midnight - Tony's Gaming PC - Techtony96's Saved Part List - PCPartPicker

 

[Arc]

Hi Techtony96.

Uninstall Norton and all Symentec products using Norton Removal tool. At least as a test. Use Microsoft Security Essentials as your antivirus with windows inbuilt firewall, and free MBAM as the on demand scanner.

Download, install and update those, and then run full system scans with both of them, one by one.
___________________________________________________________________________________________

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 19, {20, fffffa800c9a03d0, fffffa800c9a0410, 404000e}

*** WARNING: Unable to verify timestamp for IDSvia64.sys
*** ERROR: Module load completed but symbols could not be loaded for IDSvia64.sys
[B][COLOR=Red]Probably caused by : IDSvia64.sys[/COLOR][/B] ( IDSvia64+45abb )

Followup: MachineOwner
---------

fffff880`04800000 fffff880`04884000   IDSvia64 T (no symbols)           
   [COLOR=Red][B] Loaded symbol image file: IDSvia64.sys[/B][/COLOR]
   [B][COLOR=Red] Image path: \??\C:\Program Files (x86)\Norton 360\NortonData\21.1.0.18\Definitions\IPSDefs\20131220.001\IDSvia64.sys[/COLOR][/B]
    Image name: IDSvia64.sys
    Timestamp:        Fri Dec 06 07:23:44 2013 (52A12E28)
    CheckSum:         0008D1A0
    ImageSize:        00084000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

 

[Techtony96]

Hello Arc, and thank you for assisting me.

I completed the scan from MBAM, and it returned one false positive, the installation file for FileZilla, a popular FTP program. I then needed to check something in my Google Drive, and as I was logging into my Google account, my computer BSOD'd. I attached the dump file as zipped to this post.

Thank you!

 

[Arc]

The latest BSOD is not saying anything clearly.

Test your RAM modules for possible errors.
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 passes, preferably overnight.

If it start showing errors/red lines, stop testing. A single error is enough to determine that something is going bad there.

If memtest is free from errors, enable Driver Verifier to monitor the drivers.
Driver Verifier - Enable and Disable
Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

   Information

Why Driver Verifier:
It puts a stress on the drivers, ans so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.

How Can we know that DV is enabled:
It will make the system bit of slow, laggy.

   Warning

Before enabling DV, make it sure that you have earlier System restore points made in your computer. You can check it easily by using CCleaner looking at Tools > System Restore.

If there is no points, make a System Restore Point manually before enabling DV.

   Tip

• If you fail to get on the Desktop because of DV, Boot into Advanced Boot Options > Safe mode. Disable DV there. Now boot normally again, and try following the instruction of enabling DV again.
• If you cannot boot in Safe mode too, do a System Restore to a point you made earlier.

Let us know the results, with the subsequent crash dumps, if any. Post it following the Blue Screen of Death (BSOD) Posting Instructions.

 

[matts6887]

I agree with Arc; i would definitely test your ram modules by doing a memory scan/test. That way you will know if its the ram or not.

 

[Techtony96]

I have run a memtest with memtest86 for 10 hours, and got 11 passes, will try driver Verifier now.

I also had three more BSOD since my last post.

 

[Techtony96]

Ok, so I went through all the steps to enable driver verifier, the computer booted up, I signed in, and now my desktop wont show up and my screen is black. I booted into safe mode, disabled DF, and then booted booted normally. Went through the process to enable DV, and it is doing the same thing (black screen after login). Now i went back to safe mode and disabled it. What should I do next?

 

[Arc]

Ok, so I went through all the steps to enable driver verifier, the computer booted up, I signed in, and now my desktop wont show up and my screen is black. I booted into safe mode, disabled DF, and then booted booted normally. Went through the process to enable DV, and it is doing the same thing (black screen after login). Now i went back to safe mode and disabled it. What should I do next?

Very common situation.

Free up the startup. Windows does not need any other program to auto start with it, but the auto start programs often conflicts and causes various problems including BSODs.

1. Click on the Start button
2. Type “msconfig (without quotes), click the resulting link. It will open the System Configuration window.
3. Select the “Startup” tab.
4. Deselect all items other than the antivirus.
5. Apply > OK
6. Accept then restart.

Now disable Verifier again. Dont select any driver provided by "microsoft", "macrovision" and "unknown" in the list. Hopefully this time it will BSOD after getting to the desktop.

BTW, you replied that you ran memtest86+, but did not report the result :sarc:

 

[Techtony96]

I ran Memtest86 for 10 hours and got 11 passes with 0 errors, if there is some output file that i am unaware of, let me know and i can post it here.

Drivers to verify: NVIDIA, Realtek, AMD, Atheros (WiFi Card), Intel

I am NOT verifying: <unknown>, Macrovision, Malwarebytes, and Microsoft

ok, got to my desktop this time.

 

[Techtony96]

Once I got to my desktop, I opened chrome and it BSOD'd immediately.
Now it BSOD's every time windows boots up. I used Startup repair which got me back to where i can get to my desktop. I attached the minidump file from when it BSOD with DV on.

 

[Arc]

This BSOD is caused by Nvidia display driver. And unfortunately I dont know any driver version that works good with GTX 770. You may try the drivers on a trial and error basis:

• 320.49 WHQL
• 327.23 WHQL
• 331.58 WHWL
• 331.65 WHQL
• 331.82 WHQL

Get them from Drivers - Download NVIDIA Drivers

Do a clean install on all of them. Uninstall the previously installed driver first.
Uninstall All nvidia items in Control Panel > Programs and features

• • 3D Vision Control Driver
  • 3D Vision Driver
  • Graphics Driver
  • HD Audio Driver
  • PhysX
  • nvidia Update
  (Are you using nvidia chipset drivers? If so, dont uninstall anything other than those are listed).
• Now follow Drivers - Clean Left over Files after Uninstalling
• Download the target WHQL. While installing, Select Custom (Advanced) install. In the next page, follow this settings:
  
  

Lengthy process, but the only stable version of nvidia is 314.22 lately, which does not support 700 series GPUs.

__________________________________________________________________________________________

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck C4, {f6, 22c, fffffa800c4c2570, fffff8800f574879}

*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+9a879 )

Followup: MachineOwner
---------

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
A device driver attempting to corrupt the system has been caught.  This is
because the driver was specified in the registry as being suspect (by the
administrator) and the kernel has enabled substantial checking of this driver.
If the driver attempts to corrupt the system, bugchecks 0xC4, 0xC1 and 0xA will
be among the most commonly seen crashes.
Arguments:
Arg1: 00000000000000f6, Referencing user handle as KernelMode.
Arg2: 000000000000022c, Handle value being referenced.
Arg3: fffffa800c4c2570, Address of the current process.
Arg4: fffff8800f574879, Address inside the driver that is performing the incorrect reference.

Debugging Details:
------------------


BUGCHECK_STR:  0xc4_f6

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP

PROCESS_NAME:  chrome.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff800033094ec to fffff80002e7cbc0

STACK_TEXT:  
fffff880`0cdf4888 fffff800`033094ec : 00000000`000000c4 00000000`000000f6 00000000`0000022c fffffa80`0c4c2570 : nt!KeBugCheckEx
fffff880`0cdf4890 fffff800`0331ebf4 : 00000000`0000022c fffffa80`0c4c2570 00000000`00000004 fffff8a0`02e20a30 : nt!VerifierBugCheckIfAppropriate+0x3c
fffff880`0cdf48d0 fffff800`030d6890 : fffff8a0`00000003 fffff880`0cdf4b20 fffff880`0cdf4d00 fffff880`0cdf4eb0 : nt!VfCheckUserHandle+0x1b4
fffff880`0cdf49b0 fffff800`0314c6b5 : fffff8a0`02e7a900 fffff8a0`00000001 fffffa80`06d46500 00000000`00000000 : nt! ?? ::NNGAKEGL::`string'+0x2027e
fffff880`0cdf4a80 fffff800`02e7be53 : fffffa80`0b518b50 fffff880`0cdf4e38 00000000`00000002 00000000`00000000 : nt!NtQueryValueKey+0x115
fffff880`0cdf4c10 fffff800`02e78410 : fffff800`0330dd96 fffff880`0f574879 fffff880`0cdf4eb0 fffff880`0cdf4ea8 : nt!KiSystemServiceCopyEnd+0x13
fffff880`0cdf4e18 fffff800`0330dd96 : fffff880`0f574879 fffff880`0cdf4eb0 fffff880`0cdf4ea8 fffff800`02e78410 : nt!KiServiceLinkage
fffff880`0cdf4e20 fffff880`0f574879 : fffff880`0cdf58ca fffff880`0cdf4ef0 fffff880`0cdf58b8 fffffa80`07290798 : nt!VfZwQueryValueKey+0x76
fffff880`0cdf4e70 fffff880`0cdf58ca : fffff880`0cdf4ef0 fffff880`0cdf58b8 fffffa80`07290798 00000000`00000000 : nvlddmkm+0x9a879
fffff880`0cdf4e78 fffff880`0cdf4ef0 : fffff880`0cdf58b8 fffffa80`07290798 00000000`00000000 fffff880`0cdf4ea0 : 0xfffff880`0cdf58ca
fffff880`0cdf4e80 fffff880`0cdf58b8 : fffffa80`07290798 00000000`00000000 fffff880`0cdf4ea0 fffff980`00000000 : 0xfffff880`0cdf4ef0
fffff880`0cdf4e88 fffffa80`07290798 : 00000000`00000000 fffff880`0cdf4ea0 fffff980`00000000 00000000`0000022c : 0xfffff880`0cdf58b8
fffff880`0cdf4e90 00000000`00000000 : fffff880`0cdf4ea0 fffff980`00000000 00000000`0000022c fffffa80`00280026 : 0xfffffa80`07290798


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nvlddmkm+9a879
fffff880`0f574879 3d340000c0      cmp     eax,0C0000034h

SYMBOL_STACK_INDEX:  8

SYMBOL_NAME:  nvlddmkm+9a879

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  5290d7c5

FAILURE_BUCKET_ID:  X64_0xc4_f6_VRF_nvlddmkm+9a879

BUCKET_ID:  X64_0xc4_f6_VRF_nvlddmkm+9a879

Followup: MachineOwner
---------

0: kd> lmvm nvlddmkm
start             end                 module name
fffff880`0f4da000 fffff880`1011b000   nvlddmkm T (no symbols)           
    Loaded symbol image file: nvlddmkm.sys
    Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
    Image name: nvlddmkm.sys
    Timestamp:        Sat Nov 23 21:58:53 2013 (5290D7C5)
    CheckSum:         00C09A5E
    ImageSize:        00C41000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

 

[Techtony96]

I have tried all the following versions, and they either make my system BSOD or are not compatible with my games (Tested with BF4)

 

[Arc]

Then replace the GPU. Use one that is below 700 series.

Or ask your game developer if they have any custom settings or patches that is applicable for your system.

Unfortunately I am seeing no other way out at the current situation.