03-14-2012, 12:29 AM
(This post was last modified: 03-14-2012, 12:29 AM by AceInfinity.)
Been away for a few days... It would help with the actual dump file but that may be difficult in this situation.
Iastor.sys is the Intel RAID controller driver. Are you using RAID configuration in the BIOS? If not then disable RAID in the BIOS.
When you see something like this:
That just means that there's still an entry in your pending "log" created and updated whenever preceeding changes to your system are still pending. This kernel mode exception may be a result of these unprocessed "changes" pending on your system, who knows.
Ooh... That may be bad, but I won't assume things until I see further what is really going on here. Future step I may get you to see what you can see in your BIOS, but do not do anything in there at this point in time.
Have you installed any new hardware or made any changes to your system physically? I can't debug the address at 0x8364db40 from the stack, so just going by what I see in the basic analysis output from what you pasted. This appears to be a result of a memory access violation. Therefore I would recommend seeing what a memory diagnostic test will come out with:
Download and run Memtest86 on boot: http://www.memtest86.com
Note: It's highly recommended that you put Memtest86 to a disk or a floppy as using a USB key just makes things more complicated than they need to be.
Do you know your BIOS version? How big is your hard drive? Something you can try is to switch your BIOS memory options off caching or shadowing (disable them). Reboot.
Otherwise do you have access to a repair disk for your Windows 7? I can give you further instructions to try through the command prompt option from that boot disk.
~Ace
Iastor.sys is the Intel RAID controller driver. Are you using RAID configuration in the BIOS? If not then disable RAID in the BIOS.
When you see something like this:
Quote:There is a system repair pending which requires reboot to complete. Restart windows and run sfc again.
That just means that there's still an entry in your pending "log" created and updated whenever preceeding changes to your system are still pending. This kernel mode exception may be a result of these unprocessed "changes" pending on your system, who knows.
Quote:Windows cannot run disk checking on this volume because it is write protected.
Ooh... That may be bad, but I won't assume things until I see further what is really going on here. Future step I may get you to see what you can see in your BIOS, but do not do anything in there at this point in time.
Have you installed any new hardware or made any changes to your system physically? I can't debug the address at 0x8364db40 from the stack, so just going by what I see in the basic analysis output from what you pasted. This appears to be a result of a memory access violation. Therefore I would recommend seeing what a memory diagnostic test will come out with:
Download and run Memtest86 on boot: http://www.memtest86.com
- Download the latest Memtest86 and burn to disk from here: http://www.memtest.org/#downiso. (If you need software to do so I would highly recommend a program called ImgBurn, and it's also free)
- Reboot your computer and boot from the CD drive for which you have your Memtest86 disk.
- You may need to load the Boot menu which will enable you to choose a device to boot from, otherwise you'll have to change the boot order in the BIOS to boot from CD drives as first priority before the HDD
- Make sure to let it run and do it's thing for about the first 6 tests. If it passes those, then everything should be good, otherwise any failure to pass those tests indicates a corruption in your memory.
- If you get an error on one of the tests, then you should try by booting up your computer with each RAM inserted separately one at a time. When you find one that doesn't return any errors then test it in every single RAM slot to test for a bad socket.
Note: It's highly recommended that you put Memtest86 to a disk or a floppy as using a USB key just makes things more complicated than they need to be.
Do you know your BIOS version? How big is your hard drive? Something you can try is to switch your BIOS memory options off caching or shadowing (disable them). Reboot.
Otherwise do you have access to a repair disk for your Windows 7? I can give you further instructions to try through the command prompt option from that boot disk.
~Ace