BSoD on Windows 7 computer. Possible driver conflicts?

yowlexander

Honorable
Jan 25, 2014
1
0
10,510
After completely re-installing Windows 7 Professional, I thought my troubles were over. But to my dismay, a week later, my blue screens came back 10 fold. Right after my re-installation I re-installed all of my drivers from my motherboard's manufacturer site.

Site: http://www.biostar.com.tw/app/en/mb/introduction.php?S_ID=579

However, for some reason my SM Bus Controller did not install correctly and I could not find it online through Windows Update. After the next blue screen, I decided to re-install the driver chipset from the same site as before. The SM Bus Controller error went away, and my computer ran fine for a few days before this last blue screen. During the next to last blue screen (listed below), my keyboard, mouse, and monitor ceased to draw power and would not function correctly. After I got past that problem, my computer would not boot properly. The next day, I turned on the computer and all I could get was darkness and loud, single-toned repetitive beeping. I thought it could be a beep code, but as I waited through 47 of the same exact beep, I realized it was probably a just a signal to tell me that my motherboard wasn't working properly and that my computer was not able to start. I'll be posting more information as I remember it, or as it becomes available. I'm actually writing this up from the same computer that keeps blue screening. A few people have thought my motherboard is failing, but I really hope this isn't the case.

Latest Blue Screen:

IRQL_NOT_LESS_OR_EQUAL

Technical information:
*** STOP: 0x000000A (0xFFFFFA800C491918, 0x0000000000000002, 0x0000000000000001, 0xFFFFF8000C0AB881)


First BSoD (Before re-installation):

FFN_LIST_CORRUPT

Technical information:
*** STOP: 0x0000004E (0x00000000000000099, 0x000000000010B08C, 0x0000000000000004, 0x0000000000000001)


First BSoD (after re-installation):

IRQL_NOT_LESS_OR_EQUAL

Technical information:
*** STOP: 0x0000000A (0xFFFFFA80151FF8F8, 0x00000000000002, 0x000000000000001, 0xFFFFF8000C0C4A00)


My computer build:

Motherboard: BIOSTAR Tz77b LGA 1155 Intel Z77 HDMI SATA 6Gb/s USB 3.0 ATX Intel Motherboard with UEFI BIOS.

Processor: Intel Core i5-3350P Ivy Bridge 3.1GHz (3.3GHz Turbo) LGA 1155 Quad-Core Desktop Processor BX80637i5335P

RAM: DDR3 1600 (PC3 12800) Desktop Memory Model KHX 1600C9AD3B1K2/4G

HDD: Western Digital WD Blue WD10EZEX 1TB 7200 RPM SATA 6.0Gb/s 3.5" Internal Hard Drive-Bare Drive

Video Card: EVGA 02G-P3-2639-KR GeForce GT 630 2GB 128-bit DDR3 PCI Express 2.0 x16 HDCP Ready Video Card

Power Supply: COOLER MASTER eXtreme Power Plus RS-550-PCAR-E3 550W ATX12V V2.3 SLI Ready CrossFire Ready Power Supply


I actually just recovered from two more BSoDs and got this after a system repair after restart.

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.256.48
Locale ID: 1033

Additional information about the problem:
BCCode: 1a
BCP1: 0000000000000403
BCP2: FFFFF68000029438
BCP3: D0E00000660AA867
BCP4: FFFFF68000339438
OS Version: 6_1_7601
Service Pack: 1_0
Product: 256_1

Files that help describe the problem:
C:\Windows\Minidump\012514-16832-01.dmp
C:\Users\Suno\AppData\Local\Temp\WER-56503-0.sysdata.xml


EDIT: Since this last error, I tried to run a windows memory diagnostic test through my administrative tools. After only running through around 15% of the test my computer crashed again and went back to turning on for a second or two and automatically restarting until I was forced to flip the power on the back on the tower to kill the power. After trying to power back on, I could only get the same constant mono-toned beeping as before.

I got annoyed and desperate so I tried taking on my RAM sticks and using one at a time. The first time, I got the same beeping and power restart problem, but when using the other by itself, I was able to start the computer up with what seems like no problem for the moment. Stand by for update.

EDIT: 5:32PM 1/25/2014

Since being able to work on the computer again around 20 minutes ago, I tried going into my device manager and scanning for hardware changes. As my drivers were attempting to update, I found that the SM Bus Controller came up again as Device Driver not Successfully Installed: No Driver Found - SM Bus Controller. I have went to the manufacturer site and downloaded the driver under chipset on the site listed above several times. Not sure if I'm making a mistake.

From what I can tell, either my memory stick is toast, or I have conflicting drivers. The driver issue would make sense since I re-downloaded chipset drivers a few times. Here is a list of drivers listed as critical under my system information. I don't know if this is useful information, but I'm trying to give everyone willing to help me as much to go off of as possible.

Driver list from system information:
http://gyazo.com/11cfc54a571d0ee10da676ce0ca65507

I looked in my device manager and exposed hidden files and it showed that I have many duplicates (or it appears that way to me at least), I was wondering if these could be what are causing me problems, and how should I go about fixing this if so?

Device Manager extended list:
1: http://gyazo.com/4d03440be585b8fc2e372fbb090cfdba
2: http://gyazo.com/49bc5e94a359d8825775654848cc4ced
3: http://gyazo.com/1052eb67e57ef9f7a287b6fd3a2cff82
4: http://gyazo.com/fb1c83579022a86b5b6f7a05bb631ac4


Update: 2:05 PM 1/26/2014

I ran memtest86 with both sticks of memory in for 10 passes. It didn't find anything, but when I went to reboot, my computer couldn't start. After prompted to do a system restore, I did. This allowed me to get back on for now, but I don't understand why I was able to work on one stick of my RAM fine, but not only the other if no errors were found with either stick after running memtest86. All I can assume is that I have major driver conflicts.


Update: 5:05 PM 1/26/2014

I downloaded the BlueScreenViewer from NirSoft and found that these files are apparently involved in my blue screens:

1: http://gyazo.com/782398b5554ff9e7c8b90677ccb814ae
2: http://gyazo.com/c2f515214e5aac04a02c1c86c98cc814
3: http://gyazo.com/b678072077ee43aefe5c2613b2c7253a

Update: 1/28/2014 11:00 AM

After trying to uninstall my Nvidia driver, and seeing that my computer was working okay for awhile, I thought to myself that since my problems seemed to come up when I try to play TF2 or other things along those lines, that I might have found the issue. However, after trying to re-install the "most up to date" Nvidia driver from the manufacturer's site and trying to test run TF2, I crashed. Back to the same issues again. Running for a few seconds and repetitively crashing, and CMOS failure at boot after removing the stick of RAM that I before thought might be bad. I also ran memtest86 again after the crash and found 3128 errors in 12 seconds before freezing.

This listed an Unexpected Interrupt - Halting CPU0.

Due to this, I have had 3 more people diagnose me with a failing motherboard.

I have a lot more blue screen another other information which I will post as soon as I can.

For now though, any thoughts?
 

RealBeast

Titan
Moderator
I doubt that it is the motherboard. I would test the memory first with the free memtest86 from HERE -- burn it to a CD and boot from it and let it run a few passes. Any error indicates bad memory.

If the memory passes, then I would update all device drivers one at a time to find the problem driver, and it very likely could be that System Management Bus Controller driver that didn't install. You may need to do another re-install to fix it, although perhaps a repair install like THIS will do.