Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

Computer rebooting randomly.


  • Please log in to reply
5 replies to this topic

#1 Scarlet_Erza

Scarlet_Erza

  • Members
  • 4 posts
  • OFFLINE
  •  
  • Local time:02:22 AM

Posted 03 November 2016 - 11:37 AM

Hello everyone.

I've recently started experiencing random reboots and crashes without getting any BSOD on my windows 10.

In Feb 2016, I've installed a Nvidia 980TI in my pc, and all seemed well back then. Later on in June I've decided to upgrade my CPU, Motherboard and RAMs. and although all seemed fine for the first month, things started going downhill of late.

So the problem is that the computer randomly turns off for a brief second, followed by an automatic boot-up. This happens mostly when gaming (not really very graphic intensive games either - I've played Heavy graphic demanding games like WItcher 3 for 200 hours + and not a single crash).

I did a memory test, and I got no problems. so the Problem is now between the Mother board, the Graphic card, the CPU or the PSU.

The CPU is the least suspicious, it's a I7 6700K skylake 4.00ghz. and I've never had issues with it even though I use some CPU demanding softwares. but still, I wouldn't remove it from the list of suspects. (The CPU is supported by a coolermaster fan, have a NOCTUA D14 that I'll install whenever I change my computer case) but the temp on the CPU seems fine

The PSU. a 750 Corsair, about 3 year old. I'm suspecting that this is the main culprit, even though I have 0 proof. But maybe it's slowly dying?

The Motherboard - 
GIGABYTE G1 Gaming GA-Z170X-Gaming 7 -
 I can't say for sure if I'm really happy with my motherboard. has it's share of audio issues and 2 of the RAM slots seem to be dead. 

The GPU, EVGA 980TI - been running solid till the recent upgrade in my system. Still, no signs of overheat or visual distortions while gaming (usually weird lines / textures during gaming).

And at last, could it be the OS itself? 

I've checked the Event logs, and the only critical error I see is a Kernel power failure which doesn't help me much. (i can't read logs).

Is there anyway anyone can help me find a way to pinpoint the issue. I'd greatly appreciate it

 


Edited by Scarlet_Erza, 03 November 2016 - 11:40 AM.


BC AdBot (Login to Remove)

 


#2 hamluis

hamluis

    Moderator


  • Moderator
  • 55,896 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Killeen, TX
  • Local time:01:22 AM

Posted 03 November 2016 - 12:07 PM

How to receive help diagnosing Blue Screens and Windows crashes - http://www.bleepingcomputer.com/forums/topic176011.html

 

Louis



#3 Scarlet_Erza

Scarlet_Erza
  • Topic Starter

  • Members
  • 4 posts
  • OFFLINE
  •  
  • Local time:02:22 AM

Posted 03 November 2016 - 07:00 PM

Thx Louis for the help.

I've taken the steps, I wonder if you can help me here.
 

 
Microsoft ® Windows Debugger Version 10.0.14321.1024 AMD64
Copyright © Microsoft Corporation. All rights reserved.
 
 
Loading Dump File [O:\Windows\MEMORY.DMP]
Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available.
 
 
************* Symbol Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       SRV*o:\symbols*http://msdl.microsoft.com/download/symbols
Symbol search path is: SRV*o:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 10 Kernel Version 10240 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 10240.16644.amd64fre.th1.160104-1507
Machine Name:
Kernel base = 0xfffff802`e827c000 PsLoadedModuleList = 0xfffff802`e85a1070
Debug session time: Thu Feb 11 19:24:25.144 2016 (UTC - 4:00)
System Uptime: 1 days 23:52:10.122
Loading Kernel Symbols
...............................................................
................................................................
.........................................
Loading User Symbols
PEB is paged out (Peb.Ldr = 00007ff7`9336d018).  Type ".hh dbgerr001" for details
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
 
Use !analyze -v to get detailed debugging information.
 
BugCheck 3B, {c0000005, fffff80194c2c5d4, ffffd000223a1970, 0}
 
Probably caused by : NTFS.sys ( NTFS!NtfsTeardownStructures+124 )
 
Followup:     MachineOwner
---------
 
3: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
 
SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff80194c2c5d4, Address of the instruction which caused the bugcheck
Arg3: ffffd000223a1970, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.
 
Debugging Details:
------------------
 
 
DUMP_CLASS: 1
 
DUMP_QUALIFIER: 401
 
BUILD_VERSION_STRING:  10240.16644.amd64fre.th1.160104-1507
 
SYSTEM_MANUFACTURER:  To be filled by O.E.M.
 
SYSTEM_PRODUCT_NAME:  To be filled by O.E.M.
 
SYSTEM_SKU:  To be filled by O.E.M.
 
SYSTEM_VERSION:  To be filled by O.E.M.
 
BIOS_VENDOR:  American Megatrends Inc.
 
BIOS_VERSION:  1208
 
BIOS_DATE:  04/18/2012
 
BASEBOARD_MANUFACTURER:  ASUSTeK COMPUTER INC.
 
BASEBOARD_PRODUCT:  M5A97
 
BASEBOARD_VERSION:  Rev 1.xx
 
DUMP_TYPE:  1
 
BUGCHECK_P1: c0000005
 
BUGCHECK_P2: fffff80194c2c5d4
 
BUGCHECK_P3: ffffd000223a1970
 
BUGCHECK_P4: 0
 
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s.
 
FAULTING_IP: 
NTFS!NtfsTeardownStructures+124
fffff801`94c2c5d4 418b49d4        mov     ecx,dword ptr [r9-2Ch]
 
CONTEXT:  ffffd000223a1970 -- (.cxr 0xffffd000223a1970)
rax=0000000000000000 rbx=ffffc00192fbd010 rcx=ffffe0005e815a00
rdx=0000000000000004 rsi=ffffd000223a23d2 rdi=0000000000000000
rip=fffff80194c2c5d4 rsp=ffffd000223a2390 rbp=0000000000000000
 r8=ffffe000643b8da8  r9=fdffc00192fbd518 r10=7fffe000643b8da8
r11=7ffffffffffffffc r12=0000000000000000 r13=0000000000000000
r14=ffffe00066182018 r15=ffffc00192fbd038
iopl=0         nv up ei pl zr na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010246
NTFS!NtfsTeardownStructures+0x124:
fffff801`94c2c5d4 418b49d4        mov     ecx,dword ptr [r9-2Ch] ds:002b:fdffc001`92fbd4ec=????????
Resetting default scope
 
CPU_COUNT: 8
 
CPU_MHZ: e1c
 
CPU_VENDOR:  AuthenticAMD
 
CPU_FAMILY: 15
 
CPU_MODEL: 1
 
CPU_STEPPING: 2
 
DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
 
BUGCHECK_STR:  0x3B
 
PROCESS_NAME:  svchost.exe
 
CURRENT_IRQL:  0
 
ANALYSIS_SESSION_HOST:  SCARLET-PC
 
ANALYSIS_SESSION_TIME:  11-03-2016 19:39:06.0650
 
ANALYSIS_VERSION: 10.0.14321.1024 amd64fre
 
LAST_CONTROL_TRANSFER:  from fffff80194bfcb11 to fffff80194c2c5d4
 
STACK_TEXT:  
ffffd000`223a2390 fffff801`94bfcb11 : ffffe000`66182018 ffffe000`5e8153e8 00000000`00000000 ffffc001`92fbd010 : NTFS!NtfsTeardownStructures+0x124
ffffd000`223a2410 fffff801`94bfc238 : ffffe000`66182018 ffffe000`5e815180 ffffc001`92fbd010 00000000`00000001 : NTFS!NtfsIterateMft+0x221
ffffd000`223a24a0 fffff801`94c39129 : ffffe000`66182018 ffffe000`63be4bd0 ffffe000`00000000 ffffd000`00000000 : NTFS!NtfsQueryFileLayout+0x238
ffffd000`223a25f0 fffff801`94c3896c : ffffe000`66182018 ffffe000`63be4bd0 ffffe000`63be4bd0 00000000`00000000 : NTFS!NtfsUserFsRequest+0x549
ffffd000`223a2660 fffff801`943f51c4 : ffffe000`606818b0 ffffd000`223a2820 ffffe000`63be4bd0 ffffe000`63be4f70 : NTFS!NtfsFsdFileSystemControl+0x11c
ffffd000`223a2770 fffff801`94422d55 : ffffe000`60838d80 fffff802`e86b0065 00000000`00000001 ffffe000`607ed600 : FLTMGR!FltpLegacyProcessingAfterPreCallbacksCompleted+0x2a4
ffffd000`223a27f0 fffff802`e86ba6b3 : 00000000`00000001 ffffd000`223a2b80 ffffe000`6533dc60 fffff680`07065960 : FLTMGR!FltpFsControl+0x115
ffffd000`223a2850 fffff802`e86e06ca : 00001000`655de000 ffffe000`65745840 00000000`00000000 00000000`00000000 : nt!IopXxxControlFile+0x1253
ffffd000`223a2a20 fffff802`e83d5b63 : fffff6fb`40038328 fffff680`07065960 ffff2840`2e5073c6 fffff802`e86b6eac : nt!NtFsControlFile+0x56
ffffd000`223a2a90 00007fff`6925390a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
0000000e`09a4df58 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007fff`6925390a
 
 
THREAD_SHA1_HASH_MOD_FUNC:  84048fcc038d4f1e3207a82fda0ebc3e4353c289
 
THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  a635df9418d7563edb17901663ae66de7dc9a847
 
THREAD_SHA1_HASH_MOD:  a2b17c3e723296023a9c75426e293534c1a5aaf5
 
FOLLOWUP_IP: 
NTFS!NtfsTeardownStructures+124
fffff801`94c2c5d4 418b49d4        mov     ecx,dword ptr [r9-2Ch]
 
FAULT_INSTR_CODE:  d4498b41
 
SYMBOL_STACK_INDEX:  0
 
SYMBOL_NAME:  NTFS!NtfsTeardownStructures+124
 
FOLLOWUP_NAME:  MachineOwner
 
MODULE_NAME: NTFS
 
IMAGE_NAME:  NTFS.sys
 
DEBUG_FLR_IMAGE_TIMESTAMP:  565d37b4
 
IMAGE_VERSION:  10.0.10240.16601
 
STACK_COMMAND:  .cxr 0xffffd000223a1970 ; kb
 
BUCKET_ID_FUNC_OFFSET:  124
 
FAILURE_BUCKET_ID:  0x3B_NTFS!NtfsTeardownStructures
 
BUCKET_ID:  0x3B_NTFS!NtfsTeardownStructures
 
PRIMARY_PROBLEM_CLASS:  0x3B_NTFS!NtfsTeardownStructures
 
TARGET_TIME:  2016-02-11T23:24:25.000Z
 
OSBUILD:  10240
 
OSSERVICEPACK:  0
 
SERVICEPACK_NUMBER: 0
 
OS_REVISION: 0
 
SUITE_MASK:  272
 
PRODUCT_TYPE:  1
 
OSPLATFORM_TYPE:  x64
 
OSNAME:  Windows 10
 
OSEDITION:  Windows 10 WinNt TerminalServer SingleUserTS
 
OS_LOCALE:  
 
USER_LCID:  0
 
OSBUILD_TIMESTAMP:  2016-01-04 21:09:59
 
BUILDDATESTAMP_STR:  160104-1507
 
BUILDLAB_STR:  th1
 
BUILDOSVER_STR:  10.0.10240.16644.amd64fre.th1.160104-1507
 
ANALYSIS_SESSION_ELAPSED_TIME: 4e51
 
ANALYSIS_SOURCE:  KM
 
FAILURE_ID_HASH_STRING:  km:0x3b_ntfs!ntfsteardownstructures
 
FAILURE_ID_HASH:  {342dfdb4-0b0c-21d4-d913-f9307bf323df}
 
Followup:     MachineOwner
---------
 
3: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
 
SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff80194c2c5d4, Address of the instruction which caused the bugcheck
Arg3: ffffd000223a1970, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.
 
Debugging Details:
------------------
 
 
DUMP_CLASS: 1
 
DUMP_QUALIFIER: 401
 
BUILD_VERSION_STRING:  10240.16644.amd64fre.th1.160104-1507
 
SYSTEM_MANUFACTURER:  To be filled by O.E.M.
 
SYSTEM_PRODUCT_NAME:  To be filled by O.E.M.
 
SYSTEM_SKU:  To be filled by O.E.M.
 
SYSTEM_VERSION:  To be filled by O.E.M.
 
BIOS_VENDOR:  American Megatrends Inc.
 
BIOS_VERSION:  1208
 
BIOS_DATE:  04/18/2012
 
BASEBOARD_MANUFACTURER:  ASUSTeK COMPUTER INC.
 
BASEBOARD_PRODUCT:  M5A97
 
BASEBOARD_VERSION:  Rev 1.xx
 
DUMP_TYPE:  1
 
BUGCHECK_P1: c0000005
 
BUGCHECK_P2: fffff80194c2c5d4
 
BUGCHECK_P3: ffffd000223a1970
 
BUGCHECK_P4: 0
 
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s.
 
FAULTING_IP: 
NTFS!NtfsTeardownStructures+124
fffff801`94c2c5d4 418b49d4        mov     ecx,dword ptr [r9-2Ch]
 
CONTEXT:  ffffd000223a1970 -- (.cxr 0xffffd000223a1970)
rax=0000000000000000 rbx=ffffc00192fbd010 rcx=ffffe0005e815a00
rdx=0000000000000004 rsi=ffffd000223a23d2 rdi=0000000000000000
rip=fffff80194c2c5d4 rsp=ffffd000223a2390 rbp=0000000000000000
 r8=ffffe000643b8da8  r9=fdffc00192fbd518 r10=7fffe000643b8da8
r11=7ffffffffffffffc r12=0000000000000000 r13=0000000000000000
r14=ffffe00066182018 r15=ffffc00192fbd038
iopl=0         nv up ei pl zr na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010246
NTFS!NtfsTeardownStructures+0x124:
fffff801`94c2c5d4 418b49d4        mov     ecx,dword ptr [r9-2Ch] ds:002b:fdffc001`92fbd4ec=????????
Resetting default scope
 
CPU_COUNT: 8
 
CPU_MHZ: e1c
 
CPU_VENDOR:  AuthenticAMD
 
CPU_FAMILY: 15
 
CPU_MODEL: 1
 
CPU_STEPPING: 2
 
DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
 
BUGCHECK_STR:  0x3B
 
PROCESS_NAME:  svchost.exe
 
CURRENT_IRQL:  0
 
ANALYSIS_SESSION_HOST:  SCARLET-PC
 
ANALYSIS_SESSION_TIME:  11-03-2016 19:39:26.0705
 
ANALYSIS_VERSION: 10.0.14321.1024 amd64fre
 
LAST_CONTROL_TRANSFER:  from fffff80194bfcb11 to fffff80194c2c5d4
 
STACK_TEXT:  
ffffd000`223a2390 fffff801`94bfcb11 : ffffe000`66182018 ffffe000`5e8153e8 00000000`00000000 ffffc001`92fbd010 : NTFS!NtfsTeardownStructures+0x124
ffffd000`223a2410 fffff801`94bfc238 : ffffe000`66182018 ffffe000`5e815180 ffffc001`92fbd010 00000000`00000001 : NTFS!NtfsIterateMft+0x221
ffffd000`223a24a0 fffff801`94c39129 : ffffe000`66182018 ffffe000`63be4bd0 ffffe000`00000000 ffffd000`00000000 : NTFS!NtfsQueryFileLayout+0x238
ffffd000`223a25f0 fffff801`94c3896c : ffffe000`66182018 ffffe000`63be4bd0 ffffe000`63be4bd0 00000000`00000000 : NTFS!NtfsUserFsRequest+0x549
ffffd000`223a2660 fffff801`943f51c4 : ffffe000`606818b0 ffffd000`223a2820 ffffe000`63be4bd0 ffffe000`63be4f70 : NTFS!NtfsFsdFileSystemControl+0x11c
ffffd000`223a2770 fffff801`94422d55 : ffffe000`60838d80 fffff802`e86b0065 00000000`00000001 ffffe000`607ed600 : FLTMGR!FltpLegacyProcessingAfterPreCallbacksCompleted+0x2a4
ffffd000`223a27f0 fffff802`e86ba6b3 : 00000000`00000001 ffffd000`223a2b80 ffffe000`6533dc60 fffff680`07065960 : FLTMGR!FltpFsControl+0x115
ffffd000`223a2850 fffff802`e86e06ca : 00001000`655de000 ffffe000`65745840 00000000`00000000 00000000`00000000 : nt!IopXxxControlFile+0x1253
ffffd000`223a2a20 fffff802`e83d5b63 : fffff6fb`40038328 fffff680`07065960 ffff2840`2e5073c6 fffff802`e86b6eac : nt!NtFsControlFile+0x56
ffffd000`223a2a90 00007fff`6925390a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
0000000e`09a4df58 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007fff`6925390a
 
 
THREAD_SHA1_HASH_MOD_FUNC:  84048fcc038d4f1e3207a82fda0ebc3e4353c289
 
THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  a635df9418d7563edb17901663ae66de7dc9a847
 
THREAD_SHA1_HASH_MOD:  a2b17c3e723296023a9c75426e293534c1a5aaf5
 
FOLLOWUP_IP: 
NTFS!NtfsTeardownStructures+124
fffff801`94c2c5d4 418b49d4        mov     ecx,dword ptr [r9-2Ch]
 
FAULT_INSTR_CODE:  d4498b41
 
SYMBOL_STACK_INDEX:  0
 
SYMBOL_NAME:  NTFS!NtfsTeardownStructures+124
 
FOLLOWUP_NAME:  MachineOwner
 
MODULE_NAME: NTFS
 
IMAGE_NAME:  NTFS.sys
 
DEBUG_FLR_IMAGE_TIMESTAMP:  565d37b4
 
IMAGE_VERSION:  10.0.10240.16601
 
STACK_COMMAND:  .cxr 0xffffd000223a1970 ; kb
 
BUCKET_ID_FUNC_OFFSET:  124
 
FAILURE_BUCKET_ID:  0x3B_NTFS!NtfsTeardownStructures
 
BUCKET_ID:  0x3B_NTFS!NtfsTeardownStructures
 
PRIMARY_PROBLEM_CLASS:  0x3B_NTFS!NtfsTeardownStructures
 
TARGET_TIME:  2016-02-11T23:24:25.000Z
 
OSBUILD:  10240
 
OSSERVICEPACK:  0
 
SERVICEPACK_NUMBER: 0
 
OS_REVISION: 0
 
SUITE_MASK:  272
 
PRODUCT_TYPE:  1
 
OSPLATFORM_TYPE:  x64
 
OSNAME:  Windows 10
 
OSEDITION:  Windows 10 WinNt TerminalServer SingleUserTS
 
OS_LOCALE:  
 
USER_LCID:  0
 
OSBUILD_TIMESTAMP:  2016-01-04 21:09:59
 
BUILDDATESTAMP_STR:  160104-1507
 
BUILDLAB_STR:  th1
 
BUILDOSVER_STR:  10.0.10240.16644.amd64fre.th1.160104-1507
 
ANALYSIS_SESSION_ELAPSED_TIME: 519f
 
ANALYSIS_SOURCE:  KM
 
FAILURE_ID_HASH_STRING:  km:0x3b_ntfs!ntfsteardownstructures
 
FAILURE_ID_HASH:  {342dfdb4-0b0c-21d4-d913-f9307bf323df}
 
Followup:     MachineOwner
---------


#4 Scarlet_Erza

Scarlet_Erza
  • Topic Starter

  • Members
  • 4 posts
  • OFFLINE
  •  
  • Local time:02:22 AM

Posted 03 November 2016 - 07:30 PM

This is right after another crash
 

 
Microsoft ® Windows Debugger Version 10.0.14321.1024 AMD64
Copyright © Microsoft Corporation. All rights reserved.
 
 
Loading Dump File [O:\Windows\MEMORY.DMP]
Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available.
 
 
************* Symbol Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       SRV*o:\symbols*http://msdl.microsoft.com/download/symbols
Symbol search path is: SRV*o:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 10 Kernel Version 10240 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 10240.16644.amd64fre.th1.160104-1507
Machine Name:
Kernel base = 0xfffff802`e827c000 PsLoadedModuleList = 0xfffff802`e85a1070
Debug session time: Thu Feb 11 19:24:25.144 2016 (UTC - 4:00)
System Uptime: 1 days 23:52:10.122
Loading Kernel Symbols
...............................................................
................................................................
.........................................
Loading User Symbols
PEB is paged out (Peb.Ldr = 00007ff7`9336d018).  Type ".hh dbgerr001" for details
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
 
Use !analyze -v to get detailed debugging information.
 
BugCheck 3B, {c0000005, fffff80194c2c5d4, ffffd000223a1970, 0}
 
Probably caused by : NTFS.sys ( NTFS!NtfsTeardownStructures+124 )
 
Followup:     MachineOwner
---------
 
3: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
 
SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff80194c2c5d4, Address of the instruction which caused the bugcheck
Arg3: ffffd000223a1970, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.
 
Debugging Details:
------------------
 
 
DUMP_CLASS: 1
 
DUMP_QUALIFIER: 401
 
BUILD_VERSION_STRING:  10240.16644.amd64fre.th1.160104-1507
 
SYSTEM_MANUFACTURER:  To be filled by O.E.M.
 
SYSTEM_PRODUCT_NAME:  To be filled by O.E.M.
 
SYSTEM_SKU:  To be filled by O.E.M.
 
SYSTEM_VERSION:  To be filled by O.E.M.
 
BIOS_VENDOR:  American Megatrends Inc.
 
BIOS_VERSION:  1208
 
BIOS_DATE:  04/18/2012
 
BASEBOARD_MANUFACTURER:  ASUSTeK COMPUTER INC.
 
BASEBOARD_PRODUCT:  M5A97
 
BASEBOARD_VERSION:  Rev 1.xx
 
DUMP_TYPE:  1
 
BUGCHECK_P1: c0000005
 
BUGCHECK_P2: fffff80194c2c5d4
 
BUGCHECK_P3: ffffd000223a1970
 
BUGCHECK_P4: 0
 
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s.
 
FAULTING_IP: 
NTFS!NtfsTeardownStructures+124
fffff801`94c2c5d4 418b49d4        mov     ecx,dword ptr [r9-2Ch]
 
CONTEXT:  ffffd000223a1970 -- (.cxr 0xffffd000223a1970)
rax=0000000000000000 rbx=ffffc00192fbd010 rcx=ffffe0005e815a00
rdx=0000000000000004 rsi=ffffd000223a23d2 rdi=0000000000000000
rip=fffff80194c2c5d4 rsp=ffffd000223a2390 rbp=0000000000000000
 r8=ffffe000643b8da8  r9=fdffc00192fbd518 r10=7fffe000643b8da8
r11=7ffffffffffffffc r12=0000000000000000 r13=0000000000000000
r14=ffffe00066182018 r15=ffffc00192fbd038
iopl=0         nv up ei pl zr na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010246
NTFS!NtfsTeardownStructures+0x124:
fffff801`94c2c5d4 418b49d4        mov     ecx,dword ptr [r9-2Ch] ds:002b:fdffc001`92fbd4ec=????????
Resetting default scope
 
CPU_COUNT: 8
 
CPU_MHZ: e1c
 
CPU_VENDOR:  AuthenticAMD
 
CPU_FAMILY: 15
 
CPU_MODEL: 1
 
CPU_STEPPING: 2
 
DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
 
BUGCHECK_STR:  0x3B
 
PROCESS_NAME:  svchost.exe
 
CURRENT_IRQL:  0
 
ANALYSIS_SESSION_HOST:  SCARLET-PC
 
ANALYSIS_SESSION_TIME:  11-03-2016 20:27:53.0963
 
ANALYSIS_VERSION: 10.0.14321.1024 amd64fre
 
LAST_CONTROL_TRANSFER:  from fffff80194bfcb11 to fffff80194c2c5d4
 
STACK_TEXT:  
ffffd000`223a2390 fffff801`94bfcb11 : ffffe000`66182018 ffffe000`5e8153e8 00000000`00000000 ffffc001`92fbd010 : NTFS!NtfsTeardownStructures+0x124
ffffd000`223a2410 fffff801`94bfc238 : ffffe000`66182018 ffffe000`5e815180 ffffc001`92fbd010 00000000`00000001 : NTFS!NtfsIterateMft+0x221
ffffd000`223a24a0 fffff801`94c39129 : ffffe000`66182018 ffffe000`63be4bd0 ffffe000`00000000 ffffd000`00000000 : NTFS!NtfsQueryFileLayout+0x238
ffffd000`223a25f0 fffff801`94c3896c : ffffe000`66182018 ffffe000`63be4bd0 ffffe000`63be4bd0 00000000`00000000 : NTFS!NtfsUserFsRequest+0x549
ffffd000`223a2660 fffff801`943f51c4 : ffffe000`606818b0 ffffd000`223a2820 ffffe000`63be4bd0 ffffe000`63be4f70 : NTFS!NtfsFsdFileSystemControl+0x11c
ffffd000`223a2770 fffff801`94422d55 : ffffe000`60838d80 fffff802`e86b0065 00000000`00000001 ffffe000`607ed600 : FLTMGR!FltpLegacyProcessingAfterPreCallbacksCompleted+0x2a4
ffffd000`223a27f0 fffff802`e86ba6b3 : 00000000`00000001 ffffd000`223a2b80 ffffe000`6533dc60 fffff680`07065960 : FLTMGR!FltpFsControl+0x115
ffffd000`223a2850 fffff802`e86e06ca : 00001000`655de000 ffffe000`65745840 00000000`00000000 00000000`00000000 : nt!IopXxxControlFile+0x1253
ffffd000`223a2a20 fffff802`e83d5b63 : fffff6fb`40038328 fffff680`07065960 ffff2840`2e5073c6 fffff802`e86b6eac : nt!NtFsControlFile+0x56
ffffd000`223a2a90 00007fff`6925390a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
0000000e`09a4df58 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007fff`6925390a
 
 
THREAD_SHA1_HASH_MOD_FUNC:  84048fcc038d4f1e3207a82fda0ebc3e4353c289
 
THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  a635df9418d7563edb17901663ae66de7dc9a847
 
THREAD_SHA1_HASH_MOD:  a2b17c3e723296023a9c75426e293534c1a5aaf5
 
FOLLOWUP_IP: 
NTFS!NtfsTeardownStructures+124
fffff801`94c2c5d4 418b49d4        mov     ecx,dword ptr [r9-2Ch]
 
FAULT_INSTR_CODE:  d4498b41
 
SYMBOL_STACK_INDEX:  0
 
SYMBOL_NAME:  NTFS!NtfsTeardownStructures+124
 
FOLLOWUP_NAME:  MachineOwner
 
MODULE_NAME: NTFS
 
IMAGE_NAME:  NTFS.sys
 
DEBUG_FLR_IMAGE_TIMESTAMP:  565d37b4
 
IMAGE_VERSION:  10.0.10240.16601
 
STACK_COMMAND:  .cxr 0xffffd000223a1970 ; kb
 
BUCKET_ID_FUNC_OFFSET:  124
 
FAILURE_BUCKET_ID:  0x3B_NTFS!NtfsTeardownStructures
 
BUCKET_ID:  0x3B_NTFS!NtfsTeardownStructures
 
PRIMARY_PROBLEM_CLASS:  0x3B_NTFS!NtfsTeardownStructures
 
TARGET_TIME:  2016-02-11T23:24:25.000Z
 
OSBUILD:  10240
 
OSSERVICEPACK:  0
 
SERVICEPACK_NUMBER: 0
 
OS_REVISION: 0
 
SUITE_MASK:  272
 
PRODUCT_TYPE:  1
 
OSPLATFORM_TYPE:  x64
 
OSNAME:  Windows 10
 
OSEDITION:  Windows 10 WinNt TerminalServer SingleUserTS
 
OS_LOCALE:  
 
USER_LCID:  0
 
OSBUILD_TIMESTAMP:  2016-01-04 21:09:59
 
BUILDDATESTAMP_STR:  160104-1507
 
BUILDLAB_STR:  th1
 
BUILDOSVER_STR:  10.0.10240.16644.amd64fre.th1.160104-1507
 
ANALYSIS_SESSION_ELAPSED_TIME: 7bf
 
ANALYSIS_SOURCE:  KM
 
FAILURE_ID_HASH_STRING:  km:0x3b_ntfs!ntfsteardownstructures
 
FAILURE_ID_HASH:  {342dfdb4-0b0c-21d4-d913-f9307bf323df}
 
Followup:     MachineOwner
---------


#5 usasma

usasma

    Still visually handicapped (avatar is memory developed by my Dad


  • BSOD Kernel Dump Expert
  • 25,091 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Southeastern CT, USA
  • Local time:02:22 AM

Posted 04 November 2016 - 04:38 AM

Nice work with the debugger, but we can't see much in those reports.
We'll need to massage the dump files a bit, and will need other reports to help analyze this.

 

Please run this report collecting tool so that we can provide a complete analysis: (from the pinned topic at the top of the forum)   http://www.bleepingcomputer.com/forums/t/576314/blue-screen-of-death-bsod-posting-instructions-windows-10-81-8-7-vista/
FYI - I don't often use the Perfmon report, so if it doesn't work please just let me know.
NOTE:  On problem systems it can take up to 20 minutes for the log files to complete.  Please be patient and let it run.

If you still have problems with it running, there's an alternate tool here (direct download link):  https://github.com/blueelvis/BSOD-Inspector/releases/download/1.0.5/BSODInspector-1.0.5.exe

NOTE:
Please zip up the (.ZIP) files - do not use .RAR or other compression utilities. 
.ZIP is the type file that can be uploaded to the forums.

While waiting for a reply, please run these free hardware diagnostics:  http://www.carrona.org/hwdiag.html

Please start with the hard drive tests, but run ALL of them - and let us know the results.

 

If ALL of the diagnostic tests pass, then try running Driver Verifier according to these instructions:  http://www.carrona.org/verifier.html


My browser caused a flood of traffic, sio my IP address was banned. Hope to fix it soon. Will get back to posting as soon as Im able.

- John  (my website: http://www.carrona.org/ )**If you need a more detailed explanation, please ask for it. I have the Knack. **  If I haven't replied in 48 hours, please send me a message. My eye problems have recently increased and I'm having difficult reading posts. (23 Nov 2017)FYI - I am completely blind in the right eye and ~30% blind in the left eye.<p>If the eye problems get worse suddenly, I may not be able to respond.If that's the case and help is needed, please PM a staff member for assistance.

#6 Scarlet_Erza

Scarlet_Erza
  • Topic Starter

  • Members
  • 4 posts
  • OFFLINE
  •  
  • Local time:02:22 AM

Posted 04 November 2016 - 08:16 AM

Thank you so much Usasma!! I'll start taking these steps and will let you know soon.

Again, Thank you so much. I appreciate your hard work!






0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users