Hello all, 

I've been having some serious trouble since upgrading to Windows 8.1

I use this computer only for AutoCAD and for the past few days i've been getting Blue Screen errors mid-drawing.

They seem to have different error names like SYSTEM_SERVICE_EXCEPTION & IRQL_NOT_LESS_OR_EQUAL. 

Here are the minidump files. 

http://sdrv.ms/1anpEVW 

http://sdrv.ms/1anqC4v

Thanks in advance.

also should note, the system is running an Intel Core i7-4770 and an Nvidia GTX 660 GPU 32GB RAM.

I've read that there are issues with AMD drivers, but that doesn't seem to be the case here. also checked for the Windows update that was causing problems, and it is not installed.

Hi,

Here is my analysis of your dump file, and athw8x.sys is the one cause of your issue. And it's the driver for your Network adapter: http://www.processadvisory.com/driver/athw8x-sys

This response contains a reference to a third party World Wide Web site. Microsoft is providing this information as a convenience to you. Microsoft does not control these sites and has not tested any software or information found on these sites; therefore, Microsoft cannot make any representations regarding the quality, safety, or suitability of any software or information found there.

Please update it to check the issue. Make sure you download the latest one from manufacturer's website.

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


EXCEPTION_CODE: (NTSTATUS) 0xc000001d - {EXCEPTION}  Illegal Instruction  An attempt was made to execute an illegal instruction.

FAULTING_IP: 
athw8x+fa637
fffff800`02992637 0fb68424a8000000 movzx   eax,byte ptr [rsp+0A8h]

EXCEPTION_PARAMETER1:  fffff800f2bc9a80

EXCEPTION_PARAMETER2:  fffff800f2b76be0

BUGCHECK_STR:  0x1E_c000001d

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  6

ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) x86fre

LAST_CONTROL_TRANSFER:  from fffff800f2a18ee7 to fffff800f29d0ca0

FAILED_INSTRUCTION_ADDRESS: 
athw8x+fa637
fffff800`02992637 0fb68424a8000000 movzx   eax,byte ptr [rsp+0A8h]

STACK_TEXT:  
fffff800`f42df298 fffff800`f2a18ee7 : 00000000`0000001e ffffffff`c000001d fffff800`02992637 fffff800`f2bc9a80 : nt!KeBugCheckEx
fffff800`f42df2a0 fffff800`f29dc8c2 : 00000000`00000000 00000000`00000000 ffffcfae`0b77d416 00000000`00000001 : nt! ?? ::FNODOBFM::`string'+0x37d47
fffff800`f42df990 fffff800`f29da647 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000104 : nt!KiExceptionDispatch+0xc2
fffff800`f42dfb70 fffff800`02992637 : ffffe000`040e59f0 fffff800`0000000a fffff800`02b65f20 fffff800`f42dfd58 : nt!KiInvalidOpcodeFault+0x107
fffff800`f42dfd00 ffffe000`040e59f0 : fffff800`0000000a fffff800`02b65f20 fffff800`f42dfd58 00000000`00000000 : athw8x+0xfa637
fffff800`f42dfd08 fffff800`0000000a : fffff800`02b65f20 fffff800`f42dfd58 00000000`00000000 fffff800`f28d749b : 0xffffe000`040e59f0
fffff800`f42dfd10 fffff800`02b65f20 : fffff800`f42dfd58 00000000`00000000 fffff800`f28d749b 00000000`00000001 : BOOTVID!_guard_check_icall_fptr <PERF> (BOOTVID+0xa)
fffff800`f42dfd18 fffff800`f42dfd58 : 00000000`00000000 fffff800`f28d749b 00000000`00000001 fffff800`028ffe14 : athw8x+0x2cdf20
fffff800`f42dfd20 00000000`00000000 : fffff800`f28d749b 00000000`00000001 fffff800`028ffe14 ffffe000`040e5030 : 0xfffff800`f42dfd58


STACK_COMMAND:  kb

FOLLOWUP_IP: 
athw8x+fa637
fffff800`02992637 0fb68424a8000000 movzx   eax,byte ptr [rsp+0A8h]

SYMBOL_STACK_INDEX:  4

SYMBOL_NAME:  athw8x+fa637

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: athw8x

IMAGE_NAME:  athw8x.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  5195a8b5

FAILURE_BUCKET_ID:  0x1E_c000001d_BAD_IP_athw8x+fa637

BUCKET_ID:  0x1E_c000001d_BAD_IP_athw8x+fa637

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:0x1e_c000001d_bad_ip_athw8x+fa637

FAILURE_ID_HASH:  {8ce094d4-c368-a1a2-663a-6d00daa0bdb3}

Followup: MachineOwner

Here is the bug check information for your reference, you can also try steps here to check your issue:

Bug Check 0x1E: KMODE_EXCEPTION_NOT_HANDLED
http://msdn.microsoft.com/en-us/library/windows/hardware/ff557408(v=vs.85).aspx

DG

These two were related to memory exceptions.  Please run driver verifier to pinpoint the underlying driver (though I suspect it is your Symantec)

.

*

@Kate Li--  One does imply the atheros driver but the other does not.  BOth do however have the 0xC05 first parameter indicating a memory exception.