Re: DRIVER IRQL NOT LESS OR EQUAL (storport.sys)

Hi,

Please refer to the following thread and reply back here accordingly - http://www.techsupportforum.com/for...en-of-death-bsod-posting-instructions-windows-8-windows-7-and-vista-452654.html

Regards,

Patrick

 

Re: DRIVER IRQL NOT LESS OR EQUAL (storport.sys)

Hi,

Please refer to the following thread and reply back here accordingly - http://www.techsupportforum.com/for...en-of-death-bsod-posting-instructions-windows-8-windows-7-and-vista-452654.html

Regards,

Patrick

I would but my jcgriff2 file is stuck on "Waiting for SystemInfo" endlessly ... So I only have the perfmon report.

 

Re: DRIVER IRQL NOT LESS OR EQUAL (storport.sys)

Okay, attach that, and for minidumps, you can do it manually:

Please navigate to C:/Windows/Minidump and zip up any dump files located there that you'd like to have analyzed, and then attach that zip here. If there are no dumps located in C:/Windows/Minump, you may be writing full memory dumps to C:/Windows, and it'll be called MEMORY.DMP.

If there are no dumps in either of those locations, but you know you have a page file set up, any "cleaner" programs such as TuneUp Utilities, CCleaner, etc, will delete this upon use.

If you cannot get into normal mode, please do this via Safe Mode.
Regards,

Patrick

 

Re: DRIVER IRQL NOT LESS OR EQUAL (storport.sys)

Okay, attach that, and for minidumps, you can do it manually:

Please navigate to C:/Windows/Minidump and zip up any dump files located there that you'd like to have analyzed, and then attach that zip here. If there are no dumps located in C:/Windows/Minump, you may be writing full memory dumps to C:/Windows, and it'll be called MEMORY.DMP.

If there are no dumps in either of those locations, but you know you have a page file set up, any "cleaner" programs such as TuneUp Utilities, CCleaner, etc, will delete this upon use.

If you cannot get into normal mode, please do this via Safe Mode.
Regards,

Patrick

Here you go, perfmon and the minidump. I could only find one in the minidump folder.

There are files created by the jcgriff2 file but as it didn't get systeminfo I guess it's no use attaching?

 

Re: DRIVER IRQL NOT LESS OR EQUAL (storport.sys)

I unfortunately cannot understand the language in the perfmon.

Moving onto the dump, it's of the DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1) bugcheck.

A kernel-mode driver attempted to access pageable memory at a process IRQL (Interrupt Request Level) that was too high.

Usual causes are a device driver has a bug and attempted to access invalid memory, the pagefile has been corrupted or there is a memory problem.

Update to Service Pack 1 ASAP: Learn how to install Windows 7 Service Pack 1 (SP1)


After doing that, let's enable Driver Verifier to see if we can catch a device driver culprit:



Driver Verifier:

What is Driver Verifier?
Driver Verifier is included in Windows 7, Windows Server 2008 R2, Windows Vista, Windows Server 2008, Windows 2000, Windows XP, and Windows Server 2003 to promote stability and reliability; you can use this tool to troubleshoot driver issues. Windows kernel-mode components can cause system corruption or system failures as a result of an improperly written driver, such as an earlier version of a Windows Driver Model (WDM) driver.
Essentially, if there's a 3rd party driver believed to be at issue, enabling Driver Verifier will help flush out the rogue driver by flagging it and causing your system to BSOD.
Before enabling Driver Verifier, it is recommended to create a System Restore Point:
Vista - START | type rstrui - create a restore point
Windows 7 - START | type create | select "Create a Restore Point"
How to enable Driver Verifier:
Start > type "verifier" without the quotes > Select the following options -
1. Select - "Create custom settings (for code developers)"
2. Select - "Select individual settings from a full list"
3. Check the following boxes -
- Special Pool
- Pool Tracking
- Force IRQL Checking
- Deadlock Detection
- Security Checks (Windows 7)
- Concurrentcy Stress Test (Windows 8)
- DDI compliance checking (Windows 8)
- Miscellaneous Checks
4. Select - "Select driver names from a list"
5. Click on the "Provider" tab. This will sort all of the drivers by the provider.
6. Check EVERY box that is NOT provided by Microsoft / Microsoft Corporation.
7. Click on Finish.
8. Restart.
Important information regarding Driver Verifier:
- If Driver Verifier finds a violation, the system will BSOD.
- After enabling Driver Verifier and restarting the system, depending on the culprit, if for example the driver is on start-up, you may not be able to get back into normal Windows because Driver Verifier will flag it, and as stated above, that will cause / force a BSOD.
If this happens, do not panic, do the following:
- Boot into Safe Mode by repeatedly tapping the F8 key during boot-up.
- Once in Safe Mode - Start > type "system restore" without the quotes.
- Choose the restore point you created earlier.
If you did not set up a restore point, do not worry, you can still disable Driver Verifier to get back into normal Windows:
- Start > Search > type "cmd" without the quotes.
- To turn off Driver Verifier, type in cmd "verifier /reset" without the quotes.
- Restart and boot into normal Windows.
How long should I keep Driver Verifier enabled for?
It varies, many experts and analysts have different recommendations. Personally, I recommend keeping it enabled for at least 36-48 hours. If you don't BSOD by then, disable Driver Verifier.
My system BSOD'd, where can I find the crash dumps?
They will be located in C:\Windows\Minidump
Any other questions can most likely be answered by this article:
http://support.microsoft.com/kb/244617

Regards,

Patrick

 

Re: DRIVER IRQL NOT LESS OR EQUAL (storport.sys)

I unfortunately cannot understand the language in the perfmon.

Moving onto the dump, it's of the DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1) bugcheck.



Update to Service Pack 1 ASAP: Learn how to install Windows 7 Service Pack 1 (SP1)


After doing that, let's enable Driver Verifier to see if we can catch a device driver culprit:



Driver Verifier:

Regards,

Patrick

I figured that issue would happen.

Yes the language is swedish and I doubt I can make a report in english, if you know how just tell me. I doubt it's possible anyway.

I remember this process before, I'll use the Driver Verifier yeah and I'll leave it on for as long as I can. Also care to tell me how to disable it? If needed?

On top of that, I didn't have many non-microsoft drivers. So this shouldn't take long.

I will restart my computer now and see what happens.

But why would this BSOD happen? It says it's most likely caused by "Microsoft Storage Port Driver". Do you know what that is?

I haven't changed any drivers for atleast 2 months or so, the only drivers I update regularly are the drivers of my Nvidia card.

I also carry really bad news for you, installing SP1 is not a choice for me. It has never worked, I've tried this year, last year and in 2011 when I got this system but I could never install it.

During the installation it would never complete, it just gave me an error saying something along "SP1 installation encountered an error and cancelled" if I remember correctly. I don't want to try this again because I know it wont work.

And quite frankly as far as I know SP1 is not necessary for this.

If the cause is around SP1 then I will try to install it, we'll see. Cause last time I had to wait sooo long and it still failed. Big time dissapointment

 

Re: DRIVER IRQL NOT LESS OR EQUAL (storport.sys)

It seems that using Driver Verifier did make my computer BSOD in less than 30 minutes.

When I came back into my room I saw my computer restarting, I just left it on the desktop with nothing but Steam in the background as usual.

I didn't get a single new minidump, I have no idea why. Very unsual however.

I tried installing SP1 but the link you linked was no use, my Windows Update has no SP1 displayed and the manual download makes no sense. There are like 10 different files from the download center link and none of them make sense

 

Re: DRIVER IRQL NOT LESS OR EQUAL (storport.sys)

Okay:

1. To get SP1 to show up on Windows Update, you have to install many other recommended updates. You should have all of the recommended updates installed anyway.

I also carry really bad news for you, installing SP1 is not a choice for me. It has never worked, I've tried this year, last year and in 2011 when I got this system but I could never install it.

During the installation it would never complete, it just gave me an error saying something along "SP1 installation encountered an error and cancelled" if I remember correctly. I don't want to try this again because I know it wont work.

And quite frankly as far as I know SP1 is not necessary for this.

Service Packs are released for a reason, just like regular Windows security updates are. They are a large collection of enhancements, bug fixes, security patches, etc. It's also necessary to have service packs for certain programs to run properly, etc.

Do not worry, I will do my absolute best to assist you in getting SP1 installed.


2. For verifier, if it didn't generate a dump file, just try again. If it doesn't generate again, check your settings are is as follows:

1. Start > type %systemroot% which should show the Windows folder, click on it. Once inside that folder, ensure there is a Minidump folder created. If not, CTRL-SHIFT-N to make a New Folder and name it Minidump.

2. Windows key + Pause key. This should bring up System. Click Advanced System Settings on the left > Advanced > Performance > Settings > Advanced > Ensure there's a check-mark for 'Automatically manage paging file size for all drives'.

3. Windows key + Pause key. This should bring up System. Click Advanced System Settings on the left > Advanced > Startup and Recovery > Settings > System Failure > ensure there is a check mark next to 'Write an event to the system log' > Ensure 'Automatically restart' is un-checked.

Ensure Small memory dump is selected and ensure the path is %SystemRoot%\Minidump.

4. Double check that the WERS is ENABLED:

Start > Search > type services.msc > Under the name tab, find Windows Error Reporting Service > If the status of the service is not Started then right click it and select Start. Also ensure that under Startup Type it is set to Automatic rather than Manual. You can do this by right clicking it, selecting properties, and under General selecting startup type to 'Automatic', and then click Apply.

But why would this BSOD happen? It says it's most likely caused by "Microsoft Storage Port Driver". Do you know what that is?

Good question! When WinDbg lists culprits such as storport.sys (Windows system file), it's 99% of the time due to a 3rd party device driver or another complication. Windows however cannot always detect the proper culprit, as BSOD's don't happen instantly and sometimes the actual culprit gets away and leaves the murder weapon with what we see blamed before Windows catches it.

This is why we have tools such as Driver Verifier to help us catch a device driver if it's the issue, etc. Because with Driver Verifier, once that driver does whatever it isn't supposed to be doing, rather than Windows possibly be late to catching it, it will halt the system immediately with the 'probably caused by' listed as that device driver (if it's a driver issue, of course).

Regards,

Patrick

 

Re: DRIVER IRQL NOT LESS OR EQUAL (storport.sys)

Okay:

1. To get SP1 to show up on Windows Update, you have to install many other recommended updates. You should have all of the recommended updates installed anyway.

Service Packs are released for a reason, just like regular Windows security updates are. They are a large collection of enhancements, bug fixes, security patches, etc. It's also necessary to have service packs for certain programs to run properly, etc.

Do not worry, I will do my absolute best to assist you in getting SP1 installed.


2. For verifier, if it didn't generate a dump file, just try again. If it doesn't generate again, check your settings are is as follows:

1. Start > type %systemroot% which should show the Windows folder, click on it. Once inside that folder, ensure there is a Minidump folder created. If not, CTRL-SHIFT-N to make a New Folder and name it Minidump.

2. Windows key + Pause key. This should bring up System. Click Advanced System Settings on the left > Advanced > Performance > Settings > Advanced > Ensure there's a check-mark for 'Automatically manage paging file size for all drives'.

3. Windows key + Pause key. This should bring up System. Click Advanced System Settings on the left > Advanced > Startup and Recovery > Settings > System Failure > ensure there is a check mark next to 'Write an event to the system log' > Ensure 'Automatically restart' is un-checked.

Ensure Small memory dump is selected and ensure the path is %SystemRoot%\Minidump.

4. Double check that the WERS is ENABLED:

Start > Search > type services.msc > Under the name tab, find Windows Error Reporting Service > If the status of the service is not Started then right click it and select Start. Also ensure that under Startup Type it is set to Automatic rather than Manual. You can do this by right clicking it, selecting properties, and under General selecting startup type to 'Automatic', and then click Apply.

Good question! When WinDbg lists culprits such as storport.sys (Windows system file), it's 99% of the time due to a 3rd party device driver or another complication. Windows however cannot always detect the proper culprit, as BSOD's don't happen instantly and sometimes the actual culprit gets away and leaves the murder weapon with what we see blamed before Windows catches it.

This is why we have tools such as Driver Verifier to help us catch a device driver if it's the issue, etc. Because with Driver Verifier, once that driver does whatever it isn't supposed to be doing, rather than Windows possibly be late to catching it, it will halt the system immediately with the 'probably caused by' listed as that device driver (if it's a driver issue, of course).

Regards,

Patrick

Okay so, lets see.

Thank you, very friendly post. Good information. I am about to install some Windows Updates. There were 2 of them, 1 option and 1 necessary/required.

Optional was Microsoft Essential update and I will not install that because I don't use Microsoft Essential Defender or whatever it is called. I use Malwarebytes and it works a thousand times better if not more.

After this I will have to restart, and will enable the verifier again. I actually disabled it assuming it would give me a dump. But it didn't. So I'll just do it again. And I am not sure about that SP1 issue, it's not on the list. This is why I'm installing this update to see if it will appear after my restart but I kind of doubt it again.

If it doesn't, I don't know. I understand that SP1 is important but I've never been able to install it ..

Now the error report was on manual and not started, maybe that was the issue all along with the minidump? Most likely I will get one now.

I hope we will find what driver this is, it's extremely ******* annoying having BSOD. I need to play WoW with my friends over the weekends always because we do many things together and this issue ruins it all.

EDIT: BIG TIME UPDATE HERE!

I found SP1 in hidden updates which I hid, I attempted to install it but I got this an immediately cancelled update. Saying "An unidentified error occured" Code: 80246007 :huh:
By using the following thread I have fixed the above issue: Update error 80246007 installing KB975929, 979306, 976662, 976264 and - Microsoft Community

I can now download it and it's installing.

 

Re: DRIVER IRQL NOT LESS OR EQUAL (storport.sys)

Absolutely fantastic work! I am headed off to class soon, but I will check the thread in class throughout the day for your updates.

Once SP1 is installed and finished, keep verifier enabled (or enable it again if you've disabled it) and see if a DMP file generates.

Regards,

Patrick

 

Re: DRIVER IRQL NOT LESS OR EQUAL (storport.sys)

Absolutely fantastic work! I am headed off to class soon, but I will check the thread in class throughout the day for your updates.

Once SP1 is installed and finished, keep verifier enabled (or enable it again if you've disabled it) and see if a DMP file generates.

Regards,

Patrick

It was installed, successfully at that.

I immediately noticed my Firefox starts up quicker than usual. I had some issues regarding that before.

I will get verifier going and wait until I get a dump, when I get a dump I will disable it again as I dont think I will need it.

I'll be on here all night pretty much, I dont have anything else to do now. I dont want to play and randomly get shut off, it might cause issue with saving character information in games before things are completed.

You enjoy your class, hope to see a response soon if I BSOD again. When it comes to computer stuff, there is nothing more I despise than BSOD and Hardware failure. :angry:

 

Re: DRIVER IRQL NOT LESS OR EQUAL (storport.sys)

Catched the driver again it seems, but it didn't BSOD? It just locked up for a second, and closed.

I disabled restart now when I logged back in. No luck with the memory dump. Still only have the old memory dump. The dump folder is completely empty. God damnit

I'll keep waiting I guess, this sucks.

EDIT: Happend again in less than 20 minutes again, just shuts down without any BSOD and does not generate any crash report what so ever.

 

Re: DRIVER IRQL NOT LESS OR EQUAL (storport.sys)

Can't edit message so I'll just post a new post, it is necessary. Im not doing this to bump

Just had a BSOD caused by nvlddmkm.sys, no dump was created. I dont understand why. I snapped a picture, cant attach yet for some reason though. So I just use this instead http://puu.sh/3GU59.jpg

Seems to be nvidia drivers, I'll update them provided I don't crash lol. And see where that goes.

I am just afraid that I might BSOD during driver update and it might cause corruption

 

Re: DRIVER IRQL NOT LESS OR EQUAL (storport.sys)

Hi,

It's okay about the posts, don't worry. If you are worried about corruption, you can setup a system restore point.

You mentioned you often update your video card drivers, and sometimes the latest drivers do end up causing issues.

Ensure you have the latest video card drivers (double check). If you are already on the latest video card drivers, uninstall and install a version or a few versions behind the latest to ensure it's not a latest driver only issue (common). If you've already tried the latest version as well as many possible previous versions, you can try a beta driver if available.

Regards,

Patrick

 

Re: DRIVER IRQL NOT LESS OR EQUAL (storport.sys)

Hi,

It's okay about the posts, don't worry. If you are worried about corruption, you can setup a system restore point.

You mentioned you often update your video card drivers, and sometimes the latest drivers do end up causing issues.

Ensure you have the latest video card drivers (double check). If you are already on the latest video card drivers, uninstall and install a version or a few versions behind the latest to ensure it's not a latest driver only issue (common). If you've already tried the latest version as well as many possible previous versions, you can try a beta driver if available.

Regards,

Patrick

I haven't updated my nVidia drivers in like a month and a half actually now that I think of it. I've been very busy and haven't had the time.

I downloaded the latest and most stable and will attempt to install. I disabled verifier because I don't want it to crash while I install. I really hope this is as easy as an nVidia driver instead of more advanced things.

But I sense more than one thing is causing it, that would be ... Unfortunate? Yes

Edit: It has been done, updated and I will now proceed to enable verifier again. I hope I don't have another BSOD, but it's most likely inevitable. I never have that kind of luck

We'll see how it goes. I do appriciate the help I've gotten so far

 

Re: DRIVER IRQL NOT LESS OR EQUAL (storport.sys)

Yes, good work on disabling the verifier for now. Once your drivers are updated, use the system as you would regularly. If you BSOD again, try enabling verifier and see if there are still lockups rather than a BSOD and a dump generation.

Regards,

Patrick

 

Re: DRIVER IRQL NOT LESS OR EQUAL (storport.sys)

Yes, good work on disabling the verifier for now. Once your drivers are updated, use the system as you would regularly. If you BSOD again, try enabling verifier and see if there are still lockups rather than a BSOD and a dump generation.

Regards,

Patrick

I had it enabled, locked up 10 minutes after the driver install and had to restart. I think there are issues left but I will disable the verifier as you say and continue using the system as I always do.

I'll go try playing something .. I guess, I've never had BSOD's caused by Nvidia before either. This is new to me. What it could possibly conflict with is just .. I dont know. I can't come up with anything really.

 

Re: DRIVER IRQL NOT LESS OR EQUAL (storport.sys)

Okay, if you locked up again, we still have issues with a device driver. Since it's locking up rather than generating a crash dump, we are going to need to do this ONE 3rd party driver at a time, or very small groups.

So, remember how when setting up verifier you chose what drivers you wanted to select? Rather than selecting ALL 3rd party non-Microsoft drivers, we will now have to select either ONE at a time, or very few to test at a time.

This will take a little time, but it will give us an answer. Given you are crashing / locking up not too much after booting with verifier, figure you go 20-30 mins without crashing when selecting ONE 3rd party driver (or a small group), turn off verifier and select different 3rd party drivers.

Once you find the driver that is locking up the system, let me know.

Regards,

Patrick

 

Re: DRIVER IRQL NOT LESS OR EQUAL (storport.sys)

Okay, if you locked up again, we still have issues with a device driver. Since it's locking up rather than generating a crash dump, we are going to need to do this ONE 3rd party driver at a time, or very small groups.

So, remember how when setting up verifier you chose what drivers you wanted to select? Rather than selecting ALL 3rd party non-Microsoft drivers, we will now have to select either ONE at a time, or very few to test at a time.

This will take a little time, but it will give us an answer. Given you are crashing / locking up not too much after booting with verifier, figure you go 20-30 mins without crashing when selecting ONE 3rd party driver (or a small group), turn off verifier and select different 3rd party drivers.

Once you find the driver that is locking up the system, let me know.

Regards,

Patrick

You sure you wish to go through with this then? Because since I had it off I've had no BSOD's if that helps.

If you still want me to do it tell me, I guess I'll start. I imagine it will take some time however.

 

Re: DRIVER IRQL NOT LESS OR EQUAL (storport.sys)

Well, if you have had no BSOD's for now, that's fantastic. If you DO crash again, go through with the one at a time or small groups method.

Regards,

Patrick

 

Re: DRIVER IRQL NOT LESS OR EQUAL (storport.sys)

Well, if you have had no BSOD's for now, that's fantastic. If you DO crash again, go through with the one at a time or small groups method.

Regards,

Patrick

And so I shall do. I appriciate your help. Just hoping it doesn't happen again.

If it does I'll report back asap and on top of that, start using verifier again.

 

Re: DRIVER IRQL NOT LESS OR EQUAL (storport.sys)

That didn't last long.

I had a lock up, not a BSOD. The usual, mouse froze, sound on repeat etc etc.

Had to restart manually. I guess I will now start with verifier and select 1 driver at a time.

The list is the following(in order):

amdxata.sys - Advanced Micro Devices (AMD)
atmfd.dll - Adobe Systems Incorporated
dump_diskdump.sys - Unkown?
dump_dumpfve.sys - Unkown?
dump_nvstor.sys - Unkown?
hssdrv6.sys - Anchorfree Inc
mbam.sys - MalwareBytes
nvbridge.kmd - Nvidia Corporation
nvhda64v.sys - Nvidia Corporation
nvlddmkm.sys - Nvidia Corporation
nvm62x64.sys - Nvidia Corporation
nvstor.sys - Nvidia Corporation
secdrv.sys - Macrovision Corporation

That means I start with amxdata.sys now. Man this better be worth it ...

 

Re: DRIVER IRQL NOT LESS OR EQUAL (storport.sys)

Perhaps it's best to select all drivers and one by one disable them to see what the cause is?

Or 2 at a time? Please elaborate. I wont be up all night tonight so going one and one may prove difficult I think.

amdxata.sys is already proved to be clean, 20 minutes and nothing

 

Re: DRIVER IRQL NOT LESS OR EQUAL (storport.sys)

I can't edit my posts for some reason, anyway I'm going to bed and be online tomorrow and start scanning again. Thank you again.

You live in NY so your schedule shouldn't be too far off right? Oh well I dont know. 03:19 AM now as I post this.

 

Re: DRIVER IRQL NOT LESS OR EQUAL (storport.sys)

Hi,

I just returned from classes. You can do 2 at a time if you'd like, but just note if you get a lock up when selecting the 2 you do, you will have to see which 1 of the 2 it is by disabling either and seeing if you get a lock up.

Also, can you please go into detail in regards to what happens when enabling verifier? Does it lock up, and if so, how? What happens? You mentioned shutting down as well, what do you mean by that?

Any extra info greatly helps!

Regards,

Patrick

 

Re: DRIVER IRQL NOT LESS OR EQUAL (storport.sys)

Hi,

I just returned from classes. You can do 2 at a time if you'd like, but just note if you get a lock up when selecting the 2 you do, you will have to see which 1 of the 2 it is by disabling either and seeing if you get a lock up.

Also, can you please go into detail in regards to what happens when enabling verifier? Does it lock up, and if so, how? What happens? You mentioned shutting down as well, what do you mean by that?

Any extra info greatly helps!

Regards,

Patrick

Just woke up, took time sadly. But I will continue on the issue of course. 2 at a time.

And yes I will explain with more detail, but first I will tell a new issue I experienced yesterday before going to bed.

As usual it seemed like I was going to lock up, my mouse would not move, the sound in the background was stuck on loop and I figured I would have to restart but after waiting about 4 seconds maybe everything went back to normal. Then, after a minute or so it happened again and again etc.

At those times I noticed that my cursor went weird too, if I for example hovered over somewhere I could write and got the blinking I then after the freeze/hang(?) it would stay like that forever. Same goes for loading cursor.

And I've had 3 kinds of experiences with Verifier so far.

1. Lock up
2. Lock up and then shut down, as if there was a BSOD (there wasn't)
3. BSOD

The first one is like the typical lock up, I explained almost most of it above. My mouse locks up, I can't move it, the picture locks, the sound is stuck on extreme repeat and I will be forced to manually restart.

The same thing happens also with number 2, except that after the lock up it will shut down instead of giving me a BSOD. And because I've disabled automatic restart in system settings as you said. I again must restart manually.

And as for BSOD, it almost speaks for itself. It locks ups/hangs, gives me a BSOD, the information and I have to restart.

I usually dont seem to get any minidumps though, I dont know why ... All is enabled.

Anyway, I will start with verifier now. 2 at a time. You can see the list above in another post and see which ones I will continue with. I did not have a crash with amdxata.sys so I will not run it again.

 

Re: DRIVER IRQL NOT LESS OR EQUAL (storport.sys)

I figured I will scan 2 at a time except for the nvidia drivers. I'll scan all of them 2 at a time and since I doubt they are causing issues and this seems to be caused by Nvidia most likely.

I will scan all of the Nvidia drivers last and if I BSOD I will disable one by one of them.

 

Re: DRIVER IRQL NOT LESS OR EQUAL (storport.sys)

Nevermind I'll just run it as usual, all of the below have not given me any BSOD and I've ran them usualy for about 20 - 25 minutes and sometimes 30, usualy how long it takes for me to BSOD. I'll go on with Nvidia then

amdxata.sys - Advanced Micro Devices (AMD)
atmfd.dll - Adobe Systems Incorporated
dump_diskdump.sys - Unkown?
dump_dumpfve.sys - Unkown?
dump_nvstor.sys - Unkown?
hssdrv6.sys - Anchorfree Inc
mbam.sys - MalwareBytes

 

Re: DRIVER IRQL NOT LESS OR EQUAL (storport.sys)

3 locks up ever since I used verifier on nvlddmkm.sys.

It's an nVidia driver and if you remember perviously I posted I had BSOD by it, it's in the post where I took an image. No dumps at all and I've disabled verifier hoping for a natural BSOD.

I've already updated my drivers and I dont know what could be causing this. I'll try cleaning my computer and checking to see if anything is wrong

 

Re: DRIVER IRQL NOT LESS OR EQUAL (storport.sys)

Hi,

3 locks up ever since I used verifier on nvlddmkm.sys.

Rather than updating the driver to the latest, is there possibly a beta driver available or maybe rolling back to a version behind the latest as opposed to the version you were previously?

Regards,

Patrick

 

Re: DRIVER IRQL NOT LESS OR EQUAL (storport.sys)

Hi,



Rather than updating the driver to the latest, is there possibly a beta driver available or maybe rolling back to a version behind the latest as opposed to the version you were previously?

Regards,

Patrick

I will go on and install some beta drivers which are newer.

On top of that I just experienced an extremely weird issue.

My computer seemed as if it would lock up, but then it didn't and instead just sort of became EXTREMELY slow. My mouse would sometimes get stuck for 2 - 3 seconds, unstuck and repeat.

Then it would be extremely slow to do anything, like if I move my mouse to the right direction it would appear there in one second instead. Everything was lagging.

The cursor changed, was stuck on the loading O or sometimes the hand when you are about to click on things. Sometimes it would even become invisble. I have seriously no idea of what is going on here.

I'll attempt one of those jcgriff2 things with autorun or whatever and see if it works again ..

 

Re: DRIVER IRQL NOT LESS OR EQUAL (storport.sys)

You noted you are rushing to get this fixed due to having things to do soon with friends so you'll need the system. If updating the video card drivers doesn't provide a fix, it may be worth performing a clean install of Windows since you need the system.

This will also of course entirely rule out software as the issue as long as you only install the needed drivers, what you need to communicate with your friends, etc.

Regards,

Patrick

 

Re: DRIVER IRQL NOT LESS OR EQUAL (storport.sys)

You noted you are rushing to get this fixed due to having things to do soon with friends so you'll need the system. If updating the video card drivers doesn't provide a fix, it may be worth performing a clean install of Windows since you need the system.

This will also of course entirely rule out software as the issue as long as you only install the needed drivers, what you need to communicate with your friends, etc.

Regards,

Patrick

Christ .. These are not good news either. Reformating? I hate doing that.

I have nothing to back up my things on, and I have hundreeds of games on my Steam account, several WoW expansions that are massive in size which must be downloaded via Blizzard's site and so on.

If it sounds like an idea, I can uninstall my current drivers and do a complete "clean" install. Because when Nvidia installs drivers they overwrite the old ones, maybe a clean install would help?

Just please not reformating, I have too many documents, studies and images that I can't back up cause I have no other harddrive.

My biggest fear is that my graphics card is done for, I bought it in 2011 July and its not that old. Its decent too, I havent planned for buying new hardware so if it's broken that's also bad news and means I will have low FPS in games.

And also, same issue with the jcgriff2 thing, it can't get systeminfo. It's stuck on "Waiting for SystemInfo". I can still pack up whatever it collected until it came to that stage, if you wish.

 

Re: DRIVER IRQL NOT LESS OR EQUAL (storport.sys)

Yes, you can definitely try a complete uninstall of nVidia's drivers and then an install of the latest.

Also, yes, please pack up whatever else it managed to get, or the dumps manually. It's okay if the collection app is giving you trouble.

Regards,

Patrick

 

Re: DRIVER IRQL NOT LESS OR EQUAL (storport.sys)

Yes, you can definitely try a complete uninstall of nVidia's drivers and then an install of the latest.

Also, yes, please pack up whatever else it managed to get, or the dumps manually. It's okay if the collection app is giving you trouble.

Regards,

Patrick

Here you go, as I have noted I have no minidumps from any lock ups, nor BSOD's after the first one :frown:

Anyway I will attempt a clean install of the drivers, I truely hope this works but something tells me it wont.

Edit: Clean install has been done, on the new beta drivers.

 

Re: DRIVER IRQL NOT LESS OR EQUAL (storport.sys)

Just experienced something weird. My Windows Aero crashed and it went back to simple theme, then I heard my card squealing a little bit. Not a lot, but it was noticable.

Hard to explain too .. But it squealed for a while until Aero came back on again. Now it stopped. Weird? What could the cause for this be?

Can't possibly be PSU issue, I have a Cooler Master GX 750W Bronze for a year now and it works perfectly and more than enough watt for my entire computer..

 

Re: DRIVER IRQL NOT LESS OR EQUAL (storport.sys)

Are you sure it was the card squealing and not the PSU? Let's run Furmark to stress the GPU.

Furmark:

FurMark Video Stress Test - free from here: http://www.ozone3d.net/benchmarks/fur/
FurMark Setup:
- If you have more than one GPU, select Multi-GPU during setup
- In the Run mode box, select "Stability Test" and "Log GPU Temperature"
Click "Go" to start the test (Looks like it's "BURN-IN test" now)
- Run the test until the GPU temperature maxes out - or until you start having problems (whichever comes first).
- Click "Quit" to exit

Regards,

Patrick

 

Re: DRIVER IRQL NOT LESS OR EQUAL (storport.sys)

Are you sure it was the card squealing and not the PSU? Let's run Furmark to stress the GPU.

Furmark:

Regards,

Patrick

Um this doesn't seem very convincing, or safe.

You want me to stress my GPU into maximum temperature on a hot day on July? I dont know if that's safe, even slightly to be honest with you.

And my case currently has medicore airflow already, I'll get a new one soon.

And I am sure it is my GPU, the sound came from the GPU not the PSU. PSU is quiet as usual, but the GPU in particular started squealing. It's stopped and it works fine now.

I did google it and some say it's fine and some not, but my biggest issue is that aero crashed. Why would it do that?

 

Re: DRIVER IRQL NOT LESS OR EQUAL (storport.sys)

Furmark is used to determine whether or not the video card is stable. If it's not (whether it's because it's faulty, temperatures are way beyond what they should be, etc) your system will BSOD as it would if you were doing anything else.

It's a completely safe diagnostic method and I am recommending it for a reason. I have been analyzing and assisting users with BSOD related issues for almost two years now. If I recommended unsafe methods in regards to diagnostics, I don't think I would be allowed on these communities. My reply for Furmark says

Run the test until the GPU temperature maxes out - or until you start having problems (whichever comes first).

because that's what I mean. Either:

1. The test is going just fine and temperatures for the GPU are right where they should be and there are no artifacts, etc.

2. Your temperatures are getting way too high (any 90c+ shut off the test immediately).

3. Your system crashes, which implies your video card is not handling any sort of stress.

but my biggest issue is that aero crashed. Why would it do that?

GPU not properly working, possibly RAM as well as we have not yet done a Memtest. I want to rule out GPU first.

Overall, I am only trying to help you here.

Regards,

Patrick

 

Re: DRIVER IRQL NOT LESS OR EQUAL (storport.sys)

Furmark is used to determine whether or not the video card is stable. If it's not (whether it's because it's faulty, temperatures are way beyond what they should be, etc) your system will BSOD as it would if you were doing anything else.

It's a completely safe diagnostic method and I am recommending it for a reason. My reply for Furmark says



because that's what I mean. Either:

1. The test is going just fine and temperatures for the GPU are right where they should be and there are no artifacts, etc.

2. Your temperatures are getting way too high (any 90c+ shut off immediately).

3. Your system crashes, which implies your video card is not handling any sort of stress.



GPU not properly working, possibly RAM as well as we have not yet done a Memtest. I want to rule out GPU first.

Regards,

Patrick

Okay fine but my gut feelings are really horrible about this, something is telling me it won't go right.

None the less, I will attempt it. You said if it goes above 90C then I should shut it off immediately? And how exactly do you mean "shut off"?

Shut off computer? Alt + F4? Or what? Please give me a detailed response here I can't risk this and screw it up.

What makes me fear this program is, if I go into extremely high temp I am very sure that the noise will increase and that permanent damage is possible as cards are not supposed to go up to say 80C in load. I've only been up to as high as 62C on very intenstive games.

But as for RAM, I know about memtest and I've never done it. As far as I know it must be burned to a CD, I dont use CD's, I dont have any CD's at home and my CD ROM/DVD or whatever is a bit faulty, always has been so is there any alternative?

We have so far taken this from BSOD issue to hardware issue, I guess it seems like this isn't a driver problem at all then? As you said 99% of the time it would be, I suppose I am 1% now.

Since the last clean install I've had no issues except this. And I am already prepared to buy a new card as I sense this one is done for if it's failing me like this. Out of pure bloody no-where.