Random BSOD on Brand New Computer Killng Me

jerrythesurfer · Apr 21, 2015

I purchased a new computer with Windows 8.1 installed. There is no other software on this computer at all, less drivers for my hardware,. I get BSOD about 1x every few days. The reasons that shows on the BSOD are always different. I am so frustrated and don't know what to do. This is a brand new beautiful computer but the BSODs are killing me.

I think I followed your directions to create and upload the .Zip file with my crash dump. Please confirm

Thanks in advance

Jerry

[added info] -- this has been going on for 3 months. I returned the computer 2x to the manufacturer. The last time they replaced the motherboard, graphics card, power supply and memory; that's everything. None the less the problem persists

Addictive Gamer · Apr 29, 2015

Hello,
I see you waiting for so long so here is what your dumps look like:

Dump 1:

Code:

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


[B]CRITICAL_STRUCTURE_CORRUPTION (109)[/B]
[COLOR=#ff0000]This bugcheck is generated when the kernel detects that critical kernel code or
data have been corrupted. There are generally three causes for a corruption:
[/COLOR]1) A driver has inadvertently or deliberately modified critical kernel code
 or data. See http://www.microsoft.com/whdc/driver/kernel/64bitPatching.mspx
2) A developer attempted to set a normal kernel breakpoint using a kernel
 debugger that was not attached when the system was booted. Normal breakpoints,
 "bp", can only be set if the debugger is attached at boot time. Hardware
 breakpoints, "ba", can be set at any time.
3) A hardware corruption occurred, e.g. failing RAM holding kernel code or data.
Arguments:
Arg1: a3a01f5a16fa06f3, Reserved
Arg2: b3b72be069793ea6, Reserved
Arg3: fffff8017f72d380, Failure type dependent information
Arg4: 0000000000000001, Type of corrupted region, can be
    0 : A generic data region
    1 : Modification of a function or .pdata
    2 : A processor IDT
    3 : A processor GDT
    4 : Type 1 process list corruption
    5 : Type 2 process list corruption
    6 : Debug routine modification
    7 : Critical MSR modification


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




PG_MISMATCH:  200000


MEMORY_CORRUPTOR:  ONE_BIT


FAULTING_IP: 
Ntfs!NtfsFreeReservedClusters+29b00
fffff801`7f72d380 488b4b58        mov     rcx,qword ptr [rbx+58h]


CUSTOMER_CRASH_COUNT:  1


DEFAULT_BUCKET_ID:  CODE_CORRUPTION


BUGCHECK_STR:  0x109


PROCESS_NAME:  System


CURRENT_IRQL:  2


ANALYSIS_VERSION: 6.3.9600.17298 (debuggers(dbg).141024-1500) amd64fre


STACK_TEXT:  
ffffd001`12493088 00000000`00000000 : 00000000`00000109 a3a01f5a`16fa06f3 b3b72be0`69793ea6 fffff801`7f72d380 : nt!KeBugCheckEx




STACK_COMMAND:  kb


CHKIMG_EXTENSION: !chkimg -lo 50 -d !Ntfs
    fffff8017f72d3af - Ntfs!NtfsFreeReservedClusters+29b2f
    [ 48:58 ]
1 error : !Ntfs (fffff8017f72d3af)


MODULE_NAME: memory_corruption


IMAGE_NAME:  memory_corruption


FOLLOWUP_NAME:  memory_corruption


DEBUG_FLR_IMAGE_TIMESTAMP:  0


FAILURE_BUCKET_ID:  MEMORY_CORRUPTION_ONE_BIT


BUCKET_ID:  MEMORY_CORRUPTION_ONE_BIT


ANALYSIS_SOURCE:  KM


FAILURE_ID_HASH_STRING:  km:memory_corruption_one_bit


FAILURE_ID_HASH:  {e3faf315-c3d0-81db-819a-6c43d23c63a7}


Followup: memory_corruption
---------

Dump 2:

Indicates that a severe memory management error occurred, dump 1 says it could also be caused by failing RAM or or even Hard drive, just assuming because it stuck at Ntfs!NtfsFreeReservedClusters

Code:

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


[B]MEMORY_MANAGEMENT (1a)[/B]
    [COLOR=#ff0000]# Any other values for parameter 1 must be individually examined.[/COLOR]
Arguments:
Arg1: 0000000000000[COLOR=#ff0000]402[/COLOR], The subtype of the bugcheck.
Arg2: ffffc00090da4e40
Arg3: 8000000174818b8a
Arg4: ffffc00098da4e41


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




BUGCHECK_STR:  0x1a_402


CUSTOMER_CRASH_COUNT:  1


DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT


PROCESS_NAME:  System


CURRENT_IRQL:  2


ANALYSIS_VERSION: 6.3.9600.17298 (debuggers(dbg).141024-1500) amd64fre


LAST_CONTROL_TRANSFER:  from fffff8007f38e4c7 to fffff8007f361ca0


STACK_TEXT:  
ffffd000`315718d8 fffff800`7f38e4c7 : 00000000`0000001a 00000000`00000402 ffffc000`90da4e40 80000001`74818b8a : nt!KeBugCheckEx
ffffd000`315718e0 fffff800`7f28126c : 00000000`00000000 ffffe001`28970690 00000000`00384000 00000000`00384000 : nt! ?? ::FNODOBFM::`string'+0x1c307
ffffd000`31571940 fffff800`7f5ba00b : ffffe001`28970690 00000000`00002000 ffffe001`00002001 00000000`00000000 : nt!MiDeleteSegmentPages+0x1c0
ffffd000`315719d0 fffff800`7f257f69 : 00000000`00000002 ffffd000`31571a40 ffffe001`2145f080 fffff800`7f2c2226 : nt!MiSegmentDelete+0x57
ffffd000`31571a10 fffff800`7f63e944 : 00000000`00000000 00000000`00000000 ffffe001`2145f080 ffffc000`8bbb32f0 : nt!MiCheckControlArea+0x1bd
ffffd000`31571a70 fffff800`7f26401f : 00000000`00000000 ffffe001`28db92f0 ffffc000`8bbb3320 fffff800`7f4c3340 : nt!ObpRemoveObjectRoutine+0x64
ffffd000`31571ad0 fffff800`abeb5042 : ffffe001`28db92f0 ffffe001`2836f880 00000000`00000000 fffff800`7f4c3340 : nt!ObfDereferenceObject+0x8f
ffffd000`31571b10 fffff800`7f2be6bc : fffff800`7f283354 ffffe001`2836f9c0 ffffe001`26376610 fffff800`7f4c3340 : dxgmms1!VidMmProcessAsyncOperation+0x1a
ffffd000`31571b50 fffff800`7f31136c : 00000001`46dbc000 ffffe001`2836f880 00000000`00000080 ffffe001`2836f880 : nt!ExpWorkerThread+0x28c
ffffd000`31571c00 fffff800`7f3682c6 : ffffd001`c8240180 ffffe001`2836f880 ffffe001`21888880 ffffe001`29c3c6b0 : nt!PspSystemThreadStartup+0x58
ffffd000`31571c60 00000000`00000000 : ffffd000`31572000 ffffd000`3156c000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16




STACK_COMMAND:  kb


FOLLOWUP_IP: 
dxgmms1!VidMmProcessAsyncOperation+1a
fffff800`abeb5042 8b05f86dfeff    mov     eax,dword ptr [dxgmms1!Microsoft_Windows_DxgKrnlEnableBits (fffff800`abe9be40)]


SYMBOL_STACK_INDEX:  7


SYMBOL_NAME:  dxgmms1!VidMmProcessAsyncOperation+1a


FOLLOWUP_NAME:  MachineOwner


MODULE_NAME: dxgmms1


IMAGE_NAME:  dxgmms1.sys


DEBUG_FLR_IMAGE_TIMESTAMP:  54505506


IMAGE_VERSION:  6.3.9600.17415


BUCKET_ID_FUNC_OFFSET:  1a


FAILURE_BUCKET_ID:  0x1a_402_dxgmms1!VidMmProcessAsyncOperation


BUCKET_ID:  0x1a_402_dxgmms1!VidMmProcessAsyncOperation


ANALYSIS_SOURCE:  KM


FAILURE_ID_HASH_STRING:  km:0x1a_402_dxgmms1!vidmmprocessasyncoperation


FAILURE_ID_HASH:  {4cfe95d7-cae2-1726-7c73-a2ae9711b69f}


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

Dump 3:

Parameter 1 indicates whether a single DPC exceeded a timeout, or whether the system cumulatively spent an extended period of time.

Determining the cause with a first parameter of 1 is a bit more difficult because the problem is a result of DPCs running from multiple drivers, so the call stack is insufficient to determine the culprit.

Code:

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


[B]DPC_WATCHDOG_VIOLATION (133)[/B]
[COLOR=#ff0000]The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL
or above.[/COLOR]
Arguments:
Arg1: 0000000000000001, The system cumulatively spent an extended period of time at
    DISPATCH_LEVEL or above. The offending component can usually be
    identified with a stack trace.
Arg2: 0000000000001e00, The watchdog period.
Arg3: 0000000000000000
Arg4: 0000000000000000


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




DPC_TIMEOUT_TYPE:  DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDED


CUSTOMER_CRASH_COUNT:  1


DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT


BUGCHECK_STR:  0x133


PROCESS_NAME:  svchost.exe


CURRENT_IRQL:  d


ANALYSIS_VERSION: 6.3.9600.17298 (debuggers(dbg).141024-1500) amd64fre


LAST_CONTROL_TRANSFER:  from fffff8016a3f8f7e to fffff8016a3ddca0


STACK_TEXT:  
fffff801`6bf2fc88 fffff801`6a3f8f7e : 00000000`00000133 00000000`00000001 00000000`00001e00 00000000`00000000 : nt!KeBugCheckEx
fffff801`6bf2fc90 fffff801`6a2c9871 : fffff801`6bf2fe60 00000000`00261717 ffff2352`ebbd934d fffff801`762a83b5 : nt! ?? ::FNODOBFM::`string'+0xadbe
fffff801`6bf2fd20 fffff801`6a2257b5 : 00000000`00400a02 ffffd001`cddb1bf0 fffff801`762a81c0 00000000`00006001 : nt!KeClockInterruptNotify+0x91
fffff801`6bf2ff40 fffff801`6a364143 : fffff801`6bf2ff60 00000000`00000008 fffff801`6bf2ff50 00000000`0000000c : hal!HalpTimerClockIpiRoutine+0x15
fffff801`6bf2ff70 fffff801`6a3df12a : fffff801`6a271800 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0xa3
fffff801`6bf2ffb0 fffff801`6a3df50f : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiInterruptSubDispatchNoLockNoEtw+0xea
ffffd000`33a45a90 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiInterruptDispatchLBControl+0x11f




STACK_COMMAND:  kb


FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+adbe
fffff801`6a3f8f7e cc              int     3


SYMBOL_STACK_INDEX:  1


SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+adbe


FOLLOWUP_NAME:  MachineOwner


MODULE_NAME: nt


IMAGE_NAME:  ntkrnlmp.exe


DEBUG_FLR_IMAGE_TIMESTAMP:  550f41a6


IMAGE_VERSION:  6.3.9600.17736


BUCKET_ID_FUNC_OFFSET:  adbe


FAILURE_BUCKET_ID:  0x133_ISR_nt!_??_::FNODOBFM::_string_


BUCKET_ID:  0x133_ISR_nt!_??_::FNODOBFM::_string_


ANALYSIS_SOURCE:  KM


FAILURE_ID_HASH_STRING:  km:0x133_isr_nt!_??_::fnodobfm::_string_


FAILURE_ID_HASH:  {89366ad1-5557-ac2b-d015-8f6ec2fdbf31}


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

As you can see there is nothing obvious at first glance, and it looks like it won't be easy to solve.

First 2 dumps could be about either a bad driver or failing hardware.
So first step the to eliminate either of these 2 possible causes is to test you hardware nice that's easier than hunting bad drivers.
To perform memory test follow this link:
Diagnosing memory problems on your computer

To Check your hard drive for bad sectors follow this link:
Check your hard disk for errors

To diagnoze your processor:
Intel® Processor Diagnostic Tool (64-bit)

As for dump 3 we would need to sit in from of your PC to possibly catch the driver, however here is a tutorial on how to do it yourself.

Windows Performance Toolkit
Check this one too

Providing more dumps could really help, if you're able to provide more then please do so.
Since bad driver could also be the cause check this website for updates:
Gygabyte drivers

Also visit Intel, Nvidia and other official websites for latest driver updates.
If you're unsure how to find latest and correct drivers let me know...

Disabling Windows update from updating your drivers is not bad:
Disable Searching Windows Update for Device Drivers

Afterwards you can run windows update and install optional updates ( if any )

Please post results of at least first 3 tests, and after you fully updated your system drivers. and then we will continue next.

jerrythesurfer · Apr 29, 2015

More Clues

Addictive Gamer,

First, thanks for the initial feedback. I will do what you suggested.

I can add a few things that can perhaps help to isolate the issue,
1) for 1 week I disabled Sleep and the BSODs and other Event Log Errors all went away. Impossible to prove a negative but I'm thinking it Sleep related
2) I re-enabled Sleep and now I'm getting Event Log errors and another BSOD that I will include here.

Addictive Gamer · Apr 29, 2015

Hi,

This last dump is absolutely useful comparing to others, although not at first glance

042815-6046-01.dmp

Code:

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


[B]SYSTEM_SERVICE_EXCEPTION (3b)[/B]
[COLOR=#ff0000]An exception happened while executing a system service routine.[/COLOR]
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff9600019dbbf, Address of the instruction which caused the bugcheck
Arg3: ffffd001627bde80, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.


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




EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.


FAULTING_IP: 
win32k!SetHandleFlag+f
fffff960`0019dbbf 48897920        mov     qword ptr [rcx+20h],rdi


CONTEXT:  ffffd001627bde80 -- (.cxr 0xffffd001627bde80;r)
rax=ffffd001627be8b8 rbx=000000000000024c rcx=000000000000024c
rdx=0000000000000001 rsi=0000000000000000 rdi=0000000000000000
rip=fffff9600019dbbf rsp=ffffd001627be8b8 rbp=ffffd001627bea09
 r8=0000000000000000  r9=fffff901406b05d0 r10=fffff90140801020
r11=ffffd001627be630 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010246
win32k!SetHandleFlag+0xf:
fffff960`0019dbbf 48897920        mov     qword ptr [rcx+20h],rdi ds:002b:00000000`0000026c=????????????????
Last set context:
rax=ffffd001627be8b8 rbx=000000000000024c rcx=000000000000024c
rdx=0000000000000001 rsi=0000000000000000 rdi=0000000000000000
rip=fffff9600019dbbf rsp=ffffd001627be8b8 rbp=ffffd001627bea09
 r8=0000000000000000  r9=fffff901406b05d0 r10=fffff90140801020
r11=ffffd001627be630 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010246
win32k!SetHandleFlag+0xf:
fffff960`0019dbbf 48897920        mov     qword ptr [rcx+20h],rdi ds:002b:00000000`0000026c=????????????????
Resetting default scope


CUSTOMER_CRASH_COUNT:  1


DEFAULT_BUCKET_ID:  CODE_CORRUPTION


BUGCHECK_STR:  0x3B


PROCESS_NAME:  csrss.exe


CURRENT_IRQL:  0


ANALYSIS_VERSION: 6.3.9600.17298 (debuggers(dbg).141024-1500) amd64fre


LAST_CONTROL_TRANSFER:  from fffff9600019dfc1 to fffff9600019dbbf


STACK_TEXT:  
ffffd001`627be8b8 fffff960`0019dfc1 : 00000000`0000024c ffffd001`627bea09 00000000`00000000 00000000`00000000 : win32k!SetHandleFlag+0xf
ffffd001`627be8c0 fffff960`00149169 : ffffd001`627bea98 ffffd001`627bea09 00000000`00000000 fffff801`38610915 : win32k!CloseProtectedHandle+0x21
ffffd001`627be8f0 fffff960`0014aa2d : 00000000`00000000 ffffd001`627bea90 ffffd001`627be988 ffffe001`00438ec0 : win32k!xxxRestoreCsrssThreadDesktop+0x79
ffffd001`627be960 fffff960`001f5e16 : 00000000`00000000 00000000`00000000 ffffe001`00475650 00000000`00000006 : win32k!xxxSetInformationThread+0x10d
ffffd001`627bea70 fffff960`00191c74 : ffffe000`ff5d5880 00000000`00000000 00000000`00000000 00000000`00000000 : win32k!xxxUserPowerCalloutWorker+0xf2
ffffd001`627bead0 fffff801`383cd4b3 : ffffe000`ff5d5880 00000000`0000001f 00000000`00000000 000000eb`3e69f7f8 : win32k!NtUserCallNoParam+0x44
ffffd001`627beb00 00007ffd`0e7a18aa : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
000000eb`3e69f7f8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffd`0e7a18aa




CHKIMG_EXTENSION: !chkimg -lo 50 -db !win32k
20 errors : !win32k (fffff9600019d011-fffff9600019dfa1)
fffff9600019d010  00 *58  89  44  24  40  48  8d  44  24  40  48  89  83  68  01 .X.D$@H.D$@H..h.
...
fffff9600019d260  00 *c9  44  24  38  48  8b  87  08  02  00  00  48  89  45  98 ..D$8H......H.E.
...
fffff9600019d350  00  00  00  89  8d  b0  00  00  00 *1f  85  ed  00  00  00  44 ...............D
...
fffff9600019d390  00 *04  3b  e6  74  0b  41  83  fc  02  75  2f  44  8b  ce  eb ..;.t.A...u/D...
...
fffff9600019d410  bf *30  01  00  00  00  75  0d  89  b7  38  01  00  00  f0  ff .0....u...8.....
fffff9600019d420  05 *07  ae  34  00  48  8b  cf  e8  d3  db  0b  00  e9  d8  02 ...4.H..........
...
fffff9600019d470  48  8b  55  88  48  85  d2  74  59 *58  85  db  74  54  8b  47 H.U.H..tYX..tT.G
...
fffff9600019d660  03 *10  00  00  cd  29  41  f6  c7  10  74  68  48  8b  4c  24 .....)A...thH.L$
fffff9600019d670  30  e8  7a  9a  2a  00  eb  5c  48 *83  c8  ff  15  a7  45  2e 0.z.*..\H.....E.
...
fffff9600019d6c0  b9  00  80  00  00  48  c7  44  24 *7e  00  00  00  00  ff  15 .....H.D$~......
...
fffff9600019d730  00  48  81  c4  70  01  00  00  41 *4f  41  5e  41  5d  41  5c .H..p...AOA^A]A\
...
fffff9600019d850  46 *0b  01  0f  85  c6  00  00  00  48  8b  bc  24  80  00  00 F........H..$...
...
fffff9600019d9d0  d1 *26  89  4c  24  20  eb  19  8b  c8  ff  15  d8  36  2e  00 .&.L$ .......6..
...
fffff9600019dbc0  89 *79  20  41  56  48  83  ec  20  48  8b  f9  48  8b  0d  55 .y AVH.. H..H..U
...
fffff9600019dc10  e5 *60  8b  cd  48  c1  e9  03  e8  17  3e  2d  00  4c  8b  f0 .`..H.....>-.L..
...
fffff9600019dcc0  05  3b  b3  33  00  48  33  c4  48 *8b  44  24  50  49  8b  f0 .;.3.H3.H.D$PI..
...
fffff9600019deb0  90  90  90  90  48  8b  05  dd  8f *74  00  f7  80  b0  01  00 ....H....t......
fffff9600019dec0  00  00  00  00  02  75  3c  f6  42 *2e  04  75  36  48  8b  52 .....u<.B..u6H.R
...
fffff9600019df50  c8 *34  08  48  8b  d6  e8  95  00  00  00  48  85  ff  74  09 .4.H.......H..t.
...
fffff9600019dfa0  48 *8d  5c  24  08  57  48  83  ec  20  40  8a  fa  48  8b  d9 H.\$.WH.. @..H..


MODULE_NAME: memory_corruption


IMAGE_NAME:  memory_corruption


FOLLOWUP_NAME:  memory_corruption


DEBUG_FLR_IMAGE_TIMESTAMP:  0


MEMORY_CORRUPTOR:  STRIDE


STACK_COMMAND:  .cxr 0xffffd001627bde80 ; kb


FAILURE_BUCKET_ID:  MEMORY_CORRUPTION_STRIDE


BUCKET_ID:  MEMORY_CORRUPTION_STRIDE


ANALYSIS_SOURCE:  KM


FAILURE_ID_HASH_STRING:  km:memory_corruption_stride


FAILURE_ID_HASH:  {574dbc1b-92cb-fb09-cb7a-cacc1bb2c511}


Followup: memory_corruption
---------

csrss.exe is mentioned which is a client/server runtime subsystem and this is a service (not executable in this context).
however it's not this service that corrupted memory.
by looking at stack trace it leads to win32k.sys which manages window manager and GDI (Graphic device interface) in Windows.

According to this we can safely blame graphics driver.
Also in another thread you said you were pulling graphic card out and in? Why did you do that?

Edit:
Here is what debug help has to say:

"The SYSTEM_SERVICE_EXCEPTION bug check has a value of 0x0000003B. This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.

Cause:
This error has been linked to excessive paged pool usage and may occur due to user-mode graphics drivers crossing over and passing bad data to the kernel code"

Here is cut from event log according to your expectation:

Code:

The system has returned from a low power state.


Sleep Time: ?2015?-?04?-?28T13:11:57.651494000Z
Wake Time: ?2015?-?04?-?28T13:35:56.963982400Z


Wake Source: Device -Intel(R) USB 3.0 eXtensible Host Controller - 0100 (Microsoft)


Intel(R) Ethernet Connection I217-V
 Network link is disconnected.

The system has returned from a low power state.


The system time has changed to ?2015?-?04?-?28T14:18:03.500000000Z from ?2015?-?04?-?28T14:04:21.525790000Z.


Change Reason: System time synchronized with the hardware clock.

And few other event, nothing unusual from what I can say.

jerrythesurfer · Apr 29, 2015

Thanks again for your input and effort; it is very much appreciated.
I would be surprised if it is the graphics card as I've had a NVIDIA 750ti and now the 960 and my problems remain the same. With that said, here is what I was trying.

The computer is completely bare bones except for the graphics card so I was thinking of pulling it to see if resolved my issue. Unfortunately, I am not sure exactly how do this (other than the obvious). Here is what I attempted
1) via Add/Remove Programs I uninstalled all NVIDIA drivers
2) I plugged my monitor into the motherboard's on board Intel graphics.

Here are the issues/things I don't understand
a) When the NVIDIA drivers were Uninstalled the Sleep option disappeared. Without the Sleep option the whole thing is moot as my goal is to find out why I get BSODs immediately or very soon after returning from Sleep.
b) when I plugged my monitor into the motherboard the Bios start screen did not display. I read some documentation on the Gigabyte motherboard that has an option for "Initial Display". It is currently set to PCIe. I can move it to the internal Intel graphics but I was not sure.
c) when I rebooted (graphics card still in) , by magic the NVIDIA drivers reappear.

Sorry in advance if there are things here that I don't understand. I'm a bit new to all this.

Addictive Gamer · Apr 29, 2015

jerrythesurfer said:
Here are the issues/things I don't understand
a) When the NVIDIA drivers were Uninstalled the Sleep option disappeared. Without the Sleep option the whole thing is moot as my goal is to find out why I get BSODs immediately or very soon after returning from Sleep.
b) when I plugged my monitor into the motherboard the Bios start screen did not display. I read some documentation on the Gigabyte motherboard that has an option for "Initial Display". It is currently set to PCIe. I can move it to the internal Intel graphics but I was not sure.
c) when I rebooted (graphics card still in) , by magic the NVIDIA drivers reappear.

I would suggest to delete nvidia driver while using device manager option to uninstall driver.
there should be a check box in uninstall dialog offering you to "delete this driver from system"

after that reboot and see if it comes back, put pc to sleep and wake it up, so at least we would know if it's graphics driver or not.

edit:
there is also "NVIDIA Display Driver Service" try to disable that service and then put PC to sleep.
You can put PC to sleep by using power manager to schedule a sleep mode in advance:
Control Panel\Hardware and Sound\Power Options

jerrythesurfer · Apr 29, 2015

Recap and Another BSOD

To recap, the BSODs and Event Log errors occur randomly but it appears to happen only when Windows Sleep is enabled. The computer sleeps with out issue but when I it returns from sleep I sometimes get BSODs soon after and when I don't the Event Log sometimes shows Errors.

I just ran ChkDsk and Sfc and both returned with 0 problems or errors.

And I just got another BSOD, Log file attached.

I am getting very frustrated with this computer. I spent a lot of money purchase what I thought was a top-notch system.

I appreciate your help. Hopefully you can point me in the right directions

Addictive Gamer · Apr 30, 2015

You did not report results from my previous post, so we still didn't eliminate that option which does not help resolve the issue.
Are you able to put you PC to sleep after permanent NVIDIA driver removal as explained in edit of post #6 ?

Event log at the time of last system crash:

Code:

Event[5035]:  Log Name: System
  Source: Service Control Manager
  Date: 2015-04-29T20:42:50.933
  Event ID: 7026
  Task: N/A
  Level: Information
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Vybe-Apr102015
  Description: 
The following boot-start or system-start driver(s) did not load: 
dam

Event[5036]:
  Log Name: System
  Source: Microsoft-Windows-WER-SystemErrorReporting
  Date: 2015-04-29T20:42:51.000
  Event ID: 1001
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Vybe-Apr102015
  Description: 
The computer has rebooted from a bugcheck.  The bugcheck was: 0x00000024 (0x000000af000c092d, 0x000000000801a28b, 0x0000000200000000, 0x0000000200000000). A dump was saved in: C:\windows\MEMORY.DMP. [COLOR=#ff0000]Report Id: 042915-8875-01.[/COLOR]


Event[5037]:
  Log Name: System
  Source: Microsoft-Windows-Winlogon
  Date: 2015-04-29T20:42:56.703
  Event ID: 7001
  Task: N/A
  Level: Information
  Opcode: Info
  Keyword: N/A
  User: S-1-5-18
  User Name: NT AUTHORITY\SYSTEM
  Computer: Vybe-Apr102015
  Description: 
User Logon Notification for Customer Experience Improvement Program


Event[5038]:
  Log Name: System
  Source: User32
  Date: 2015-04-29T20:43:47.400
  Event ID: 1074
  Task: N/A
  Level: Information
  Opcode: N/A
  Keyword: Classic
  User: S-1-5-21-3896830975-3480266051-481357720-1001
  User Name: VYBE-APR102015\Jerry
  Computer: Vybe-Apr102015
  Description: 
The process C:\windows\Explorer.EXE (VYBE-APR102015) has initiated the restart of computer VYBE-APR102015 on behalf of user Vybe-Apr102015\Jerry for the following reason: Other (Unplanned)
 Reason Code: 0x0
 Shutdown Type: restart
 Comment:

Please open elevated command prompt and type line by line:

c:
cd \
powercfg /energy

wait for command to complete then go to C drive by using Windows explorer.
There you'll find HTML power report file which you need to zip and attach here.

Also please tell with what options and on what volumes/drives did you ran the chkdsk and sfc ?

Report Id: 042915-8875-01 ( see event log -> scroll right )

Code:

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


[B]NTFS_FILE_SYSTEM (24)[/B]
    If you see NtfsExceptionFilter on the stack then the 2nd and 3rd
    parameters are the exception record and context record. Do a .cxr
    on the 3rd parameter and then kb to obtain a more informative stack
    trace.
Arguments:
Arg1: 000000af000c092d
Arg2: 000000000801a28b
Arg3: 0000000200000000
Arg4: 0000000200000000


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




CUSTOMER_CRASH_COUNT:  1


DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT


BUGCHECK_STR:  0x24


PROCESS_NAME:  iexplore.exe


CURRENT_IRQL:  0


ANALYSIS_VERSION: 6.3.9600.17298 (debuggers(dbg).141024-1500) amd64fre


LAST_CONTROL_TRANSFER:  from fffff8010de90884 to fffff80259152ca0


STACK_TEXT:  
ffffd000`320b2528 fffff801`0de90884 : 00000000`00000024 000000af`000c092d 00000000`0801a28b 00000002`00000000 : nt!KeBugCheckEx
ffffd000`320b2530 fffff801`0de7789d : 00000000`00000000 00000000`00000000 00000080`1a28b000 ffffe001`f5019d50 : Ntfs!NtfsPagingFileIo+0x336d4
ffffd000`320b2640 fffff801`0da02b1e : ffffe001`f3a854c0 ffffe001`f50199b0 00000000`00000001 ffffe001`f5019d98 : Ntfs!NtfsFsdRead+0x3ad
ffffd000`320b26f0 fffff801`0da010c2 : ffffd000`320b27b0 ffffe001`f2b14920 ffffe001`f4da3e00 ffffe001`f50199b0 : fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x2ce
ffffd000`320b2790 fffff802`59069d1c : ffffe001`f4803fa0 ffffe001`f4da3d01 ffffd000`320b2a80 00000000`0000000c : fltmgr!FltpDispatch+0xb2
ffffd000`320b27f0 fffff802`59069aa0 : ffffe001`f4da3d30 ffffe001`f4da3d50 ffffe001`f4da3d90 ffffe001`f4da3d80 : nt!IoPageRead+0x234
ffffd000`320b2840 fffff802`59068991 : 00000000`00000002 ffffd000`320b28f0 ffffe001`f4da3d30 ffffd000`320b28f0 : nt!MiIssueHardFaultIO+0xc8
ffffd000`320b2880 fffff802`5905568a : ffffe001`f49e4d98 ffffe001`f4803880 00000000`00000000 fffff680`0009f1c0 : nt!MiIssueHardFault+0x135
ffffd000`320b2940 fffff802`5915cf2f : 00000000`00000000 00000000`00000fc0 00000000`7ecd6001 ffffe001`f70fd680 : nt!MmAccessFault+0x5ba
ffffd000`320b2b00 00000000`705e530b : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x12f
00000000`0524bf88 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x705e530b




STACK_COMMAND:  kb


FOLLOWUP_IP: 
Ntfs!NtfsPagingFileIo+336d4
fffff801`0de90884 cc              int     3


SYMBOL_STACK_INDEX:  1


SYMBOL_NAME:  Ntfs!NtfsPagingFileIo+336d4


FOLLOWUP_NAME:  MachineOwner


MODULE_NAME: Ntfs


IMAGE_NAME:  Ntfs.sys


DEBUG_FLR_IMAGE_TIMESTAMP:  54387b6b


IMAGE_VERSION:  6.3.9600.17399


BUCKET_ID_FUNC_OFFSET:  336d4


FAILURE_BUCKET_ID:  0x24_Ntfs!NtfsPagingFileIo


BUCKET_ID:  0x24_Ntfs!NtfsPagingFileIo


ANALYSIS_SOURCE:  KM


FAILURE_ID_HASH_STRING:  km:0x24_ntfs!ntfspagingfileio


FAILURE_ID_HASH:  {d671f571-ce88-c0f6-1555-417ad557fd4c}


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

jerrythesurfer · Apr 30, 2015

1) sfc /scannow found no errors. SFC only runs against the Windows OS files
2) chdksk was run on C:, D: and E: and no errors on any drive
3) having trouble using the tool provided on this website to attach the powercfg report
4) removed NVidia card and so far no BSODs and/or Event Log Errors

Perhaps it is the NVidia driver. I spoke with the Maingear (the computer manufacturer) and they said that this is not the first report they have heard from customers.

My idea is to roll-back to some of the earlier drivers to see if that helps. If it does not, I'm not sure what the next step is assuming I want to use the graphics card (less disable Sleep). Thoughts?

Addictive Gamer · Apr 30, 2015

Hi jerry,

Sorry but I didn't understand if you are able to put computer to sleep after nvidia driver removal, and scheduling sleep mode by going to:
Control Panel\Hardware and Sound\Power Options

To upload HTML file you need to zip the file first.

jerrythesurfer · Apr 30, 2015

My computer goes into Sleep mode just fine, whether done manually or by the sleep time, always has. The issue is the when I wake the computer (jiggle the mouse) I sometimes soon after get a BSOD and/or the Event Log shows Errors with the time exactly matching the "wake" time. When I disable Sleep I do not get BSODs or errors in the Event Log.

So far with the graphics card removed the computer has not generated any errors or BSODs upon waking. I think this points to a problem with the graphics card driver. I have the most recent driver. My thoughts are to try earlier driver versions. I don't know what else to do if I want to use the Windows Sleep feature.

Attached is the energy report however, I don't think it will reveal anything related to why the computer has problems waking with the graphic card/driver installed.

Addictive Gamer · Apr 30, 2015

Following is just a speculation and does not need to true,

Nvidia GTX 960 uses PCI Express 3

And energy-report reports an error:

Platform Power Management CapabilitiesCI Express Active-State Power Management (ASPM) Disabled
PCI Express Active-State Power Management (ASPM) has been disabled due to a known incompatibility with the hardware in this computer.

Not sure sure if the above error has to do anything with Nvidia card and drawing any conclusion without testing various drivers.
Preventing PC to go into sleep mode to see if that makes any change over some time is what I would do with latest Nvidia driver installed ( assuming driver is not guilty, because it was not caught in dumps )

Nvidia is a nice piece of hardware and I would not give up from testing just to ensure that driver is OK.

Addictive Gamer · Apr 30, 2015

Your BIOS seems to out of date, please keep in mind that failed BIOS update may result in machine being unusable.
So follow instructions, download manual and before all ensure you type correct model number into following website:

Hopefully an update could solve this:
GIGABYTE - Support

jerrythesurfer · Apr 30, 2015

May Have Isolated the Problem to NVidia Graphics Card

I see.

I did physically remove the graphics card and the Windows Sleep feature was present and is working. To recap the current state, my rig is running with Sleep enabled and without a graphics card installed. In this configuration it as of this moment not having any issues when waking up from Sleep, ie. no BSODs or Errors in the Event Log

Per you request I am including the energy report.

Please let me know if what I am reporting makes sense and is complete.

Best,

jerrythesurfer · Apr 30, 2015

Oops, sorry for my duplicate post. I didn't realize there was a page-2 here,

jerrythesurfer · Apr 30, 2015

I have run the rig for 1 week with Sleep disabled and there were zero (0) BSODs or Error in the Event Log.
I'm not sure what I'm reading with
Platform Power Management CapabilitiesCI Express Active-State Power Management (ASPM) Disabled
PCI Express Active-State Power Management (ASPM) has been disabled due to a known incompatibility with the hardware in this computer.
Does that point to the graphics card, and/or driver?

I can update my Bios. I'm not sure how but I will read up on it. There is a new NVidia driver as of 4/13/15. I was running the one dated 347.88 dated March 17, 2015

I'm running Bios F7 and there is an F8 but F8 says you can't go back once you install it. That's scary.

I do really appreciate your effort. I'd be stuck without your help

Addictive Gamer · Apr 30, 2015

Both reports look the same so obviously these errors have nothing to do with Nvidia.
And since you said BSOD's are gone on wake up, what I would to is to wait a day or 2 to see if this is not false positive, and then put the card back and test different drivers.

There is always a chance to find a beta drivers on Nvidia website

At this moment I'm out of ideas without new dumps.

Edit:
Yes download this one, it's probably beta driver and it could work

jerrythesurfer · May 2, 2015

I removed the NVidia card and removed all associated drivers. Sleep is an option and the computer goes into Sleep just fine as it always did. However, even with the card removed I continue to get occasional BSODs.

What now?

Addictive Gamer · May 2, 2015

Hi,
In your first post you said that manufacturer replaced most of the hardware and problem still persist, and that you run no additional software except Windows itself and drivers on your PC.
You also said you get new BSOD's, ( paste them all here, including system info )

Therefore we have 2 options:
1. enabling driver verifier against manufacturers drivers.
2. booting into safe mode and observing system behavior for a while.

Note: In worst case scenario driver verifier might prevent you from booting into system, so system restore point is recommended.
Creating bootable USB stick or DVD installation media.

jerrythesurfer · May 12, 2015

I'm back

To answer the above question, yes I was able to Sleep the computer after removal of the NVidia graphics card. However and unfortunately I still occasionally get BSODs. I also notice errors in the Event Log at the exact time when returning from Sleep. It seems that the computer is not happy about Sleep mode. When I disable Sleep the Event Log is free of Errors and no BSODs.

Not exactly sure where that leaves me. Can this somehow be BIOS related as in there are setting that need to be changed?

Thanks

Random BSOD on Brand New Computer Killng Me

New Member

My Computer

New Member

My Computer

New Member

My Computer

New Member

My Computer

New Member

My Computer

New Member

My Computer

New Member

My Computer

New Member

My Computer

New Member

My Computer

New Member

My Computer

New Member

My Computer

New Member

My Computer

New Member

My Computer

New Member

My Computer

New Member

My Computer

New Member

My Computer

New Member

My Computer

New Member

My Computer

New Member

My Computer

New Member

My Computer