Posted 13 September 2012 - 07:22 AM
Posted 13 September 2012 - 07:59 AM
This sounds more like an issue with the OS (actually with the hard disk or the filesystem on it) than anything else.
This woud explain nicely why no errors are found through memtest86+ testing.
The POST is however BEFORE NTLDR (or anything OS related) comes into play.
You may want to use a Live CD (*any* Linux distro or Windows based PE would do) and test the PC "diskless" (yes, physically detaching the hard disk cable).
Also, you can use a grub4dos bootdisk so that you can easily "separate" the POST phase from the actual OS loading one.
This post has been edited by jaclaz: 13 September 2012 - 07:59 AM
Posted 13 September 2012 - 08:46 AM
Posted 13 September 2012 - 08:58 AM
And again you have three possibilities:
- "main" Hardware (motherboard CPU, etc.) that however tests OK with memtest+
- "specific" Hardware (hard disk controller, hard disk drive, hard disk cables)
- Software (filesystem, actual files corrupted, botched install)
The suggested troubleshooting way (that you partially already took using memtest+) is to test the motherboard with ANOTHER OS loaded form ANOTHER MEDIA (CD/DVD or USB).
If you insist on keeping the three listed items "together" you will never be able to find out which is which is not by sheer luck .
- ← measurement on a 200mm fan with a circular frame
- Hardware Hangout
- Biostar TA790GXBE board has stopped powering up →