Sign in with
Sign up | Sign in
Your question

Causes of bsod

Last response: in Systems
Share
November 28, 2012 9:15:23 PM

Hello,
My computer has me confused and lost. I keep getting bsod when just sitting on the desktop doing nothing or surfing the web. What has me confused is I can play Skyrim HD and Planestside 2 and only once in a great while do I get a bsod. I have left skyrim on pause overnight and it was still going in the morning. Though I closed it and about a minute later as soon as I opened IE I got a bsod. I thought maybe it was IE issues so I booted Firefox was on it for maybe 5 mins and bsod. While searching for how to read the .dmp files on my phone my computer got 4 more bsod and then locked up at the bios menu start up. I have gotten the .dmp files off my computer and looked up the over 20 files and each one has a different error. My system is a HP pavilionp6000 series but I have upgraded the cpu to an amd x6 1045T and video is an pny 550gt 5gb ram 1tb seagate sata harddrive. I started getting the issues after winblows 7 updated but I have sense done a low level format and reinstalled winblows 7. I ran a cpu torture test program, Memtest, benchmark and scandisk. All came back wth no errors.

*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {fffffac005f36ee8, 2, 0, fffff8000310cfb4}

Probably caused by : CI.dll ( CI!SHATransform+236 )

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

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

IRQL_NOT_LESS_OR_EQUAL (a)
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 a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: fffffac005f36ee8, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff8000310cfb4, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff8000330f100
fffffac005f36ee8

CURRENT_IRQL: 2

FAULTING_IP:
nt!MiResolveMappedFileFault+94
fffff800`0310cfb4 4d8b0a mov r9,qword ptr [r10]

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0xA

PROCESS_NAME: System

TRAP_FRAME: fffff880009a8ba0 -- (.trap 0xfffff880009a8ba0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000040182035 rbx=0000000000000000 rcx=00000000e89808aa
rdx=00000000c6966474 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88000cebcd6 rsp=fffff880009a8d30 rbp=00000000d0050400
r8=00000000292f6acf r9=00000000f8dc68aa r10=00000000aa5ae0e9
r11=00000000c57d8eb8 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na po cy
CI!SHATransform+0x236:
fffff880`00cebcd6 8b7334 mov esi,dword ptr [rbx+34h] ds:00000000`00000034=????????
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff800030df569 to fffff800030dffc0

STACK_TEXT:
fffff880`009a8468 fffff800`030df569 : 00000000`0000000a fffffac0`05f36ee8 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`009a8470 fffff800`030de1e0 : 00000000`00000002 00000000`00060000 fffff880`009a85c0 fffff8a0`001759c8 : nt!KiBugCheckDispatch+0x69
fffff880`009a85b0 fffff800`0310cfb4 : fffff780`c0000000 fffffa80`03072090 fffff6fc`c0012968 fffff800`03312b00 : nt!KiPageFault+0x260
fffff880`009a8740 fffff800`030fe02c : fac005f3`6ee80420 fffff800`03312b00 fffff8a0`001759c8 f8a00017`59c80400 : nt!MiResolveMappedFileFault+0x94
fffff880`009a88a0 fffff800`030fc893 : f8a00017`59c80400 fffff980`0252e000 fffff6fc`c0012970 fffff800`03312b00 : nt!MiResolveProtoPteFault+0x47c
fffff880`009a8930 fffff800`030ed00b : 00000000`00000000 00000000`00000000 ffffffff`ffffffff fffffa80`00000022 : nt!MiDispatchFault+0x1c3
fffff880`009a8a40 fffff800`030de0ee : 00000000`00000000 fffff980`0252e000 00000000`767fba00 fffff980`0252dfcc : nt!MmAccessFault+0xe1b
fffff880`009a8ba0 fffff880`00cebcd6 : f4bc0300`00645e00 00d45b00`76e29ad0 00545f00`d0bc0300 c7f0bfa1`c61d9eea : nt!KiPageFault+0x16e
fffff880`009a8d30 fffff880`00cecd0c : fffff880`009a8f28 fffffa80`e62e3c19 00000000`d35fec32 fffff800`d947b1a2 : CI!SHATransform+0x236
fffff880`009a8dc0 fffff880`00ca9830 : fffff8a0`00217a00 fffff980`024000e0 00000000`00000002 00000000`00000000 : CI!A_SHAUpdate+0xcc
fffff880`009a8e00 fffff880`00ca1b38 : fffff980`02400188 00000000`00000000 00000000`00000400 00000007`00001000 : CI!HashpHashBytes+0x40
fffff880`009a8e30 fffff880`00ca1281 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : CI!CipImageGetImageHash+0x310
fffff880`009a9010 fffff880`00c9ffbb : 00000000`00000001 fffff880`009a92d0 fffff880`009a92d0 00000000`00000000 : CI!CipValidateFileHash+0x211
fffff880`009a9180 fffff800`03348824 : 00000000`000001a9 00000000`000fffff fffffa80`05f83050 00000000`00000000 : CI!CiValidateImageHeader+0x213
fffff880`009a9260 fffff800`0334862a : 00000000`00000000 00000000`00000080 fffffa80`05f36dc0 00000000`00000000 : nt!SeValidateImageHeader+0x58
fffff880`009a92a0 fffff800`033d8c26 : fffffa80`05f83050 fffffa80`05f36dc0 00000000`00000001 00000000`000001a9 : nt!MiValidateImageHeader+0x21a
fffff880`009a9370 fffff800`033b70f2 : fffff880`009a95c0 fffff880`009a96e0 fffff880`009a9878 00000000`00000001 : nt!MmCreateSection+0x966
fffff880`009a9570 fffff800`030df253 : fffffa80`045fa550 fffff880`009a9818 fffff880`009a9608 00000000`00000000 : nt!NtCreateSection+0x171
fffff880`009a95f0 fffff800`030db810 : fffff800`034b4e96 fffff8a0`00289000 fffffa80`04526000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
fffff880`009a97f8 fffff800`034b4e96 : fffff8a0`00289000 fffffa80`04526000 00000000`00000000 ffffffff`800000c0 : nt!KiServiceLinkage
fffff880`009a9800 fffff800`035215f6 : ffffffff`800000c0 00000000`00100000 00000000`c0000034 fffff800`00000030 : nt!MmCheckSystemImage+0x96
fffff880`009a9930 fffff800`03521989 : 00000000`002a0028 00000000`00000000 00000000`00000001 fffff800`035d7a80 : nt!PspLocateSystemDll+0x86
fffff880`009a9a00 fffff800`0360b32d : fffff800`008128a0 00000000`00000002 00000000`00000000 fffff800`03252e80 : nt!PsLocateSystemDlls+0x69
fffff880`009a9a40 fffff800`0360e4b5 : 00000000`00000007 00000000`00000010 ffffffff`8000002c fffff800`008181d0 : nt!IoInitSystem+0x85d
fffff880`009a9b40 fffff800`0355ec49 : 8b493873`8b49306b fffffa80`045fa550 00000000`00000080 fffffa80`045faae0 : nt!Phase1InitializationDiscard+0x1275
fffff880`009a9d10 fffff800`03376e5a : 48402444`88014824 00000000`00000080 9024848b`48e04389 fffff800`030d0d19 : nt!Phase1Initialization+0x9
fffff880`009a9d40 fffff800`030d0d26 : fffff800`03252e80 fffffa80`045fa550 fffff800`03260cc0 48187089`48106889 : nt!PspSystemThreadStartup+0x5a
fffff880`009a9d80 00000000`00000000 : fffff880`009aa000 fffff880`009a4000 fffff880`009a8000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND: kb

FOLLOWUP_IP:
CI!SHATransform+236
fffff880`00cebcd6 8b7334 mov esi,dword ptr [rbx+34h]

SYMBOL_STACK_INDEX: 8

SYMBOL_NAME: CI!SHATransform+236

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: CI

IMAGE_NAME: CI.dll

DEBUG_FLR_IMAGE_TIMESTAMP: 4ce7c944

FAILURE_BUCKET_ID: X64_0xA_CI!SHATransform+236

BUCKET_ID: X64_0xA_CI!SHATransform+236

Followup: MachineOwner


*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff800031f907d, fffff8800a29eb30, 0}

Probably caused by : hardware ( nt!ExFreePoolWithTag+2ed )

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

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

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


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

FAULTING_IP:
nt!ExFreePoolWithTag+2ed
fffff800`031f907d 0000 add byte ptr [rax],al

CONTEXT: fffff8800a29eb30 -- (.cxr 0xfffff8800a29eb30)
rax=0000000000000004 rbx=fffff8a00bf129c0 rcx=fffff88003289900
rdx=fffff88003288180 rsi=0000000000000003 rdi=0000000000000001
rip=fffff800031f907d rsp=fffff8800a29f510 rbp=0000000000000000
r8=0000000000000002 r9=0000000000000090 r10=fffff8000304e000
r11=00000000000005dd r12=0000000000000009 r13=fffff8a00bf129d0
r14=0000000000000000 r15=fffffa8004570280
iopl=0 nv up ei pl nz na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010206
nt!ExFreePoolWithTag+0x2ed:
fffff800`031f907d 0000 add byte ptr [rax],al ds:002b:00000000`00000004=??
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0x3B

PROCESS_NAME: lsm.exe

CURRENT_IRQL: 0

MISALIGNED_IP:
nt!ExFreePoolWithTag+2ed
fffff800`031f907d 0000 add byte ptr [rax],al

LAST_CONTROL_TRANSFER: from fffff800033d75ff to fffff800031f907d

STACK_TEXT:
fffff880`0a29f510 fffff800`033d75ff : fffff8a0`0a7ed060 00000000`00008814 fffff880`64536553 00000000`000007ff : nt!ExFreePoolWithTag+0x2ed
fffff880`0a29f5c0 fffff800`033b4012 : fffff880`0a29f930 fffff880`0a29fb68 fffffa80`0457ced0 fffff800`033b3785 : nt!RtlpNewSecurityObject+0xe5f
fffff880`0a29f850 fffff800`033b2ee2 : 00000000`00000000 fffffa80`04c553d0 fffff880`0a29fb68 00000000`00000000 : nt!ObpAssignSecurity+0x82
fffff880`0a29f8c0 fffff800`0336cde3 : 00000000`02000000 00000000`00dfeea0 00000000`00000000 00000000`00000001 : nt!ObInsertObjectEx+0x1e2
fffff880`0a29fb10 fffff800`030cc253 : fffffa80`04b98540 00000000`00dfede8 fffff880`0a29fbc8 00000000`ff538442 : nt!NtDuplicateToken+0x17b
fffff880`0a29fbb0 00000000`7744173a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`00dfedc8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7744173a


FOLLOWUP_IP:
nt!ExFreePoolWithTag+2ed
fffff800`031f907d 0000 add byte ptr [rax],al

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: nt!ExFreePoolWithTag+2ed

FOLLOWUP_NAME: MachineOwner

IMAGE_NAME: hardware

DEBUG_FLR_IMAGE_TIMESTAMP: 0

STACK_COMMAND: .cxr 0xfffff8800a29eb30 ; kb

MODULE_NAME: hardware

FAILURE_BUCKET_ID: X64_IP_MISALIGNED

BUCKET_ID: X64_IP_MISALIGNED

Followup: MachineOwner



*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1E, {0, 0, 0, 0}

Probably caused by : ntkrnlmp.exe ( nt!KiKernelCalloutExceptionHandler+e )

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

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

KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: 0000000000000000, The exception code that was not handled
Arg2: 0000000000000000, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception

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


EXCEPTION_CODE: (Win32) 0 (0) - The operation completed successfully.

FAULTING_IP:
+3634303630323335
00000000`00000000 ?? ???

EXCEPTION_PARAMETER1: 0000000000000000

EXCEPTION_PARAMETER2: 0000000000000000

ERROR_CODE: (NTSTATUS) 0 - STATUS_WAIT_0

BUGCHECK_STR: 0x1E_0

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: System

CURRENT_IRQL: 2

EXCEPTION_RECORD: fffff880032b03a8 -- (.exr 0xfffff880032b03a8)
ExceptionAddress: fffff800030d9b02 (nt!KiProcessExpiredTimerList+0x00000000000000f2)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

TRAP_FRAME: fffff880032b0450 -- (.trap 0xfffff880032b0450)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=241aca5e84d70000
rdx=ffffffffffffffdf rsi=0000000000000000 rdi=0000000000000000
rip=fffff800030d9b02 rsp=fffff880032b05e0 rbp=fffffa800747e168
r8=0000000000000003 r9=0000000000000002 r10=fffff80003050000
r11=fffff880032b05b0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na po nc
nt!KiProcessExpiredTimerList+0xf2:
fffff800`030d9b02 488b6ef8 mov rbp,qword ptr [rsi-8] ds:ffffffff`fffffff8=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff800030c69be to fffff800030cef90

STACK_TEXT:
fffff880`032af488 fffff800`030c69be : fffffa80`06350d20 fffffa80`06350c00 fffff880`032afc00 fffff800`030f9e20 : nt!KeBugCheck
fffff880`032af490 fffff800`030f9aed : fffff800`032d56f8 fffff800`032121b0 fffff800`03050000 fffff880`032b03a8 : nt!KiKernelCalloutExceptionHandler+0xe
fffff880`032af4c0 fffff800`030f88c5 : fffff800`03215fac fffff880`032af538 fffff880`032b03a8 fffff800`03050000 : nt!RtlpExecuteHandlerForException+0xd
fffff880`032af4f0 fffff800`03109851 : fffff880`032b03a8 fffff880`032afc00 fffff880`00000000 fffff880`032b0608 : nt!RtlDispatchException+0x415
fffff880`032afbd0 fffff800`030ce642 : fffff880`032b03a8 fffffa80`0747e168 fffff880`032b0450 00400000`00000000 : nt!KiDispatchException+0x135
fffff880`032b0270 fffff800`030ccf4a : 00000000`00000000 fffffa80`06049010 00000000`00000009 fffff880`032b08c8 : nt!KiExceptionDispatch+0xc2
fffff880`032b0450 fffff800`030d9b02 : fffffa80`0747e120 fffffa80`0747e168 fffffa80`0747e168 00400000`00000000 : nt!KiGeneralProtectionFault+0x10a
fffff880`032b05e0 fffff800`030d99be : 00000053`b08b4cd3 fffff880`032b0c58 00000000`00232872 fffff880`0328b3c8 : nt!KiProcessExpiredTimerList+0xf2
fffff880`032b0c30 fffff800`030d97a7 : 00000077`d4555dc1 00000077`00232872 00000077`d4555d2f 00000000`00000072 : nt!KiTimerExpiration+0x1be
fffff880`032b0cd0 fffff800`030c6cca : fffff880`03288180 fffff880`03293040 00000000`00000001 fffff880`00000000 : nt!KiRetireDpcList+0x277
fffff880`032b0d80 00000000`00000000 : fffff880`032b1000 fffff880`032ab000 fffff880`032b0d40 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!KiKernelCalloutExceptionHandler+e
fffff800`030c69be 90 nop

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt!KiKernelCalloutExceptionHandler+e

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 503f82be

FAILURE_BUCKET_ID: X64_0x1E_0_nt!KiKernelCalloutExceptionHandler+e

BUCKET_ID: X64_0x1E_0_nt!KiKernelCalloutExceptionHandler+e

Followup: MachineOwner

*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff80003374c2c, fffff8800a577a60, 0}

Probably caused by : dxgkrnl.sys ( dxgkrnl!DXGCONTEXT::p resent+1c5a )

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

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

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


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

FAULTING_IP:
nt!ObReferenceObjectByHandleWithTag+10c
fffff800`03374c2c 0fb64518 movzx eax,byte ptr [rbp+18h]

CONTEXT: fffff8800a577a60 -- (.cxr 0xfffff8800a577a60)
rax=ffbffa80084ca821 rbx=fffff8a002407380 rcx=ffbffa80084ca820
rdx=0000000000000002 rsi=fffff8a00227b380 rdi=fffffa8008419060
rip=fffff80003374c2c rsp=fffff8800a578440 rbp=ffbffa80084ca820
r8=fffff8a002406000 r9=0000000000000008 r10=0000000000000000
r11=fffffa8008419060 r12=0000000000000000 r13=00000000000004e0
r14=0000000000000001 r15=fffffa8007e4db30
iopl=0 nv up ei ng nz na pe nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010282
nt!ObReferenceObjectByHandleWithTag+0x10c:
fffff800`03374c2c 0fb64518 movzx eax,byte ptr [rbp+18h] ss:0018:ffbffa80`084ca838=??
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0x3B

PROCESS_NAME: SetPoint.exe

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from fffff80003358ed5 to fffff80003374c2c

STACK_TEXT:
fffff880`0a578440 fffff800`03358ed5 : fffff880`0a578900 fffff880`00000002 fffffa80`046ea570 fffff880`0a578801 : nt!ObReferenceObjectByHandleWithTag+0x10c
fffff880`0a578510 fffff880`046c90de : 00000000`00000000 00000000`00000000 fffff8a0`025321e0 fffff900`c0190380 : nt!ObReferenceObjectByHandle+0x25
fffff880`0a578560 fffff880`046c6e7b : fffff8a0`40000dc0 fffff8a0`00000000 fffff880`0a5788c0 fffff880`0a5788f0 : dxgkrnl!DXGCONTEXT::p resent+0x1c5a
fffff880`0a578880 fffff960`002606b8 : fffffa80`08419060 00000000`040ff1f0 00000000`000007dc fffff8a0`00dda000 : dxgkrnl!DxgkPresent+0x543
fffff880`0a578bf0 fffff800`03082253 : fffffa80`08419060 00000000`00000000 00000000`00da7a64 fffffa80`07442700 : win32k!NtGdiDdDDIPresent+0x18
fffff880`0a578c20 000007fe`fe1c145a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`040fee18 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7fe`fe1c145a


FOLLOWUP_IP:
dxgkrnl!DXGCONTEXT::p resent+1c5a
fffff880`046c90de 488bbc24b0010000 mov rdi,qword ptr [rsp+1B0h]

SYMBOL_STACK_INDEX: 2

SYMBOL_NAME: dxgkrnl!DXGCONTEXT::p resent+1c5a

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: dxgkrnl

IMAGE_NAME: dxgkrnl.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4ce799fa

STACK_COMMAND: .cxr 0xfffff8800a577a60 ; kb

FAILURE_BUCKET_ID: X64_0x3B_dxgkrnl!DXGCONTEXT::p resent+1c5a

BUCKET_ID: X64_0x3B_dxgkrnl!DXGCONTEXT::p resent+1c5a

Followup: MachineOwner

That's just a few of the errors. Now I was thinking video card but as I said I can play high graphic games but without being in the games I can't do much of anything.

More about : bsod

November 29, 2012 4:59:52 PM

Here's a dumb question. Do you still get BSOD's in safe mode? If not, I'd say some kind of driver conflict. Do you get lock ups while it's booting or in just the bios or whatever? If you are able to run a different OS, do you still get issues?
Being as you ran torture tests and they came out fine, my guess is some kind of driver incompatability.

-d
m
0
l
November 30, 2012 7:26:00 PM

Sill get bsod in safe mode. The lockups only happen after a bsod and it's when bios is starting to switch to load windows. Though the last few days I've been running verifier and it hasn't bsod but has said it found issues with memory and wanted to run the memory diagnostic test. I let it run through on the standard test then ran it through on the extended test. The standard found no issues but the extended found issues. Ran memtest again a few times and it still finds no errors. So don't know if the windows memory tester is wrong or if the memtest is wrong.
m
0
l
!