BSOD IRQL not less or equal after installing new CPU

[enknaran202]

I installed a new Intel I5 4590 and visited a systemrequirementslab.com and it told me I had an Intel(R) Pentium(R) CPU G3258 @ 3.20GHz. I launched Speccy and that confirmed I had an Intel i5.
I ignored the misnomer and launched a game. It crashed after 30 minutes. Then a bsod with the error Driver IRQL not less or equal popped up. It has happened three times in total. I am 90% certain it was my new CPU but i checked the Intel Driver Update Utility and that told me there were no drivers found for my product.

My build:
Win 8.1 64 bit

Intel Core i5 4590 @ 3.30GHz (New Part)

8.00GB Single-Channel DDR3 @ 799MHz

ASRock H97M Anniversary (CPUSocket)

2047MB NVIDIA GeForce GTX 750 Ti (EVGA)

931GB Seagate ST1000DM003-1ER162 (SATA)

And my MiniDump file for the past couple BSODs

http://s000.tinyupload.com/?file_id=54479831524380560398

http://s000.tinyupload.com/?file_id=76186566525437794473

Any sort of help would be great

 

[johnbl]

you might also consider getting a bios update:
http://www.asrock.com/mb/Intel/H97M%20Anniversary/?cat=Download&os=BIOS

I did not see a fix relating to USB, but the BIOS setups the electronics for the USB and old versions tend to have bugs.
you have version p1.02 dated 08/04/2014
the current version is 2.2 dated 7/31/2015 (be sure to pick up any updated drivers also, updated BIOS and updated USB drivers should go together)

note: the actual driver that failed was
Intel Keyboard Class Upper Filter Driver (but I think it is going to be a bug in another usb driver)

well the system bugcheck because something connected to your USB tried to write to read only memory.

you have Apple iPod/iPhone Mobile USB device driver usbaapl64.sys running these are often used to charge apple devices on a PC but they attempt to override the max current that is allowed on a USB port. This can cause the USB hub to think there is a short circuit and shutdown the hub. Really causes a problem when you have USB storage. (you might remove the driver to see if it is the cause of your problem)

you also have a driver 033a608e-396 these are made up from random numbers so you can not google to find out what it is.
it might be a serial number for product. You might want to find out what it is for.

anyway, I think your problem will be in the USB hub or a device connected to the USB hub.
Minidumps don't save the required debug info and logs to debug USB problems, you have to change the memory dump type to a kernel memory dump to save the debug info.
https://www.sophos.com/en-us/support/knowledgebase/111474.aspx
(select kernel memory dump, the file saved will be c:\windows\memory.dmp)