Too many BSOD codes, trouble with new build.

[GitRightStik]

I did not want this.
I accidentally purchased a motherboard with integrated graphics, and the last 24 hours confirms my initial fear of purchasing one.
CPU has integrated graphics. Motherboard, same. Throw in a stand-alone graphics card and you can start to imagine the train wreck of BSOD codes I get.
Updated BIOS and updated all drivers direct from each manufacturer's site.
Able to access Safe Mode with Networking.
If I remove the Video card, I could run normal mode off the motherboard's graphics, but no DirectX 3D acceleration. Updated the CPU with a 3D driver from their site, and Windows won't work anymore unless I run Safe Mode, (with networking.)
Paging fault errors, IRQL errors, Memory Management errors, and more all show up in BSOD when I try to run off the video card in normal mode.
Tried to disable the integrated graphics on the motherboard, but all it lets me do is choose whether to boot/run off PEG or IGD. Obviously I tried both, but they only work when I run in safe mode.

BSOD Dump file attached.

 

[koolkat77]

*******************************************************************************
*                                                                             *
*                        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: ffffffffc000001d, The exception code that was not handled
Arg2: fffff88001b3b120, The address that the exception occurred at
Arg3: fffff880033c0f48, Exception Record Address
Arg4: fffff880033c07a0, Context Record Address

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

TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2

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

FAULTING_IP: 
aswSP+9120
fffff880`01b3b120 2f              ???

EXCEPTION_RECORD:  fffff880033c0f48 -- (.exr 0xfffff880033c0f48)
ExceptionAddress: fffff88001b3b120 (aswSP+0x0000000000009120)
   ExceptionCode: c000001d (Illegal instruction)
  ExceptionFlags: 00000000
NumberParameters: 0

CONTEXT:  fffff880033c07a0 -- (.cxr 0xfffff880033c07a0)
rax=0000000000000000 rbx=0000000000000001 rcx=fffff880033c1200
rdx=0000000000000004 rsi=fffffa8007faa800 rdi=fffff880033c1200
rip=fffff88001b3b120 rsp=fffff880033c1180 rbp=0000000000000004
 r8=fffff8a0066b8c01  r9=00000000000000b0 r10=fffff80003601000
r11=0000000000000752 r12=0000000000120001 r13=fffffa800838d000
r14=0000000000000000 r15=fffff880033c1390
iopl=0         nv up ei ng nz ac po cy
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010297
aswSP+0x9120:
fffff880`01b3b120 2f              ???
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_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 fffffa800838d010 to fffff88001b3b120

FAILED_INSTRUCTION_ADDRESS: 
aswSP+9120
fffff880`01b3b120 2f              ???

STACK_TEXT:  
fffff880`033c1180 fffffa80`0838d010 : fffffa80`083798c0 fffff880`033c1298 fffff880`01b975ee 00000000`00000000 : aswSP+0x9120
fffff880`033c1188 fffffa80`083798c0 : fffff880`033c1298 fffff880`01b975ee 00000000`00000000 fffff880`00d9a4b7 : 0xfffffa80`0838d010
fffff880`033c1190 fffff880`033c1298 : fffff880`01b975ee 00000000`00000000 fffff880`00d9a4b7 fffff880`033c1390 : 0xfffffa80`083798c0
fffff880`033c1198 fffff880`01b975ee : 00000000`00000000 fffff880`00d9a4b7 fffff880`033c1390 fffffa80`07ed2d20 : 0xfffff880`033c1298
fffff880`033c11a0 00000000`00000000 : fffff880`00d9a4b7 fffff880`033c1390 fffffa80`07ed2d20 fffffa80`0838d010 : aswSP+0x655ee


FOLLOWUP_IP: 
aswSP+9120
fffff880`01b3b120 2f              ???

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  aswSP+9120

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: aswSP

IMAGE_NAME:  aswSP.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  52a56cc2

STACK_COMMAND:  .cxr 0xfffff880033c07a0 ; kb

FAILURE_BUCKET_ID:  X64_0x7E_BAD_IP_aswSP+9120

BUCKET_ID:  X64_0x7E_BAD_IP_aswSP+9120

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

Avast is contributing to your BSOD's. Please remove it for testing purpose. Use Microsoft Security Essentials.

Recommended from a strict BSOD perspective, compatibility & stability compared to other security software:

Microsoft Security Essentials - Free Antivirus for Windows

Malwarebytes - Free

http://www.sevenforums.com/system-security/206705-good-free-system-security-combination.html

Reduce items at start-up: http://www.sevenforums.com/tutorials/1401-startup-programs-change.html

Perform a clean boot: http://www.sevenforums.com/tutorial...ation-conflicts-performing-clean-startup.html

Daemon Tools/Alchohol is known to cause BSODs:
How to remove sptd.sys from system
Registry and SPTD problems | DAEMON Pro Help

Use Revo Uninstaller to uninstall stubborn software. Opt for Advance Mode while uninstalling which allows leftover registry removal:Download Revo Uninstaller Freeware - Free and Full Download - Uninstall software, remove programs, solve uninstall problems

Run a System file check (SFC): http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html

Scan with Kaspersky TDSSKiller:Anti-rootkit utility TDSSKiller

ESET online scanner: Free Online Virus Scanner | ESET

Run Disk Check on your Hard Drive(s): http://www.sevenforums.com/tutorials/433-disk-check.html

Check for heating issues using Speccy or HWmonitor

Upload a screen shot: http://www.sevenforums.com/tutorials/9733-screenshots-files-upload-post-seven-forums.html

Keep us posted.

 

[GitRightStik]

-Cleared more out of Startup list.
-Ran the SPTD program, it said I don't have anything for it to uninstall.
-Tried Startup Repair. Got BSOD Paging fault one time and BSOD IRQL error the other time.
-Ran Speccy and Speedfan, no heat issues. Speccy could not see my CPU or Motherboard or Video card.
-Ran ScanNow command. It found some problems but could not repair them.
-DVD drive is not compatible with new motherboard, so attempting to download Win7 ISO to thumbdrive, to try to repair installation from USB boot.

 

[koolkat77]

What about Avast?

 

[GitRightStik]

What about Avast?

Removed Avast.
Ran Kaspersky. No issues found.
Rebooted into Safe Mode with Networking.
Now my boot freezes on classpnp.sys.
I followed suggestions and now my system won't even boot to Safe Mode. This is really growing frustrating.

 

[koolkat77]

Work upon http://www.sevenforums.com/tutorials/219533-troubleshooting-windows-7-failure-boot.html

 

[GitRightStik]

Started over. Wiped the hard drive. Reinstalled Win 7.
No issues.
Used MSI motherboard driver disk to install LAN.
No issues.
Installed MSI driver disk Chipset drivers.
Restart goes to BSOD.
Startup recovery fixed it.
Tried again with SVGA drivers.
Restarts to BSOD.
Startup recovery fixed it.
Works fine with terribad VGA graphics, as long as I don't install any more of the figurative offal that MSI calls drivers on their disk.

 

[GitRightStik]

Still stuck with integrated graphics, every time I try to boot with the video card installed or with any graphics drivers installed, it BSOD's.
The CPU chipset graphics drivers and the mobo graphics drivers both cause BSOD if I add them in. This is all while still using only the integrated graphics too.

 

[Arc]

Still stuck with integrated graphics, every time I try to boot with the video card installed or with any graphics drivers installed, it BSOD's.
The CPU chipset graphics drivers and the mobo graphics drivers both cause BSOD if I add them in. This is all while still using only the integrated graphics too.

Which chipset Graphics driver you applied there?

Your CPU is Intel(R) Pentium(R) CPU G2030 @ 3.00GHz, It is Ivy Bridge. Make it sure that you are installing the appropriate one. See the screenshot below:

View attachment 308698

Get it from here: MSI Global B75MA-E33

Then, let us see any further crash dump after applying this VGA driver, and not applying the existing GPU.

 

[GitRightStik]

Grabbed the driver you said. 90% sure I've done that one before.
Installed the 64 bit one.
Restarted, Started Windows, just before login screen it froze then reboots. Ran system restore.
Back at ground zero.
Tried the 32bit driver, but it denied for system specifications. (of course it does not work, I'm running 64bit)
Ran Windows Update for a few more trivial things.
Installed them all, but one:
Intel Corporation - Graphics Adapter WDDM1.1, Graphics Adapter WDDM1.2, Graphics Adapter WDDM1.3 - Intel(R) HD Graphics
Tried that one, while in integrated graphics only, and it BSOD.

 

[GitRightStik]

Managed something new.
Used Device Manager to disable the Integrated Motherboard VGA generic adapter.
Running purely off the integrated graphics in the CPU I managed to boot to Safe Mode with the video card installed.
Installed the Nvidia drivers, then rebooted.
Unable to progress past Safe Mode without BSOD.
Tried to install the CPU drivers again, they caused a BSOD on their own, and same when I tried it with the video card installed.
Kernel Dump is while in Normal Mode, with CPU driver rolled back and no video card installed currently.

 

[Arc]

Grabbed the driver you said. 90% sure I've done that one before.
Installed the 64 bit one.
Restarted, Started Windows, just before login screen it froze then reboots. Ran system restore.
Back at ground zero.
Tried the 32bit driver, but it denied for system specifications. (of course it does not work, I'm running 64bit)
Ran Windows Update for a few more trivial things.
Installed them all, but one:
Intel Corporation - Graphics Adapter WDDM1.1, Graphics Adapter WDDM1.2, Graphics Adapter WDDM1.3 - Intel(R) HD Graphics
Tried that one, while in integrated graphics only, and it BSOD.

If it BSODs with the integrated graphics driver installed, you have to change the motherboard.