Strange BSOD pattern every week or so.

mwa2784 · 12 Mar 2015

Hi everybody

First time posting because I got a peculiar problem in my hands and don't really know what to do anymore.
Hopefully some of you here can help me solve this issue.

Ill try to explain this as well as i can:

Very randon bsod. Can happen during a game or while in the internet.

I get the bdos (which i hope you can see in the attachment), computer shuts downs and that's it.

I started up again and my screens are just black. Here's where it gets interesting for me ....

I'll start up my computer multiple times. Sometimes i can hear my hard drive starting (from the spinning sound) and sometimes it doesn't. Either way, the screens are black.

I literally have to sit there 30 minutes waiting and it just magically fixes itself like nothing had happened and it works fine for 5-7 days.

Same thing happened tonight but after the bsod, i saw this message : Bootmgr image is corrupt. The System cannot boot.

Another interesting thing is i tried testing my ram by taking one out and putting the other and botting etc...

I take one ram out.. my computer beeps.
I put back the ram and take out the beeping one... it beeps again.
I simply switch their places in the slots and again it beeps.
I put them back as they are originally... no beeping.

It's like they bound to that slot!

Worth noting they only work in the 2-4 slots .. not in the 1-3 slots.. computer just beeps if i do that.

I build this pc myself around 5 years ago maybe. It was my pride and joy and I understand i might be having to let her go...

Is there anyway I can save her for a little longer?

Any help will be highly appreciated!

Aris

koolkat77 · 13 Mar 2015

Welcome to the forum.

The dump doesn't provide much details. However it does look like it happened in the process running NVstream. How often do you use the software?

Code:

Microsoft (R) Windows Debugger Version 6.3.9600.16384 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\YUSRA\Downloads\Compressed\ARIS-PC-Thu_03_12_2015_230720_67\031215-29359-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available


************* Symbol Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.18741.amd64fre.win7sp1_gdr.150202-1526
Machine Name:
Kernel base = 0xfffff800`02c11000 PsLoadedModuleList = 0xfffff800`02e55890
Debug session time: Fri Mar 13 02:17:06.267 2015 (UTC + 6:00)
System Uptime: 0 days 4:28:17.204
Loading Kernel Symbols
.

Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.

..............................................................
................................................................
..........................
Loading User Symbols
Loading unloaded module list
...........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {fffff80012c8869a, 2, 8, fffff80012c8869a}

Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+260 )

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

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

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: fffff80012c8869a, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000008, value 0 = read operation, 1 = write operation
Arg4: fffff80012c8869a, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002ebf100
GetUlongFromAddress: unable to read from fffff80002ebf1c0
 fffff80012c8869a Nonpaged pool

CURRENT_IRQL:  2

FAULTING_IP: 
+3d2d2a0
fffff800`12c8869a ??              ???

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0xD1

PROCESS_NAME:  nvstreamsvc.ex

ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre

TRAP_FRAME:  fffff8800af067b0 -- (.trap 0xfffff8800af067b0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=000007fffff90000 rbx=0000000000000000 rcx=00000000c0000102
rdx=00000000000007ff rsi=0000000000000000 rdi=0000000000000000
rip=fffff80012c8869a rsp=fffff8800af06940 rbp=fffffa80086b7060
 r8=fffffa80095630e8  r9=0000000000000000 r10=ffffffffffffffef
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe nc
fffff800`12c8869a ??              ???
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002c85469 to fffff80002c85ec0

FAILED_INSTRUCTION_ADDRESS: 
+3d2d2a0
fffff800`12c8869a ??              ???

STACK_TEXT:  
fffff880`0af06668 fffff800`02c85469 : 00000000`0000000a fffff800`12c8869a 00000000`00000002 00000000`00000008 : nt!KeBugCheckEx
fffff880`0af06670 fffff800`02c840e0 : 00000000`00000000 fffffa80`086b7100 00000000`00000008 fffff880`009b2180 : nt!KiBugCheckDispatch+0x69
fffff880`0af067b0 fffff800`12c8869a : 00000000`00000000 ffffffff`fffffffe 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x260
fffff880`0af06940 00000000`00000000 : ffffffff`fffffffe 00000000`00000000 00000000`00000000 00000000`00000000 : 0xfffff800`12c8869a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!KiPageFault+260
fffff800`02c840e0 440f20c0        mov     rax,cr8

SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  nt!KiPageFault+260

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  54d0317d

IMAGE_VERSION:  6.1.7601.18741

FAILURE_BUCKET_ID:  X64_0xD1_CODE_AV_BAD_IP_nt!KiPageFault+260

BUCKET_ID:  X64_0xD1_CODE_AV_BAD_IP_nt!KiPageFault+260

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_0xd1_code_av_bad_ip_nt!kipagefault+260

FAILURE_ID_HASH:  {6bd5d5ae-0d5f-a868-e768-b885477b4a76}

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

Have you check for an update on the BIOS?

Code:

BIOS Version/Date	Intel Corp. KGIBX10J.86A.5936.2011.0630.2250, 6/30/2011

mwa2784 · 13 Mar 2015

Hi

Thank you for your reply

I just searched now what Nvstream is. I never use it. Didn't even know i had it ! Getting rid of it could be the source right ? I assume it's a simple unistall from control panel.

Never really ever found out or read on how to update a BIOS .... Will look it up unless you can provide some guid lines on how to do it.

Looking forward to hearing from you soon.

Aris

koolkat77 · 13 Mar 2015

Google :)

And you can check this link: https://downloadcenter.intel.com/dow...-KGIBX10J-86A-

mwa2784 · 13 Mar 2015

I tried updating form the link you provided and it said that it was the same version as mine.

I also went to nvidia experience >preference> and disabled nvstream from there. Is there anything else that dump file says i need to do ?

Could that simple nvstream be the cause of beeping ram and all that stuff i described ?

I've had nvidia gfx cards on this system since the beginning.

koolkat77 · 13 Mar 2015

Driver Verifier runs in the background, "testing" drivers for bugs. If it finds one, a Blue Screen of Death (BSOD) will result; the corresponding dump file will hopefully show the faulty driver.

Driver Verifier

Simply follow the instructions on tutorial:

Driver Verifier - Enable and Disable

mwa2784 · 13 Mar 2015

Disable verifier.. got it

Thanks a million... hopefully i don't have to throw this one away yet:)