PC issues from hell... help :[

[glenjj]

I have a few issues that have recently been very frequent and now I cannot solve.

My PC gets a BSOD almost everytime I either play a game/watch a video or render a video. occasionally with other, and they mainly tend to be things like normal web browsing but the main pattern of crashes are definitely related to the gaming/video use.

I have also recently started getting black boxes/rectangles etc on webpages browsing, and other parts of pages get jumbled ect, just at random, refreshing gets rid of it, but it never used to happen until recently :/

I would post crash dumps to help solve it but for some reason my pc will not create dumps after BSOD.. so I guess I need to fix that first before I can even begin to identify the problem :/
Though the last few have been 7e, 1e, 0a, 0a, 50 (I took photos with my phone lol)

My PC specs are:

Win 7 Home premium. 64bit.
CPU: Intel i7-3770 3.40ghz (I don't overclock and never have)
RAM: 16gb RAM (apacer)
MB: ASrock H77 Pro4-m
GPU: Nvidia geforce GTX 660 2047mb
PSU: Cooler power gx750 Something like this: Cooler Power GX750W Extreme 750Watt ATX VER2 2 80PLUS 4 4pin CPU 6pin VGA X2 | eBay (The seller put this in and insists its a good brand)

Any help is really appreciated, I've tried to sort this issue in the past but people get stumped pretty quick and stop replying to help me out :/

Just to clarify, what do you mean with BSOD?
Some state it as a Blackscreen, others as a Bluescreen.

It's always a blue screen, shows error code then restarts, on other rarer occasions (like say 10%) my pc just freezes up completely and I have to turn it off to restart it

 

[axe0]

A reason why no dump is saved is hardware damage.
If the hardware is damaged too bad, no dump CAN be saved.
If hardware is damaged, but not that bad, then it shouldn't be a problem to save a dump.

Diagnostics Test

 HDD TEST

Run SeaTools to check the integrity of your HDD. http://www.sevenforums.com/tutorials/313457-seatools-dos-windows-how-use.html

   Note

Do not run SeaTools on an SSD as the results will be invalid.

Run chkdsk http://www.sevenforums.com/tutorials/433-disk-check.html

Run HDTune to scan for errors, health and benchmark.
Let me know what the results are, prefered screenshots.

Diagnostic Test

 RAM TEST

Run MemTest86+ to analyse your RAM. MemTest86+ - Test RAM - Windows 7 Forums

   Note

MemTest86+ needs to be run for at least 8 passes for conclusive results. Set it running before you go to bed and leave it overnight. We're looking for zero errors here. Even a single error will indicate RAM failure.

Diagnostic Test

 CPU TEST

Run Prime95 to stress test your CPU. Prime95 - Stress Test Your CPU - Windows 7 Forums

   Warning

Your CPU temperatures will rise quickly while under this stress test. Keep a keen eye on them and abort the test if overheating occurs.

 

[glenjj]

A reason why no dump is saved is hardware damage.
If the hardware is damaged too bad, no dump CAN be saved.
If hardware is damaged, but not that bad, then it shouldn't be a problem to save a dump.

Diagnostics Test

 HDD TEST

Run SeaTools to check the integrity of your HDD. http://www.sevenforums.com/tutorials/313457-seatools-dos-windows-how-use.html

   Note

Do not run SeaTools on an SSD as the results will be invalid.

Run chkdsk http://www.sevenforums.com/tutorials/433-disk-check.html

Run HDTune to scan for errors, health and benchmark.
Let me know what the results are, prefered screenshots.

Diagnostic Test

 RAM TEST

Run MemTest86+ to analyse your RAM. MemTest86+ - Test RAM - Windows 7 Forums

   Note

MemTest86+ needs to be run for at least 8 passes for conclusive results. Set it running before you go to bed and leave it overnight. We're looking for zero errors here. Even a single error will indicate RAM failure.

Diagnostic Test

 CPU TEST

Run Prime95 to stress test your CPU. Prime95 - Stress Test Your CPU - Windows 7 Forums

   Warning

Your CPU temperatures will rise quickly while under this stress test. Keep a keen eye on them and abort the test if overheating occurs.

Ah ok then, well I will run these tests and get back with the results asap, may take a day or two
cheers

 

[glenjj]

Haven't had free time to do the tests just yet, I only have one pc and I have to use it for work almost daily, plus the bsod crashes haven't been as frequent lately.

But anyway the point of this post is I finally got a minidump after my latest crash finally, so I thought it may help to identify the issues I'm still having.

 

[axe0]

Recommended to run the dm log collector when another crash has occured, for next time.

A driver tried to write data to an invalid memory address, this usually is caused by the driver.
Run driver verifier for an attempt to find the driver(s) causing this.
Note that driver verifier may cause crashes, but doesn't always reveal the driver in the dumps. This is why driver verifier may need to be enabled a few times. Read the instructions below carefully.

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced.  This cannot be protected by try-except,
it must be protected by a Probe.  Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: [COLOR="red"]fffff7fffb62f050[/COLOR], [COLOR="red"]memory referenced[/COLOR].
Arg2: [COLOR="Red"]0000000000000001[/COLOR], value 0 = read operation, [COLOR="red"]1 = write operation[/COLOR].
Arg3: fffff800037644e4, If non-zero, the instruction address which referenced the bad memory
	address.
Arg4: 0000000000000002, (reserved)

Diagnostic Test

 DRIVER VERIFIER

   Warning

Please make a backup of your important files and get your rescue media or create one.
Please create a restore point.

Please follow this tutorial to run driver verifier.

Driver verifier stresses your drivers and will crash your pc if any driver fails due to a violation.

Driver verifier should be performed for a max of 48 hours, or when you have a bluescreen, whatever comes first.

If driver verifier has found a violation and you can't get back into windows normally, try to boot into safe mode and reset in safe mode driver verifier, or in the troubleshooting options open command prompt and type verifier /reset.

   Note

Your system will act very sluggishly while driver verifier is enabled, this is normal as your drivers will be being subjected to heavy testing in order to make them crash.

 

[glenjj]

Recommended to run the dm log collector when another crash has occured, for next time.

A driver tried to write data to an invalid memory address, this usually is caused by the driver.
Run driver verifier for an attempt to find the driver(s) causing this.
Note that driver verifier may cause crashes, but doesn't always reveal the driver in the dumps. This is why driver verifier may need to be enabled a few times. Read the instructions below carefully.

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced.  This cannot be protected by try-except,
it must be protected by a Probe.  Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: [COLOR="red"]fffff7fffb62f050[/COLOR], [COLOR="red"]memory referenced[/COLOR].
Arg2: [COLOR="Red"]0000000000000001[/COLOR], value 0 = read operation, [COLOR="red"]1 = write operation[/COLOR].
Arg3: fffff800037644e4, If non-zero, the instruction address which referenced the bad memory
	address.
Arg4: 0000000000000002, (reserved)

Diagnostic Test

 DRIVER VERIFIER

   Warning

Please make a backup of your important files and get your rescue media or create one.
Please create a restore point.

Please follow this tutorial to run driver verifier.

Driver verifier stresses your drivers and will crash your pc if any driver fails due to a violation.

Driver verifier should be performed for a max of 48 hours, or when you have a bluescreen, whatever comes first.

If driver verifier has found a violation and you can't get back into windows normally, try to boot into safe mode and reset in safe mode driver verifier, or in the troubleshooting options open command prompt and type verifier /reset.

   Note

Your system will act very sluggishly while driver verifier is enabled, this is normal as your drivers will be being subjected to heavy testing in order to make them crash.

Okay I will try that too
though yesterday I had another bsod (D1) yet no new minidump appeared :/