BSOD dmp file upload

[civilwar142pa]

BSOD dmp file upload

 

[essenbe]

Hello civilwar142pa, and welcome to the forums. I will try to help you if I can. I need you to do a few things first. Please give me some details of exactly what happened, what you were doing, if there is any certain activity that you do that causes it. Any information you can provide to help me determine the problem.

Please run the BSOD Posting Instructions http://www.sevenforums.com/bsod-help-support/96879-blue-screen-death-bsod-posting-instructions.html and upload the zip file with your next post.

Please fill out your system specs in as much detail as possible with Manufacturer and Model number. Also include you PSU and CPU cooler. This may help you accomplish this:

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, making sure to click save at the bottom of the page. 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​

Please open an 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.

Your dump file listed this

[COLOR=red]DRIVER_POWER_STATE_FAILURE (9f)
[/COLOR]A driver has failed to complete a power IRP within a specific time.
Arguments:
Arg1: 0000000000000004, The power transition timed out waiting to synchronize with the Pnp
 subsystem.
Arg2: 000000000000012c, Timeout in seconds.
Arg3: ffffe000bb2ae040, The thread currently holding on to the Pnp lock.
Arg4: ffffd0012ddec980, nt!TRIAGE_9F_PNP on Win7 and higher

ffffd001`43445798  fffff800`7c13a931*** WARNING: Unable to verify timestamp for iaStorA.sys
[COLOR=red]*** ERROR: Module load completed but symbols could not be loaded for iaStorA.sys[/COLOR]
 iaStorA+0x81931

iaStor is Intel's Raid Driver (IRST) which also contains Intel's AHCI driver. Are you running Raid? which and how many hard drives do you have. I really need a lot more information to be able to advise you on what to do.

 

[civilwar142pa]

I didn't think anyone would reply to this or I would've put a lot more information in the post.

Anyway, I did everything you suggested already for different reasons. I started checking things out because after the most recent Windows updates, windows media player wouldn't open properly and my computer was intermittently restarting itself when I told it to sleep. On one of those occasions I got that BSOD. It hasn't happened before or since, and I checked to make sure the software was up to date for RAID, and it is.

Resetting my power options seemed to fix the original problem, but I ran the system file checker anyway in an elevated cmd prompt to make sure there weren't any other issues. It turns out it found corrupted files each time I ran it and couldn't fix them. I don't have any other issues besides media player at this point.

 

[essenbe]

I'm wondering, just for curiosity, why you thought no one would answer. There are only a few of us who do this and a ton of posts in the BSOD section. We miss some occasionally, but we do try hard not to.

Please run the BSOD Posting instructions and upload the zip file here in your next post. But, from what I saw in the one dump file looked to be errors in your Hard drive. IRST is what ended up getting the most blame. But, there were references to I/O errors, Storage Port drivers, Filter Manager and all of those point to a Hard Drive problem, plus the sfc scan is saying you have corrupted files on the hard drive. Please add to your System Specs what hard drives you have and your PSU.

please tell me what hard drives you have and which ones you have in Raid. Raid is really not advisable for desktop systems. It is more of a Server function. The risks usually outweigh any gains you get. Just like in this case. You are going to have to break the Raid in order to test the hard drives, I am pretty sure.

 

[civilwar142pa]

Yeah, I've heard some interesting things about RAID. I didn't install it, though, it came that way and I never felt the need to change it. I only have the one hard drive with a recovery partition. Not surprisingly, I've replaced nearly everything else except for the hard drive in the time I've had this laptop, so I'm not shocked it's having some issues.

Thanks for taking the time to look at everything. I can upload the log files I have from the file checker if that's of any use to you.

 

[essenbe]

wait. You can't be running Raid with 1 hard drive, it takes a minimum of 2 hard drives. Please go into BIOS and look for the sata controller and tell me what it is set to (IDE, AHCI or Raid) It will probably be hard to find. Most OEMs lock down their BIOS pretty tight and make everything hard to find.

Please do not run any hard drive cleaners. They, by default, delete all windows error reporting and dump files. If you are talking about the CBS files generated by the sfc /scannow, save them we may need them pretty soon. What I need is the BSOD Posting instructions http://www.sevenforums.com/bsod-help-support/96879-blue-screen-death-bsod-posting-instructions.html and upload them here.

 

[civilwar142pa]

I checked the BIOS and there's absolutely no information about the hard drive in there. I've just been assuming that since there is a RAID controller installed and running on the computer that that is running the HDD. RAID doesn't really 'need' two hard drives, that's just what it's actually for.

I've heard of manufacturers using it just so they can put RAID in their product name and sound cool. That's not surprising to me.

Is there a way to find that information if I were to pull the HDD and plug it in as an external HDD to another computer? I can do that easily.

 

[essenbe]

Just because you have raid selected in the BIOS for the sata controller does not mean you are running raid. Raid stands for Redundant Array of Independent disks. If you only have one hard drive, you do not have independent disks.

Please go to Device Manager and post a screenshot http://www.sevenforums.com/tutorials/9733-screenshots-files-upload-post-seven-forums.html of device manager with IDE ATA/ATAPI controllers expanded.

I will have a look at your files and get back with you shortly.

 

[civilwar142pa]

I understand completely what RAID is for, but I have seen laptops ship using it with only one hard drive. It doesn't make sense, but it happens sometimes. My desktop shipped with it, too, but at least that made a little bit of sense since it came with one drive but could be expanded to two.

I don't have an IDE/ATAPI category in device manager at all.

 

[essenbe]

civilwar142pa, the only dump file you have is the one I looked at last night.

Please uninstall Dameon tools. It is a known BSOD cause.
Daemon Tools, Alcohol 120% and Power Archiver Pro uses SCSI Pass Through Direct (SPTD), which is a well known cause of BSOD's.

1. Uninstall Daemon Tools.
2. Download the SPTD standalone installer and follow these steps:
- Double click the executable to open it
- Click the button shown below



If the button it is grayed out, as shown in the image, there is no more SPTD installation on your system, and you can just close the window.


After that, please open an 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.

Please also run Seatools for DOS http://www.sevenforums.com/tutorials/313457-seatools-dos-windows-how-use.html#Part3

Please let me know the results. Have you had more than just the one BSOD? If you have had several please make sure your computer is configured for Small Memory Dumps http://www.sevenforums.com/tutorials/174459-dump-files-configure-windows-create-bsod.html

Can you tell me which version of Chrome you are using? Is it the BETA Version?

 

[civilwar142pa]

I've only had the one BSOD. I'll try this and let you know how it goes, although I've never had any problems with Daemon tools before, and I've had it installed for a long time.

Thanks for your help.

 

[civilwar142pa]

Ok, I've uninstalled Daemon Tools.

I ran sfc three times and still got corrupt files.

On the second reboot, I got another BSOD.

On Seatools, I ran the short generic test, which passed.

My Chrome is the stable version 42.0.2311.90 m

 

[essenbe]

Could I get you to run the extended test in Seatools please. The reason I asked about Chrome is I found a lot of errors from Chrome. Could I also get you to run the BSOD Posting instructions again. The file you uploaded was empty.

 

[civilwar142pa]

There was a new BSOD anyway (two actually) caused by the same file iastor.sys which I believe is an Intel driver.

Each time I try to run Seatools now that BSOD comes up. I'm having the Intel driver utility update anything that needs it right now to see if I can get Seatools to work.

In the meantime, here's the updated minidump.

 

[essenbe]

There are no dump files. If you were running Seatools for DOS, the it was running from ram and Windows was not loaded. That means there would be no dump file. iaStor is the Intel Raid driver. It should not have been loaded.

 

[civilwar142pa]

I was trying to run Seatools for Windows. I'll try DOS and see what happens. Either way that's an issue. There's still no dump file showing in that zip folder?

 

[essenbe]

Only the one you originally had. Check and make sure your computer is configured for Small Memory dumps. http://www.sevenforums.com/tutorials/174459-dump-files-configure-windows-create-bsod.html
Then go to C:/Windows and make sure you have a Folder named Minidump. If you do not, create one.

 

[civilwar142pa]

Everything is set up to create the files, so I have no idea why it's not doing it.

I've tried every way I can think of to run SeaTools for DOS with no luck. I can't get it to boot from an internal CD drive, an external CD drive, or a USB drive. I'm going to try pulling out the HDD and connecting it as an external drive to a different computer and running the scan. Obviously something isn't working correctly.

 

[civilwar142pa]

Even plugging the HDD Into a different computer doesn't work. So I'm thinking the easiest thing might be to try refreshing windows and if that doesn't work to format the drive and reinstall windows. Do you think that will fix whatever is going on?

 

[essenbe]

A clean install should fix it, unless the hard drive is bad or unless there is another hardware problem. When you downloaded Seatools, did you download the one for DOS? It should be an ISO file, which should boot.