New
#41
Thanks for the update :) .
This topic is pretty much solved , but I won't mind hearing the final verdict about the source of the noise.
Thanks for the update :) .
This topic is pretty much solved , but I won't mind hearing the final verdict about the source of the noise.
It's been a few days and the noise hasn't come back after a fan stopped working.. so I think it's safe to say that the fan that broke was the source of the humming noise. Among other news, I just got a BSOD on my mostly new system. Not sure if this is a random occurrence and won't happen again, but let's be on the safe side and check?
Sure no problem :) .
The bugcheck is quite obviously due to intel rapid storage (Driver Reference Table - iaStor.sys),
it's all over the stack.
What is your storage configuration, RAID, basic / dynamic? It would be helpful if you generate a new
.rar file with the SFDT :) .
When you installed the new motherboard, did you install the Gigabyte software that ships with it?
Did you download all of the latest drivers from Gigabyte's website or did you use the CD?
I forgot about the CD and I no longer have it now. When I reformatted/reinstalled windows, I went and downloaded software that scans for all outdated drivers/missing drivers and auto-downloads/installs them all, so I think it should all be up to date. I'm not sure what you mean by storage configuration, so I'd assume it's default (basic?)
I attached the SFDT for my current pc
Thanks :) .
What software was it?
Auto driver downloaders are usually incompetent in installing the properly tested WHQL drivers
which means they do more harm than good.
If the dump was a one time occurrence, I wouldn't change anything just yet and spare IRST for now .
Just a side note, you have a 3TB HDD (WDC WD30EZRX-00MMMB0), it is formatted as a NTFS
file system which peaks at 2TB, so you have an unallocated space.
Please > Disk Management - Post a Screen Capture Image
Yeah I have a 3TB HDD that has around 750GB of wasted space that I can't use. I tried following these steps: http://answers.microsoft.com/en-us/w...c-68b599b31bf5 and it simply didn't work.
I'm not using all of the space yet, so it's alright, here's the screenshot: https://i.imgur.com/9XKcnDM.png
The driver scanner type application that I used, I'm 99% certain you're unfamiliar with it because it's chinese (my cousin did it for me) so I don't even know what it is myself.
Should I download my motherboard's bios and install?
I got another bsod earlier this morning, attached is the minidump.
Last edited by Mangaza; 24 Oct 2013 at 14:57.
Thanks for the feedback :) .
As I said before the automatic driver installers are good at breaking drivers installations and installing
half-decent drivers and should never be used.
It seems that it has been proven why that is with your recent bugchecks as the latest is typical for driver
fault, unfortunately it wasn't caught red handed so we have some digging to do.
First I would deal with IRST, then enable Driver Verifier to help us catch it in the act.
As for the BIOS update normally it would be a valid idea only if the drivers were installed
in the correct manner and order, I read on Gigabyte's website that the USB driver must
be updated in advanced prior to flashing the BIOS so I would hold off on doing that at the moment.
Please enable driver verifier following this TUTORIAL | But using the settings below:Arc said:
Keep us posted :) .
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation", "Force Pending I/O Requests", "IRP Logging" and click "Next"
- Select "Select driver names from a list" and click "Next"
- Then select all drivers NOT provided by Microsoft, Unknown, or Macrovision and click "Next"
- Select "Finish" on the next page.
[QUOTE=YoYo155;2575131]
I followed the instructions above and get this message: https://i.imgur.com/JBLq0Mm.pngArc said:
I have rebooted my computer twice after getting the message that I have to restart my computer to apply these changes but the message keeps on coming up. Any thoughts or negatives for this? Also, I'm not exactly sure uninstalling the intel stuff did.
After I apply those settings to verifier and restart my computer... loading windows takes 4-5x longer than usual and cpu usage is consistently above 70% and each time I try to do something it's super laggy and slow, to the point where I literally can't do anything because things respond so slowly. I deleted the settings on verifier and restarted my PC and everything went back to normal.
Thanks for the update :) .
Do you mean that every time you restart the PC the drivers are being reinstalled?
Did you remove IRST from the Add or remove programs as well?
Which drivers / options did you select for Driver Verifier?
It's normal for DV to take a toll on system resources and make the PC slower than usual.
What you're describing is a bit excessive, although performance hit and usability is some what relative.
Yeah I uninstalled the IRST program and uninstalled the driver. I 100% followed the instructions you provided me. Windows is on an ssd too so I was baffled how long the windows load took. It was so bad that when I opened up speedfan (I usually leave that open to monitor temps), it froze up instead of completely loading and gave me the message that speedfan was taking super long to load and gave me the options of closing the program, reopening it, and some other option. I did this:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation", "Force Pending I/O Requests", "IRP Logging" and click "Next"
- Select "Select driver names from a list" and click "Next"
- Then select all drivers NOT provided by Microsoft, Unknown, or Macrovision and click "Next"
- Select "Finish" on the next page.
Also, the computer needs to restart for changes to take effect stopped after restarting like 4 times.