BSOD Kernel/iaStor?

toastpaint

toastpaint

Member
Joined
Aug 3, 2012
Posts
20
Hi All,

Been getting these BSODs for a while ranging from 0x0D1 to Ox01E issues - I ran Verifier today, and it narrowed it down to iaStor.sys - but can't work out where to head now. It's up to date and running AHCI. The BSODs seem occur randomly - but something is triggering it. The process responsibile in the Debugger doesn't seem to matter either - once it said Origin.exe (game client) and another time googletalkplugin.

· OS - Win7
· x64
· Win7
· OEM/TechNet Legit
· 6 months old hardware
· 4 months old OS

· CPU Intel i7-2700K 3.5ghz
· Video Card - Gainward GTX580
· MotherBoard - Intel DP67BG
· Power Supply - Thermaltake 875W

· System Manufacturer - DIY

View attachment 1256


Any further things I need to add, let me know.

Cheers,

Jack
 
Hi,

The process in which crashed isn't helpful in most cases, but in some, it can narrow it down. For example, if you're getting random crashes, and 10/10 crash dumps say the AVG process crashed, AVG may be the issue... but Windows just cannot pinpoint the driver depending on how early the crash happened and how long it took Windows to figure it out, etc.

First off, iaStor.sys - http://downloadcenter.intel.com/Default.aspx (Intel Storage Matrix drivers)

Although you mentioned you're up to date, just double check. Also ensure that all drivers- chipset, etc.. are up to date.

In my time as a BSOD analyst, I have seen iaStor.sys BSOD situations be the fault of a rootkit, specifically BSOD's that are of the IRQL_NOT_LESS_OR_EQUAL stop code (which in your case, you do have said stop code mentioned). After updating the drivers, if you're still having issues, I would at least recommend running TDSSKiller in safe mode just to ensure your system is not infected with a rootkit:

http://support.kaspersky.com/viruses/solutions?qid=208280684

Regards,

Patrick
 
E-Peen said:
Regards,

Patrick
Click to expand...


Patrick - the iaStor driver is definetely up to date, and the Kaspersky script under safe mode found nothing. :|
All drivers are up to date - using (awaiting mixed opinion) Driver Detective.
Your help is much appreciated :)

Cheers,

Jack
 
Your awaiting mixed opinion comment was definitely correct!

I would not personally recommend the use of a 3rd party program that updates drivers for you. Some of these programs, if not all in most cases, do not always offer the latest drivers. Said drivers can also be buggy as well, and these programs do not also offer firmware updates, which in some cases are very important. I would recommend always manually checking Intel's site to make sure your chipset drivers are up to date, audio, the works (except video card and such, you'll want to go to nVidia's site for that).

Question, do you use an SSD? If so, make sure it's on the latest firmware.

Regards,

Patrick
 
Last edited:
Yeah. I got this program as a result of these BSODs due to sighting it on SevenForums and other places.
Seems like the DP67BG has a lacking of drivers... but it's definitely up to date.

No - no SSD.

Regards,

Jack
 
Thanks for the update, Jack.

Often physical memory problems can cause iaStor.sys culprits / BSOD's because the memory is corrupted so it's often blamed on something else. I'd recommend running Metest86+ -

Memtest86+:



Download Memtest86+ here:
Click to expand...
http://www.memtest.org/http://www.memtest.org/



Which should I download?



You can either download the pre-compiled ISO that you would burn to a CD and then boot from the CD, or you can download the auto-installer for the USB key. What this will do is format your USB drive, make it a bootable device, and then install the necessary files. Both do the same job, it's just up to you which you choose, or which you have available (whether it's CD or USB).



How Memtest works:



Memtest86 writes a series of test patterns to most memory addresses, reads back the data written, and compares it for errors.



The default pass does 9 different tests, varying in access patterns and test data. A tenth test, bit fade, is selectable from the menu. It writes all memory with zeroes, then sleeps for 90 minutes before checking to see if bits have changed (perhaps because of refresh problems). This is repeated with all ones for a total time of 3 hours per pass.



Many chipsets can report RAM speeds and timings via SPD (Serial Presence Detect) or EPP (Enhanced Performance Profiles), and some even support changing the expected memory speed. If the expected memory speed is overclocked, Memtest86 can test that memory performance is error-free with these faster settings.



Some hardware is able to report the "PAT status" (PAT: enabled or PAT: disabled). This is a reference to Intel Performance acceleration technology; there may be BIOS settings which affect this aspect of memory timing.



This information, if available to the program, can be displayed via a menu option.



Any other questions, they can most likely be answered by reading this great guide here:



http://forum.canardpc.com/threads/28864-FAQ-please-read-before-postinghttp://forum.canardpc.com/threads/28864-FAQ-please-read-before-posting
Click to expand...

You'll want to run for at least 7-8 passes, that will take multiple hours.

Regards,

Patrick
 
Last edited:
Memtest is one of those things that are better to go overkill on...

A personal example for you...

When I first built my system a few years ago I had a set of RAM where one stick was faulty...

I installed windows using this faulty set and had nothing but issues and BSODs with it frequently...

Even after a clean install it persisted...

Thinking it might be my hardware I ran through hardware diagnostics and passed all...

I then decided to test each ram stick individually using memtest and they both passed, It was not until I ran them individually over night that I found the corruption on one of my sticks on the 100+ pass...

Returned the RAM and have been up and running ever since... :thumbsup2:
 
Just FYI - the longer that you run MemTest86+, the more likely you are to uncover errors.
I've run it over the weekend and have sometimes found an error or two - but most often haven't had any errors.
At that point you've gotta wonder if Windows built-in error correcting mechanism's will take care of the problem.

For rare errors using MemTest86+:
If it's a warranty repair, we replace the RAM at work.
If it's not covered under warranty, then we let the customer decide (after explaining it to them). They can always come back and replace the RAM if the problems continue.

Another nice test for RAM is Prime95 (the Blend test). It stresses the RAM, so you may see different results - but it's a good test to round out a memory assessment: http://www.carrona.org/hwdiag.html#prime95

More info that I've scribbled about Prime95: http://www.carrona.org/prime95.html
 
Good morning!
This morning, after leaving it run for about 9 hours with all sticks - here are the before and afters.

photobef.jpgphoto.jpg

Not really sure where to head from here. Seems like the stick in DIMM2 or DIMM2 itself is the problem?

Cheers,

Jack
 
RED = BAD
Remove it, then run the tests again to see if the RED stays away

Then, if the RED stays away, try running the good stick in the DIMM2 slot
 
Last edited:
Correct. A little troubleshooting and you'll figure it out, let us know if you run into any walls.

Regards,

Patrick
 
Not to interrupt or interfere with anything that is being done so far in this thread but just to add another thought as I have had some experience with weird memory issues which I wrote about here http://windows7forums.com/blogs/trou...d-odyssey.html
It seems that unfortunately the extra burden placed on the controller only rears its' ugly head when you are using DDR3 1333 (667Mhz) memory or faster and you are testing with all sticks in place. In my case, single sticks or any combination of 3 sticks or less produced no errors, either in memtest or in prime95. DDR3 1066 (533Mhz) or setting 1333 memory to run at 1066 speeds (7, 7, 7, 20) seems to not produce the problem or fix the issue if you dumb down the memory.
Probably should also be noted that since I wrote that particular Blog entry, I have reset my memory from 1066 (533Mhz) back to 1333 (667Mhz) and bumped my memory voltage from 1.5V to 1.6V
No problems since.
I am not sure that this actually addresses your particular issue as my particular problem was with and AMD config but as I understand it the problem does occur in some rare instances with intel boards as well. While I'm a rank amateur when it comes to BSOD analysis, I thought I would share this anyway as a just in case type FYI.
Regards
Randy
 
Hi Trouble - that's appreciated, I thought it could be something like that.

On a side note - I'm completely baffled.
I tested the stick in another system last night for 15 hours - no errors.
Left the other 3 sticks in the original system for 10 hours with p95 running blend -nothing. BUT! I stopped the p95 workers this morning, went to check my email - and hey presto, freaking BSOD. I've never head-desked so hard in my life.

I'm going to do the other three sticks in memtest86+ over the next few days. Hopefully I'll survive.

Cheers,

Jack
 
Very sorry to hear that, and it is not likely at all then that our problems are or were ever similar, as I never had any such issue when running three sticks or less. I'll bow out and return you to the good capable hands of those here who actually know something about what they are doing.
I know these types of problems can be difficult and frustrating as was my case but it sounds to me like you are on the right track in troubleshooting individual sticks and slots. Perseverance and some soft foam between your head and the desk will likely get you through.
Since the issue may be a single module or a single slot on the MoBo involving a second machine could be a double edged sword. You may be able to semi-prove a known good stick of ram using the second system (assuming the physical architecture is similar enough that the memory is being identified identically by MemTest86+, but identifying a possible bad slot will require testing a known good stick in each slot individually.
Notice how I said that, just like you didn't already know it?
Good luck
Randy
 
Oh Randy - it's all clear as mud.
Intel will compensate me for lost time right - if it turns out to be a freaking DIMM slot?

 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top