Driver BSODs on Windows 8 and 7

I started having BSODs a while ago while I was on Windows 8 and 8.1, but they weren't too bad for some time so I didn't really feel the need to take care of them. Unfortunately, the frequency of the occurrences began to increase, and so I did a fresh OS install and moved back to Windows 7, hoping that all it was were just some badly optimized drivers. Unfortunately, I just got my first BSOD, so I decided to finally get some help.

Thanks in advance for any help you can provide.

Note: the BSOD title is DRIVER_IRQL_NOT_LESS_OR_EQUAL, if that's any help. I'm going to turn off automatic restart so I can catch the stop #s next time around.

Here's the BSOD package:
Attachment 300965

There were a few .dmps I couldn't open, but from what I saw you have a problem with an Altheros driver, Steam, and something called migetnextnode that refers to a Doxygen Program used for C++ programming.

There is some dxm and chrome problems, but I believe those are artifacts from the bigger problems mentioned above.

How did you do your re-install? Did you follow something like this? Clean Install Windows 7

Since it is a custom build I would go back to the basics and remove anything that specifically does not have anything to do with the OS.

Make sure the OS is running strong, double check that altheros driver. Then add your desired programs one at a time and run then for a while to see if one of them makes your machine cough up a BSOD.

If it balks at the first new program then I'd say there's something wrong with the OS or Hardware that is not up to snuff, and you will have to go back and check those areas out.

Your new .dmp points to:

Code:

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

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
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.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c000001d, The exception code that was not handled
Arg2: 8ae46801, The address that the exception occurred at
Arg3: 8cd134ac, Exception Record Address
Arg4: 8cd13090, Context Record Address

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


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

FAULTING_IP: 
cng!SHA512Transform+1361
8ae46801 0facfe1c        shrd    esi,edi,1Ch

EXCEPTION_RECORD:  8cd134ac -- (.exr 0xffffffff8cd134ac)
ExceptionAddress: 8ae46801 (cng!SHA512Transform+0x00001361)
   ExceptionCode: c000001d (Illegal instruction)
  ExceptionFlags: 00000000
NumberParameters: 0

CONTEXT:  8cd13090 -- (.cxr 0xffffffff8cd13090)
eax=00000010 ebx=2e070ff6 ecx=6d0e0981 edx=e070ff67 esi=2e070ff6 edi=7d237072
eip=8ae46801 esp=8cd13574 ebp=8cd138fc iopl=0         ov up ei ng nz na po cy
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010a83
cng!SHA512Transform+0x1361:
8ae46801 0facfe1c        shrd    esi,edi,1Ch
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x7E

PROCESS_NAME:  System

CURRENT_IRQL:  0

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

LAST_CONTROL_TRANSFER:  from 8ae47c3a to 8ae46801

FAILED_INSTRUCTION_ADDRESS: 
cng!SHA512Transform+1361
8ae46801 0facfe1c        shrd    esi,edi,1Ch

STACK_TEXT:  
8cd138fc 8ae47c3a 8cd1395c 0000000e 0000000b cng!SHA512Transform+0x1361
8cd1391c 8ae36561 00000000 affb1000 00000006 cng!SHA512Update+0xea
8cd13c78 8ae1315e 00000000 00000000 8cd13c98 cng!GatherRandomKey+0x508
8cd13cdc 8ae131bf 00000000 8cd13d00 8324b62f cng!ReadExternalEntropyIntoPool+0x1a6
8cd13ce8 8324b62f 85f0fdc8 00000000 85b12730 cng!scavengingWorkItemRoutine+0x15
8cd13d00 830b414b 85b12730 00000000 8560c020 nt!IopProcessWorkItem+0x2d
8cd13d50 8324013d 00000001 a59cb491 00000000 nt!ExpWorkerThread+0x10d
8cd13d90 830e7559 830b403e 00000001 00000000 nt!PspSystemThreadStartup+0x9e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19


FOLLOWUP_IP: 
cng!SHA512Transform+1361
8ae46801 0facfe1c        shrd    esi,edi,1Ch

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  cng!SHA512Transform+1361

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: cng

IMAGE_NAME:  cng.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  501946b4

STACK_COMMAND:  .cxr 0xffffffff8cd13090 ; kb

FAILURE_BUCKET_ID:  0x7E_BAD_IP_cng!SHA512Transform+1361

BUCKET_ID:  0x7E_BAD_IP_cng!SHA512Transform+1361

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

1: kd> .exr 0xffffffff8cd134ac
ExceptionAddress: 8ae46801 (cng!SHA512Transform+0x00001361)
   ExceptionCode: c000001d (Illegal instruction)
  ExceptionFlags: 00000000
NumberParameters: 0

The explanation for 0x7e is Bug Check 0x7E: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (Windows Debuggers) and offers a list of resolutions.

There is an expanded explanation here: STOP 0x0000007E: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED - carrona.org

The cng.sys file is an OS file - Microsoft Windows Kernel Cryptography, Next Generation file.
It may be possible to repair this with a Disk Check then SFC /SCANNOW Command - System File Checker after that.
If these two scans finish okay, and you worked through the resolutions of the bugcheck, but still continue to have BSOD's after you install a third-party program, you should try a re-install of the OS.

I would say you are having problems with your OS.

• Where did you obtain your copy of Windows?
• Did you have any problems with the install?
• Did you trim the SSD?
• Can you post a screenshot of your Disk Management - Post a Screen Capture Image