Frequent and multiple different BSOD Errors with no clear pattern

[Caridor]

Over the past month or so, I've been suffering from several different BSOD issues. Sometimes it displays "IRQL not less or equal" and sometimes, it's simply a string of error numbers, with 0x000001e being the most frequent.

I've attached the contents of my minidump folder and I do apologise for how many files there are. I've tried a few fixes before this.

 

[Caridor]

Also, there's an advert below my post, claiming it's a "recommended fix", is that for real or an ad?
​

 

[Caridor]

Bump

 

[Caridor]

Adding new information, I know it's not my computer temperature, my graphics card drivers or windows update and according to kaspersky, malwarebytes anti-malware and rootkit, it's not caused by a virus either.
I can also tell you that steam seems to be related, since almost all crashes occur while playing steam games.

 

[essenbe]

It's an add, not for real.

 

[essenbe]

Here is what the dumps are showing. The first one 2 dumps showed the Nvidia driver

lmvm nvlddmkm
start             end                 module name
fffff880`0f698000 fffff880`10326000   nvlddmkm T (no symbols)           
    Loaded symbol image file: nvlddmkm.sys
    Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
    Image name: [COLOR=red]nvlddmkm[/COLOR].sys
    Timestamp:        Wed Jul 02 12:42:02 2014 (53B4446A)
    CheckSum:         00C4C7C9
    ImageSize:        00C8E000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

I would update the driver according to this tutorial, which will give you the cleanest install
http://www.sevenforums.com/tutorials/327414-nvidia-drivers-avoid-problems.html

lmvm klif
start             end                 module name
fffff880`03255000 fffff880`032fa000   klif     T (no symbols)           
    Loaded symbol image file: [COLOR=red]klif.sys[/COLOR]
    Image path: \SystemRoot\system32\DRIVERS\klif.sys
    Image name: klif.sys
    Timestamp:        Thu Mar 06 10:39:36 2014 (5318A4C8)
    CheckSum:         0009F650
    ImageSize:        000A5000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Klif Mini-Filter fre_wnet_x86 (Kaspersky) you may find an updated version at Free Kaspersky Antivirus Trial | Kaspersky Lab US

[CODE lmvm usbhub
start end module name
fffff880`04622000 fffff880`0467c000 usbhub (pdb symbols) c:\symcache\usbhub.pdb\7ACC879946324EA48B13386DE80EC2E61\usbhub.pdb
Loaded symbol image file: usbhub.sys
Mapped memory image file: c:\symcache\usbhub.sys\52954DD05a000\usbhub.sys
Image path: \SystemRoot\system32\DRIVERS\usbhub.sys
Image name: usbhub.sys
Timestamp: Tue Nov 26 19:41:36 2013 (52954DD0)
CheckSum: 0005F52B
ImageSize: 0005A000
File version: 6.1.7601.18328
Product version: 6.1.7601.18328
File flags: 0 (Mask 3F)
File OS: 40004 NT Win32
File type: 2.0 Dll
File date: 00000000.00000000
Translations: 0409.04b0
CompanyName: Microsoft Corporation
ProductName: Microsoft® Windows® Operating System
InternalName: usbhub.sys
OriginalFilename: usbhub.sys
ProductVersion: 6.1.7601.18328
FileVersion: 6.1.7601.18328 (win7sp1_gdr.131126-1436)
FileDescription: Default Hub Driver for USB][/CODE]

This tutorial may help with that http://www.sevenforums.com/tutorials/165554-usb-driver-general-fix-problems.html

Try these and see how it works out. Let us know the results.

 

[Caridor]

Thanks for the response. I've been through the steps and if it's still fine in a couple of days, I'll mark this as solved

 

[essenbe]

Just keep us posted.

 

[Caridor]

So after doing all the steps, I was just playing Risk of Rain and I got BSOD, with an IRQL Not Less or Equal error.
I went to my minidump folder to upload the log, but I have no logs on 08/08.
I'm not really sure what information I can provide

 

[essenbe]

Make sure your computer is set to create Small Memory Dumps. This will show you how. http://www.sevenforums.com/tutorials/174459-dump-files-configure-windows-create-bsod.html Also

Please fill out your System Specs​

   Information

Your System Specs will help us to help you, and doing it in this manner will make them available to all helpers in every post and keep us from hunting for them. We ask that you fill them out in as much detail as possible including Desktop or Laptop, Model number if it is an OEM computer and all components with the Manufacturer and Model number if possible.

If you will go to your last post and click the 'System Specs' in the bottom left of the post, you will find a link to update your system specs. Please fill those out in as much detail as possible. If you would like to know what we would like, you can click 'My System Specs' at the bottom left of this post to see mine. If you do not know what your components are, this will help you accomplish this task. http://www.sevenforums.com/tutorials/180324-system-info-see-your-system-specs.html​

 

[Caridor]

Right, I've put in my system specs and configured it to make small dumps, not kernal dumps, I'll upload them as soon as possible

 

[essenbe]

Good, that will help. Make sure you have a C:/windows/Minidump folder. If there is not one, create a folder called Minidump in C:/windows.

 

[Caridor]

I'm not getting any crash dumps.
I don't know what went wrong. Here's a screenshot of my settings, I don't think I've missed anything. http://i.imgur.com/zyPV0WB.png

 

[essenbe]

They look right, but you may try to uncheck 'Automatically restart'.

 

[Caridor]

Ok, done that. Hopefully it will work next time it crashes.

 

[essenbe]

I hope so. We need the dump files.

 

[essenbe]

Also, open a elevated command prompt ( click start, type cmd in the search box, right click on the cmd entry and select run as administrator) in the black box that opens, copy/paste sfc /scannow. If you decide to type it, notice the space between the sfc and the /. It is a system file checker which will scan your system files and attempt to correct any missing or corrupt files. What we want are the results to say windows found no integrity violations. If it says files were found but could not be repaired, close the box, reboot and run it again, after opening the administrative command prompt. You may have to reboot and run it three times for it to repair all system files. If it can't repair them after 3 reboots, let us know.

 

[Caridor]

So it's still not giving me any crash dumps, which is annoying. I've tried the second option fix and that didn't work either.

But on the plus side, after running the command prompt, it said there were no integrity violations on the second time through. Hopefully, that's done it.

 

[essenbe]

I hope so. Are you still getting BSODs since you ran the system file checker?

 

[Caridor]

Yes, sadly so.
So far, only ones displaying an IRQL_NOT_LESS_OR_EQUAL error.

And the second option didn't work on the crash dumps.