| Forum Home | ||||
| Press F1 | ||||
| Thread ID: 119392 | 2011-07-21 04:45:00 | upgrading to Win 7 | Driftwood (5551) | Press F1 |
| Post ID | Timestamp | Content | User | ||
| 1218066 | 2011-08-16 08:17:00 | If the mobo is still under warranty, I would take it back. And get something else | Speedy Gonzales (78) | ||
| 1218067 | 2011-08-16 09:26:00 | It's out of warrenty but I may still replace it. The hardest part is deciding which one to get. Also weather to stick with the current CPU or not. At this stage I still don't know what is causing the problem. I'm going to start with a new HD anyway, seeing one of those hase died. They were around 5 yrs old. |
Driftwood (5551) | ||
| 1218068 | 2011-08-16 19:19:00 | Did you ever run memtest ? faulty ram can cause all the symptoms you describe including making a drive appear faulty. may not be it but worth checking. :pf1mobmini: |
dugimodo (138) | ||
| 1218069 | 2011-08-16 20:38:00 | Havent run memtest, is it likely to be better than the burnin test? The faulty drive is quite uneccessable, have tried it on another system as well. |
Driftwood (5551) | ||
| 1218070 | 2011-08-16 21:49:00 | The Burnin test I suggested does the following: BurnInTest tests the CPU, hard drives, RAM, CD-ROMs, CD burners, DVDs, sound cards, 2D graphics, 3D graphic, network connection, printers, video playback. What BurnInTest does is thoroughly exercise the hardware in a PC in a short period of time, in the same way as normal applications use a PC over a long period of time. This takes advantage of the fact that computer hardware tends to fail either very early in its life or after many thousands of hours of use. It does have a Memory tester in it, but it wouldn't hurt to run memtest on its own. |
wainuitech (129) | ||
| 1218071 | 2011-08-16 23:29:00 | Currently running memtest now. Up to 75% no errors |
Driftwood (5551) | ||
| 1218072 | 2011-08-17 04:11:00 | No errors on memtest. System went good for about 4 hrs & then bluescreened when I left it for 15 min. Nothing came up on the bluescreen viewer. Stop: 0x0000007A (0xFFFFF6FB800083F8, 0xFFFFFFFFC000000E, 0x0000000078295880, 0xFFFFF7000107FFF8) |
Driftwood (5551) | ||
| 1218073 | 2011-08-17 04:15:00 | Looks like that stop error means something is wrong with the hdd (answers.microsoft.com) How big is the hdd?? This may apply if Win7 is 64 bit (support.microsoft.com) |
Speedy Gonzales (78) | ||
| 1218074 | 2011-08-17 04:58:00 | Thats why I've ordered a new one. Current one is only 160GB & win7 is 64bit. I should have stayed on Vista 32 & I wouldn't be having all these problems. |
Driftwood (5551) | ||
| 1218075 | 2011-08-17 21:24:00 | Murphy is alive and kicking, it was just a matter of time! Let's hope it is the HDD at fault. Strange tiugh that it happens only when you leave the screen. You'll love Win7 over Vista once you have it up and running. |
Bryan (147) | ||
| 1 2 3 4 5 6 7 8 9 10 | |||||