BSOD while watch, playing and testing-Driver IRQL and KMODE EXCEPTION

Dave76 · 26 Sep 2012

Looks like you ruled out the graphics card and keyboard.

Did the crashes seem better or worse to any degree?

Last 7 crashes on the 25th:

Code:

STOP 0x000000D1: DRIVER_IRQL_NOT_LESS_OR_EQUAL
Usual causes:  Device driver
Probably caused by : nvlddmkm.sys ( nvlddmkm+bd656 )
IMAGE_NAME:  nvlddmkm.sys
FAILURE_BUCKET_ID:  X64_0xD1_nvlddmkm+bd656
--------------------------------------------------------------------------------------------------------------------------------------------
STOP 0x0000003B: SYSTEM_SERVICE_EXCEPTION
Usual causes:  System service, Device driver, graphics driver, ?memory
Probably caused by : ntkrnlmp.exe ( nt!KiSystemServiceHandler+7c )
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
PROCESS_NAME:  Steam.exe
FAILURE_BUCKET_ID:  X64_0x3B_nt!KiSystemServiceHandler+7c
--------------------------------------------------------------------------------------------------------------------------------------------
STOP 0x000000D1: DRIVER_IRQL_NOT_LESS_OR_EQUAL
Usual causes:  Device driver
Probably caused by : nvlddmkm.sys ( nvlddmkm+1c9a49 )
IMAGE_NAME:  nvlddmkm.sys
FAILURE_BUCKET_ID:  X64_0xD1_CODE_AV_NULL_IP_nvlddmkm+1c9a49
--------------------------------------------------------------------------------------------------------------------------------------------
STOP 0x000000D1: DRIVER_IRQL_NOT_LESS_OR_EQUAL
Usual causes:  Device driver
Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+260 )
PROCESS_NAME:  Steam.exe
IMAGE_NAME:  ntkrnlmp.exe
FAILURE_BUCKET_ID:  X64_0xD1_CODE_AV_NULL_IP_nt!KiPageFault+260
--------------------------------------------------------------------------------------------------------------------------------------------
STOP 0x000000D1: DRIVER_IRQL_NOT_LESS_OR_EQUAL
Usual causes:  Device driver
Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+260 )
PROCESS_NAME:  System
IMAGE_NAME:  ntkrnlmp.exe
FAILURE_BUCKET_ID:  X64_0xD1_CODE_AV_NULL_IP_nt!KiPageFault+260
--------------------------------------------------------------------------------------------------------------------------------------------
STOP 0x000000D1: DRIVER_IRQL_NOT_LESS_OR_EQUAL
Usual causes:  Device driver
Probably caused by : nvlddmkm.sys ( nvlddmkm+1c9a49 )
PROCESS_NAME:  FlashPlayerPlu
IMAGE_NAME:  nvlddmkm.sys
FAILURE_BUCKET_ID:  X64_0xD1_CODE_AV_NULL_IP_nvlddmkm+1c9a49
--------------------------------------------------------------------------------------------------------------------------------------------
STOP 0x0000001E: KMODE_EXCEPTION_NOT_HANDLED
Usual causes:  Device driver, hardware, System service, compatibility, Remote control programs, memory, BIOS
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+48d3d )
PROCESS_NAME:  svchost.exe
IMAGE_NAME:  ntkrnlmp.exe
FAILURE_BUCKET_ID:  X64_0x1E_nt!_??_::FNODOBFM::_string_+48d3d

When was the last time you did a clean Win7 install?

Run a full AV scan.

Driver Verifier didn't show anything previously, so that won't help.
Let's try a Clean Boot.
Clean Boot by unchecking everything in msconfig>Startup except AV: Startup Programs - Change. After reboot enter msconfig>Services, check the box to Hide All MS Services, repeat above.

Are there any yellow triangles in Device Manager?

Check all the PSU connections, remove the cable, inspect cable end and socket, firmly replace the cable.
Try to re-create the crash scenario.

CPUs are normally not the cause, but they do occasionally fail, since you have one to test with swap them out and test.

EatYaVeggies · 29 Sep 2012

Sorry for the delay, school just started and I've been busy with that the past few days.

Crashes seemed the same.

I think its been 2-3 months since I installed windows on this setup.

By AV I'm assuming you mean antivirus(I use security essentials). Ran the scan, found nothing.

Ran msconfig. Unchecked everything in the start-up tab except windows itself and security essentials, and rebooted. Then did the same in the services tab after Hiding All MS Services.

On device manager, under system devices ATK0110 ACPI UTILITY has a yellow triangle and so does ASMedia XHCI Controller under Universal Serial Bus Controllers.

Got 2 crashes on OCCT after "it stopped working" once. One of those was unusual as I've never seen the error message in the BSOD before.

Checked all PSU connected and reseated most of them.

And got another crash OCCT.

Dave76 · 29 Sep 2012

Did you get any graphs from OCCT?
If you did, post them.

Uninstall CPUZ v135 and install the newest version.
download CPUZ

Install the ASMedia driver.
Asmedia USB3.0 Controller Driver V1.14.3.0 for Windows XP/Vista/7 32bit & 64bit.

ATK0110 ACPI UTILITY - That is for the AI Booster utility, you don't need it.

Last crashes:

Code:

STOP 0x00000113: VIDEO_DXGKRNL_FATAL_ERROR
Probably caused by : dxgkrnl.sys ( dxgkrnl!COREACCESS::AcquireShared+4c )
PROCESS_NAME:  csrss.exe
IMAGE_NAME:  dxgkrnl.sys
FAILURE_BUCKET_ID:  X64_0x113_dxgkrnl!COREACCESS::AcquireShared+4c
-----------------------------------------------------------------------------------
STOP 0x000000D1: DRIVER_IRQL_NOT_LESS_OR_EQUAL
Usual causes:  Device driver
IMAGE_NAME:  nvlddmkm.sys
FAILURE_BUCKET_ID:  X64_0xD1_CODE_AV_NULL_IP_nvlddmkm+1c9a49

Diagnosing basic problems with DirectX
Run the dxdiag tool again.
DirectX Diagnostic Tool

The second crash is blaming your graphics driver.
Are you using the 306.23 - WHQL graphics driver?
If you are try GeForce 301.42 Driver - WHQL

EatYaVeggies · 29 Sep 2012

Unfortunately no. It doesn't seem to produce them when the interface crashes or a blue-screen occurs.

I could try to get a 5-10 minute run if you want.

Dave76 · 29 Sep 2012

No need for the OCCT graphs for now.

Read my last post, I've added some info.

EatYaVeggies · 30 Sep 2012

Uninstalled CPUZ and my graphics drivers and installed the latest CPUZ( thought I had that already) and the version of the graphics drivers specified. Al os installed the ASMedia driver.

Seems to be getting harder to get a bluescreen, but most of the programs that did before now just crash without a BSOD, so I'm wondering if that's progress or not lol. But I managed to get one.

When I was trying to get a BSOD, I ran OCCT power supply and it passed a 20 minute test. Included it just in case.

Kept trying the OCCT CPU one and every time kept getting the "stopped working" message, and it once gave me the error message about trying overwrite protected memory that I mentioned before.

Dave76 · 01 Oct 2012

If you haven't tried switching the RAM cards out, let's try it now.
Remove the current RAM card, install the other card in slot #1, next time you have a crash either BSOD or app crash move the RAM card to slot#3.

Seeing some voltage fluctuations in the OCCT graphs on the 5v, 12v and CPU Vcore.
Bump the CPU Offset Voltage to 1.50v
Bump the Cpu/NB Offset Voltage 1.300v
Is the settings DRAM voltage still at 1.550v?

Your last crash,

Code:

STOP 0x000000D1: DRIVER_IRQL_NOT_LESS_OR_EQUAL
Usual causes:  Device driver
Probably caused by : nvlddmkm.sys ( nvlddmkm+211cde ) nVidia driver
IMAGE_NAME:  nvlddmkm.sys
FAILURE_BUCKET_ID:  X64_0xD1_CODE_AV_BAD_IP_nvlddmkm+211cde

This is blaming the nVidia driver.
Too bad you don't have another mobo slot to try it in.

EatYaVeggies · 05 Oct 2012

School weeks over, time to troubleshoot. My Cpu/Nb was still at 1.300v, and DRAM is still at 1.550v. Pushed the CPU Offset to 1.50v.

Since its still blaming display drivers, I went back to nvidia driver version 296.10.

I have down DRAM switching before, but there's no reason not to try again, so I'm off to do that now. Before I made these changes, was running minecraft and skype, and got BSOD with and without usb mic attached. Thought I'd post it since there havent been that many this past week or so.

Dave76 · 05 Oct 2012

Good news, hope we are getting closer.
Disconnect all USB devices that you don't absolutely need, example leave only keyboard and mouse.

Last nine crashes:

Code:

STOP 0x0000001E: KMODE_EXCEPTION_NOT_HANDLED
Usual causes:  Device driver, hardware, System service, compatibility, Remote control programs, memory, BIOS
Probably caused by : dxgmms1.sys
PROCESS_NAME:  FlashPlayerPlu
IMAGE_NAME:  dxgmms1.sys
FAILURE_BUCKET_ID:  X64_0x1E_dxgmms1!VidSchiProcessDpcCompletedPacket+3a5
------------------------------------------------------------------------------------------------------------------
STOP 0x000000D1: DRIVER_IRQL_NOT_LESS_OR_EQUAL
Usual causes:  Device driver
PROCESS_NAME:  FlashPlayerPlu
FAILURE_BUCKET_ID:  X64_0xD1_CODE_AV_NULL_IP_nt!KiPageFault+260
------------------------------------------------------------------------------------------------------------------
STOP 0x000000D1: DRIVER_IRQL_NOT_LESS_OR_EQUAL
Usual causes:  Device driver
Probably caused by : dxgmms1.sys
PROCESS_NAME:  FlashPlayerPlu
IMAGE_NAME:  dxgmms1.sys
FAILURE_BUCKET_ID:  X64_0xD1_dxgmms1!VidSchiProcessDpcCompletedPacket+38e
------------------------------------------------------------------------------------------------------------------
Four of these:
STOP 0x000000D1: DRIVER_IRQL_NOT_LESS_OR_EQUAL
Usual causes:  Device driver
Probably caused by : dxgmms1.sys
PROCESS_NAME:  System
IMAGE_NAME:  dxgmms1.sys
FAILURE_BUCKET_ID:  X64_0xD1_dxgmms1!VidSchiProcessDpcCompletedPacket+38e
------------------------------------------------------------------------------------------------------------------
Two of these:
STOP 0x000000D1: DRIVER_IRQL_NOT_LESS_OR_EQUAL
Usual causes:  Device driver
Probably caused by : USBPORT.SYS
PROCESS_NAME:  System
IMAGE_NAME:  USBPORT.SYS
FAILURE_BUCKET_ID:  X64_0xD1_CODE_AV_BAD_IP_USBPORT!USBPORT_Core_UsbIocDpc_Worker+14e

Update Flash Player, if you have the latest version, uninstall it and install the next older version.

Unplug all USB devices that aren't required, leave only keyboard and mouse, for testing.
This includes any hub, cell phone, memory stick, dongle of any kind.

Seeing a lot of errors with MSE updating.
Manually update MSE and run a full scan.

EatYaVeggies · 13 Oct 2012

Reinstalled flast player with the latest version. Also had to reinstall MSE as manually updating it was also unsuccessful. Ran a full scan with it once it was reinstalled and updated and came up clean.

There's been one BSOD since my last post, maybe more.

Starting to consider reinstalling windows, but that still last resort type of thing at this point.