XPost: alt.comp.periphs.mainboard, alt.comp.periphs.mainboard.supermicro, alt.comp.pheriphs.mainboard.supermicro
XPost: alt.windows7.general
On 7/2/2010 8:50 AM, Bolwerk wrote:
Bolwerk wrote:
Gene E. Bloch wrote:
Some motherboards require special Windows drivers (or at least that was
true for me a few years ago). You might have to check into that at the
manufacturer's site.
As I recall, Windows provides an opportunity to install drivers during
installation of the OS - which might not be what you want to do. If
there
are drivers needed, and if you're lucky, the manufacturer might tell you >>> how to install them without reinstalling Windows.
Well, I've had some success. It's definitely a BIOS problem. I mass
disabled some BIOS features. I'll see if I can isolate what the
problem was and report back.
It looks like having Core Multi-Processing enabled in the BIOS was the show-stopper for Windows. So I am able to get back into Windows again.
I'm still getting blue screens. They're much less frequent (every few hours, instead of a few times an hour). I'm not sure what the culprit
is. It seems upgrading the video driver improved things, but daily
BSODs is still a bit much.
Anybody have any ideas? Memory?
Thanks!
Char Jackson mentioned Hiram's Boot Disk with a memory test program in a previous message, another option is an Ubuntu Linux Live CD, which comes
with Memtest86+, also you can download and run the utility (free)
cpuburn to stress test the CPU.
https://www.howtogeek.com/howto/16666/diagnose-hardware-problems-with-an-ubuntu-live-cd/
--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)