- Feb 20, 2015
- 2
- 0
- 4,510
Greetings everyone on Tom's Hardware. I have been constantly looking at this site for info, however now I must request more personal help. As the title suggest, I have begun to encounter multiple BSODS.
I am actually completely unsure of when everything went wrong. No new programs were installed, no hardware, no software--nothing seemed to be the cause. I have run memtest86+ for 24 hours in SMC mode in round robin, (because test 7 crashes or hard freezes, a common issue). I have run Intel's diagnostic tool for checking my processor, and for my graphics card, I have clean installed the newest driver. ■ I feel like the only thing it may be is the motherboard, but I want to leave it to more knowledgable people. In BlueScreenview, the bug check code is constantly either 0x50 or 0xfc.
If anything, it may still be the nvidia driver? Not sure.
I have run sfc /scannow, chkdsk, and ran windows update all to no avail. It seems that my system bluescreens only when I open like 3 tabs and one of which is a video or when I play a game; it is when the computer is very active. Additionally, no viruses seem to be on my computer as I have run a full scan with Kaspersky and a Malwarebytes.
As of now, everything appears stable. However, I am tempted to think that it is not after constant and endless BSODS.
My specs: Intel I5 3570k at stock with a stock cooler, EVGA GTX 980 Classified, the 3980k version. Windows 7 home premium, Asus pz77-v lk motherboard, and 8GB Corsair Vengeance 1866 memory (4x2). Additionally, I'm using the XMP profile..
Nothing is technically overclocked (XMP).
The dump files, (I'll put in more if requested): https://drive.google.com/file/d/0B4vhN0faonr2WDFCT1RVM2w1bjg/view
Using bluescrenview and other utilities, I see mostly ntoskrnl.exe ( nt+74ec0 and ntoskrnl.exe ( nt+76100 ) and other ntoskrnl.exe as the issues.
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\022015-245514-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.18717.amd64fre.win7sp1_gdr.150113-1808
Machine Name:
Kernel base = 0xfffff800`03860000 PsLoadedModuleList = 0xfffff800`03aa4890
Debug session time: Thu Feb 19 20:00:27.509 2015 (UTC - 6:00)
System Uptime: 0 days 0:16:55.306
Loading Kernel Symbols
...............................................................
................................................................
.........................................
Loading User Symbols
Loading unloaded module list
..................................................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck FC, {fffff8a004e3c897, a1200001a65c8943, fffff8800e5d0910, 2}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+44dfc )
Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY (fc)
An attempt was made to execute non-executable memory. The guilty driver
is on the stack trace (and is typically the current instruction pointer).
When possible, the guilty driver's name (Unicode string) is printed on
the bugcheck screen and saved in KiBugCheckDriver.
Arguments:
Arg1: fffff8a004e3c897, Virtual address for the attempted execute.
Arg2: a1200001a65c8943, PTE contents.
Arg3: fffff8800e5d0910, (reserved)
Arg4: 0000000000000002, (reserved)
Debugging Details:
------------------
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xFC
PROCESS_NAME: chrome.exe
CURRENT_IRQL: 0
TRAP_FRAME: fffff8800e5d0910 -- (.trap 0xfffff8800e5d0910)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000
rdx=fffffa8009aa1060 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8a004e3c897 rsp=fffff8800e5d0aa0 rbp=fffff8800e5d0b60
r8=0000000000000000 r9=0000000000000000 r10=fffff8800e5d0070
r11=fffffa8009aa1060 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na po nc
fffff8a0`04e3c897 0000 add byte ptr [rax],al ds:000f:00000000`00000000=??
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80003953b78 to fffff800038d4ec0
STACK_TEXT:
fffff880`0e5d07a8 fffff800`03953b78 : 00000000`000000fc fffff8a0`04e3c897 a1200001`a65c8943 fffff880`0e5d0910 : nt!KeBugCheckEx
fffff880`0e5d07b0 fffff800`038d2fee : 00000000`00000008 fffff8a0`04e3c897 00000000`00000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x44dfc
fffff880`0e5d0910 fffff8a0`04e3c897 : 00000000`00000000 00000000`0033e930 00000000`00000000 ffffffff`fff5c6d0 : nt!KiPageFault+0x16e
fffff880`0e5d0aa0 00000000`00000000 : 00000000`0033e930 00000000`00000000 ffffffff`fff5c6d0 00000000`0033fd20 : 0xfffff8a0`04e3c897
STACK_COMMAND: kb
FOLLOWUP_IP:
nt! ?? ::FNODOBFM::`string'+44dfc
fffff800`03953b78 cc int 3
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: nt! ?? ::FNODOBFM::`string'+44dfc
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 54b5f6ff
FAILURE_BUCKET_ID: X64_0xFC_nt!_??_::FNODOBFM::_string_+44dfc
BUCKET_ID: X64_0xFC_nt!_??_::FNODOBFM::_string_+44dfc
Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY (fc)
An attempt was made to execute non-executable memory. The guilty driver
is on the stack trace (and is typically the current instruction pointer).
When possible, the guilty driver's name (Unicode string) is printed on
the bugcheck screen and saved in KiBugCheckDriver.
Arguments:
Arg1: fffff8a004e3c897, Virtual address for the attempted execute.
Arg2: a1200001a65c8943, PTE contents.
Arg3: fffff8800e5d0910, (reserved)
Arg4: 0000000000000002, (reserved)
Debugging Details:
------------------
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xFC
PROCESS_NAME: chrome.exe
CURRENT_IRQL: 0
TRAP_FRAME: fffff8800e5d0910 -- (.trap 0xfffff8800e5d0910)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000
rdx=fffffa8009aa1060 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8a004e3c897 rsp=fffff8800e5d0aa0 rbp=fffff8800e5d0b60
r8=0000000000000000 r9=0000000000000000 r10=fffff8800e5d0070
r11=fffffa8009aa1060 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na po nc
fffff8a0`04e3c897 0000 add byte ptr [rax],al ds:000f:00000000`00000000=??
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80003953b78 to fffff800038d4ec0
STACK_TEXT:
fffff880`0e5d07a8 fffff800`03953b78 : 00000000`000000fc fffff8a0`04e3c897 a1200001`a65c8943 fffff880`0e5d0910 : nt!KeBugCheckEx
fffff880`0e5d07b0 fffff800`038d2fee : 00000000`00000008 fffff8a0`04e3c897 00000000`00000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x44dfc
fffff880`0e5d0910 fffff8a0`04e3c897 : 00000000`00000000 00000000`0033e930 00000000`00000000 ffffffff`fff5c6d0 : nt!KiPageFault+0x16e
fffff880`0e5d0aa0 00000000`00000000 : 00000000`0033e930 00000000`00000000 ffffffff`fff5c6d0 00000000`0033fd20 : 0xfffff8a0`04e3c897
STACK_COMMAND: kb
FOLLOWUP_IP:
nt! ?? ::FNODOBFM::`string'+44dfc
fffff800`03953b78 cc int 3
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: nt! ?? ::FNODOBFM::`string'+44dfc
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 54b5f6ff
FAILURE_BUCKET_ID: X64_0xFC_nt!_??_::FNODOBFM::_string_+44dfc
BUCKET_ID: X64_0xFC_nt!_??_::FNODOBFM::_string_+44dfc
Followup: MachineOwner
---------
I am actually completely unsure of when everything went wrong. No new programs were installed, no hardware, no software--nothing seemed to be the cause. I have run memtest86+ for 24 hours in SMC mode in round robin, (because test 7 crashes or hard freezes, a common issue). I have run Intel's diagnostic tool for checking my processor, and for my graphics card, I have clean installed the newest driver. ■ I feel like the only thing it may be is the motherboard, but I want to leave it to more knowledgable people. In BlueScreenview, the bug check code is constantly either 0x50 or 0xfc.
If anything, it may still be the nvidia driver? Not sure.
I have run sfc /scannow, chkdsk, and ran windows update all to no avail. It seems that my system bluescreens only when I open like 3 tabs and one of which is a video or when I play a game; it is when the computer is very active. Additionally, no viruses seem to be on my computer as I have run a full scan with Kaspersky and a Malwarebytes.
As of now, everything appears stable. However, I am tempted to think that it is not after constant and endless BSODS.
My specs: Intel I5 3570k at stock with a stock cooler, EVGA GTX 980 Classified, the 3980k version. Windows 7 home premium, Asus pz77-v lk motherboard, and 8GB Corsair Vengeance 1866 memory (4x2). Additionally, I'm using the XMP profile..
Nothing is technically overclocked (XMP).
The dump files, (I'll put in more if requested): https://drive.google.com/file/d/0B4vhN0faonr2WDFCT1RVM2w1bjg/view
Using bluescrenview and other utilities, I see mostly ntoskrnl.exe ( nt+74ec0 and ntoskrnl.exe ( nt+76100 ) and other ntoskrnl.exe as the issues.
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\022015-245514-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.18717.amd64fre.win7sp1_gdr.150113-1808
Machine Name:
Kernel base = 0xfffff800`03860000 PsLoadedModuleList = 0xfffff800`03aa4890
Debug session time: Thu Feb 19 20:00:27.509 2015 (UTC - 6:00)
System Uptime: 0 days 0:16:55.306
Loading Kernel Symbols
...............................................................
................................................................
.........................................
Loading User Symbols
Loading unloaded module list
..................................................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck FC, {fffff8a004e3c897, a1200001a65c8943, fffff8800e5d0910, 2}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+44dfc )
Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY (fc)
An attempt was made to execute non-executable memory. The guilty driver
is on the stack trace (and is typically the current instruction pointer).
When possible, the guilty driver's name (Unicode string) is printed on
the bugcheck screen and saved in KiBugCheckDriver.
Arguments:
Arg1: fffff8a004e3c897, Virtual address for the attempted execute.
Arg2: a1200001a65c8943, PTE contents.
Arg3: fffff8800e5d0910, (reserved)
Arg4: 0000000000000002, (reserved)
Debugging Details:
------------------
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xFC
PROCESS_NAME: chrome.exe
CURRENT_IRQL: 0
TRAP_FRAME: fffff8800e5d0910 -- (.trap 0xfffff8800e5d0910)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000
rdx=fffffa8009aa1060 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8a004e3c897 rsp=fffff8800e5d0aa0 rbp=fffff8800e5d0b60
r8=0000000000000000 r9=0000000000000000 r10=fffff8800e5d0070
r11=fffffa8009aa1060 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na po nc
fffff8a0`04e3c897 0000 add byte ptr [rax],al ds:000f:00000000`00000000=??
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80003953b78 to fffff800038d4ec0
STACK_TEXT:
fffff880`0e5d07a8 fffff800`03953b78 : 00000000`000000fc fffff8a0`04e3c897 a1200001`a65c8943 fffff880`0e5d0910 : nt!KeBugCheckEx
fffff880`0e5d07b0 fffff800`038d2fee : 00000000`00000008 fffff8a0`04e3c897 00000000`00000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x44dfc
fffff880`0e5d0910 fffff8a0`04e3c897 : 00000000`00000000 00000000`0033e930 00000000`00000000 ffffffff`fff5c6d0 : nt!KiPageFault+0x16e
fffff880`0e5d0aa0 00000000`00000000 : 00000000`0033e930 00000000`00000000 ffffffff`fff5c6d0 00000000`0033fd20 : 0xfffff8a0`04e3c897
STACK_COMMAND: kb
FOLLOWUP_IP:
nt! ?? ::FNODOBFM::`string'+44dfc
fffff800`03953b78 cc int 3
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: nt! ?? ::FNODOBFM::`string'+44dfc
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 54b5f6ff
FAILURE_BUCKET_ID: X64_0xFC_nt!_??_::FNODOBFM::_string_+44dfc
BUCKET_ID: X64_0xFC_nt!_??_::FNODOBFM::_string_+44dfc
Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY (fc)
An attempt was made to execute non-executable memory. The guilty driver
is on the stack trace (and is typically the current instruction pointer).
When possible, the guilty driver's name (Unicode string) is printed on
the bugcheck screen and saved in KiBugCheckDriver.
Arguments:
Arg1: fffff8a004e3c897, Virtual address for the attempted execute.
Arg2: a1200001a65c8943, PTE contents.
Arg3: fffff8800e5d0910, (reserved)
Arg4: 0000000000000002, (reserved)
Debugging Details:
------------------
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xFC
PROCESS_NAME: chrome.exe
CURRENT_IRQL: 0
TRAP_FRAME: fffff8800e5d0910 -- (.trap 0xfffff8800e5d0910)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000
rdx=fffffa8009aa1060 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8a004e3c897 rsp=fffff8800e5d0aa0 rbp=fffff8800e5d0b60
r8=0000000000000000 r9=0000000000000000 r10=fffff8800e5d0070
r11=fffffa8009aa1060 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na po nc
fffff8a0`04e3c897 0000 add byte ptr [rax],al ds:000f:00000000`00000000=??
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80003953b78 to fffff800038d4ec0
STACK_TEXT:
fffff880`0e5d07a8 fffff800`03953b78 : 00000000`000000fc fffff8a0`04e3c897 a1200001`a65c8943 fffff880`0e5d0910 : nt!KeBugCheckEx
fffff880`0e5d07b0 fffff800`038d2fee : 00000000`00000008 fffff8a0`04e3c897 00000000`00000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x44dfc
fffff880`0e5d0910 fffff8a0`04e3c897 : 00000000`00000000 00000000`0033e930 00000000`00000000 ffffffff`fff5c6d0 : nt!KiPageFault+0x16e
fffff880`0e5d0aa0 00000000`00000000 : 00000000`0033e930 00000000`00000000 ffffffff`fff5c6d0 00000000`0033fd20 : 0xfffff8a0`04e3c897
STACK_COMMAND: kb
FOLLOWUP_IP:
nt! ?? ::FNODOBFM::`string'+44dfc
fffff800`03953b78 cc int 3
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: nt! ?? ::FNODOBFM::`string'+44dfc
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 54b5f6ff
FAILURE_BUCKET_ID: X64_0xFC_nt!_??_::FNODOBFM::_string_+44dfc
BUCKET_ID: X64_0xFC_nt!_??_::FNODOBFM::_string_+44dfc
Followup: MachineOwner
---------
Facebook
Twitter
Instagram