Windows 7 - BSOD -Full Info Provided. irql_not_less_or_equal

Maddog12 · 02-04-2012

I have uploaded all the infomation required (i think), this BSOD is pretty much random, i do not run many programs at a time, mainly internet browser, and p2p file transfer program.
I have Norton 360 installed, fully updated and scans show no virus. Windows updated are set to automatic.
Hopefully someone can help with this, if any more info is required, could you tell me where to find it please?
My OS is OEM.
System is about 2 year old.

See attached file for BSOD info.
Thanks

edit: Sytem Spec is here

System Manufacturer/Model Number Acer/Aspire 5750
OS Windows 7 Home Premium 64bit SP1
CPU Intel Core i3-2310M @2.10Ghz 2 Cores, 4 Logical Processors
Motherboard N/A
Memory 6GB RAM,
Graphics Card(s) Intel HD
Sound Card Realtek High Definition Audio
Monitor(s) Displays Generic Pnp Monitor
Screen Resolution 1366x768x60 hertz
Hard Drives c: WDC WD6400BPVT-22HXZT1 600gb(Original in laptop)
d: MATSHITA DVD-RAM UJ8A0AS (Original in laptop)
PSU N/A
Case N/A
Cooling N/A
Keyboard 'Standard PS/2'
Mouse Synaptics PS/2 Port TouchPad
Internet Speed N/A
Other Info N/A

usasma · 02-04-2012

Please run Driver Verifier according to these directions: Driver Verifier Settings . Let it crash 2 or 3 times before collecting the memory dumps.
To try and make it crash, work in McAfee Family Protection and Norton 360 and/or watch a movie or play a game (that's my hunch as to what's wrong).

Further info on BSOD error messages available at: http://www.carrona.org/bsodindx.html

The following info is just FYI, I've already addressed the issues that I saw in the above paragraphs:
3RD PARTY DRIVERS PRESENT IN THE DUMP FILES
- Create a System Restore Point prior to doing any of this. DO NOT mess with the drivers themselves - leave the Windows\System32\drivers directory alone unless we specifically direct you to it!
- Please either update the older drivers from the device manufacturer's website - or uninstall them from your system. Reference links are included below.
- DO NOT use Windows Update or the Update Drivers function of Device Manager.
- Please feel free to post back about any drivers that you are having difficulty locating.
- Windows Update exceptions may be noted below for Windows drivers.

Code:


amdxata.sys             Fri Mar 19 12:18:18 2010 (4BA3A3CA)
iaStor.sys              Mon Sep 13 21:23:32 2010 (4C8ECE94)
SYMNETS.SYS             Tue Apr 19 18:33:31 2011 (4DAE0DBB)
SYMEVENT64x86.SYS       Thu Mar 24 19:02:36 2011 (4D8BCD8C)
SYMDS64.SYS             Tue Dec 07 19:16:58 2010 (4CFECE7A)
SRTSPX64.SYS            Tue Mar 29 22:46:18 2011 (4D92997A)
SYMEFA64.SYS            Sun Mar 13 23:20:58 2011 (4D7D899A)
Ironx64.SYS             Fri Nov 12 18:06:50 2010 (4CDDC88A)
eeCtrl64.sys            Fri Oct 21 21:18:28 2011 (4EA219E4)
EraserUtilRebootDrv.sys Fri Oct 21 21:18:29 2011 (4EA219E5)
dump_iaStor.sys         Mon Sep 13 21:23:32 2010 (4C8ECE94)
SynTP.sys               Thu Jul 29 23:26:57 2010 (4C524681)
UBHelper.sys            Tue Jul 06 00:19:26 2010 (4C32AECE)
NTIDrvr.sys             Mon Apr 19 21:37:59 2010 (4BCD0577)
GEARAspiWDM.sys         Mon May 16 16:56:05 2011 (4DD18F65)
k57nd60a.sys            Mon Jan 17 19:52:37 2011 (4D34E455)
BHDrvx64.sys            Wed Nov 23 14:32:10 2011 (4ECD4A3A)
nusb3hub.sys            Thu Sep 30 00:00:03 2010 (4CA40B43)
igdkmd64.sys            Fri Mar 25 21:17:43 2011 (4D8D3EB7)
bScsiMSa.sys            Wed Jan 19 23:28:06 2011 (4D37B9D6)
b57xdbd.sys             Thu Jan 20 21:13:45 2011 (4D38EBD9)
Sftfslh.sys             Mon Sep 13 18:03:14 2010 (4C8E9FA2)
Sftplaylh.sys           Mon Sep 13 18:03:15 2010 (4C8E9FA3)
Sftredirlh.sys          Mon Sep 13 18:03:26 2010 (4C8E9FAE)
HECIx64.sys             Tue Oct 19 19:33:43 2010 (4CBE2AD7)
bScsiSDa.sys            Thu Jan 13 21:21:56 2011 (4D2FB344)
Sftvollh.sys            Mon Sep 13 18:02:56 2010 (4C8E9F90)
RTKVHD64.sys            Tue Mar 15 06:27:07 2011 (4D7F3EFB)
IntcDAud.sys            Fri Oct 15 04:28:17 2010 (4CB810A1)
b57xdmp.sys             Thu Jan 20 21:13:47 2011 (4D38EBDB)
ENG64.SYS               Fri Jul 29 09:17:51 2011 (4E32B2FF)
SRTSP64.SYS             Tue Mar 29 22:46:12 2011 (4D929974)
IDSvia64.sys            Tue Nov 22 15:23:23 2011 (4ECC04BB)
EX64.SYS                Fri Jul 29 09:15:11 2011 (4E32B25F)
athrx.sys               Thu Oct 28 20:29:03 2010 (4CCA154F)
nusb3xhc.sys            Thu Sep 30 00:00:03 2010 (4CA40B43)
IDSvia64.sys            Wed Jul 20 09:19:46 2011 (4E26D5F2)

Code:


Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\020412-22885-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Sat Feb  4 07:17:02.925 2012 (UTC - 5:00)
System Uptime: 0 days 2:29:39.800
Probably caused by : dxgmms1.sys ( dxgmms1!VidMmiProcessTerminationCommand+5f )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xA_dxgmms1!VidMmiProcessTerminationCommand+5f
Bugcheck code 0000000A
Arguments 00000000`00000000 00000000`00000002 00000000`00000000 fffff800`02c84c02
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\012212-21278-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Sun Jan 22 10:16:16.244 2012 (UTC - 5:00)
System Uptime: 0 days 0:17:52.545
Probably caused by : dxgmms1.sys ( dxgmms1!VidMmiProcessTerminationCommand+5f )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xA_dxgmms1!VidMmiProcessTerminationCommand+5f
Bugcheck code 0000000A
Arguments 00000000`00000000 00000000`00000002 00000000`00000000 fffff800`02cdcc02
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\011612-23883-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Mon Jan 16 16:08:06.115 2012 (UTC - 5:00)
System Uptime: 0 days 3:28:14.379
Probably caused by : dxgmms1.sys ( dxgmms1!VidMmiProcessTerminationCommand+5f )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xA_dxgmms1!VidMmiProcessTerminationCommand+5f
Bugcheck code 0000000A
Arguments 00000000`00000000 00000000`00000002 00000000`00000000 fffff800`02c8cc02
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

Maddog12 · 02-05-2012

Thanks for these directions, i have ran the verifier as it describes, highlighting all non-Microsoft drivers, and separately all Norton drivers for two separate re-boots. There have been no BSOD's, so i will let my system run continuously today and see if one occurs then, highlighting all non-Microsoft drivers.
If nothing happens, should i verify the Microsoft drivers?
Could this be a hardware problem as it references?
Thanks for your help

usasma · 02-05-2012

I usually don't suggest running Verifier on Microsoft drivers. This is because of:
- System File Checker's protection that helps keep the Microsoft drivers from getting corrupted.
- the ability to run sfc.exe /scannow and replace any corrupted files
- the ability to run a repair install to fix other problems.
- the ability to wipe the hard drive and reinstall Windows "clean" in order to rule out Windows drivers.
Please run Verifier for at least 36 hours as I described.

As for hardware, I would run Video stress tests (both the Furmark and the misc. tests) and Memory tests (both MemTest and Prime95) because of dxgmms1.sys being mentioned in the memory dumps (video driver for DirectX). These are free tests and I've described them all here: Hardware Diags

Good luck!

Maddog12 · 02-09-2012

I've run the verifier, no bsods. Als ran the sfc/scannow, nothing.
Ive ran Furmark, Prime95 and Memtest(to 150%), and also no problems.

I updated my DirectX with all available updates.
Any other suggestions?

usasma · 02-10-2012

I'm about out of ideas here.
Maybe malware? Try the free diags here: Free Online AntiMalware Resources
Then, either run the rest of the diags, or try a clean install of Windows.

Maddog12 · 02-12-2012

Got two more BSOD's today, right after each other. First one i was downloading a lot using P2p, not sure if thats a coincidence or not.
I ran some of the malware diags you mentioned, nothing out of the ordinary came up.
attached is the new data with the two bsods from today in there somewhere. There's a new PERFMON file in there as well, from today.
Do you think a clean install would solve any problems? Im not even entirely sure what the problem is...
Cheers for your help!

usasma · 02-13-2012

No network device listed in systeminfo32. Any idea of why that would happen?
Both wired and wireless are listed in MSINFO32

The Security Processor Loader device shows up as a Problem Device in MSINFO32. This is usually a sign of an infection, or of an incomplete repair of the damage that an infection has done.

Right now I think it's one of these:
- residuals of a malware infection
- video problems (either drivers or hardware)
- issues between McAfee and Norton.

Try uninstalling the McAfee and Norton and temporarily replace it with a free antivirus (just to see if the problem stops).

Beyond that, I'd either suggest getting more expert anti-malware help over in the Security forums - or backing up your stuff, wiping the hard drive clean, and then reinstalling Windows from your recovery disks. Here's a suggestion of how to do it:

Quote:

For testing purposes, it's best to install Windows "clean".
This is, basically, installing it the way that Microsoft intended (using drivers from Windows Update).
This procedure is for Windows 7, Vista is similar (but has 2 service packs)

You will need your installation/recovery DVD(s) before you start. Once you wipe the hard drive there's no going back!!!

1. Backup all your data.
This will wipe everything off of your hard drive, so anything that you want to keep will need to be saved elsewhere.

NOTE: If this is due to an infection, remember to scan the data with another system's current antivirus in order to locate and remove any malware.

2. Connect the system to the internet (if the system says disconnect from the Internet, then do so).

3. Use one of these free utilities to wipe the hard drive clean:
DBAN ( DBAN Download | Darik's Boot And Nuke )
KillDisk ( Freeware Download Active@ KillDisk ).
This will also delete any recovery partitions on the system - so the installation/recovery DVD's are essential!!!

4. Install Windows by booting from the installation/recovery DVD - DO NOT tweak any settings!!!

5. Visit Windows Update and get all updates

6. Check Device Manager for any unknown/disabled devices - if there are unknown/disabled devices, fix them with the latest drivers from the device manufacturer's website (not the PC Manufacturer)

7. Visit Windows Update and get Service Pack 1 (usually under Important Updates). Read these notes for installing SP1: Steps to follow before you install Windows 7 SP1 and Windows Server 2008 R2 SP1 from the Microsoft Download Center

8. Visit Windows Update and get any other available updates

9. Download, install, and update a free antivirus so you don't get infected while testing ( Free AntiVirus ).

If the problems persist, then the problem is most likely with your hardware.

CAVEAT: If you have an Asus motherboard, check the date on the C:\Windows\System32\driver\ASACPI.sys file. 2004/2005 is a problem, 2009/2010 is OK. Updates are available at the Asus support website.

CAVEAT: If you have a Sony system, make sure that you DO NOT have the 2007 (or earlier) version of the Sony Firmware Extension Parser (SFEP.sys). Update this driver immediately!!!

Further info on BSOD error messages available at: http://www.carrona.org/bsodindx.html

The following info is just FYI, I've already addressed the issues that I saw in the above paragraphs:
3RD PARTY DRIVERS PRESENT IN THE DUMP FILES
- Create a System Restore Point prior to doing any of this. DO NOT mess with the drivers themselves - leave the Windows\System32\drivers directory alone unless we specifically direct you to it!
- Please either update the older drivers from the device manufacturer's website - or uninstall them from your system. Reference links are included below.
- DO NOT use Windows Update or the Update Drivers function of Device Manager.
- Please feel free to post back about any drivers that you are having difficulty locating.
- Windows Update exceptions may be noted below for Windows drivers.

Code:


iaStor.sys              Mon Sep 13 21:23:32 2010 (4C8ECE94)
amdxata.sys             Fri Mar 19 12:18:18 2010 (4BA3A3CA)
SYMNETS.SYS             Tue Apr 19 18:33:31 2011 (4DAE0DBB)
SYMEVENT64x86.SYS       Thu Mar 24 19:02:36 2011 (4D8BCD8C)
SRTSPX64.SYS            Tue Mar 29 22:46:18 2011 (4D92997A)
SYMDS64.SYS             Tue Dec 07 19:16:58 2010 (4CFECE7A)
SYMEFA64.SYS            Sun Mar 13 23:20:58 2011 (4D7D899A)
Ironx64.SYS             Fri Nov 12 18:06:50 2010 (4CDDC88A)
HECIx64.sys             Tue Oct 19 19:33:43 2010 (4CBE2AD7)
BHDrvx64.sys            Wed Nov 23 14:32:10 2011 (4ECD4A3A)
dump_iaStor.sys         Mon Sep 13 21:23:32 2010 (4C8ECE94)
IDSvia64.sys            Tue Nov 22 15:23:23 2011 (4ECC04BB)
eeCtrl64.sys            Fri Jan 20 18:39:48 2012 (4F19FB44)
EraserUtilRebootDrv.sys Fri Jan 20 18:39:49 2012 (4F19FB45)
Sftfslh.sys             Mon Sep 13 18:03:14 2010 (4C8E9FA2)
Sftplaylh.sys           Mon Sep 13 18:03:15 2010 (4C8E9FA3)
Sftredirlh.sys          Mon Sep 13 18:03:26 2010 (4C8E9FAE)
igdkmd64.sys            Fri Mar 25 21:17:43 2011 (4D8D3EB7)
k57nd60a.sys            Mon Jan 17 19:52:37 2011 (4D34E455)
bScsiSDa.sys            Thu Jan 13 21:21:56 2011 (4D2FB344)
bScsiMSa.sys            Wed Jan 19 23:28:06 2011 (4D37B9D6)
b57xdbd.sys             Thu Jan 20 21:13:45 2011 (4D38EBD9)
SynTP.sys               Thu Jul 29 23:26:57 2010 (4C524681)
UBHelper.sys            Tue Jul 06 00:19:26 2010 (4C32AECE)
NTIDrvr.sys             Mon Apr 19 21:37:59 2010 (4BCD0577)
GEARAspiWDM.sys         Mon May 16 16:56:05 2011 (4DD18F65)
nusb3hub.sys            Thu Sep 30 00:00:03 2010 (4CA40B43)
athrx.sys               Thu Oct 28 20:29:03 2010 (4CCA154F)
nusb3xhc.sys            Thu Sep 30 00:00:03 2010 (4CA40B43)
Sftvollh.sys            Mon Sep 13 18:02:56 2010 (4C8E9F90)
RTKVHD64.sys            Tue Mar 15 06:27:07 2011 (4D7F3EFB)
IntcDAud.sys            Fri Oct 15 04:28:17 2010 (4CB810A1)
b57xdmp.sys             Thu Jan 20 21:13:47 2011 (4D38EBDB)
SRTSP64.SYS             Tue Mar 29 22:46:12 2011 (4D929974)
ENG64.SYS               Fri Jul 29 09:17:51 2011 (4E32B2FF)
EX64.SYS                Fri Jul 29 09:15:11 2011 (4E32B25F)

Code:


Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\021212-21949-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Sun Feb 12 10:43:42.857 2012 (UTC - 5:00)
System Uptime: 0 days 0:13:02.731
Probably caused by : dxgmms1.sys ( dxgmms1!VidMmiProcessTerminationCommand+5f )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xA_dxgmms1!VidMmiProcessTerminationCommand+5f
Bugcheck code 0000000A
Arguments 00000000`00000000 00000000`00000002 00000000`00000000 fffff800`02c84c02
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\021212-26894-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Sun Feb 12 10:30:18.846 2012 (UTC - 5:00)
System Uptime: 0 days 1:12:59.110
Probably caused by : dxgmms1.sys ( dxgmms1!VidMmiProcessTerminationCommand+5f )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xA_dxgmms1!VidMmiProcessTerminationCommand+5f
Bugcheck code 0000000A
Arguments 00000000`00000000 00000000`00000002 00000000`00000000 fffff800`02ce8c02
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

Maddog12 · 02-13-2012

i dont know how to look into systeminfo32, but i dont have any idea why it wouldnt be listed if it lists all other components as well. I have wireless adapter + wired port on my laptop, makes sense that both are listed in msinfo32 (system information??)
How did you get to see that it was a problem device? Should i uninstall/stop the device driver and see how i run? I went into device manager and found it under non plug+play drivers.

After running the antimalware diags and norton scan, is there still a likely case for residual malware infection? I will run avg free and see what comes up.

The same video driver is listed in the two dumps from yesterday as it was in the others. Is there anything we can do to update this driver? If it is to do with DirectX, i installed all the latest updates within the last week. Is it possible to uninstall it and work without it?

My intel graphics driver is dated 25/03/2011, i went to update using the download feature they have to determine your graphics driver etc, and then when i went to install it from my downloads a message said i had the wrong version... I dont know if this is related at all

I also dont have McAfee installed, only norton. is it advisable for me to uninstall norton and see if there are any more bsods while there's still the potential for malware infection?

I may just wipe and re-install, but i cant find the installation dvds, or the box for that matter.

everything important is backed up though so im not fussed if it all goes.

I checked my system, it is only about a year (year and a half tops) old, is it possible to return it if it is a fault not to do with my usage of the laptop?

Thanks!

usasma · 02-13-2012

Don't worry about the network stuff for now.

It's not a malware infection that's likely - it's likely that there was some damage caused by malware, and the damage wasn't fixed.

Warranty on most systems is 1 year. Warranty will cover hardware issues only - not damage to the OS from an infection (OS is software, and the infection is software). There's no sign of hardware problems here, so trying to get the reseller to exchange the computer is probably not likely.

MSINFO32 says you do have McAfee installed:

Quote:

Start Menu\Programs\McAfee Family Protection Public:Start Menu\Programs\McAfee Family Protection Public

Please uninstall both McAfee and Norton - then use a free antivirus for protection temporarily while testing.

If you found the latest video driver at the Intel website, then it's the latest version. Interestingly, there's no info on your video device in dxdiag - yet there is info in MSINFO32. This says (IMO) that the OS is significantly damaged.
I'd suggest contacting Acer for a set of recovery disks (Instructions for the USA: Order Recovery Discs (USA) )

Once you have the recovery disks, please do the following:

Quote:

For testing purposes, it's best to install Windows "clean".
This is, basically, installing it the way that Microsoft intended (using drivers from Windows Update).
This procedure is for Windows 7, Vista is similar (but has 2 service packs)

You will need your installation/recovery DVD(s) before you start. Once you wipe the hard drive there's no going back!!!

1. Backup all your data.
This will wipe everything off of your hard drive, so anything that you want to keep will need to be saved elsewhere.

NOTE: If this is due to an infection, remember to scan the data with another system's current antivirus in order to locate and remove any malware.

2. Connect the system to the internet (if the system says disconnect from the Internet, then do so).

3. Use one of these free utilities to wipe the hard drive clean:
DBAN ( DBAN Download | Darik's Boot And Nuke )
KillDisk ( Freeware Download Active@ KillDisk ).
This will also delete any recovery partitions on the system - so the installation/recovery DVD's are essential!!!

4. Install Windows by booting from the installation/recovery DVD - DO NOT tweak any settings!!!

5. Visit Windows Update and get all updates

6. Check Device Manager for any unknown/disabled devices - if there are unknown/disabled devices, fix them with the latest drivers from the device manufacturer's website (not the PC Manufacturer)

7. Visit Windows Update and get Service Pack 1 (usually under Important Updates). Read these notes for installing SP1: Steps to follow before you install Windows 7 SP1 and Windows Server 2008 R2 SP1 from the Microsoft Download Center

8. Visit Windows Update and get any other available updates

9. Download, install, and update a free antivirus so you don't get infected while testing ( Free AntiVirus ).

If the problems persist, then the problem is most likely with your hardware.

CAVEAT: If you have an Asus motherboard, check the date on the C:\Windows\System32\driver\ASACPI.sys file. 2004/2005 is a problem, 2009/2010 is OK. Updates are available at the Asus support website.

CAVEAT: If you have a Sony system, make sure that you DO NOT have the 2007 (or earlier) version of the Sony Firmware Extension Parser (SFEP.sys). Update this driver immediately!!!

Windows 7 - BSOD -Full Info Provided. irql_not_less_or_equal

BSOD -Full Info Provided. irql_not_less_or_equal problems?