I tried posting this in BSODs and crash debugging, but I just got ignored. I became annoyed, since this is a SERIOUS problem that's been persisting for more than a month. I've provided as many possible details about the machine as I can, and I've listed all of my tests and diagnostics. Please read the whole post. Specs: Mobo: Asus M4A89TD Pro USB3
RAM: G. Skill Ripjaws x2 2GB
CPU: AMD Phenom II Black x4
PSU: Corsair HX 650W
HDD: Western Digital Caviar Blue 500gb SATA 6.0 x2
GPU: Sapphire Radeon ATI HD 5770 PCIe
Case: Cooler Master CM690II Advanced
I've built two computers in the recent past, one for myself and one for my boyfriend. I've noticed that when shutting down my boyfriend's machine, and powering it back on, Windows will crash to a BSOD or get stuck on a black screen. The suspicious thing is, this will ONLY
happen when shutting down and powering back on. If the system is simply restarted, Windows will start up every single time without a crash. Restarts don't cause problems, only powering on.
Strangely, his computer will not record the BSODs that occur when they happen at the startup logo. This means that I cannot post the analyzed BSODs here with BlueScreenView or any other program, so PLEASE DON'T ASK ME TO. They do not show up on any BSOD reader. The crashes DO NOT appear in the minidump folder. Please DO NOT ask me to supply the minidump folder.
I have run a Memtest on each individual stick, each with 6 passes with zero errors.
I wrote down the most recent errors that popped up when his computer crashed on starting up, since I can't look at his blue screens otherwise. The first said SYSTEM_SERVICE_EXCEPTION, BCC was 3B.
The second crash didn't give an error name/message, it just gave a STOP error ending in 7F and the related file was ahcix64.sys, which I have seen multiple times on various BSODs on his system, as well as my own.
Another recent one was DRIVER_IRQL_NOT_LESS_OR_EQUAL with Stop error D1.
ntoskrnl is also a file I see frequently during BSODs.
Each time the system is reset after powering it on, it gets farther and farther in the startup process until eventually it will give in and start up without a crash. Once Windows is up, it is, strangely, stable. Games will run perfectly without errors. Programs will function normally. Performance is exceptional, and the computer is very fast. It will run perfectly for weeks without a single crash, hangup, or problem.
I have not done a startup repair yet. The main reason for that is, his hard drives are set up in RAID 0. I'm afraid that it may damage the array somehow. If I get reassurance that it won't, I might try to fix it.
All of his drivers
are up to date. All of his programs are up to date. His Directx is fully functioning with no errors. His Windows 7 is fully updated. Everything else seems to be A-Okay, except for the startup problem.
I also scanned his PC for viruses and he doesn't have a single one.
This problem was happening long before I had installed anti-virus software on his machine. Anti-virus software is not the culprit.
I've also cleared his CMOS.
I've already done a SFC Scan and no corrupt files were found. I can't run a chkdsk because he has RAID 0.
I have cleared all of his temporary files.
I have defragmented his disks.
Knowing I've taken all of these measures... please don't ask me to repeat them. I've done everything I can. I've downloaded every tool I could to help. I have no answers.
A most recent development has me thinking it could be a hardware problem. When touching the front/top USB ports on the case, the display crashes to a black screen. The rear USB ports don't cause this to happen, only the top/front ones. The USB ports are directly next to the power and reset switches. I can provide System Info and Event Logs as needed, if some of you want to actually help, or even can help if your knowledge is applicable. I know this is a lot of information, but people on forums like these tend to get annoyed when not enough information is given. Ironically, when posting long messages like these, I rarely get a response despite how detailed and informative they are. I realize not being able to use BlueScreenView or WhoCrashed to solve a problem makes it harder to troubleshoot, but I know it's not impossible. If you CAN help, I beseech your guidance.