SrtTrail, Bugcheck and error codes

Hello @ MajorGeeks...

I hope I am posting in the right place and hope someone can explain.

I am having trouble with a friends desktop and following hardware: 2.2Ghz Athlon 64 bit x2, 4GB 800Mhz RAM, Gigabyte M68M-S2P motherboard, 200GB Seagate HDD and the OS is Windows 7 Home Premium 64 bit.
Having rebuilt it I (the MB is new) installed said OS and all was functioning perfectly, I set it up for him at home and thought that it was a job well done but that was only the beginning. Every few weeks he rings and tells me it's happened again - it boots as far as the round windows logo on the black screen and goes no further, startup repair does not work. I get it running, check event viewer etc but find nothing of relevance.
I have checked the HDD with Seatools - nothing, Memtest results are also good and the PSU is good too. I can not for the life of me figure out what is causing the issue!
The only lead I have is the following...

Every category of the Startup Repair diagnosis and repair log completeted successfully but at the end of the report the following was found:

Root cause found:
---------------------------
Unknown Bugcheck: Bugcheck 7e. Parameters = 0xffffffffc0000005, 0xfffff80002ad2b65, 0xfffff88003f950b8, 0xfffff88003f94910.

Repair action: System files integrity check and repair
Result: Failed. Error code = 0x45d

I would be very grateful if some kind person would shed some light on this as I can't seem to find anything on the web which comes close to helping me find a solution and sadly my friend is not too good with computers so I only have limited information regarding what he did just before the pc died each time.
Thanks a million in advance...

MrOrange

 

Greetings, MrOrange, and welcome to MajorGeeks...

The fact that this happens only sporadically makes troubleshooting (especially remotely) very difficult.

What steps do you have to perform to get the machine running again? Do you know if the same symptoms occur when the machine is booted into Safe Mode?

You might try uploading the most recent crash dumps and someone may be able to spot something - navigate to the C: > Windows > Minidumps folder, copy those files to the Desktop, zip and upload them as an attachment.

Also, please download and run Speccy, a free system information tool. When the scan completes click 'File', 'Save as Text file', name the report, and save to an easily found location. Be advised: the report will display your IP Address and Windows Product Key. You may delete this information if you so wish. Then attach that file to your next post.

 

Thanks Caliban,

the pc has been collected again so I'll have to wait till it gives trouble again :-(

I was rather hoping somebody could explain what the meaning of the errors as listed are?

Root cause found:
---------------------------
Unknown Bugcheck: Bugcheck 7e. Parameters = 0xffffffffc0000005, 0xfffff80002ad2b65, 0xfffff88003f950b8, 0xfffff88003f94910.

Repair action: System files integrity check and repair
Result: Failed. Error code = 0x45d

However, as said, thank you for your quick reply and should I receive the machine again I will follow your instructions

MrOrange

 

Good morning...

The Unknown Bugcheck: Bugcheck 7e portion of the error message covers a wide range, but I'd be willing to bet this is a driver-related problem. If you do get the machine back, make sure your first troubleshooting steps include booting into Safe Mode and/or a clean boot to help isolate any 3rd-party software culprits.

Keep us informed, and good luck!

 

Caliban's close to the mark when he suggests that it's likely to be a 3rd party driver at the root of this, I'd normally suspect a bad or old driver when seeing the first parameter of C0000005 with a 0x7E.

Motherboard utilities can cause BSOD's; check for Gigabyte's Easy Tune 6 or similar, if it's installed, uninstall it. The same goes for virtual CD/DVD programs like Daemon Tools, uninstall them during the testing period.

Having said the above, the timing of the BSOD (at boot) doesn't feel 'right', a selection of minidumps is needed (also suggested by Caliban) to enable a better feel for what's happening here. (Perhaps you could access the computer remotely using TeamViewer to retrieve the dump files?).