Troubleshooting Bluescreens - Techist - Tech Forum

Go Back   Techist - Tech Forum > Computer Hardware > Hardware Repairs and Troubleshooting
Click Here to Login
Reply
 
Thread Tools Display Modes
 
Old 05-11-2017, 08:51 PM   #1 (permalink)
Newb Techie
 
Join Date: May 2017
Location: US
Posts: 24
Post Troubleshooting Bluescreens

So a few days ago, my computer just starts randomly blue screening while using it, mostly after closing applications. Not really sure what is causing these things, but how do I check to see whats wrong and what isn't working properly?
__________________

Jweegee is offline   Reply With Quote
Old 05-11-2017, 08:52 PM   #2 (permalink)
Private Joker
 
carnageX's Avatar
 
Join Date: Feb 2007
Location: South Dakota
Posts: 24,388
Default Re: Troubleshooting Bluescreens

Well what's the STOP code that it gives you when it happens? Should be formatted as: "0x000000##" where ## is some alphanumeric combination.

Do you have the minidump files from your crashes under C:\Windows\Minidumps ?
__________________

__________________
Laptop: MSI GT70 2OC-059us | i7-4700MQ | 16GB | GTX 770m | 500GB SSD / 750GB HDD | 17.3" | Win10 Pro
Desktop: 4690k | 12GB g.Skill RipJaws | GTX 970 | 520hx | Z87X-UD4H | Corsair Vengeance C70 | Corsair H110 | Acer 25" | Acer 22" | Win10
Mobile: Samsung Galaxy Note 5


If I help you, or you just like what I said, rep me by clicking the under my post
carnageX is offline   Reply With Quote
Old 05-11-2017, 09:11 PM   #3 (permalink)
Newb Techie
 
Join Date: May 2017
Location: US
Posts: 24
Default Re: Troubleshooting Bluescreens

The stop code is normally 7A

As for the minidumps, here are a few:
Attached Files
File Type: zip Folder (1).zip (74.7 KB, 2 views)
Jweegee is offline   Reply With Quote
Old 05-11-2017, 09:42 PM   #4 (permalink)
Private Joker
 
carnageX's Avatar
 
Join Date: Feb 2007
Location: South Dakota
Posts: 24,388
Default Re: Troubleshooting Bluescreens

Here's the dumps as outputted by WinDbg:

1/16 dump:
Code:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff88005789ae0, fffff8800ad23a10, 0}

Probably caused by : nvlddmkm.sys ( nvlddmkm+92ae0 )

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

12: 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: fffff88005789ae0, Address of the instruction which caused the bugcheck
Arg3: fffff8800ad23a10, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

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


DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING:  7601.19110.amd64fre.win7sp1_gdr.151230-0600

SYSTEM_MANUFACTURER:  ASUS

SYSTEM_PRODUCT_NAME:  All Series

SYSTEM_SKU:  All

SYSTEM_VERSION:  System Version

BIOS_VENDOR:  American Megatrends Inc.

BIOS_VERSION:  1203

BIOS_DATE:  12/10/2014

BASEBOARD_MANUFACTURER:  ASUSTeK COMPUTER INC.

BASEBOARD_PRODUCT:  X99-A

BASEBOARD_VERSION:  Rev 1.xx

DUMP_TYPE:  2

BUGCHECK_P1: c0000005

BUGCHECK_P2: fffff88005789ae0

BUGCHECK_P3: fffff8800ad23a10

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: 
nvlddmkm+92ae0
fffff880`05789ae0 418b4208        mov     eax,dword ptr [r10+8]

CONTEXT:  fffff8800ad23a10 -- (.cxr 0xfffff8800ad23a10)
rax=0000000000000000 rbx=0000000000000000 rcx=fffff8a005593908
rdx=0000000000100114 rsi=0000000000100114 rdi=fffffa800fc10790
rip=fffff88005789ae0 rsp=fffff8800ad243f8 rbp=000000000001ef00
 r8=0000000000000000  r9=0000000000000000 r10=460c6e8bc75ddd6f
r11=fffff8a018a75210 r12=0000000080000000 r13=fffffa800fc10790
r14=0000000000000001 r15=fffffa800fc10790
iopl=0         nv up ei pl nz na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010206
nvlddmkm+0x92ae0:
fffff880`05789ae0 418b4208        mov     eax,dword ptr [r10+8] ds:002b:460c6e8b`c75ddd77=????????
Resetting default scope

CPU_COUNT: 10

CPU_MHZ: bb6

CPU_VENDOR:  GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 3f

CPU_STEPPING: 2

CPU_MICROCODE: 6,3f,2,0 (F,M,S,R)  SIG: 29'00000000 (cache) 29'00000000 (init)

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0x3B

PROCESS_NAME:  csrss.exe

CURRENT_IRQL:  0

ANALYSIS_SESSION_HOST:  MAKO

ANALYSIS_SESSION_TIME:  05-11-2017 21:37:38.0858

ANALYSIS_VERSION: 10.0.10586.567 amd64fre

LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff88005789ae0

STACK_TEXT:  
fffff880`0ad243f8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nvlddmkm+0x92ae0


THREAD_SHA1_HASH_MOD_FUNC:  d79c3f9e9541b50dff558588ee91b494a55f2aae

THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  aec45d7f8a6ffa744cacd570be4de2306ffa003f

THREAD_SHA1_HASH_MOD:  d79c3f9e9541b50dff558588ee91b494a55f2aae

FOLLOWUP_IP: 
nvlddmkm+92ae0
fffff880`05789ae0 418b4208        mov     eax,dword ptr [r10+8]

FAULT_INSTR_CODE:  8428b41

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nvlddmkm+92ae0

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  560f3569

STACK_COMMAND:  .cxr 0xfffff8800ad23a10 ; kb

FAILURE_BUCKET_ID:  X64_0x3B_nvlddmkm+92ae0

BUCKET_ID:  X64_0x3B_nvlddmkm+92ae0

PRIMARY_PROBLEM_CLASS:  X64_0x3B_nvlddmkm+92ae0

TARGET_TIME:  2016-01-16T18:43:36.000Z

OSBUILD:  7601

OSSERVICEPACK:  1000

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK:  272

PRODUCT_TYPE:  1

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 7

OSEDITION:  Windows 7 WinNt (Service Pack 1) TerminalServer SingleUserTS

OS_LOCALE:  

USER_LCID:  0

OSBUILD_TIMESTAMP:  2015-12-30 11:49:16

BUILDDATESTAMP_STR:  151230-0600

BUILDLAB_STR:  win7sp1_gdr

BUILDOSVER_STR:  6.1.7601.19110.amd64fre.win7sp1_gdr.151230-0600

ANALYSIS_SESSION_ELAPSED_TIME: 5b9

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_0x3b_nvlddmkm+92ae0

FAILURE_ID_HASH:  {63abe66a-7da9-590f-5929-43c65c82f0b4}

Followup:     MachineOwner
---------
1/14 dump:
Code:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 7A, {fffff6fc40006f98, ffffffffc000009d, 94f0e860, fffff88000df393c}

GetPointerFromAddress: unable to read from fffff80003702278
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : memory_corruption

Followup:     memory_corruption
---------

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

KERNEL_DATA_INPAGE_ERROR (7a)
The requested page of kernel data could not be read in.  Typically caused by
a bad block in the paging file or disk controller error. Also see
KERNEL_STACK_INPAGE_ERROR.
If the error status is 0xC000000E, 0xC000009C, 0xC000009D or 0xC0000185,
it means the disk subsystem has experienced a failure.
If the error status is 0xC000009A, then it means the request failed because
a filesystem failed to make forward progress.
Arguments:
Arg1: fffff6fc40006f98, lock type that was held (value 1,2,3, or PTE address)
Arg2: ffffffffc000009d, error status (normally i/o status code)
Arg3: 0000000094f0e860, current process (virtual address for lock type 3, or PTE)
Arg4: fffff88000df393c, virtual address that could not be in-paged (or PTE contents if arg1 is a PTE address)

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


DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING:  7601.19110.amd64fre.win7sp1_gdr.151230-0600

SYSTEM_MANUFACTURER:  ASUS

SYSTEM_PRODUCT_NAME:  All Series

SYSTEM_SKU:  All

SYSTEM_VERSION:  System Version

BIOS_VENDOR:  American Megatrends Inc.

BIOS_VERSION:  1203

BIOS_DATE:  12/10/2014

BASEBOARD_MANUFACTURER:  ASUSTeK COMPUTER INC.

BASEBOARD_PRODUCT:  X99-A

BASEBOARD_VERSION:  Rev 1.xx

DUMP_TYPE:  2

BUGCHECK_P1: fffff6fc40006f98

BUGCHECK_P2: ffffffffc000009d

BUGCHECK_P3: 94f0e860

BUGCHECK_P4: fffff88000df393c

ERROR_CODE: (NTSTATUS) 0xc000009d - STATUS_DEVICE_NOT_CONNECTED

DISK_HARDWARE_ERROR: There was error with disk hardware

BUGCHECK_STR:  0x7a_c000009d

CPU_COUNT: 10

CPU_MHZ: bb6

CPU_VENDOR:  GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 3f

CPU_STEPPING: 2

CPU_MICROCODE: 6,3f,2,0 (F,M,S,R)  SIG: 29'00000000 (cache) 29'00000000 (init)

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  CODE_CORRUPTION

PROCESS_NAME:  System

CURRENT_IRQL:  0

ANALYSIS_SESSION_HOST:  MAKO

ANALYSIS_SESSION_TIME:  05-11-2017 21:39:06.0499

ANALYSIS_VERSION: 10.0.10586.567 amd64fre

TRAP_FRAME:  fffff8800375c4e0 -- (.trap 0xfffff8800375c4e0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff88000deb500 rbx=0000000000000000 rcx=fffffa800e078050
rdx=fffffa800dbe2950 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88000df393c rsp=fffff8800375c678 rbp=fffffa801209c430
 r8=0000000000000007  r9=fffffa800e0781a0 r10=0000000000000000
r11=fffffa800dbe2ab0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz ac po cy
ataport!ChannelQueryDeviceRelations:
fffff880`00df393c 0000            add     byte ptr [rax],al ds:fffff880`00deb500=??
Resetting default scope

LOCK_ADDRESS:  fffff800036cec40 -- (!locks fffff800036cec40)

Resource @ nt!PiEngineLock (0xfffff800036cec40)    Available

WARNING: SystemResourcesList->Flink chain invalid. Resource may be corrupted, or already deleted.


WARNING: SystemResourcesList->Blink chain invalid. Resource may be corrupted, or already deleted.

1 total locks

PNP_TRIAGE: 
	Lock address  : 0xfffff800036cec40
	Thread Count  : 0
	Thread address: 0x0000000000000000
	Thread wait   : 0x0

LAST_CONTROL_TRANSFER:  from fffff80003537522 to fffff800034c4c00

STACK_TEXT:  
fffff880`0375c1c8 fffff800`03537522 : 00000000`0000007a fffff6fc`40006f98 ffffffff`c000009d 00000000`94f0e860 : nt!KeBugCheckEx
fffff880`0375c1d0 fffff800`034ec13f : fffffa80`121c5830 fffff880`0375c340 fffff800`03705540 fffffa80`121c5830 : nt! ?? ::FNODOBFM::`string'+0x353ea
fffff880`0375c2b0 fffff800`034d29c9 : 00000000`00000000 00000000`00000008 ffffffff`ffffffff fffffa80`0ce0a0b8 : nt!MiIssueHardFault+0x28b
fffff880`0375c380 fffff800`034c2d2e : 00000000`00000008 fffff880`00df393c fffffa80`0ce0a000 fffffa80`0dbe2950 : nt!MmAccessFault+0x1399
fffff880`0375c4e0 fffff880`00df393c : fffff880`00df14ce 00000000`00000000 fffff880`0375c740 fffff800`035c4780 : nt!KiPageFault+0x16e
fffff880`0375c678 fffff880`00df14ce : 00000000`00000000 fffff880`0375c740 fffff800`035c4780 fffffa80`0e06e2d0 : ataport!ChannelQueryDeviceRelations
fffff880`0375c680 fffff800`03887dae : 00000000`00000000 00000000`00000001 fffffa80`1209c430 fffff880`02fe6180 : ataport!IdePortDispatchPnp+0x22
fffff880`0375c6b0 fffff800`0388811a : 00000000`00000001 fffffa80`1209c430 fffff800`035c4780 fffffa80`1209c430 : nt!PnpAsynchronousCall+0xce
fffff880`0375c6f0 fffff800`0388a467 : fffff800`036cea00 fffffa80`0e073010 00000000`00000002 00000000`00000800 : nt!PnpQueryDeviceRelations+0xfa
fffff880`0375c7b0 fffff800`038b004c : fffffa80`0e073010 fffffa80`0e070020 fffffa80`0e073010 00000000`00000002 : nt!PipEnumerateDevice+0x117
fffff880`0375c810 fffff800`038b0658 : fffff800`036cc5c0 00000000`00000000 00000000`00000001 fffff800`0372cbdc : nt!PipProcessDevNodeTree+0x21c
fffff880`0375ca80 fffff800`035c64e7 : 00000001`00000003 00000000`00000000 00000000`00000001 00000000`00000000 : nt!PiProcessReenumeration+0x98
fffff880`0375cad0 fffff800`034cea69 : fffff800`035c61c0 fffff800`0366f201 fffffa80`0cde8600 00000000`00000000 : nt!PnpDeviceActionWorker+0x327
fffff880`0375cb70 fffff800`0375d926 : 02050402`06050207 fffffa80`0cde8660 00000000`00000080 fffffa80`0cdaa720 : nt!ExpWorkerThread+0x111
fffff880`0375cc00 fffff800`034b60e6 : fffff880`03517180 fffffa80`0cde8660 fffff880`035222c0 01000101`00010100 : nt!PspSystemThreadStartup+0x5a
fffff880`0375cc40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16


STACK_COMMAND:  kb

CHKIMG_EXTENSION: !chkimg -lo 50 -db !ataport
3591 errors : !ataport (fffff88000df3000-fffff88000df3fff)
fffff88000df3000 *00 *00 *00 *00 *00 *00 *00 *00  00 *00 *00 *00 *00 *00 *00 *00 ................
fffff88000df3010 *00  00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 ................
fffff88000df3020 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 ................
fffff88000df3030 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 ................
fffff88000df3040 *00 *00 *00 *00 *00 *00 *00 *00  00  00  00 *00 *00 *00 *00 *00 ................
fffff88000df3050 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 ................
fffff88000df3060 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 ................
fffff88000df3070 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 ................
fffff88000df3080 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 ................
fffff88000df3090 *00  00  00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00  00  00 *00 ................
fffff88000df30a0 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00  00 ................
fffff88000df30b0  00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00  00  00 *00 *00 *00 ................
fffff88000df30c0 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 ................
fffff88000df30d0 *00 *00 *00 *00 *00 *00 *00  00  00 *00 *00 *00 *00  00  00 *00 ................
fffff88000df30e0 *00 *00 *00  00  00  00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 ................
fffff88000df30f0 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 ................
fffff88000df3100 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 ................
fffff88000df3110 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 ................
fffff88000df3120 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 ................
fffff88000df3130 *00 *00 *00 *00 *00 *00 *00 *00  00  00 *00 *00 *00  00  00  00 ................
fffff88000df3140 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 ................
fffff88000df3150 *00  00  00 *00 *00 *00 *00 *00 *00 *00 *00  00  00  00 *00 *00 ................
fffff88000df3160 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 ................
fffff88000df3170 *00 *00 *00 *00 *00 *00 *00 *00 *00  00  00 *00 *00 *00 *00 *00 ................
fffff88000df3180 *00 *00 *00 *00 *00  00  00 *00 *00 *00 *00 *00 *00 *00  00  00 ................
fffff88000df3190 *00 *00 *00 *00 *00 *00 *00 *00  00  00 *00 *00 *00 *00 *00 *00 ................
fffff88000df31a0 *00 *00 *00  00  00 *00 *00 *00 *00 *00  00 *00 *00 *00 *00 *00 ................
fffff88000df31b0 *00 *00 *00 *00  00  00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 ................
fffff88000df31c0 *00 *00 *00 *00 *00 *00 *00 *00  00 *00  00  00 *00 *00 *00 *00 ................
fffff88000df31d0 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 ................
fffff88000df31e0 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 ................
fffff88000df31f0 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 ................
fffff88000df3200 *00 *00 *00 *00 *00 *00  00  00  00 *00 *00 *00 *00 *00 *00 *00 ................
fffff88000df3210 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 ................
fffff88000df3220 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 ................
fffff88000df3230 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 ................
fffff88000df3240 *00 *00  00  00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 ................
fffff88000df3250 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 ................
fffff88000df3260 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 ................
fffff88000df3270 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 ................
fffff88000df3280 *00 *00 *00 *00 *00 *00  00  00 *00 *00 *00 *00 *00 *00 *00 *00 ................
fffff88000df3290 *00 *00 *00  00  00 *00 *00 *00 *00  00  00 *00 *00 *00 *00 *00 ................
fffff88000df32a0  00  00 *00 *00 *00 *00  00  00 *00 *00 *00 *00 *00  00  00 *00 ................
fffff88000df32b0 *00 *00 *00 *00 *00 *00 *00  00  00 *00 *00 *00 *00 *00 *00 *00 ................
fffff88000df32c0 *00 *00 *00 *00  00  00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 ................
fffff88000df32d0 *00 *00 *00  00  00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 ................
fffff88000df32e0 *00  00  00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00  00 ................
fffff88000df32f0  00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00  00  00 *00 ................
fffff88000df3300 *00 *00 *00 *00 *00 *00 *00  00  00 *00 *00 *00 *00 *00 *00 *00 ................
fffff88000df3310 *00 *00 *00 *00 *00  00  00 *00 *00 *00 *00 *00 *00  00  00 *00 ................
WARNING: !chkimg output was truncated to 50 lines. Invoke !chkimg without '-lo [num_lines]' to view  entire output.

MODULE_NAME: memory_corruption

IMAGE_NAME:  memory_corruption

FOLLOWUP_NAME:  memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MEMORY_CORRUPTOR:  LARGE_4096

FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_LARGE_4096

BUCKET_ID:  X64_MEMORY_CORRUPTION_LARGE_4096

PRIMARY_PROBLEM_CLASS:  X64_MEMORY_CORRUPTION_LARGE_4096

TARGET_TIME:  2016-01-15T00:55:39.000Z

OSBUILD:  7601

OSSERVICEPACK:  1000

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK:  272

PRODUCT_TYPE:  1

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 7

OSEDITION:  Windows 7 WinNt (Service Pack 1) TerminalServer SingleUserTS

OS_LOCALE:  

USER_LCID:  0

OSBUILD_TIMESTAMP:  2015-12-30 11:49:16

BUILDDATESTAMP_STR:  151230-0600

BUILDLAB_STR:  win7sp1_gdr

BUILDOSVER_STR:  6.1.7601.19110.amd64fre.win7sp1_gdr.151230-0600

ANALYSIS_SESSION_ELAPSED_TIME: afa

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_memory_corruption_large_4096

FAILURE_ID_HASH:  {e2df8c99-e1e2-9063-1436-3db085e63f6e}

Followup:     memory_corruption
---------
First one seems to be from nVidia driver - are you on the latest driver version from nVidia's website?

Second one points to either memory issues or bad / loose HDD cable. According to the Bugcheck 0x7a with Parameter value 0xC000009D, it's more likely an issue with a bad or loose cable (or motherboard or HDD controller):
https://msdn.microsoft.com/en-us/lib...(v=vs.85).aspx
__________________
Laptop: MSI GT70 2OC-059us | i7-4700MQ | 16GB | GTX 770m | 500GB SSD / 750GB HDD | 17.3" | Win10 Pro
Desktop: 4690k | 12GB g.Skill RipJaws | GTX 970 | 520hx | Z87X-UD4H | Corsair Vengeance C70 | Corsair H110 | Acer 25" | Acer 22" | Win10
Mobile: Samsung Galaxy Note 5


If I help you, or you just like what I said, rep me by clicking the under my post
carnageX is offline   Reply With Quote
Old 05-11-2017, 10:00 PM   #5 (permalink)
Newb Techie
 
Join Date: May 2017
Location: US
Posts: 24
Default Re: Troubleshooting Bluescreens

Ok I installed the latest drivers and went through all the cables so hopefully that fixed it. I guess you'll here back from me if something goes wrong again. Thanks though!
Jweegee is offline   Reply With Quote
Old 05-11-2017, 11:00 PM   #6 (permalink)
Private Joker
 
carnageX's Avatar
 
Join Date: Feb 2007
Location: South Dakota
Posts: 24,388
Default Re: Troubleshooting Bluescreens

Sounds good - hopefully it fixes your issues.

Though those dumps were from January...have you still been getting the 0x7A BSOD more recently than that?
__________________
Laptop: MSI GT70 2OC-059us | i7-4700MQ | 16GB | GTX 770m | 500GB SSD / 750GB HDD | 17.3" | Win10 Pro
Desktop: 4690k | 12GB g.Skill RipJaws | GTX 970 | 520hx | Z87X-UD4H | Corsair Vengeance C70 | Corsair H110 | Acer 25" | Acer 22" | Win10
Mobile: Samsung Galaxy Note 5


If I help you, or you just like what I said, rep me by clicking the under my post
carnageX is offline   Reply With Quote
Old 05-13-2017, 12:23 AM   #7 (permalink)
Newb Techie
 
Join Date: May 2017
Location: US
Posts: 24
Default Re: Troubleshooting Bluescreens

For some reason my computer hasn't made any more minidumps since then which is weird, I was getting that 0x7A more recently, but after doing what you said, it hasn't happened since.
Jweegee is offline   Reply With Quote
Old 05-13-2017, 10:34 AM   #8 (permalink)
Private Joker
 
carnageX's Avatar
 
Join Date: Feb 2007
Location: South Dakota
Posts: 24,388
Default Re: Troubleshooting Bluescreens

Hopefully that's all it was then - good luck! Let us know if it starts happening again.
__________________
Laptop: MSI GT70 2OC-059us | i7-4700MQ | 16GB | GTX 770m | 500GB SSD / 750GB HDD | 17.3" | Win10 Pro
Desktop: 4690k | 12GB g.Skill RipJaws | GTX 970 | 520hx | Z87X-UD4H | Corsair Vengeance C70 | Corsair H110 | Acer 25" | Acer 22" | Win10
Mobile: Samsung Galaxy Note 5


If I help you, or you just like what I said, rep me by clicking the under my post
carnageX is offline   Reply With Quote
Old 05-14-2017, 08:49 PM   #9 (permalink)
Newb Techie
 
Join Date: May 2017
Location: US
Posts: 24
Default Re: Troubleshooting Bluescreens

Ok it happened again, and now my computer is no longer making minidumps, how do i get it to start making them again?
Jweegee is offline   Reply With Quote
Old 05-14-2017, 11:57 PM   #10 (permalink)
Private Joker
 
carnageX's Avatar
 
Join Date: Feb 2007
Location: South Dakota
Posts: 24,388
Default Re: Troubleshooting Bluescreens

Whether it creates minidumps or not depends on how the system crashed. If it can create them, it will.

What was the BSOD this time? 0x7a again?
__________________

__________________
Laptop: MSI GT70 2OC-059us | i7-4700MQ | 16GB | GTX 770m | 500GB SSD / 750GB HDD | 17.3" | Win10 Pro
Desktop: 4690k | 12GB g.Skill RipJaws | GTX 970 | 520hx | Z87X-UD4H | Corsair Vengeance C70 | Corsair H110 | Acer 25" | Acer 22" | Win10
Mobile: Samsung Galaxy Note 5


If I help you, or you just like what I said, rep me by clicking the under my post
carnageX is offline   Reply With Quote
Reply

Tags
bluescreen

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Windows XP: Getting randomly bluescreens/restarts on my new PC K1boRG Microsoft Windows and Software 20 07-13-2008 09:03 AM
Help with Bluescreens and such kez350 Hardware Repairs and Troubleshooting 1 02-18-2006 10:33 AM
Bluescreens!!!!!!!!! aleyva Hardware Repairs and Troubleshooting 1 12-29-2005 11:47 PM
0x50 and Irql bluescreens uber Hardware Repairs and Troubleshooting 4 09-12-2005 03:48 PM
Bluescreens... of death and destruction r1y23 Monitors, Printers and Peripherals 17 11-28-2004 10:40 AM


Our Communities

Our communities encompass many different hobbies and interests, but each one is built on friendly, intelligent membership.

» More about our Communities

Automotive Communities

Our Automotive communities encompass many different makes and models. From U.S. domestics to European Saloons.

» More about our Automotive Communities

Marine Communities

Our Marine websites focus on Cruising and Sailing Vessels, including forums and the largest cruising Wiki project on the web today.

» More about our Marine Communities


Copyright 2002- Social Knowledge, LLC All Rights Reserved.

All times are GMT -5. The time now is 08:08 AM.


Powered by vBulletin® Version 3.8.8 Beta 1
Copyright ©2000 - 2017, vBulletin Solutions, Inc.