Windows 10: BSOD irql not less or equal after upgrading cpu. hardware or software?

Upgraded CPU and started getting IRQL Not Less or Equal BSOD. Everything was working fine before the upgrade.
Might be a hardware issue, but just want to get confirmation.

Upgraded from Intel E6500 to Intel Q9400 on a Asus P5Q Pro Turbo MB.
Videocard Geforce 8800GT
4 GB of DDR2 RAM
Do not know what other information is needed, but any help would be welcomed.

upgraded bios but to no

Attachment 49181

:)

 

IRQL Less or Equal BSOD

Shared items 10-22-2017

Worked out how to upload the files. Will check out the other things you linked in the meantime, thanks for the response!

 

IRQL Less or Equal BSOD

Hi,

BugCheck A, {fffffb6bc0138000, 2, 0, fffff803588dea56}
*** WARNING: Unable to verify timestamp for RTL8192su.sys

*** ERROR: Module load completed but symbols could not be loaded for RTL8192su.sys

Probably caused by : RTL8192su.sys ( RTL8192su+17f9a ) <- RealTek NIC driver.

BugCheck C4, {2004, ffff9688c5958ca8, fffff8005d110200, ffffd70168f696b8}
Probably caused by : ntkrnlmp.exe ( nt!VerifierBugCheckIfAppropriate+6b ) <- Windows component which means something else drove it into Fault.

RTL8192su.sys dated 3/28/2013 RealTek Network driver.

tosrfcom.sys dated Toshiba Bluetooth RFCOMM Driver.

Update those at Toshiba - Check with their support, on-line documentation & drivers, and check their forums.

Toshiba - Support

http://www.csd.toshiba.com/cgi-bin/tais/support/jsp/home.jsp



Toshiba - Contacts

http://www.csd.toshiba.com/cgi-bin/tais/support/jsp/navShell.jsp?cf=su_contact

Toshiba - Drivers - navigate to your model

http://www.csd.toshiba.com/cgi-bin/tais/support/jsp/home.jsp?nav=Download

Toshiba - Forums (The forums are no longer active however their is so help at this link in the form of KB Articles and How-To Videos.)

Not Available

See ALL the methods in my previous reply.

Hope this helps.

--------------------------------------------------------------------------------------------

Rob Brown -
Microsoft MVP <- profile - Windows and Devices for IT : Bicycle - Mark Twain said it right.

 

Hello Blackcalvus and welcome to the Forums. I looked at your dump files and found

Code: Use !analyze -v to get detailed debugging information. BugCheck 1000007E, {ffffffffc000001d, fffff80171ff857e, ffffd001a8d785d8, ffffd001a8d77df0} Probably caused by : hardware ( dxgmms1!VidSchiSendToExecutionQueue+59e ) Followup: MachineOwner[/quote] That is not always Hardware. It can be hardware failing or can be a driver causing the hardware to act like it is failing.

Code: STACK_TEXT: ffffd001`a8d78810 fffff801`7201e40e : ffffe000`9545b5e0 ffffe000`9545b5e0 ffffe000`90de5a60 ffffe000`90de6000 : dxgmms1!VidSchiSendToExecutionQueue+0x59e ffffd001`a8d78920 fffff801`72037f12 : ffffe000`9545b5e0 ffffe000`90de6000 ffffe000`00000000 ffffe000`00000005 : dxgmms1!VidSchiSubmitRenderCommand+0x5ee ffffd001`a8d78c70 fffff801`72037e5d : ffffe000`90de6000 00000000`00000080 ffffe000`903c3840 ffffe000`903c3800 : dxgmms1!VidSchiRun_PriorityTable+0xb2 ffffd001`a8d78cc0 fffff800`bf5746d8 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWorkerThread+0x8d ffffd001`a8d78d00 fffff800`bf5e0d06 : ffffd001`a3fce180 ffffe000`90de7840 ffffd001`a3fdabc0 00000000`00000000 : nt!PspSystemThreadStartup+0x58 ffffd001`a8d78d60 00000000`00000000 : ffffd001`a8d79000 ffffd001`a8d73000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16[/quote] That shows it appears to be the Video Card or the Graphics drivers.

Code: Use !analyze -v to get detailed debugging information. BugCheck D1, {ffffe0012db748a9, 2, 0, fffff8004820de76} Probably caused by : hardware ( USBPORT!USBPORT_Core_ProcessScatterGatherList+4b6 ) Followup: MachineOwner[/quote] That says it is the USB Ports.

Code: IRQL_NOT_LESS_OR_EQUAL (a) An attempt was made to access a pageable (or completely invalid) address at an interrupt request level (IRQL) that is too high. This is usually caused by drivers using improper addresses. If a kernel debugger is available get the stack backtrace. Arguments: Arg1: ffffe009a9641828, memory referenced Arg2: 0000000000000002, IRQL Arg3: 0000000000000000, bitfield : bit 0 : value 0 = read operation, 1 = write operation bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status) Arg4: fffff802f7c28435, address which referenced memory[/quote] What I would like to do is for you to go to Download Drivers
and see if you can find a Windows 10 driver for your graphics card. Uninstall your current drivers and the run DDU (Display Driver Uninstaller: How to use - Windows 7 Help Forums) to clean them all out. Be sure and only check the AMD Graphics driver box. Then install the new drivers using the custom install and try to only install the Graphics driver.

Next please right click on the start icon and select Command prompt administrator, give admin permissions and copy/paste this into the window that opens and press enter sfc /scannow . If you decide to type it in, please notice the space between the sfc and the /. We want it to say no integrity violations were found. If it says there where corrupt files that could not be repaired, please reboot and run it again. You may have to run it 3 times with reboots in between each time.

Let me know if that makes any difference for you.

 

Hello essenbe,
thanks for your help, i will try to follow your instructions. The only think so far is that the "download drivers", it's pointing me towards AMD drivers and not the nvidia drivers. Should i be going to the nvidia website instead?

 

Yes, I'm sorry I put in the wrong link. It should be the Nvidia Web Site Download Drivers | NVIDIA and with DDU Uninstaller check the Nvidia Graphics drivers only. Then the Custom install and only check the Graphics driver and PhysX driver and make sure the clean install box is checked. I'm sorry for the confusion. It was my fault. I am glad you asked.