New
#11
and i found out something, like some sort of a pattern.. whenever i stay idle for a while, i get the BSoD..
but then.. even then i dont stay idle, i'll get the BSoD after a certain time..
this is very frustrating..
and i found out something, like some sort of a pattern.. whenever i stay idle for a while, i get the BSoD..
but then.. even then i dont stay idle, i'll get the BSoD after a certain time..
this is very frustrating..
Wilson, also please fill out your system specs. You can click 'My System Specs' in the bottom left of your last post, In that window will be a link 'Update my system specs', click that. Update them as completely as possible including model numbers where appropriate. When finished, click save at the bottom. It will help us to help you. At the bottom left of this post, click My system Specs to see mine for an example of what we would like to see.
If you ran the sfc /scannow System file verification, even if that is the one you BSOD during, see if anything is in the file it creates. Open an elevated command prompt (right click command prompt and select run as administrator) copy/paste this into the window. findstr /c:"[SR]" %windir%\Logs\CBS\CBS.log >"%userprofile%\Desktop\sfcdetails.txt" It should place a txt file on your desktop of the CBS log. Right click the txt file, select send to>compressed zip folder. place that on your desktop and upload the zip folder when you reply after finishing running Koolkat's other instructions.
Also, find a good utility like Core temp or real temp to monitor your system temps. If you have a dedicated graphics card there are utilities provided by the manufacturer of your card that will help with that. And as always with these type situations, if you are overclocking, reset everything to default values.
I'm sorry, i mean I couldnt finish the Disk Check step, because I always get the BSoD at the last step. I'm done with all other steps. All scans show no threats found.
After i ran the system file check, I followed your (essenbe) steps. However, nothing was in the text file that was created.
So what are the next steps I have to take to solve my BSod problem..?
I suspect you are using the Hatachi drive for a data drive. I would recommend you backing up your data to an external drive. If you have an extra hard drive, replace the Hatachi. The Caution on the Crystal Disk Mark means the drive is likely to fail and may be the reason for at least the majority of your issues. If you are still under Warranty, Dell can replace the drive for you, if you run their diagnostic scan which should be built into your computer. Let me know exactly what you use the Hitachi for, and any other hardware you have replaced since owning the laptop. Try running this test for your memory. RAM - Test with Memtest86+ It runs from ram and will not be using the hard drive. It is best run overnight as it takes quite a few hours to finish. Try to get 7 passes from it. If you get any errors you can stop right then.
I'm using my hitachi hard drive as my C drive, where everything is installed on it and downloaded on it. it's basically the main hard drive..
I've noticed something on my IRST: my hitachi drive is marked as failed.. any ways on how to fix it?
I ran the diagnostic scan from dell, no errors or whatsoever..
Have you downloaded and monitored your temps with core temp, linked to in post #13? Also see what results you get from Hitachi's hard drive diagnostic test. I believe you said you were unable to complete disk check. Try that again along with Memtest86+. Chrystal disk Mark simply monitors the hard drive SMART results ( the drives own Self Monitoring and Error Reporting function).
Of all the tests you have done so far, the only one that has given any indication of having a problem is the Crystal Disk Mark test. Then you were unable to complete Check disk. So, I would continue to pursue that angle, while also monitoring temps whenever you are running the laptop. A very high percentage of BSODs are ram related, which is why I asked you to run Memtest86+. That is why we are asking these things. Also, if you have had several BSODs since you turned in the SF diagnostic results, you may want to run that again to see if Koolkat can get more info on the cause of the BSODs. Unfortunately, this is not an exact science and we have to run tests to find out the problem. I hope this explains a little of why we are asking you to do these things. Once we find the problem, we can usually rectify it. So far the only problem we have found is an indication it is a hard drive problem, possibly. In the first results, Kitkat asked you to remove the IRST driver, which is a storage driver, again pointing in that same direction.
I just downloaded Core Temp, and so far, the readings are around 45-47 C .. is that considered high?
So you want me to uninstall my Intel Rapid Storage Technology to see if BSoDs still occur after uninstallation?
If those temps are at idle, yes a little high but not a great deal. Laptops always run hotter than desktops. I'll leave the IRST up to the expert. Koolkat reads the dump files, I'm not that smart. I use it and have never had a problem with it as long as you keep it updated, but again, that's up to Koolkat.
The crashes are blaming the iaStorA.sys driver, this is the Intel RST SATA driver.
There are known issues with the latest Intel RST drivers, this can also be caused by the hard drive failing, it's possible that the issue with the Intel RST driver is causing the HDD to show errors.
Run the hard disk test first, then install an older RST driver if the HDD tests pass.
Crystal Disk Mark is indicating a problem with the hard drive.
First run the Hitachi HDD test.
D/L and run the HGST Drive Fitness Test
Use the Flash drive version, this will test the hard drive without the RST driver.
Run the Quick Test first, if it passes then run the Advanced Test.
Let us know the results.
If the above tests pass, then install the Intel RST Version: 11.2.0.1006 driver.
The drivers after this version have been known to cause instability in some computers, I have seen it with a couple Dells, using this version will help if the RST driver is causing the crashes.
Let us know if you have any questions.