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

[EatYaVeggies]

Can't get any charts since it crashes, but the latest 3 dumps were from it crashing.

I'll keep trying, if I see it make it past 5 minutes ill stop it just to get the charts.

EDIT: Just ran it again and Got this message: An error has occurred - Attempted to read or write to protected memory. This is often an indication that other memory is corrupt. Then it goes on to say to send an error report or not to the makers of OCCT.

 

[Dave76]

What were the CPU core temps while running OCCT?

The error message can be indicating system RAM or GPU RAM.

Is the DRAM voltage still set to 1.550v?
Change the Cpu/NB Offset Voltage to 1.300v.

Run OCCT again.

If it fails, test your graphics card.
Video Card - Stress Test with Furmark

Two of your last crashes blames or was attributed to OCCT.

STOP 0x0000001E: KMODE_EXCEPTION_NOT_HANDLED    (go to top of page)
Usual causes:  Device driver, hardware, System service, compatibility, Remote control programs, memory, BIOS
IMAGE_NAME:  dxgkrnl.sys - DirectX Graphics Kernel
FAILURE_BUCKET_ID:  X64_0x1E_dxgkrnl!DxgkCddUnlock+118

Run the dxdiag tool.
DirectX Diagnostic Tool

 

[EatYaVeggies]

The max temp i saw any core go to was 49, but mostly they stayed at 47-48.

DRAM voltage is still at 1.550v-raised the CPU/NB offset from 1.200v to 1.300v

Ran OCCT before change and after, crashed both times.

Ran Furmark-temp evened out at 72, and occasionally briefly went to 73. Ran it for ten minutes. Nothing makes my GPU fan spin like furmark lol. Took a screencap in case theres any info you needed.

Ran dxdiag, and every tab had no problems at the bottom.

 

[JMV2009]

underclock

Try to underclock your cpu and/or gpu and/or memory

 

[Dave76]

The Furmark temps and test look good.

Move the RAM card to slot #1.

If OCCT says it failed it should generate the graphs, if it had enough time before the blue screen.
Look for the OCCT graphs in C:\(your user name)\My Documents\OCCT folder.
Run OCCT Power Supply test, it uses LinPack and tests graphics, set it to test for 20 minutes before you start it.
Let's try this as you mentioned it passed Linpack before.

Is your PC Power and Cooling PSU model a Silencer or Silencer MK II?

If OCCT won't run and generate the graphs, you may want to replace, for testing, some of the hardware components, can you borrow some for testing?
I would recommend in this order, graphics card, PSU, and since you have a CPU available for testing, you might as well try it also.

You last 6 crashes:

STOP 0x0000001E: KMODE_EXCEPTION_NOT_HANDLED
Usual causes:  Device driver, hardware, System service, compatibility, Remote control programs, memory, BIOS
This is a very common bugcheck.
Probably caused by : USBPORT.SYS ( USBPORT!USBPORT_Core_IncIoRequestCount+c3 )
PROCESS_NAME:  prime95.exe
IMAGE_NAME:  USBPORT.SYS
-------------------------------------------------------------------------------------------------------------------------------------
STOP 0x0000003B: SYSTEM_SERVICE_EXCEPTION - An exception happened while executing a system service routine.
Usual causes:  System service, Device driver, graphics driver, ?memory
Probably caused by : nvlddmkm.sys ( nvlddmkm+1e2854 )
This error has been linked to excessive paged pool usage and may occur due to user-mode graphics drivers crossing over and passing bad data to the kernel code.
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
PROCESS_NAME:  OCCT.exe
IMAGE_NAME:  nvlddmkm.sys
FAILURE_BUCKET_ID:  X64_0x3B_nvlddmkm+1e2854
-------------------------------------------------------------------------------------------------------------------------------------
STOP 0x0000001E: KMODE_EXCEPTION_NOT_HANDLED
Usual causes:  Device driver, hardware, System service, compatibility, Remote control programs, memory, BIOS
This is a very common bugcheck.
Probably caused by : dxgkrnl.sys ( dxgkrnl!DxgkCddUnlock+118 )
PROCESS_NAME:  csrss.exe
IMAGE_NAME:  dxgkrnl.sys
FAILURE_BUCKET_ID:  X64_0x1E_dxgkrnl!DxgkCddUnlock+118
-------------------------------------------------------------------------------------------------------------------------------------
STOP 0x0000001E: KMODE_EXCEPTION_NOT_HANDLED
Usual causes:  Device driver, hardware, System service, compatibility, Remote control programs, memory, BIOS
This is a very common bugcheck.
Probably caused by : USBPORT.SYS ( USBPORT!USBPORT_Xdpc_iSetState+2a )
PROCESS_NAME:  prime95.exe
IMAGE_NAME:  USBPORT.SYS
FAILURE_BUCKET_ID:  X64_0x1E_USBPORT!USBPORT_Xdpc_iSetState+2a
-------------------------------------------------------------------------------------------------------------------------------------
STOP 0x0000001E: KMODE_EXCEPTION_NOT_HANDLED
Usual causes:  Device driver, hardware, System service, compatibility, Remote control programs, memory, BIOS
This is a very common bugcheck.
Probably caused by : USBPORT.SYS ( USBPORT!USBPORT_Core_iIrpCsqCompleteDoneTransfer+1c8 )
PROCESS_NAME:  prime95.exe
IMAGE_NAME:  USBPORT.SYS
FAILURE_BUCKET_ID:  X64_0x1E_USBPORT!USBPORT_Core_iIrpCsqCompleteDoneTransfer+1c8
-------------------------------------------------------------------------------------------------------------------------------------
STOP 0x0000001E: KMODE_EXCEPTION_NOT_HANDLED
Usual causes:  Device driver, hardware, System service, compatibility, Remote control programs, memory, BIOS
This is a very common bugcheck.
Probably caused by : USBPORT.SYS ( USBPORT!USBPORT_Xdpc_Worker+1d9 )
PROCESS_NAME:  prime95.exe
IMAGE_NAME:  USBPORT.SYS
FAILURE_BUCKET_ID:  X64_0x1E_USBPORT!USBPORT_Xdpc_Worker+1d9

Most of these are caused by Prime95 and OCCT testing programs. Blaming the USBPORT may be due to a device connected to a USB port.

First crash: Do you have another keyboard and mouse you can use for testing?
The USBPORT is blamed, IO request.
If you have any other USB devices connected, remove them for testing, let me know what they are if you have any.

Second crash: blames the graphics driver.


Problem Devices;
ATK0110 ACPI UTILITY ACPI\ATK0110\1010110 39
AsIO ROOT\LEGACY_ASIO\0000 This device is not present, is not working properly, or does not have all its drivers installed.
AsUpIO ROOT\LEGACY_ASUPIO\0000 This device is not present, is not working properly, or does not have all its drivers installed.


AsIO - Asus PCProbe Utility

AsUpIO - ASUS hardware monitoring software related

Have you updated all the drivers from your motherboard support site?
Asus M5A88-m support

What BIOS version are you using?
The latest is M5A88-M BIOS 1401 - 2012.09.11, the description is 'Improve system stability'.
Update to this version if you don't have it now.

Have you ran a HDD test?
Download and run Seatools on your HDD.
How to use SeaTools for Windows
Short Drive Self Test and Long Drive Self Test.

To be sure none of the Win7 system files are corrupt run the System File Checker.
SFC /SCANNOW Command - System File Checker
Use Option Two, and #2 To Scan and Repair System Files
If it says it can't fix files with errors, re-boot and run it a minimum of three times with re-boots after each run.
It does the repairs when re-booting.

 

[EatYaVeggies]

Switched the RAM back to slot one. OCCT has never produced charts. The only ones I have are ones I got from it when I accidentally stopped it a second or two after the idle period.

I don't think I ever talked about passing a Linpack before. Anyway ran the Power supply test and after 5-6 minutes, I got the "OCCT has stopped working" Message and windows closed the main interface, but the fur rendering window stayed up. I closed that and noticed that my CPU and RAM were still being used, and task manager revealed that Linpack was still running in my processes.

I might be able to get a graphic card, but not a PSU. Then I already have the CPU. I'm guessing I don't want to use the on board graphics.

I changed my mouse from usb to ps/2 and now Prime95 doesn't crash anymore. Don't know how relavent this is, but found it interesting.

 

[Dave76]

Let OCCT run for as long as you think you can, then stop it and post the graphs.
As long as it runs the test for several minutes.
Five minutes might give us some information.

Intel Burn test is based on LinPack.

I will continue editing post #25 with the last crash info, so check it a couple of times.

 

[EatYaVeggies]

Ya I changed to a ps/2 mouse after I posted that. The only other usb device im using is the keyboard as this motherboard has only 1 ps/2 input.

I just completely wiped my video drivers, then swept them with driver sweeper, then installed the newest drivers and made it to 5 minutes, stopped and got graphs for the CPU:OCCT test.

And I did flash my bios with that one shortly after it came out.

And as far as I know, I up to date on every motherboard update except the ATI catalyst you told me to uninstall.

 

[Dave76]

Good info.

Check Post #25 for the additional info and recommended tests to run.

Did you get Linpack stopped?

Hope the new graphics drivers will help, cleaning them up with Driver Sweeper should be a help.

The OCCT graphs look good, voltages seem to be stable.

If you can borrow a graphics card for testing it would help to eliminate the card and verify the PCIe slot on the motherboard.
A PSU can cause a lot of different issues, the OCCT graphs are showing it to be stable so no need for that, might have to come back to it later.
Don't change the CPU until the other testing is done, other components are more likely to be the cause, at this point.

Very relevant interesting news on the mouse, keep the PS2 mouse connected for the testing.
A bad mouse and keyboard can cause a lot of hard to find issues.
If issues continue, find another keyboard to test with.

Good info on the BIOS and drivers.

Run the other tests in post #25, and let me know the results.

 

[EatYaVeggies]

I have run Seatools (all tests except advanced). Sorry, guess I forgot to mention that at the start of the thread.

Ran SFC scan and it didn't find any errors.

Should I run the CPU OCCT test again and go for a longer time, or the Power Supply test?

Or should i do something else?

Oh and I stopped the linpack process though task manager.

 

[Dave76]

When did you run SeaTools?

Did you run the SFC scan today?
Having a lot of BSoDs can cause OS corruption, best to run it today if you haven't.

Run the OCCT Power Supply test again, it will test the graphics card and the graphics card memory, which I suspect.
The GTX460 is not known as one of nVidia's most stable cards.

Borrow another graphics card to test in your system.

 

[EatYaVeggies]

Ran Seatools the 4th( going off when I installed it) so might be a little later.

Ran SFC Scan after you told me to ( didn't even know about it before that.)

EDIT: Ran Power supply test for 10 minutes, got through it. Think I'm gonna try the 20 minute run now.

 

[Dave76]

The OCCT graphs look pretty good.

If OCCT runs for 20 minutes, then run it again for 30 Minutes.

Let me know the results.

 

[EatYaVeggies]

Getting BSOD again while trying to run OCCT. System Service Exceptions

 

[Dave76]

Not much useful info on the last two crashes.
Crash reports don't have any new info.
Event Logs end on the 20th.

What was the brand of the mouse you removed?
Do you have any drivers installed for that mouse?
If you did, uninstall them.

Swap out the keyboard when you can, will have to be a USB.

 

[EatYaVeggies]

Sorry about that, must have forgot to update all the info on the SF Tool. Should be up to date now.

The removed mouse was a razor and I never installed its drivers on this installation.

I have been on a usb keyboard since I switched to just a usb Microsoft mouse( with a ps2 adapter). The new keyboard is the only usb device plugged in atm.

 

[Dave76]

You event logs only went to 23rd.

Your last two crashes:

STOP 0x000000D1: DRIVER_IRQL_NOT_LESS_OR_EQUAL
Usual causes:  Device driver
Probably caused by : nvlddmkm.sys ( nvlddmkm+1c9a49 )
PROCESS_NAME:  FlashPlayerPlu
SYMBOL_NAME:  nvlddmkm+1c9a49
IMAGE_NAME:  nvlddmkm.sys
---------------------------------------------------------------------
STOP 0x0000003B: SYSTEM_SERVICE_EXCEPTION
Usual causes:  System service, Device driver, graphics driver, ?memory
PROCESS_NAME:  explorer.exe
FAILURE_BUCKET_ID:  X64_0x3B_win32k!HANDLELOCK::vLockHandle+51

Borrow another graphics card and test with it.

Can you get another keyboard to test with?

 

[EatYaVeggies]

So a third keyboard? Cause I've only been using my current one for a few days ( since I switched my mouse).

Should be able get one if that's the case and should be able to borrow a graphics card tomorrow.

 

[Dave76]

Didn't know you switched the keyboard already, no need to do it again if you're sure it's good.

Let us know your status with the other graphics card.

 

[EatYaVeggies]

The keyboard should be fine. Think it came with one computer we've bought at some point and no one needed it. Was still in its box and everything.

Installed the other graphics card (its a GTS 250) BSOD on the first try of OCCT, then bluescreened again on the windows log in screen. Then I got the "OCCT has stopped working" message twice ( both times the program actually stressing the system did not close, so had to close it manually.)

The second time, I tried it with no keyboard connected (just in case). Actually shut down to stop the stressing program that time, as I had no CTRL+ALT+DEL.

Finally tried to force a browser video BSOD and got that too after 20-30 minutes.(Again with no keyboard plugged in.)