[SOLVED] Frequent Bluescreens about once a day - Windows 7 x64

D

dyslexicfurby

New member
Joined
Feb 17, 2014
Posts
4
I'm grasping at straws here. I get a blue screen about once a day, sometimes longer, but I can't go longer than about 5 days without a crash. The crashes seem to be random (I can be in-game, or web browsing). The check code is different nearly every time as is the offending file. Additionally, these parts are all brand new, purchased around Christmas. I built this rig myself.

I have tried(In no particular order):

1. Installing latest nVidia drivers

2. Installing several earlier nVidia drivers (and beta drivers)

3. sfc /scannow (No errors)

4. memtest86x (run overnight. No errors)

5. Reseating graphics card and RAM (no change, still blue screens)

6. Speedfan (temps seem normal, system does not crash under load while gaming)

7. WhoCrashed - This suggests the issue is with a driver. See 1 and 2. Output is attached

8. Complete reformat and reinstall of Windows 7 (64bit)

9. Chkdsk (No errors)

10. Cleaning dust from the case

11. Driver Verifier (This is shown in the February crash dumps on 2/14, as I forced the system to crash repeatedly to pin down the problem. Yet I still have blue screens after replacing the driver)


There is a gap in the crash logs because I reformatted in January and in my infinite wisdom did not back up the crash dumps. A collection of minidumps is attached. I'm pretty tech savvy, and I've tried quite a few things and I cannot for the life of me figure out what's wrong.

Specs:

Windows 7 - 64 Bit full retail version

System age - 2 Months

OS Age - 1 Month (Reformatted in January)

Intel i7 4770K

GA-B85-HD3 Motherboard

GeForce GTX 780

16GB RAM

1SSD (160GB)

1SSD (300GB)

1HDD (2TB) SATA

PSU CORSAIR CX750M 750W R

View attachment Windows7_Vista_jcgriff2.zip
View attachment Minidumps from Dec and Feb.zip
View attachment WhoCrashedOutput.html
View attachment Feb Crash List.html
View attachment Dec Crash List.html

Thanks beforehand
 
Hi,

We have two consistent bug checks:

PAGE_FAULT_IN_NONPAGED_AREA (50)

This indicates that invalid system memory has been referenced.

Bug check 0x50 usually occurs after the installation of faulty hardware or in the event of failure of installed hardware (usually related to defective RAM, be it main memory, L2 RAM cache, or video RAM).

Another common cause is the installation of a faulty system service.

Antivirus software can also trigger this error, as can a corrupted NTFS volume.

If we take a look at the call stack:
Code: 
4: kd> kv
Child-SP          RetAddr           : Args to Child                                                           : Call Site
fffff880`0aae57d8 fffff800`02b5a5b3 : 00000000`00000050 fffff901`c00c2250 00000000`00000000 fffff880`0aae5940 : nt!KeBugCheckEx
fffff880`0aae57e0 fffff800`02adbcee : 00000000`00000000 fffff901`c00c2250 fffff900`c2a85300 fffffa80`0e84e4e0 : nt! ?? ::FNODOBFM::`string'+0x43801
fffff880`0aae5940 fffff960`0073c1ca : fffffa80`0e84e4e0 fffff960`00000000 00000000`00000000 fffff960`00742000 : nt!KiPageFault+0x16e (TrapFrame @ fffff880`0aae5940)
fffff880`0aae5ad0 fffff960`0074914c : 00000000`00000000 00000000`00000000 fffff900`c00c1020 fffff880`0aae6390 : [COLOR=#ff0000][I][B]cdd!CStagingPool::GetGdiSurface+0xfa[/B][/I][/COLOR]
fffff880`0aae5b40 fffff960`0074a123 : 00000000`00000000 fffff900`c1d3dcd8 fffff900`c31e1018 00000000`00000000 : [COLOR=#ff0000][I][B]cdd!BitBltBitmap+0x53c[/B][/I][/COLOR]
fffff880`0aae60d0 fffff960`0074b130 : 00000000`00000000 00000000`00000a80 00000000`00000000 00000000`00000000 : [COLOR=#ff0000][I][B]cdd!DrvBitBlt+0x17b[/B][/I][/COLOR]
fffff880`0aae62f0 fffff960`00273107 : fffff900`c1c8a738 fffff900`c31e1000 fffff880`0aae6460 00000000`00000001 : [COLOR=#ff0000][I][B]cdd!DrvCopyBits+0x44[/B][/I][/COLOR]
fffff880`0aae6360 fffff960`001b7614 : 00000000`00000000 00000000`00000000 00000000`0000cccc 00000000`00000000 : win32k!OffCopyBits+0xc7
fffff880`0aae63c0 fffff960`001b7aa8 : fffff900`c1d3dcd8 00000000`00000000 00000000`00000000 00000000`00000000 : win32k!SpBitBlt+0x418
fffff880`0aae67b0 fffff960`0020a2bc : 00000000`00000000 fffff900`c00bf240 fffff900`c0000de0 fffff900`c00bf240 : win32k!SpCopyBits+0x44
fffff880`0aae6820 fffff960`0009a79b : 00000000`2c0110cf fffffa80`0ee37b50 fffff880`0aae6b60 00000000`0024ddc8 : win32k!NtGdiBitBltInternal+0xc94
fffff880`0aae6a00 fffff800`02adce53 : fffff880`0aae6b60 fffff800`02ae6aba 00000000`00000024 00000000`74e02450 : win32k!NtGdiBitBlt+0x5b
fffff880`0aae6a70 00000000`74e4fe5a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13 (TrapFrame @ fffff880`0aae6ae0)
00000000`0024dda8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x74e4fe5a

We have a few cdd.dll routines that call into page fault. cdd.dll is the Canonical Display Driver (system driver), and is usually seen when the video card is an issue.

DRIVER_VERIFIER_DETECTED_VIOLATION (c4)

This is the general bug check code for fatal errors found by Driver Verifier.

If we take a look at the call stack:
Code: 
5: kd> kv
Child-SP          RetAddr           : Args to Child                                                           : Call Site
fffff880`0c913878 fffff800`02f144ec : 00000000`000000c4 00000000`000000f6 00000000`000001ac fffffa80`0d97db30 : nt!KeBugCheckEx
fffff880`0c913880 fffff800`02f29bf4 : 00000000`000001ac fffffa80`0d97db30 00000000`00000004 00000000`00000000 : nt!VerifierBugCheckIfAppropriate+0x3c
fffff880`0c9138c0 fffff800`02ce1890 : fffff8a0`000018b0 fffff880`0c913b10 fffff880`0c913c00 fffff880`0c913ea0 : nt!VfCheckUserHandle+0x1b4
fffff880`0c9139a0 fffff800`02d576b5 : fffff8a0`016d7e00 fffff8a0`00000001 fffffa80`0d494260 00000000`00000000 : nt! ?? ::NNGAKEGL::`string'+0x2027e
fffff880`0c913a70 fffff800`02a86e53 : fffffa80`0d4e8b50 fffff880`0c913e28 00000000`00000002 00000000`00000000 : nt!NtQueryValueKey+0x115
fffff880`0c913c00 fffff800`02a83410 : fffff800`02f18d96 fffff880`0f0c70a1 fffff880`0c913ea0 fffff880`0c913e98 : nt!KiSystemServiceCopyEnd+0x13 (TrapFrame @ fffff880`0c913c70)
fffff880`0c913e08 fffff800`02f18d96 : fffff880`0f0c70a1 fffff880`0c913ea0 fffff880`0c913e98 fffff800`02a83410 : nt!KiServiceLinkage
fffff880`0c913e10 fffff880`0f0c70a1 : fffff880`0c9148ca fffff880`0c913ee0 fffff880`0c9148b8 fffffa80`0ce21a98 : nt!VfZwQueryValueKey+0x76
fffff880`0c913e60 fffff880`0c9148ca : fffff880`0c913ee0 fffff880`0c9148b8 fffffa80`0ce21a98 00000000`00000000 : [COLOR=#ff0000][I][B]nvlddmkm+0x9b0a1[/B][/I][/COLOR]
fffff880`0c913e68 fffff880`0c913ee0 : fffff880`0c9148b8 fffffa80`0ce21a98 00000000`00000000 fffff880`0c913e90 : 0xfffff880`0c9148ca
fffff880`0c913e70 fffff880`0c9148b8 : fffffa80`0ce21a98 00000000`00000000 fffff880`0c913e90 fffff980`00000000 : 0xfffff880`0c913ee0
fffff880`0c913e78 fffffa80`0ce21a98 : 00000000`00000000 fffff880`0c913e90 fffff980`00000000 00000000`000001ac : 0xfffff880`0c9148b8
fffff880`0c913e80 00000000`00000000 : fffff880`0c913e90 fffff980`00000000 00000000`000001ac fffffa80`00320030 : 0xfffffa80`0ce21a98

-- FAILURE_BUCKET_ID: X64_0xc4_f6_nvlddmkm+9b0a1

^^ DV flagged the nVidia video driver. We can't look into this dump in-depth as it's a minidump, we'd need a Kernel.

-----------

Given you've run Memtest, tried various video card versions, etc, this is likely a faulty video card. Do you have integrated graphics, or access to a secondary GPU to test?

Code: 
6: kd> !sysinfo machineid
Machine ID Information [From Smbios 2.7, DMIVersion 39, Size=3154]
BiosMajorRelease = 4
BiosMinorRelease = 6
BiosVendor = American Megatrends Inc.
BiosVersion = F4

You have the F4 bios rev, which is the release date BIOS. The latest is F6, which includes PCI-e compatibility, likely a few stability fixes, etc. I'd install it. Do note that you have to update the USB driver in advance according to Gigabyte - GIGABYTE - Motherboard - Socket 1150 - GA-B85-HD3 (rev. 1.x)

Regards,

Patrick
 
I had not considered updating my BIOS as I learned that one should not unless necessary. I think in this case it's necessary; I will update the BIOS and get back to you. I really hope it's not the graphics card, as it's brand new. Additionally, whether or not the system is under load (i.e. gaming) does not seem to influence whether or not I get a BSOD. I also see no artifacts, or tearing, or anything to suggest the card itself is faulty (except of course the BSODs but this is me being hopeful, as it was an expensive card). I do have integrated graphics but I do not have another graphics card I can test with unfortunately.

I would also like to point out that there were quite a few other minidumps that were lost when I reformatted my computer, and nvlddmkm was not nearly as prominent. It didn't really start appearing until driver verifier forced it to crash. Thank you for your input, I will post again once I update the BIOS.

Also, is there a way to tell Windows to do a full memory dump and *not* override a previous full memory dump? Although I suppose I could copy the dump manually...
 
Also, is there a way to tell Windows to do a full memory dump and *not* override a previous full memory dump?
Click to expand...

Windows key + Pause key. This should bring up System. Click Advanced System Settings on the left > Advanced > Startup and Recovery > Settings > System Failure >

sysnative123123.png

Un-check this option.

Regards,

Patrick
 
Updated the BIOS. No BSOD yet. The display driver crashed once but Windows was able to recover (unlike before where it would simply bluescreen). Additionally, the driver I'm using is an old beta driver (I was trying a dozen different display drivers to pin down the problem. ) so I'm not too surprised. The longest I've gone is about five days without a crash, so I will post again in a week (or at the next BSOD, whichever comes first) and declare my results.
 
The display driver crashing even though being unable to recover is a bit worrying, but sometimes it happens even on 100% functioning systems depending on the situation at the time. Keep me updated.

Regards,

Patrick
 
Well, it's been about a week since I updated the BIOS and I have not had a single BSOD. My machine is on 24/7 and I have no complaints. It looks like the problem is solved. Thanks for your help.
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top