 |
| Register | Login | |||||
 |
Main
| Memberlist
| Active users
| Calendar
| Chat
| Online users Ranks | FAQ | ACS | Stats | Color Chart | Search | Photo album |
|
| | ||
|
| Register | Login | |||||
|
Main
| Memberlist
| Active users
| Calendar
| Chat
| Online users Ranks | FAQ | ACS | Stats | Color Chart | Search | Photo album |
|
| | ||
| 0 users currently in Hardware / Software. |
| Acmlm's Board - I3 Archive - Hardware / Software - Forbidden |
New poll |  |  |
| Add to favorites | Next newer thread | Next older thread |
| User | Post | ||
|
Metal Man88 Gold axe It appears we have been transported to a time in which everything is on fire!                  Since: 11-17-05 Last post: 6298 days Last view: 6298 days |
| ||
| Well, if you thought the last two problems I had were fun, say hello to Windows XP's BSOD. The whole computer's all installing. The hard drive is partioned, and has basic setup info from XP on it. Well, it goes to install (after reboot) and gets 75% the way through 'device setup' every time I try to install it, and then... BSOD!!! With the following error code things:
0x000000F4 (0x00000003, 0x8... 0x8... etc) Something about an important thread to Windows terminating unexpectedly. I suspect it being angry at either where the hard drive is plugged in, the BIOS, or perhaps something else. Do you know of any specific possibilities? (And yes, this is the same error I get each time, no randomness which suggests memory errors, unless this sort of error is of the same ilk) |
|||
|
Tripcode Mel (USER WAS TOTALLY AWESOME FOR THIS POST)   Since: 11-18-05 From: さげMOTHERFUCKER DO YOU SPEAK IT Last post: 6302 days Last view: 6302 days |
| ||
| http://www.simg.de/ramtest/
Sounds like you've got a bad stick of RAM. Exact same thing happened to me. |
|||
HyperHacker Star Mario Finally being paid to code in VB! If only I still enjoyed that. <_< Wii #7182 6487 4198 1828 Since: 11-18-05 From: Canada, w00t! My computer's specs, if anyone gives a damn. STOP TRUNCATING THIS >8^( Last post: 6298 days Last view: 6298 days |
| ||
| Another popular memory tester. Also, there could be corrupt files on the install CD or possibly hardware issues.
BTW, any time you get a BSOD, go to microsoft.com and search for the numbers, like "STOP 0x000000F4 0x00000003". Usually just the first will find what you need (might need to include the second) but write them all down so you can tell exactly what happened. Oh, and if the letters randomly change on the BSOD, it's a memory problem.  |
|||
|
Metal Man88 Gold axe It appears we have been transported to a time in which everything is on fire! Since: 11-17-05 Last post: 6298 days Last view: 6298 days |
| ||
| Nope, happens same time every time, same error. I went to call the tech support and got reminded that, because I skimped on it (it is OEM) I'd have to pay up. Since I haven't tried everything yet, I'm gonna wait and try out the memory testers. It happens 3/4 through 'configuring devices' on the installation every time. I'm thinking it's either memory or some hardware component it dislikes. One thing that is odd: I bought dual-channel memory, stuck them in the right slots, and it reports the right amount of memory but says 'Single-Channel mode' instead of what it's supposed to be.
--Went through memtest86 test (1 runthrough of all memory) without a single error. Hrm. I could test it over and over again, but shouldn't it have shown its ugly face by now? (edited by Metal Man88 on 11-23-05 05:06 PM) |
|||
BMF54123 Since: 11-18-05 From: MOOGLES Last post: 6298 days Last view: 6298 days |
| ||
Originally posted by Metal Man88 Generally, you want to run MemTest86 overnight, as some errors only appear after a certain number of passes (usually after the hardware's been stressed enough). If there are no errors the next morning, it's safe to assume the problem lies elsewhere. |
|||
|
Metal Man88 Gold axe It appears we have been transported to a time in which everything is on fire! Since: 11-17-05 Last post: 6298 days Last view: 6298 days |
| ||
| I know Windows 98 is less sensitive about memory, but I plugged in an old drive with it already installed and it boots up just fine. Unfortunately, it doesn't seem to be able to see the CD-rom drive... if I could get it to see that, I'd be set. At least, until I could get the SATA drive to install or something. Thusly, Windows XP must be complaining about a compatibility error unique to their own 'improved' installation system. |
| Add to favorites | Next newer thread | Next older thread |
| Acmlm's Board - I3 Archive - Hardware / Software - Forbidden |
| |
