The first driver to update is your Realtek Ethernet driver when you get to the driver updating stage. http://www.realtek.com.tw/downloads/...&GetDown=false
As to the crash, it does indeed point to memory... Did you ever find the motherboard revision number?
Just double checked again, it is in fact GA-MA770T-UD3P Revision 1.1.
I'll go ahead and install things as recommended, if I can't trust the gurus, who can I trust?Unfortunately that link gives me an error blocking direct links to inside content.
Yeah, the page may be down at this time. See if you can get at it later. You can also try Rt64win7.sys which has the same link to Realtek drivers.
It took it awhile but the Realtek site came back up at some point. Got the linked drivers installed.
Upon retrospect, I think the issue ended up being a third degree PEBKAC. I never bothered to identify the motherboard properly in the first place trusting in Gigabytes identification tool when I couldn't find my specific model via their dropdown lists. Speccy was reporting the right motherboard the whole time I think considering I posted the correct model at the start of the thread. From there on it was a series of wrong drivers over and over which eventually lead to instability, at least I think/hope.
There hasn't been another crash yet at all, so thusfar things are looking good. Though, this wouldn't be the first time I thought that. Either way, I'm confident that the worst trouble is solved simply in manual identification.
Good news! Keep us posted how the system responds over the next few days. Best wishes!
Further good news is I was able to update the audio and chipset drivers from the manufacturer page. Last time the chipset drivers resulted in windows failing to boot but everything's going well now.
Should be able to call it officially fixed if I don't see a crash in the next few days!
That is excellent news.Keep us updated as things progress.
Alrighty, it's been a few days since the format and I've spent the time since stressing the system with as much ram and cpu intensive software as I can, playing high end games, leaving them running benchmark loops overnight, running Prime95, OCCT, running HD video, needlessly compiling HD videos out of random other HD videos, the list goes on. I have had zero crashes, everything has been super stable.
At this point I'm ready to call everything simple user error, I should have checked the mainboard directly instead of trusting in identification software. Many lessons have been learned and many a blue streak has been uttered.
As a rundown of events for anyone who follows into this thread at a later date:
Windows 7 64bit, though, I'm sure it applies to 32bit as well, began randomly crashing anywhere from every few minutes to a couple weeks, the bugcheck codes were almost entirely 0x1e, 0x3b and 0x7e. Checking the majority of them in Windbg pointed to VISTA_DRIVER in some variation. Turns out, this is completely the case as what had happened were the wrong drivers were installed for the motherboard, starting with drivers for GA-MA770-UD3 rev 1.0, then GA-MA770T-UD3 rev 1.0 and 1.1, and finally the correct GA-MA770T-UD3P Rev 1.1, however, at this point the number of bad drivers piled up was just too much and windows completely broke down, even after being repaired.
It's easy to simply trust in a manufacturer's hardware identification software as much as it is to trust in programs like Speccy and CPU-Z to tell you what hardware is, but if you're working with an older system or used hardware (which is unwise in itself), you had best physically open the case and confirm model and make yourself.
And finally, thanks again, writhziden for your help, I learned a lot from you as well and have added another resource to my personal knowledge bank with these forums. I probably would've just ignored the bluescreens eventually and lived with them if I hadn't kept updating stuff till it broke windows! This isn't meant at all as a slight, I seriously am thankful to have broken things so badly that I was forced to fix them with the reinstall and manual hardware checks. I never would have otherwise I don't think. And I know this never would have happened in itself if I hadn't supplied erroneous information in the first place. But now all is well from what I can tell, and I can stop obsessing over fixing it, a massive load off my mind.
You're welcome. Glad to see things are going well. :)
And don't worry, I did not take it as a slight. Sometimes it takes some wrong steps to eventually get to the right steps. I am just happy it all worked out in the end.
Quote