Hello,
I have a really spooky problem with my newly built
computer and I would appreciate any help you can give.
I know this is a fairly long post, but I wanted to
give as much detail as I could in the first place.
Thank you in advance for your time.
The system is as follows:
AN7 V1.0, BIOS seems to be 1.2 (just bought it, no
flashing), no cut trace on the back, plastic ZIF lever
XP-M 2500+ IQYHA (forgot to take the week no)
Thermaltake Silent Boost K7 w. Arctic Silver 5
ASUS 5900XT
2x256 Kingmax PC3200
20G Seagate Barracuda ATA III, UDMA 100
Chenbro Gaming Bomb Case, Standard edition
360W PSU, FSP Group Inc., model no. FSP350-60PN (PF)
+3.3V -> 28A
+5V -> 30A
+12V -> 16A
+5Vsb -> 2A
-5V -> 0.3A
-12V -> 0.8A
(+3.3V & +5V = 220W Max)
Things went like this: I assembled the pc, boot it up
and set the basic things in bios, such as time, date,
boot sequence, etc. Then I entered the SoftMenu to up
the processor a bit as it was at a 5x100 default. I
set it at 14x133@1.465V because I wanted to play safe
at first and just go with the AMD defaults until I
have an OS up and ready for testing/tweaking/OCing. I
had only Win98SE to install at the time so I went with
it.
Things went smoothly through the whole process until
the end. After the last restart though, when the SO
was booting for the first time "for real", I got a
BSOD out of nowhere, while still in the "text" portion
of the startup sequence, with the motherboard's
digital display stuck on "48". The same thing after a
couple of restarts. I looked up the code in ABIT'
manual - nowhere to be found, only "47" and "49" were
documented and nothing in between. I entered in "safe
mode" and windows booted until the graphic UI as per
usual.
The next "normal" restart I got this error message:
"There is a problem with your display settings. The
adapter type is incorrect, or the current settings do
not work with your hardware.". I noticed the digital
display on the mb switched to "48" right from this
stage. Pressed "OK" and the "Display Properties"
window popped up with (Unknown Monitor) on (Unknown
device), 16 colors, 640x480, unchangeable. "OK" on
this one and another window with Yes/No option: "Yes"
for "resetting" display settings on the next restart
at 640x480x16 and "No" to retain my original settings.
First I chose "Yes" and restarted -> BSOD at text
startup. Hard reset -> "normal" boot -> "There is a
problem with your display settings..." error. Another
"Yes", reboot "normal" -> the same error again. This
time I chose "No" and I remained in windows. Restart
"normal" -> this time not even a BSOD, a completely
blank screen and the monitor switched on standby like
it hadn't received any kind of video signal. From now
on, the "normal" boots would always hang up with blank
screen and no vid signal; if preceded by a
"safe-mode", I had the aforementioned error and the
yes/no option, after which the whole loop would repeat
itself.
This remained the same even after a full, from-scratch
windows reinstall (three times). Moreover, I also
booted in my linux distro, a Suse 8.2. The startup
would go just fine, until trying to switch from the
text (console) mode to graphic mode, which failed with
this message from the X server: "Fatal error: no
display adapters detected".
I started swapping components: the same thing with
either my old video card or my old PSU or both. Both
the video cards and the power supplies worked just
fine when tried on the old system. There was nothing
else in the new system at the time, just the basic
components as listed atop, to minimize installation
hassle. The outcome was always the same. Tested with
single channel or dual channel -> the same. I have to
say that the only components I couldn't swap and test
with something different were the processor and the
memory, for I didn't have any "spares" for them.
Besides this video-related problem, I also had one
with the onboard IEEE1394 controller. Both windows and
linux would completely hang up when trying to
initialize it. Disabling it from BIOS was the only
solution. Needless to say, this looked like nothing
compared to the display related problem, this was just
another kick in the ribs.
At this point, I brought the board back to the vendor,
asking him to check it out, because it sounded like a
hardware problem to me. The second day he called and
said that when he tried to power up the board, it had
no voltage on the AGP port, got no video signal and
couldn't even get himself into bios. That was weird
enough, as it booted just fine in my hands, just had
that hanging "48" problem. But he said that he would
return my board to the distributer / importer and give
me a new one. Easy said, easy done and I'm back at
home with a new AN7 to try out. The VERY SAME thing
happened.. I couldn't believe it. Like the first one,
the new board would also hang at a "normal" boot into
windows, with the same mysterious error code of "48",
in the same conditions as before. At this point I was
running out of ideas and I started looking on the
internet for that "48" code. Nada, niente, zilch..
also, I found many other users with various problems
related to this board, but nothing exactly like mine.
I kindly ask anyone who might have an idea about
what's going on to lend me a helping hand, I'm all out
of ideas..
Thanks in advance,
Peter
I have a really spooky problem with my newly built
computer and I would appreciate any help you can give.
I know this is a fairly long post, but I wanted to
give as much detail as I could in the first place.
Thank you in advance for your time.
The system is as follows:
AN7 V1.0, BIOS seems to be 1.2 (just bought it, no
flashing), no cut trace on the back, plastic ZIF lever
XP-M 2500+ IQYHA (forgot to take the week no)
Thermaltake Silent Boost K7 w. Arctic Silver 5
ASUS 5900XT
2x256 Kingmax PC3200
20G Seagate Barracuda ATA III, UDMA 100
Chenbro Gaming Bomb Case, Standard edition
360W PSU, FSP Group Inc., model no. FSP350-60PN (PF)
+3.3V -> 28A
+5V -> 30A
+12V -> 16A
+5Vsb -> 2A
-5V -> 0.3A
-12V -> 0.8A
(+3.3V & +5V = 220W Max)
Things went like this: I assembled the pc, boot it up
and set the basic things in bios, such as time, date,
boot sequence, etc. Then I entered the SoftMenu to up
the processor a bit as it was at a 5x100 default. I
set it at 14x133@1.465V because I wanted to play safe
at first and just go with the AMD defaults until I
have an OS up and ready for testing/tweaking/OCing. I
had only Win98SE to install at the time so I went with
it.
Things went smoothly through the whole process until
the end. After the last restart though, when the SO
was booting for the first time "for real", I got a
BSOD out of nowhere, while still in the "text" portion
of the startup sequence, with the motherboard's
digital display stuck on "48". The same thing after a
couple of restarts. I looked up the code in ABIT'
manual - nowhere to be found, only "47" and "49" were
documented and nothing in between. I entered in "safe
mode" and windows booted until the graphic UI as per
usual.
The next "normal" restart I got this error message:
"There is a problem with your display settings. The
adapter type is incorrect, or the current settings do
not work with your hardware.". I noticed the digital
display on the mb switched to "48" right from this
stage. Pressed "OK" and the "Display Properties"
window popped up with (Unknown Monitor) on (Unknown
device), 16 colors, 640x480, unchangeable. "OK" on
this one and another window with Yes/No option: "Yes"
for "resetting" display settings on the next restart
at 640x480x16 and "No" to retain my original settings.
First I chose "Yes" and restarted -> BSOD at text
startup. Hard reset -> "normal" boot -> "There is a
problem with your display settings..." error. Another
"Yes", reboot "normal" -> the same error again. This
time I chose "No" and I remained in windows. Restart
"normal" -> this time not even a BSOD, a completely
blank screen and the monitor switched on standby like
it hadn't received any kind of video signal. From now
on, the "normal" boots would always hang up with blank
screen and no vid signal; if preceded by a
"safe-mode", I had the aforementioned error and the
yes/no option, after which the whole loop would repeat
itself.
This remained the same even after a full, from-scratch
windows reinstall (three times). Moreover, I also
booted in my linux distro, a Suse 8.2. The startup
would go just fine, until trying to switch from the
text (console) mode to graphic mode, which failed with
this message from the X server: "Fatal error: no
display adapters detected".
I started swapping components: the same thing with
either my old video card or my old PSU or both. Both
the video cards and the power supplies worked just
fine when tried on the old system. There was nothing
else in the new system at the time, just the basic
components as listed atop, to minimize installation
hassle. The outcome was always the same. Tested with
single channel or dual channel -> the same. I have to
say that the only components I couldn't swap and test
with something different were the processor and the
memory, for I didn't have any "spares" for them.
Besides this video-related problem, I also had one
with the onboard IEEE1394 controller. Both windows and
linux would completely hang up when trying to
initialize it. Disabling it from BIOS was the only
solution. Needless to say, this looked like nothing
compared to the display related problem, this was just
another kick in the ribs.
At this point, I brought the board back to the vendor,
asking him to check it out, because it sounded like a
hardware problem to me. The second day he called and
said that when he tried to power up the board, it had
no voltage on the AGP port, got no video signal and
couldn't even get himself into bios. That was weird
enough, as it booted just fine in my hands, just had
that hanging "48" problem. But he said that he would
return my board to the distributer / importer and give
me a new one. Easy said, easy done and I'm back at
home with a new AN7 to try out. The VERY SAME thing
happened.. I couldn't believe it. Like the first one,
the new board would also hang at a "normal" boot into
windows, with the same mysterious error code of "48",
in the same conditions as before. At this point I was
running out of ideas and I started looking on the
internet for that "48" code. Nada, niente, zilch..
also, I found many other users with various problems
related to this board, but nothing exactly like mine.
I kindly ask anyone who might have an idea about
what's going on to lend me a helping hand, I'm all out
of ideas..
Thanks in advance,
Peter
Facebook
Twitter