New
#41
Thanks Dave... this is good info to know. I've read in many places about people installing Windows 7 from USB or CD sources and never knew how they got them.
Thanks Dave... this is good info to know. I've read in many places about people installing Windows 7 from USB or CD sources and never knew how they got them.
The USB memory stick method is easy to do and a much faster way to run the installation.
I've been using it for about a year now, and it's great.
Hi -
If problems creep up again, to help ascertain if the Windows 7 installation DVD you have is corrupted in some manner and causing trouble, I suggest that you install the Windows 7 Enterprise Edition 90-day trial version. You can download the ISO directly from Microsoft and burn it to DVD.
Windows 7 Enterprise | Trial, Evaluation, Test, Download
Use KillDisk on the HDD prior to installation.
If you encounter similar problems installing the Windows 7 Enterprise Edition, then hardware must be scrutinized more closely.
BSODs occur under Windows. The BSOD you reported had a bugcheck = 0x50 = invalid memory referenced.
Meanwhile, I would allow ALL Windows Updates to come in.
www.update.microsoft.com
Regards. . .
jcgriff2
`
Whoops, another crash! Wasn't doing anything at all... I got Windows to successfully install, and was just going to leave it idling for a day or two with no activity. Here are some attachments for the pro's to look at. Keep in mind that after the install of Windows, I didn't install anything, including drivers. It was a barebone install of the OS to check system stability.
0x50- Probably Caused By hardware.
Update your Realtek network adapter drivers: Realtek
Update your ATI drivers: https://a248.e.akamai.net/f/674/9206...win7_64_dd.exe
...Summary of the Dumps:Code:Built by: 7600.16385.amd64fre.win7_rtm.090713-1255 Debug session time: Sun Aug 29 01:15:40.813 2010 (UTC - 4:00) System Uptime: 0 days 0:10:48.910 BugCheck 50, {ffffffffffffff8b, 1, fffff800028ce1af, 0} Probably caused by : hardware ( nt!ExAcquireResourceExclusiveLite+142 ) BUGCHECK_STR: 0x50 PROCESS_NAME: System ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии
What were the grounding issues?
You should have the HDD SATA cable plugged into SATA port 0, the CD/DVD can be plugged into any other port but recommended to use the last port.
Do you get a single short beep with everything connected internally and externally?
Is the above with nothing connected externally and everything still connected to the motherboard inside the case?
(Obviously, just to confirm)
Is the CD/DVD cable still connected?
If this is correct, what do you normally connect externally?
Keyboard, Mouse, Monitor, and?
Don't know if this is normal...
Is the 47c temp when it's running at idle?
Seems a bit high.
Check your temps with Core Temp.
Did you assemble the computer?
Stock CPU cooler?
What case and cooling fans?
Last edited by Dave76; 29 Aug 2010 at 05:34.
At some early point during assembly, I was unable to successfully power on anything. I thought my power supply was bad... so I did a load test on the 24-pin plug and verified the power supply was working properly. I then removed the motherboard from the case and it powered on correctly. Guess it was screwed down too tightly.
Currently, the HDD is plugged into port 0, CD/DVD is plugged into port 4
Yes, single short beep with all externals removed and only the internals hooked up to the motherboard. ...and yes, the CD/DVD cable is still connected. I was going to disconnect that to possibly rule out a bad drive.
...speakers and network cable
I'll check temps and post back
Yes, I assembled it... It's the stock heatsink that came with the CPU. Using a Rosewill Challenger case with stock fans inside.
CPU temp is currently 29-35 degrees Celsius. ...checked with CoreTemp 0.99.7
This question is important.
Do you get a single short beep with everything connected internally and externally?
Normal use scenario.
Good job answering the questions.
The temps are in range.
Most AMD temps I've seen are usually the same for all and a little lower.
We might come back to this.
Check the temps next time you run Memtest86+ or Prime95, let us know the results.
Give Prime95 torture test - blend, a quick run, just until the temps stabilize.
Yes... single short beep with everything connected, both internals and externals. I'm kind of iffy running Prime 95... I've read some stuff that doesn't sound too safe, such as "...this step cooks your CPU", etc. I'm just afraid I'll run into a scenario where I won't be able to get back into Windows. This happened before after running KillDisk, although I eventually got Windows to reinstall on the hard drive.
Also, everything has been running fairly stable for the past 36 hours or so. I turned off the computer several times and it has been able to boot back up with no halts or crashes. But, I was beginning an installation for Wow.exe earlier today, and I received a generic error and some screen flashing/freezing. The computer restarted itself and CHKDSK ran following a restart (seemed to edit some bad files or something). I was starting to suspect a video card error, since when I tried to access the BIOS screen, it was just a bunch of wierd illegible characters. Everything seems to be back to normal now though, as long as I don't do anything :P