New installation of windows 7 keeps crashing, different types of BSOD

Hello,

My fairly old computer has been unfunctional for a while and I decided to reinstall windows 7 pro x64. I am having so many troubles I probably wont remember all of them.

What I do (multiple times with variations):

• Boot installer from USB, delete all partitions
• Install win7 on my 1 TB drive, leave other drive unallocated.
• Insert new USB with software: Avast Free Antivirus, Network Adapter Driver (Atheros-FORCED-7x64-AR8171-drp), manual windows update file (Windows6.1-KB3138612-x64) because automatic windows update gets stuck, All-in-1 MOBO drivers&utilities (I suspected these, but am now crashing without them installed)
• During setup, use verifier.exe to see if things work so far
• Try, sometimes with crash, to install GFX card driver
• When things seem to go "well" I install a game (Pillars of Eternity). This frequently causes crashes after a short while.
• I have run memtest86+-5.01.usb.installer and removed a single block of RAM which is different from the others. I now have 3x 4 GB RAM which all pass memtest in all sockets, and also pass when tested together.

I am running out of ideas here, and I cannot interpret dmp files, like the experts. My last idea is to install win7 on my other HDD, and remove my 1 TB drive. But I have a bad feeling that an important component is defective, or even multiple components being defective.

Any assistance or ideas would be greatly appreciated!

PS. I recently cleaned up my office and I think I lost some install CDs that may be important - specifically the MOBO driver CD. I hoped to just get these drivers online.

I have added some items to the system specs in my profile (using the tool). Is that what you needed? I hope the manual fill-outs are understandable.

There is a BIOS update from ASRock, I will try to install that.

Hi Morten,
you also appear to be having troubles with windows Updates.
Please TURN OFF driver updates within it, see screenshot.

Roy

torchwood said:

Hi Morten,
you also appear to be having troubles with windows Updates.
Please TURN OFF driver updates within it, see screenshot.

Roy

What makes you say that? Windows Update has installed useful drivers for me such as a driver for GTX 460 SE. Not the latest, but enough to get full HD enabled.

EDIT: I have now updated my BIOS.

Hi Morten,
from the WU log,
Matched driver to device PCI\VEN_10DE&DEV_0E23&SUBSYS_089E10DE&REV_A1
2016-10-02 12:03:37:338 408 180 Driver Status: 0x180200a, ProblemNumber: 00000000
2016-10-02 12:03:37:338 408 180 Driver Matched driver to device MONITOR\BNQ78CD
2016-10-02 12:03:37:338 408 180 Driver Status: 0x180600a, ProblemNumber: 00000000
2016-10-02 12:03:51:729 408 1378 AU Launched new AU client for directive 'Download Approval', session id = 0x1


note that log is extremely large for 1 day.

Roy

2nd note.

As you have a custom install, its best to install drivers direct from the manufacturer.

Roy

torchwood said:

Hi Morten,
from the WU log,
Matched driver to device PCI\VEN_10DE&DEV_0E23&SUBSYS_089E10DE&REV_A1
2016-10-02 12:03:37:338 408 180 Driver Status: 0x180200a, ProblemNumber: 00000000
2016-10-02 12:03:37:338 408 180 Driver Matched driver to device MONITOR\BNQ78CD
2016-10-02 12:03:37:338 408 180 Driver Status: 0x180600a, ProblemNumber: 00000000
2016-10-02 12:03:51:729 408 1378 AU Launched new AU client for directive 'Download Approval', session id = 0x1


note that log is extremely large for 1 day.

Roy

I don't understand what that means. What log is large? Where is the size indicated?
So my monitor is mentioned in the log, but BenQ say on their website that it should be plug and play.

torchwood said:

2nd note.

As you have a custom install, its best to install drivers direct from the manufacturer.

Roy

If you are referring to the CDs that might have come with the MOBO and/or CPU and GFX, I don't think I have those. I have however, been looking for those on the manufacturers' websites. On the current attempt to get the install to work, I have not run the mobo driver setup, because previously, they caused crashes with verifier.exe.