ok so not entirely sure what all you wizards are going to need from a humble dabbler such as I in the way of info, just tell me what you need and were to get it and ill post it.

heres what i do know, i have a Hp envy H8-1559 desk top computer, my motherboard is a M3970am-HP (angelica2)

• Manufacturer: Gigabyte

• Chipset: AMD 970

• Processor socket: AM3-b

• Amd fx 8350 eight core 4 GHz processor

• 8 gigs of ram

• nividia geforce gtx 760

I also replaced the power supply recently to accommodate the increased draw of the video card.

So heres whats happening, the computer crashes, and the worst part is it seem to be entirely random, but since this issue has been going on for well over a year now i have noticed a few patterns. crash pattern 1 is i will be watching a video or playing a video game and the sound will go, this can mean completely silent or weird robotic Megatron voices. at the same time one of ether my mouse or keyboard but never both at the same time will die, this happens exactly the same time the sound messes up. i have recently tried moving the effected device to a different usb port and have had power and usability restored by doing so, this shows that its likely not a driver related conflict as i had been thinking up until now. the computer will then continue to run as normal for no longer then 20 min before going to bsod, it will then tell me that it is collecting data with 0% collected and a kernel error. the computer will then ether freeze here and never move past the 0% or will just turn its self off with out collecting any info.

pattern 2 if you can call it that is a sudden and abrupt shut down, there is no warnings and the bsod is only visible for a fraction of a second.

the craziest part of all this is that the issue just seem to flair up from time to time, i have gone months with out a crash only to have 3 or 4 in the same day. i have already tried a reformat/clean install with out results. i have also used memtest86 and passed with flying colors though the test did take almost 4 strait days. I would also post a dump or minidump for you guys but i have no idea where there hiding that stuff now a days.

Help me tech wizards you'er my only hope.

Hi TailV.

Minidump files should be in c:\windows\minidump.

(The following "procedure" has been done on windows 8.1, but it is very similar to other windows versions)

They should be enabled in (translating from italian, sorry) Control panel\system and security\system, advanced system properties, click the settings... button (on your screen) under the start-up and recovery frame and check if under write debugging information it is selected small memory dump (256kb).
If not, select it and click always ok.

The pagefile.sys MUST be present on the system partition (that is usually C:\).
Always in advanced system properties, click the settings... button (on your screen) under the performance frame, select the advanced tab, click the Change... button and set the values of your virtual memory = pagefile.sys. They could be equal. The minimum size is 16MB.

Hope this helps (to create and send a minidump here). :)

  We do need the actual log files (called a DMP files) as they contain the only record of the sequence of events leading up to the crash, what drivers were loaded, and what was responsible.  

Please follow our instructions for finding and uploading the files we need to help you fix your computer. They can be found here If you have any questions about the procedure please ask

Thank you Xilolee. I have done as requested and will wait for the next crash so as to have a fresh and new minidump file. I will post again when the info is available.

Hi TailV,

How about the issue ,is there anything to update ?

If the issue persists ,please upload the dmp files here and we will try our best to help you to resolve the issue .

Best regards

Without the dump files, there is no way for us to identify the cause of your system crashes. Most system crashes are caused by malfunctioning drivers or software that interferes with the basic operation of the operating system. You can start by updating any drivers that have more up-to-date versions available from the device or system manufacturer.