BSOD to death

Toggle sidebar Toggle sidebar
K

kyle101roppe

Prominent
Aug 12, 2017
9
0
510
I have been getting nothing but BSOD since I upgraded to win 10 from 7 in January, iv reinstall win 10 four times and keep getting the same issues. I normally get memory_management BSOD, but now I just got a cache_manager BSOD.
 
Sort by date Sort by votes
Microsoft (R) Windows Debugger Version 10.0.15063.468 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Kyles\Desktop\MEMORY.DMP]
Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available.

Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 14393 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 14393.1593.amd64fre.rs1_release.170731-1934
Machine Name:
Kernel base = 0xfffff802`b861b000 PsLoadedModuleList = 0xfffff802`b8919040
Debug session time: Sat Aug 12 20:36:17.351 2017 (UTC - 7:00)
System Uptime: 0 days 0:43:41.102
Loading Kernel Symbols
...............................................................
Page af080 not present in the dump file. Type ".hh dbgerr004" for details
................................................................
................................................................

Loading User Symbols

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

Use !analyze -v to get detailed debugging information.

BugCheck 34, {5117a, ffff8681657b14d8, ffff8681657b0d10, fffff802b8667229}

Probably caused by : memory_corruption ( nt!MiOffsetToProtos+99 )

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

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

CACHE_MANAGER (34)
See the comment for FAT_FILE_SYSTEM (0x23)
Arguments:
Arg1: 000000000005117a
Arg2: ffff8681657b14d8
Arg3: ffff8681657b0d10
Arg4: fffff802b8667229

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


DUMP_CLASS: 1

DUMP_QUALIFIER: 401

BUILD_VERSION_STRING: 14393.1593.amd64fre.rs1_release.170731-1934

SYSTEM_MANUFACTURER: To be filled by O.E.M.

SYSTEM_PRODUCT_NAME: To be filled by O.E.M.

SYSTEM_SKU: SKU

SYSTEM_VERSION: To be filled by O.E.M.

BIOS_VENDOR: American Megatrends Inc.

BIOS_VERSION: 0501

BIOS_DATE: 01/13/2016

BASEBOARD_MANUFACTURER: ASUSTeK COMPUTER INC.

BASEBOARD_PRODUCT: 970 PRO GAMING/AURA

BASEBOARD_VERSION: Rev 1.xx

DUMP_TYPE: 1

BUGCHECK_P1: 5117a

BUGCHECK_P2: ffff8681657b14d8

BUGCHECK_P3: ffff8681657b0d10

BUGCHECK_P4: fffff802b8667229

EXCEPTION_RECORD: ffff8681657b14d8 -- (.exr 0xffff8681657b14d8)
ExceptionAddress: fffff802b8667229 (nt!MiOffsetToProtos+0x0000000000000099)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

CONTEXT: ffff8681657b0d10 -- (.cxr 0xffff8681657b0d10)
rax=c47d40ffffae8adb rbx=0000000000000040 rcx=c47d40ffffae8adb
rdx=0000000000400000 rsi=0000000000000000 rdi=ffffd601fc208c20
rip=fffff802b8667229 rsp=ffff8681657b1710 rbp=ffff970912bc0000
r8=ffff8681657b1800 r9=0000000000000001 r10=7fffd601fc3668a8
r11=7ffffffffffffffc r12=0000000000000000 r13=0000000000000002
r14=0000000000400000 r15=ffff8681657b1800
iopl=0 nv up ei ng nz na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010286
nt!MiOffsetToProtos+0x99:
fffff802`b8667229 488b4008 mov rax,qword ptr [rax+8] ds:002b:c47d40ff`ffae8ae3=????????????????
Resetting default scope

CPU_COUNT: 8

CPU_MHZ: 126c

CPU_VENDOR: AuthenticAMD

CPU_FAMILY: 15

CPU_MODEL: 2

CPU_STEPPING: 0

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

PROCESS_NAME: System

CURRENT_IRQL: 2

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s.

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

EXCEPTION_CODE_STR: c0000005

EXCEPTION_PARAMETER1: 0000000000000000

EXCEPTION_PARAMETER2: ffffffffffffffff

FOLLOWUP_IP:
nt!MiOffsetToProtos+99
fffff802`b8667229 488b4008 mov rax,qword ptr [rax+8]

FAULTING_IP:
nt!MiOffsetToProtos+99
fffff802`b8667229 488b4008 mov rax,qword ptr [rax+8]

BUGCHECK_STR: 0x34

READ_ADDRESS: ffffffffffffffff

ANALYSIS_SESSION_HOST: DESKTOP-KTL1M9E

ANALYSIS_SESSION_TIME: 08-12-2017 22:05:21.0576

ANALYSIS_VERSION: 10.0.15063.468 amd64fre

LAST_CONTROL_TRANSFER: from fffff802b8a3a9ed to fffff802b8667229

STACK_TEXT:
ffff8681`657b1710 fffff802`b8a3a9ed : 00000000`00000000 ffffd602`03e07f18 00000000`00000040 ffff9709`12bc0000 : nt!MiOffsetToProtos+0x99
ffff8681`657b17d0 fffff802`b86670e9 : 00000000`00000400 00000000`00000000 fffff000`10b45c30 00000000`00000000 : nt!MmHardFaultBytesRequired+0x2d
ffff8681`657b1800 fffff802`b8a3a8dc : 00000000`00400000 00000000`00000000 00000000`00000001 ffff8681`657b1910 : nt!CcFetchDataForRead+0x79
ffff8681`657b1860 fffff802`b86b4191 : ffffd602`03e07f18 00000000`00400000 00000000`00040000 00000000`00000001 : nt!CcMapAndCopyFromCache+0xdc
ffff8681`657b1900 fffff802`b86b601b : 00000000`00000800 fffff802`b8916640 fffff802`b8934ec0 fffff802`b8934eb0 : nt!CcPerformReadAhead+0x325
ffff8681`657b1aa0 fffff802`b8681419 : fffff802`b89d0100 ffffd602`02302800 ffffd601`fb14e860 fffff300`00000e00 : nt!CcWorkerThread+0x24b
ffff8681`657b1b80 fffff802`b86d17c5 : b56646ef`5939fd7f 00000000`00000080 ffffd601`fb0af240 ffffd602`02302800 : nt!ExpWorkerThread+0xe9
ffff8681`657b1c10 fffff802`b876fd36 : ffff8681`62c40180 ffffd602`02302800 fffff802`b86d1784 ee177577`312d4432 : nt!PspSystemThreadStartup+0x41
ffff8681`657b1c60 00000000`00000000 : ffff8681`657b2000 ffff8681`657ac000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16


THREAD_SHA1_HASH_MOD_FUNC: 4ef1bfabf5067fd7a5dc6d1f57d91a3219161396

THREAD_SHA1_HASH_MOD_FUNC_OFFSET: e0c1b6873919979c9d0878d0a7cce756401c9968

THREAD_SHA1_HASH_MOD: 9f457f347057f10e1df248e166a3e95e6570ecfe

FAULT_INSTR_CODE: 8408b48

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: nt!MiOffsetToProtos+99

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP: 5980c87e

STACK_COMMAND: .cxr 0xffff8681657b0d10 ; kb

IMAGE_NAME: memory_corruption

BUCKET_ID_FUNC_OFFSET: 99

FAILURE_BUCKET_ID: 0x34_nt!MiOffsetToProtos

BUCKET_ID: 0x34_nt!MiOffsetToProtos

PRIMARY_PROBLEM_CLASS: 0x34_nt!MiOffsetToProtos

TARGET_TIME: 2017-08-13T03:36:17.000Z

OSBUILD: 14393

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: 2017-08-01 11:29:18

BUILDDATESTAMP_STR: 170731-1934

BUILDLAB_STR: rs1_release

BUILDOSVER_STR: 10.0.14393.1593.amd64fre.rs1_release.170731-1934

ANALYSIS_SESSION_ELAPSED_TIME: 4c9

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:0x34_nt!mioffsettoprotos

FAILURE_ID_HASH: {54f5cbd8-24cb-7d2b-6ef6-b702ec8e83eb}

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

 
Upvote 0 Downvote
it happens randomly when using the pc, iv had 2 tabs open or 7 tabs. NOTE - google chrome will not work on this pc it locks up the whole pc, I have to use edge.

hd1-toshiba q300 500gb sdd - win 10 install
hd2-st500lt012 500gb - laptop hd that has just 3ds max model projects
hd3-wd blue 1000 gb - games 1
hd4-wd blue 500 gb - games 2 and music

EXTRA- also have my external hd.
 
Upvote 0 Downvote
On Sun 8/13/2017 4:40:42 AM your computer crashed
crash dump file: C:\Windows\Minidump\081317-41328-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14F870)
Bugcheck code: 0x139 (0x3, 0xFFFFAF00E0C782D0, 0xFFFFAF00E0C78228, 0x0)
Error: KERNEL_SECURITY_CHECK_FAILURE
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: The kernel has detected the corruption of a critical data structure.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

On Sun 8/13/2017 4:40:42 AM your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: win32kfull.sys (win32kfull!Win32AllocPoolImpl+0x2E)
Bugcheck code: 0x139 (0x3, 0xFFFFAF00E0C782D0, 0xFFFFAF00E0C78228, 0x0)
Error: KERNEL_SECURITY_CHECK_FAILURE
file path: C:\Windows\system32\win32kfull.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Full/Desktop Win32k Kernel Driver
Bug check description: The kernel has detected the corruption of a critical data structure.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
 
Upvote -1 Downvote
On Sat 8/12/2017 8:36:17 PM your computer crashed
crash dump file: C:\Windows\Minidump\081217-25312-01.dmp
This was probably caused by the following module: ntfs.sys (NTFS+0xB846A)
Bugcheck code: 0x34 (0x5117A, 0xFFFF8681657B14D8, 0xFFFF8681657B0D10, 0xFFFFF802B8667229)
Error: CACHE_MANAGER
file path: C:\Windows\system32\drivers\ntfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT File System Driver
Bug check description: This indicates that a problem occurred in the file system's cache manager.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Sat 8/12/2017 7:51:34 PM your computer crashed
crash dump file: C:\Windows\Minidump\081217-51359-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14F870)
Bugcheck code: 0x1A (0x41284, 0xFFFF8681898D2000, 0x5993000599301, 0xFFFF860010804310)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. This problem might also be caused because of overheating (thermal issue).
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sat 8/12/2017 3:31:07 PM your computer crashed
crash dump file: C:\Windows\Minidump\081217-50234-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14F870)
Bugcheck code: 0x1A (0x41284, 0x1BB286E8000, 0x1197, 0xFFFF870010804310)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. This problem might also be caused because of overheating (thermal issue).
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
 
Upvote -1 Downvote
Yep I tested it for about 4 hours this morning found that the new corsair ram that I just bought a month ago was bad put my patriot mem back in and all passed

Tested it a stick at a time and a dim at a time as well
 
Upvote 0 Downvote
You must log in or register to reply here.

TRENDING THREADS

Latest posts

Moderators online

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom