Solved BSOD error 7a,f4,109

[lzb2811]

Hi,

I have a custom build pc without any problems for the past 3 years. Just three days ago, I get random BSOD from time to time, and everytime it BSOD, I get different error code that comes with it. I tried to solve it myself using google remove memory, unplug my SSD HDD one by one (apart from my main system SSD), nothing solve the problem. Please help.

I've attached the debug file and my system info.

Windows 7 Home Edition 64 bit
i5-2500k
Gigabyte Z68X-UD4-B3
2 X 4GB Kingston Hyper-X DDR3
Crucial M4 SSD 128 GB (System)
Crucial M4 SSD 128 GB (Data)
Hitachi HDS723020 2TB (Data)
GTX 680 SLI (1 Asus and 1 EVGA)

 

[essenbe]

lzb2811, You had only 1 dump file in the SF Diagnostic info you attached. It could not find some system files and therefore would not work with the debugger.

Please make sure you have the latest firmware updates on your crucial SSDs. Crucial Firmware at one point had a bug in their firmware that would make it BSOD quite often after 5000 hours of use. Later Firmware fixed this.

Also, please make sure your computer is configured for Small Memory Dumps and that you have a folder in C:/Windows named Minidump. If there is not one there please create one. This will tell you how to configure your computer. make sure it is small memory dumps
http://www.sevenforums.com/tutorials/174459-dump-files-configure-windows-create-bsod.html

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

 

[lzb2811]

lzb2811, You had only 1 dump file in the SF Diagnostic info you attached. It could not find some system files and therefore would not work with the debugger.

Please make sure you have the latest firmware updates on your crucial SSDs. Crucial Firmware at one point had a bug in their firmware that would make it BSOD quite often after 5000 hours of use. Later Firmware fixed this.

Also, please make sure your computer is configured for Small Memory Dumps and that you have a folder in C:/Windows named Minidump. If there is not one there please create one. This will tell you how to configure your computer. make sure it is small memory dumps
http://www.sevenforums.com/tutorials/174459-dump-files-configure-windows-create-bsod.html

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

Hi,

I updated my ssd's firmware 4 days ago and it hasn't BSOD since. I think it's safe to say that it's now solved. Thanks for your help essenbe

 

[essenbe]

No problem, you're very welcome. I hope your good fortune continues. If you have any other problems, we're open 24/7.