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

Dave76 · 13 Oct 2012

Last two crashes:

Code:

STOP 0x000000D1: DRIVER_IRQL_NOT_LESS_OR_EQUAL
Usual causes:  Device driver
PROCESS_NAME:  javaw.exe
FAILURE_BUCKET_ID:  X64_0xD1_CODE_AV_NULL_IP_nt!KiPageFault+260
Inconclusive
------------------------------------------------------------------------------------
STOP 0x000000D1: DRIVER_IRQL_NOT_LESS_OR_EQUAL
Usual causes:  Device driver
Probably caused by : dxgmms1.sys ( dxgmms1!VidSchiProcessDpcCompletedPacket+38e )
PROCESS_NAME:  javaw.exe
IMAGE_NAME:  dxgmms1.sys
FAILURE_BUCKET_ID:  X64_0xD1_dxgmms1!VidSchiProcessDpcCompletedPacket+38e

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

Let's run Driver Verifier again, see if we can get more information to use.
Driver Verifier - Enable and Disable
Use your computer normally, run for 24 hours.
Post the full crash report files if you get a crash.

EatYaVeggies · 21 Oct 2012

Ran Dxdiag, and everything seemed fine. Took screenshots to be safe.

Have been running Verifier and have gotten a lot more crashes.

Dave76 · 22 Oct 2012

You can disable Driver Verifier.

Install both RAM cards.
Run memtest86+ for 7 full passes.
You can stop the test if you get any errors.

System Event Logs only go to 23 Sept.

To check the System Event Log settings.
1. Start Event Viewer.
2. In the console tree, expand Windows Logs and select System.
3. On the Action menu, click Properties.
4. In the General Tab, ensure 'Enable logging' is checked.
Maximum log size should be 20480
Under 'When maximum event log size is reached': select 'Overwrite events as needed (oldest events first)'
Click OK.

If you are still not getting new System Event Logs, you can 'Clear Log' on the same page.

Starting on 19 Oct:

Code:

STOP 0x000000D1: DRIVER_IRQL_NOT_LESS_OR_EQUAL
Usual causes:  Device driver
Probably caused by : dxgmms1.sys ( dxgmms1!VidSchiProcessDpcCompletedPacket+38e )
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME:  Steam.exe
FAILURE_BUCKET_ID:  X64_0xD1_dxgmms1!VidSchiProcessDpcCompletedPacket+38e
-------------------------------------------------------------------------------------------------------------------------------------------
STOP 0x000000D1: DRIVER_IRQL_NOT_LESS_OR_EQUAL
Usual causes:  Device driver
Probably caused by : dxgmms1.sys ( dxgmms1!VidSchiProcessDpcCompletedPacket+38e )
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xD1_VRF_dxgmms1!VidSchiProcessDpcCompletedPacket+38e
-------------------------------------------------------------------------------------------------------------------------------------------
STOP 0x00000050: PAGE_FAULT_IN_NONPAGED_AREA
Usual causes:  Defective hardware (particularly memory - but not just RAM), Faulty system service, Antivirus, Device driver, NTFS corruption, BIOS
Probably caused by : afd.sys ( afd!AfdFreeEndpointResources+157 ) - Ancillary Function Driver for WinSock, a Windows Driver
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
IMAGE_NAME:  afd.sys
FAILURE_BUCKET_ID:  X64_0x50_afd!AfdFreeEndpointResources+157
-------------------------------------------------------------------------------------------------------------------------------------------
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'+487ad )
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME:  plugin-contain
FAILURE_BUCKET_ID:  X64_0x1E_VRF_nt!_??_::FNODOBFM::_string_+487ad
-------------------------------------------------------------------------------------------------------------------------------------------
STOP 0x000000C4: DRIVER_VERIFIER_DETECTED_VIOLATION
Usual causes:  Device driver - see parameters for more information
Probably caused by : nvlddmkm.sys ( nvlddmkm+858df ) - nVidia Video drivers
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME:  hl2.exe - A Steam process
IMAGE_NAME:  nvlddmkm.sys
FAILURE_BUCKET_ID:  X64_0xc4_91_VRF_nvlddmkm+858df
-------------------------------------------------------------------------------------------------------------------------------------------
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'+487ad )
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME:  MsMpEng.exe - MSE process
FAILURE_BUCKET_ID:  X64_0x1E_VRF_nt!_??_::FNODOBFM::_string_+487ad
-------------------------------------------------------------------------------------------------------------------------------------------
Same as #4 above 
-------------------------------------------------------------------------------------------------------------------------------------------
STOP 0x000000C4: DRIVER_VERIFIER_DETECTED_VIOLATION
Usual causes:  Device driver - see parameters for more information
Probably caused by : Rt64win7.sys ( Rt64win7+2851 ) - Realtek RTL8168D/8111D Family PCI-E Gigabit Ethernet NIC
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME:  firefox.exe
FAILURE_BUCKET_ID:  X64_0xc4_91_VRF_Rt64win7+2851

First and second are blaming DirectX and indicating Steam is involved, let's see if other drivers come up,

Third, not being Driver Verifier caused, is hardware caused. RAM is most likely, next hard drive, with Directx mentioned above it also implicates the graphic card.

Forth, Also hardware blamed, verifier enabled, points to RAM, including graphics card.

Fifth, is directly blaming Steam. Info found mentions that running other programs while gaming can cause this crash, due to the resources required.

Sixth, blaming hardware, mentions MSE.

Seventh, same as the forth.

Eighth, similar to the fifth, blaming Firefox.

App Events Log:

Code:

Event[42477]:
  Log Name: Application
  Source: Application Error
  Date: 2012-10-21T19:19:10.000
  Event ID: 1000
  Task: Application Crashing Events
  Level: Error
  Opcode: Info
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Veggies-PC
  Description: 
Faulting application name: Steam.exe, version: 1.0.1446.623, time stamp: 0x5004ae1a
Faulting module name: libcef.dll, version: 1.989.464.0, time stamp: 0x502d6408
Exception code: 0xc0000005
Fault offset: 0x005c8e1f
Faulting process id: 0xc1c
Faulting application start time: 0x01cdafe3b090493a
Faulting application path: C:\Program Files (x86)\Steam\Steam.exe
Faulting module path: C:\Program Files (x86)\Steam\bin\libcef.dll
Report Id: dcf2bf7f-1bee-11e2-af90-c86000cefd2e


Event[42478]:
  Log Name: Application
  Source: Windows Error Reporting
  Date: 2012-10-21T19:19:20.000
  Event ID: 1001
  Task: N/A
  Level: Information
  Opcode: Info
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Veggies-PC
  Description: 
Fault bucket , type 0
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: Steam.exe
P2: 1.0.1446.623
P3: 5004ae1a
P4: libcef.dll
P5: 1.989.464.0
P6: 502d6408
P7: c0000005
P8: 005c8e1f
P9: 
P10: 

Attached files:

These files may be available here:
C:\Users\Veggies\AppData\Local\Microsoft\Windows\WER\ReportArchive\AppCrash_Steam.exe_9942fa8be44c83316a83c773fec5431eac3a919_0a823516

Analysis symbol: 
Rechecking for solution: 0
Report Id: dcf2bf7f-1bee-11e2-af90-c86000cefd2e
Report Status: 0

Code:

Event[42382]:
  Log Name: Application
  Source: Application Error
  Date: 2012-10-20T23:24:42.000
  Event ID: 1000
  Task: Application Crashing Events
  Level: Error
  Opcode: Info
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Veggies-PC
  Description: 
Faulting application name: javaw.exe, version: 7.0.70.11, time stamp: 0x5049b022
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x0000000000000000
Faulting process id: 0xdd4
Faulting application start time: 0x01cdaf4a41decba7
Faulting application path: C:\Program Files\Java\jre7\bin\javaw.exe
Faulting module path: unknown
Report Id: ff92599c-1b47-11e2-b0f0-c86000cefd2e

Update Java.

Code:

Event[42310]:
  Log Name: Application
  Source: Application Hang
  Date: 2012-10-20T13:02:48.000
  Event ID: 1002
  Task: N/A
  Level: Error
  Opcode: Info
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Veggies-PC
  Description: 
The program dota.exe version 0.0.0.0 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Action Center control panel.
 Process ID: 7c0
 Start Time: 01cdaefbb8d0460a
 Termination Time: 2840
 Application Path: C:\Program Files (x86)\Steam\steamapps\common\dota 2 beta\dota.exe
 Report Id: 

Event[42308]:
  Log Name: Application
  Source: Windows Error Reporting
  Date: 2012-10-20T13:00:22.000
  Event ID: 1001
  Task: N/A
  Level: Information
  Opcode: Info
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Veggies-PC
  Description: 
Fault bucket , type 0
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: Steam.exe
P2: 1.0.1446.623
P3: 5004ae1a
P4: libcef.dll
P5: 1.989.464.0
P6: 502d6408
P7: c0000005
P8: 005c8e1f
P9: 
P10: 

Attached files:
C:\Users\Veggies\AppData\Local\Temp\WER8B5D.tmp.appcompat.txt
C:\Users\Veggies\AppData\Local\Temp\WER90F9.tmp.WERInternalMetadata.xml
C:\Users\Veggies\AppData\Local\Temp\WER9129.tmp.hdmp
C:\Users\Veggies\AppData\Local\Temp\WER96A6.tmp.mdmp

These files may be available here:
C:\Users\Veggies\AppData\Local\Microsoft\Windows\WER\ReportQueue\AppCrash_Steam.exe_9942fa8be44c83316a83c773fec5431eac3a919_cab_0bd19896

Analysis symbol: 
Rechecking for solution: 0
Report Id: c512867c-1af0-11e2-be0a-c86000cefd2e
Report Status: 4

Either Steam is crashing or you have hardware that is crashing Steam.

Run SeaTools extended test.

If SeaTools and memtest86+ passes, it's leaving the mother board as about all that's left.
You can try a OS Clean install, before we blame the motherboard.

JMV2009 · 23 Oct 2012

Run hcidesign / memtest.

It detects errors for me which memtest86 doesn't.

EatYaVeggies · 29 Oct 2012

Installed the second stick and ran memtest 86+ v4.20 for eight full passes and no errors.

Ran Seatools and did not get any errors on the long generic test.

Lastly, I went to the event viewer and it seems to be making logs, just not adding them to to my SF folder.

JMV2009 · 30 Oct 2012

Run memtest from hcidesign

It detects errors for me which memtest86 doesn't.

Dave76 · 30 Oct 2012

I've just reviewed the thread, the things that keep coming up is the CPU test/OCCT crashes and the fluctuating Vcore.
Considering all the other tests you have ran, this indicates motherboard and/or PSU.
Since you have changed the motherboard and RAM and still have the same issues, you need to test with another PSU.

EatYaVeggies · 31 Oct 2012

Damn, I don't have another one to test. While I try to get one, I'll try switching the CPU(I know it has little chance of changing anything, but its the only hardware I have an spare of for now. ) Also will try reinstalling the OS soon. If both prove unsuccessful, I'll get another PSU. and finally if that doesn't work, I'll send my mobo to the manufacturer for since it is still under warranty.

Thanks for all the help. I'll check back when I've done some of this.

Dave76 · 31 Oct 2012

Sounds like a good plan, let me know the results.

EatYaVeggies · 02 Nov 2012

quick question. With my current set-up, how powerful of a PSU do I need for testing? Just want to know as a less beefy one would be easier to come by.