BSOD - Custom Build Unstable - Unable to identify solution

[DavidG8]

I've built dozens of computers - all have been very stable - for years - until now.

I built the computer back in March / had to re-install in May and did a refresh in August. I've done a couple of restore point recoveries since then as well.

In September, the Logitech keyboard started experiences long typing delays but only in Chrome 32-bit. BSOD once or twice a week. I'm using 64-bit IE and Chrome and it appears to help bit. Seems like once I have multiple Chrome tabs open, the typing delay begins to increase.

In October, had to update Samsung EVO firmware due to SSD issue. Seems ok now, but after one of the more recent BSOD, a few personalization settings were changed. This issue seemed thermal related as I couldn't reboot the PC for 10 minutes. Temperatures are a bit high 125F - doesn't seem right, but re-attached CPU twice.

Also tried updating Catalyst drivers - first to 14.9 and then to beta (might have made things worse). Likely to go back to 14.9.1

When using my monitor and TV and computer goes to sleep, have to shut off TV to get control of main monitor.

I don't know if this is a Windows 8.1 Pro issue, drivers issue or a possible hardware issue or a combination of all three.

I'm very frustrated. Any help would be appreciated.

Thanks

 

[Arc]

I've built dozens of computers - all have been very stable - for years - until now.

So you must know about maintaining computers. I am not suggesting anything to you, just interpreting the crash dump. Hopefully that will be enough for you.

The crash dump (not me) blamse Panda Antivirus for the BSOD.

I should guess that you will be able to make your system stable back based on that info.
___________________________________________

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

Use !analyze -v to get detailed debugging information.

BugCheck 50, {ffffe000762af000, 0, fffff801cd832e04, 0}

*** WARNING: Unable to verify timestamp for NNSHttp.sys
*** ERROR: Module load completed but symbols could not be loaded for NNSHttp.sys

Could not read faulting driver name
Probably caused by : NNSHttp.sys ( NNSHttp+11e04 )

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

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

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced.  This cannot be protected by try-except,
it must be protected by a Probe.  Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: ffffe000762af000, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff801cd832e04, If non-zero, the instruction address which referenced the bad memory
    address.
Arg4: 0000000000000000, (reserved)

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


Could not read faulting driver name

DUMP_FILE_ATTRIBUTES: 0x8
  Kernel Generated Triage Dump

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff803ed177138
unable to get nt!MmNonPagedPoolStart
unable to get nt!MmSizeOfNonPagedPoolInBytes
 ffffe000762af000 

FAULTING_IP: 
NNSHttp+11e04
fffff801`cd832e04 42803c000d      cmp     byte ptr [rax+r8],0Dh

MM_INTERNAL_CODE:  0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

BUGCHECK_STR:  AV

PROCESS_NAME:  System

CURRENT_IRQL:  0

ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) amd64fre

TRAP_FRAME:  ffffd0006dc687c0 -- (.trap 0xffffd0006dc687c0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=00000000000019f3 rbx=0000000000000000 rcx=fffff801cd849480
rdx=ffffc00014c93000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff801cd832e04 rsp=ffffd0006dc68950 rbp=ffffe000762ad5fa
 r8=ffffe000762ad60d  r9=ffffd0006dc68a38 r10=0000000000000000
r11=ffffc00014c980e0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na po cy
NNSHttp+0x11e04:
fffff801`cd832e04 42803c000d      cmp     byte ptr [rax+r8],0Dh ds:ffffe000`762af000=??
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff803ecf9fab8 to fffff803ecf661a0

STACK_TEXT:  
ffffd000`6dc68568 fffff803`ecf9fab8 : 00000000`00000050 ffffe000`762af000 00000000`00000000 ffffd000`6dc687c0 : nt!KeBugCheckEx
ffffd000`6dc68570 fffff803`ece7be78 : 00000000`00000000 ffffe000`28c28900 ffffd000`6dc687c0 fffff803`ece9c36e : nt! ?? ::FNODOBFM::`string'+0x29408
ffffd000`6dc68610 fffff803`ecf7042f : ffffc000`14c93000 00000000`00000000 00000000`00000000 ffffd000`6dc687c0 : nt!MmAccessFault+0x758
ffffd000`6dc687c0 fffff801`cd832e04 : fffff801`cd844b90 fffff801`cd846148 fffff801`cd846148 fffff801`cd83b104 : nt!KiPageFault+0x12f
ffffd000`6dc68950 fffff801`cd844b90 : fffff801`cd846148 fffff801`cd846148 fffff801`cd83b104 fffff801`cd83b104 : NNSHttp+0x11e04
ffffd000`6dc68958 fffff801`cd846148 : fffff801`cd846148 fffff801`cd83b104 fffff801`cd83b104 00000000`0000000c : NNSHttp+0x23b90
ffffd000`6dc68960 fffff801`cd846148 : fffff801`cd83b104 fffff801`cd83b104 00000000`0000000c 00000000`00000000 : NNSHttp+0x25148
ffffd000`6dc68968 fffff801`cd83b104 : fffff801`cd83b104 00000000`0000000c 00000000`00000000 fffff801`cd83223c : NNSHttp+0x25148
ffffd000`6dc68970 fffff801`cd83b104 : 00000000`0000000c 00000000`00000000 fffff801`cd83223c fffff801`cd844b90 : NNSHttp+0x1a104
ffffd000`6dc68978 00000000`0000000c : 00000000`00000000 fffff801`cd83223c fffff801`cd844b90 ffffd000`6dc385d0 : NNSHttp+0x1a104
ffffd000`6dc68980 00000000`00000000 : fffff801`cd83223c fffff801`cd844b90 ffffd000`6dc385d0 ffffe000`2f33a1d0 : 0xc


STACK_COMMAND:  kb

FOLLOWUP_IP: 
NNSHttp+11e04
fffff801`cd832e04 42803c000d      cmp     byte ptr [rax+r8],0Dh

SYMBOL_STACK_INDEX:  4

SYMBOL_NAME:  NNSHttp+11e04

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: NNSHttp

IMAGE_NAME:  NNSHttp.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  53a16661

FAILURE_BUCKET_ID:  AV_NNSHttp+11e04

BUCKET_ID:  AV_NNSHttp+11e04

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:av_nnshttp+11e04

FAILURE_ID_HASH:  {da57e4e7-a991-9adb-bf86-d4efb8b474fa}

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

2: kd> lmvm NNSHttp
start             end                 module name
fffff801`cd821000 fffff801`cd84f000   NNSHttp  T (no symbols)           
    Loaded symbol image file: NNSHttp.sys
    Image path: NNSHttp.sys
    Image name: NNSHttp.sys
    Timestamp:        Wed Jun 18 15:43:53 2014 (53A16661)
    CheckSum:         00027A44
    ImageSize:        0002E000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

 

[DavidG8]

Thanks so much - I appreciate your time looking into this and your advice

 

[Arc]

Thanks so much - I appreciate your time looking into this and your advice

I havent advised you ... as you built lots of computers I assumed that you are able to guide yourself if the root of the issue is known. I just checked what the crash dump says, to get the root of the issue.

I think I should not treat you as a noob, you are not.

If any more assistance is needed about this issue, feel free to ask.