windows stops working and reboots

[san]

Two days ago i did a clean install. Several times now the computer stops working and reboots. I expected the clean install would fix this issue. This usually happens after I ve played games, strangely enough not during playing. Although when alt-tabbing out of games I get the message that the computer is running slow.

I attached the win7 diagnostic file, cpu-z screenshots and the Rammon file.

 

[YoYo155]

Hi san .

The bugchecks uploaded are all 0x109 and a single 0x7F (8).

One might be caused by the Realtek driver being old I want to take a different approach
in this case. Please follow the detailed quote in order to help us uncover the culprit.

Your crash dumps are not showing any finite probable cause.

Test your RAM modules for possible errors.
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 passes, preferably overnight.

First run it with all the existing/installed RAM modules. If it comes with no error, all is good.

But if it starts showing errors, Stop testing. Errors/red lines means one or more RAM is faulty. But the fault may occur due to a faulty DIMM slot, too, which is a motherboard component. Using memtest86+, you can discriminate between a faulty RAM and a faulty motherboard.

How? Say you have two RAM sticks and two DIMM slots. You obtained errors at the test with all RAM sticks installed. Now, remove all the sticks but one. Test it in all the available slots, one by one. Continue the same procedure for all the available sticks.
How to make the inference that is it a RAM issue or it is a motherboard issue? Suppose you have got the result like that:

test|Slot1|Slot2
RAM1| Error | Error
RAM2|Good|Good

It is a RAM, a bad RAM.

But if you have got a result like that:

test|Slot1|Slot2
RAM1| Error |Good
RAM2| Error |Good

It is a motherboard issue. The particular slot is bad.

If memtest comes free from errors, enable Driver Verifier to monitor the drivers.
Driver Verifier - Enable and Disable
Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

   Information

Why Driver Verifier:
It puts a stress on the drivers, ans so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.

How Can we know that DV is enabled:
It will make the system bit of slow, laggy.

   Warning

Before enabling DV, make it sure that you have earlier System restore points made in your computer. You can check it easily by using CCleaner looking at Tools > System Restore.

If there is no points, make a System Restore Point manually before enabling DV.

   Tip

• If you fail to get on the Desktop because of DV, Boot into Advanced Boot Options > Safe mode. Disable DV there. Now boot normally again, and try following the instruction of enabling DV again.
• If you cannot boot in Safe mode too, do a System Restore to a point you made earlier.

Let us know the results, with the subsequent crash dumps, if any.

 

[san]

thanks for response gonna let memtest run overnight let you know outcome.

Also I took a screenschot when windows said the system is running slow with a taskmanager open.

Its in Dutch. see in attach

 

[san]

Update: I ran memtest 8 passes 0 errors. I am going to run driver verifier now

 

[san]

When I was typing my reply Windows gave me a BSOD. I have added the W7F diagnostic report

 

[YoYo155]

Thanks for the update .
I don't know Dutchm but if I am not mistaking it's asking to switch to the Basic Theme, this is normal
when running certain programs / games and I do see WOW running in the background.

It's the same 0x109 bugcheck :\ ..
Does it happen under certain circumstances and while running / performing certain tasks?

:ar: Please try and leave Driver Verifier on for another day so we will maybe get
a more informative bugcheck.

Before running the scans Disable Driver Verifier.

:ar: Please scan for possible infection and file corruption:

• Download TDSS-Killer and scan for rootkits.
• Download Kaspersky Rescue CD and scan for other types of infections. (a how-to tutorial)
• Download Malwarebytes and DON'T activate the trail (uncheck the box at the end of the installation)
• Follow this tutorial on how to use the SFC/ SCANNOW tool in Windows.

(*Kaspersky Rescue CD from a USB thumbdrive)

 

[san]

Update:

I did all the above reply suggested. Nothing wrong came up.

I also:
- updated my realtek drivers
- disabled the jmicron controller in bios because I read on the internet it was no good.
- disabled the firewire controller in bios because I don't use it
- updated my Intel chipset drivers
- monitored temperatures of cpu and gpu all of which were normal
- haven't changed any hardware

For about 10 days my computer worked without BSOD until today. When I was out of the room and my computer was idling I got a BSOD.

I did restart my computer again and a few windows 7 updates started to install. The installation process managed to get to 32 % when I received a second BSOD.

Can someone please take a look? Thank you very much.

 

[YoYo155]

Hello again .

The bugchecks are due to code corruption those are more often than not an indication
of RAM failing. Please systematically remove on of the RAM modules until the system is completely
stable.


Also to minimize the possible culprits please roll back to a known stable release of your GPU driver.

Install the 314.22 WHQL only.

• Uninstall All nvidia items in Control Panel > Programs and features
  • 3D Vision Control Driver
  • 3D Vision Driver
  • Graphics Driver
  • HD Audio Driver
  • PhysX
  • nvidia Update
  (Are you using nvidia chipset drivers? If so, dont uninstall anything other than those are listed).
• Now follow Drivers - Clean Left over Files after Uninstalling
• Boot normally now. Download 314.22 WHQL. While installing, Select Custom (Advanced) install. In the next page, follow this settings:
  
  

Let us know the results.