My Laptop keeps Crashing after I select a diff graphics card

[Phalanx]

I was trying to get the new Battlefront game to work, so I switched the graphics card to my house. Ever since then I had my computer crash about 6-8 times and reverted all changes but it still happens. I need help as to what to do to fix this problem

Laptop specs:
ASUS ROG GL551J
Intel i7-4710HQ/BGA
Nvidia GeforceGTX 860m

 

[carnageX]

Could you be more specific when you say your laptop crashes? Is it BSOD'ing? Is the driver crashing and causing the game to crash? Have you tried updating your drivers? Have you checked to see what your temps are?

Also, what exactly do you mean by "switch graphics cards" ? Do you mean switch from integrated to dedicated?

Do the following to disable auto system restart on BSOD:
Control Panel -> System -> Advanced System Settings on the left panel -> 'Settings' under 'Startup and Recovery' -> uncheck 'Automatically Restart" and click OK on all open dialogs. Go ahead and play Battlefront again and try and get it to crash.

If it BSOD's, then upload the dump files it generates under C:\Windows\Minidump

 

[Phalanx]

I made sure all my drivers were up to date and double checked them.

My computer is BDOS'ing and when the computer crashes,everything is frozen. not even crtl+alt+del does anything. when I'm lucky, it says "Display driver stopped responding and has recovered" or "Application Battlefront.exe has been blocked from accessing graphics hardware".

Also, since my built in graphics cards apparently doesnt meat the minimum requirements for Battlefront, i switched my preferred graphics proccessor to my Nvidia GPU. Since i did this, my computer has been constantly freezing then crashing, having me restart the computer.

 

[carnageX]

Have you checked your temps?

Check under C:\Windows\Minidump and if there are any DMP files, zip them up and upload them here so I can analyze them for you.

 

[Phalanx]

My Temps are fine. and these were the only files in the dump
View attachment DMP.zip

 

[carnageX]

August dump:

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

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffff961ac59f030, 0, fffff961ac5c40b8, 0}


Could not read faulting driver name
Probably caused by : cdd.dll ( cdd!DrvDeleteDeviceBitmapEx+18 )

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

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

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced.  This cannot be protected by try-except,
it must be protected by a Probe.  Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: fffff961ac59f030, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff961ac5c40b8, If non-zero, the instruction address which referenced the bad memory
	address.
Arg4: 0000000000000000, (reserved)

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


Could not read faulting driver name

READ_ADDRESS: unable to get nt!MmSpecialPoolStart
unable to get nt!MmSpecialPoolEnd
unable to get nt!MmPagedPoolEnd
unable to get nt!MmNonPagedPoolStart
unable to get nt!MmSizeOfNonPagedPoolInBytes
 fffff961ac59f030 

FAULTING_IP: 
cdd!DrvDeleteDeviceBitmapEx+18
fffff961`ac5c40b8 488b4030        mov     rax,qword ptr [rax+30h]

MM_INTERNAL_CODE:  0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

BUGCHECK_STR:  AV

PROCESS_NAME:  archeage.exe

CURRENT_IRQL:  2

ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) amd64fre

TRAP_FRAME:  ffffd00024fe1390 -- (.trap 0xffffd00024fe1390)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff961ac59f000 rbx=0000000000000000 rcx=fffff9014569ab50
rdx=0000000000000001 rsi=0000000000000000 rdi=0000000000000000
rip=fffff961ac5c40b8 rsp=ffffd00024fe1520 rbp=ffffd00024fe1650
 r8=0000000000000000  r9=0000000000000000 r10=7ffff90140015fb8
r11=7ffffffffffffffc r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
cdd!DrvDeleteDeviceBitmapEx+0x18:
fffff961`ac5c40b8 488b4030        mov     rax,qword ptr [rax+30h] ds:fffff961`ac59f030=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80229fbb04a to fffff80229f6ad00

STACK_TEXT:  
ffffd000`24fe1148 fffff802`29fbb04a : 00000000`00000050 fffff961`ac59f030 00000000`00000000 ffffd000`24fe1390 : nt!KeBugCheckEx
ffffd000`24fe1150 fffff802`29e3c536 : 00000000`00000000 00000000`00000000 ffffd000`24fe1390 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x4174a
ffffd000`24fe1240 fffff802`29f73dbd : 00000000`000000ff 00000000`00000000 409de5dc`00000005 34ef781c`00000005 : nt!MmAccessFault+0x696
ffffd000`24fe1390 fffff961`ac5c40b8 : 00000000`000023a8 00000000`000029f7 fffff901`4024ef28 fffff901`4560d870 : nt!KiPageFault+0x13d
ffffd000`24fe1520 fffff961`ac3c376a : fffff901`400cd010 ffffd000`24fe1650 fffff901`4560d870 00000000`00000001 : cdd!DrvDeleteDeviceBitmapEx+0x18
ffffd000`24fe1550 fffff961`ac3e4e28 : ffffe001`00000000 00000000`00000001 ffffd000`24fe1810 00000000`00000000 : win32kbase!SURFACE::bDeleteSurface+0x7da
ffffd000`24fe17a0 fffff961`ac42d444 : 00000000`000023a8 00000000`700529f7 00000000`00000001 00000000`00000000 : win32kbase!SURFREF::bDeleteSurface+0x14
ffffd000`24fe17d0 fffff961`ac3e3105 : 00000000`00000001 00000000`000023a8 fffff901`4560d870 00000000`00000000 : win32kbase!vCleanupSurfaces+0x49f64
ffffd000`24fe1800 fffff961`ac3e2d70 : 00000000`000023a8 ffffe001`3ba49080 fffff901`465d8380 fffff961`ac3eb5d4 : win32kbase!NtGdiCloseProcess+0xe5
ffffd000`24fe1840 fffff961`ac0d337f : fffff901`457dbc10 fffff901`457dbc10 00000000`00000000 ffffe001`3ecdced0 : win32kbase!GdiProcessCallout+0x40
ffffd000`24fe18c0 fffff802`2a2d6f72 : ffffd000`24fe19d8 ffffd000`24fe1a99 ffffe001`3ecdced0 00000000`00000000 : win32kfull!W32pProcessCallout+0xbf
ffffd000`24fe18f0 fffff802`2a2d768f : 00000000`00000000 ffffe001`418e0c90 ffffd000`24fe1a99 00000000`00000001 : nt!PsInvokeWin32Callout+0x42
ffffd000`24fe1930 fffff802`2a2be32a : 00000000`c0000005 ffffd000`24fe1a01 00000000`00000000 ffffe001`3ba49080 : nt!PspExitThread+0x66f
ffffd000`24fe1a30 fffff802`29f75363 : ffffe001`4858b080 00000000`00000000 ffffe001`4858b080 ffffe001`4b947930 : nt!NtTerminateProcess+0x11a
ffffd000`24fe1b00 00000000`57a21e52 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0009efd8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x57a21e52


STACK_COMMAND:  kb

FOLLOWUP_IP: 
cdd!DrvDeleteDeviceBitmapEx+18
fffff961`ac5c40b8 488b4030        mov     rax,qword ptr [rax+30h]

SYMBOL_STACK_INDEX:  4

SYMBOL_NAME:  cdd!DrvDeleteDeviceBitmapEx+18

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: cdd

IMAGE_NAME:  cdd.dll

DEBUG_FLR_IMAGE_TIMESTAMP:  559f38ff

IMAGE_VERSION:  10.0.10240.16384

BUCKET_ID_FUNC_OFFSET:  18

FAILURE_BUCKET_ID:  AV_cdd!DrvDeleteDeviceBitmapEx

BUCKET_ID:  AV_cdd!DrvDeleteDeviceBitmapEx

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:av_cdd!drvdeletedevicebitmapex

FAILURE_ID_HASH:  {75a826ac-81ab-7822-6d60-6a74de0736c9}

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

This one seems to be related to memory.. I'd suggest running Memtest86+: Memtest86+ - Advanced Memory Diagnostic Tool
Burn the ISO to a disc and boot off of it. Run it for a minimum of 4 hours (overnight is best) - if you get any errors back at all, then it's a bad memory stick. You'll have to test each stick individually to find out which one is the bad stick then.

October Dump:

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

Use !analyze -v to get detailed debugging information.

BugCheck 119, {2, ffffffffc000009a, ffffd000a65bb9f0, ffffe00115eb06a0}

Probably caused by : dxgmms2.sys ( dxgmms2!VidSchiSendToExecutionQueue+8422 )

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

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

VIDEO_SCHEDULER_INTERNAL_ERROR (119)
The video scheduler has detected that fatal violation has occurred. This resulted
in a condition that video scheduler can no longer progress. Any other values after
parameter 1 must be individually examined according to the subtype.
Arguments:
Arg1: 0000000000000002, The driver failed upon the submission of a command.
Arg2: ffffffffc000009a
Arg3: ffffd000a65bb9f0
Arg4: ffffe00115eb06a0

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


CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

BUGCHECK_STR:  0x119

PROCESS_NAME:  System

CURRENT_IRQL:  0

ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) amd64fre

LAST_CONTROL_TRANSFER:  from fffff801cdcb3c3d to fffff8034c559240

STACK_TEXT:  
ffffd000`a65bb928 fffff801`cdcb3c3d : 00000000`00000119 00000000`00000002 ffffffff`c000009a ffffd000`a65bb9f0 : nt!KeBugCheckEx
ffffd000`a65bb930 fffff801`d14e9ea2 : ffffe001`15eb06a0 00000000`c000009a 00000000`00000008 00000000`00000000 : watchdog!WdLogEvent5_WdCriticalError+0xcd
ffffd000`a65bb970 fffff801`d1557363 : ffffe001`15eb06a0 ffffe001`15eb06a0 ffffe001`15eb9000 ffffe001`17599530 : dxgmms2!VidSchiSendToExecutionQueue+0x8422
ffffd000`a65bba90 fffff801`d1526388 : ffffe001`17599530 ffffe001`15e90010 ffffe001`17599530 ffffe001`15e90010 : dxgmms2!VidSchiSubmitPagingCommand+0x343
ffffd000`a65bbb60 fffff801`d152348a : ffffe001`15eb9000 ffffd000`a65bbbc8 ffffe001`15e90010 ffffe001`00000000 : dxgmms2!VidSchiSubmitQueueCommand+0x18118
ffffd000`a65bbb90 fffff801`d1523440 : ffffe001`15eb9000 ffffe001`15eb9000 ffffe001`0e54d780 ffffd000`a552fcc0 : dxgmms2!VidSchiRun_PriorityTable+0x46
ffffd000`a65bbbc0 fffff803`4c4f1e88 : ffffe001`0e54d780 ffffd000`a65bbc90 ffffd000`a5523180 fffff803`4c55e250 : dxgmms2!VidSchiWorkerThread+0x80
ffffd000`a65bbc00 fffff803`4c55e326 : ffffd000`a5523180 ffffe001`15eba800 ffffd000`a552fcc0 00000000`00000000 : nt!PspSystemThreadStartup+0x58
ffffd000`a65bbc60 00000000`00000000 : ffffd000`a65bc000 ffffd000`a65b6000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_IP: 
dxgmms2!VidSchiSendToExecutionQueue+8422
fffff801`d14e9ea2 cc              int     3

SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  dxgmms2!VidSchiSendToExecutionQueue+8422

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: dxgmms2

IMAGE_NAME:  dxgmms2.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  55fa55af

IMAGE_VERSION:  10.0.10240.16515

BUCKET_ID_FUNC_OFFSET:  8422

FAILURE_BUCKET_ID:  0x119_2_DRIVER_FAILED_SUBMIT_COMMAND_dxgmms2!VidSchiSendToExecutionQueue

BUCKET_ID:  0x119_2_DRIVER_FAILED_SUBMIT_COMMAND_dxgmms2!VidSchiSendToExecutionQueue

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:0x119_2_driver_failed_submit_command_dxgmms2!vidschisendtoexecutionqueue

FAILURE_ID_HASH:  {9a11bf9c-270e-962e-7a82-3efdab93c10e}

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

This one is related to GPU... Doing research on this, kinda points to a bad GPU. If you've already tried updating your driver (or even reverting back to a previous version), as well as tried updating your other drivers (such as chipset drivers).

If it's not a driver issue...you could try doing a fresh install to see if it's a software issue. If a reinstall or drivers don't work, then it's most likely hardware related (i.e. your GPU).