Solved Random resets Windows 7

[Oowead]

Greetings and congratulations for the good job in the Forums.
My PC is having random resets for quite a while now. No specific trigger, no pattern, except that it mostly happens when systems is on light load or even idle. Sometimes it happened once in a week and sometimes 3-4 times in a day. I tested CPU, RAM and video card with various stress testing programs (Load Tester, Orthos Prime, Furmark, VGA Memory Stress Test, Goldmemory, Memtest86+, Memtest, Windows Memory Diagnostic) without problems. Tested HDD with HDD Regenerator and it was ok. Recently, I tried a Windows reinstallation. After booting from the Windows DVD and loading the initial files, the PC had a reset when it was idling for a couple of minutes at the first screen of Windows Setup! I re-tried and installed Windows successfully. With the new installation, with no drivers or updates installed, the random resets kept happening. After doing a second Windows reinstallation the situation is the same. I have gradually replaced all replaceable hardware components with known-to-work ones, except for the CPU and motherboard. I replaced PSU, RAM and HDD (and its SATA cable) and added a dedicated ATI HD 4350 Video card. Updated to latest BIOS. Disabled integrated components from BIOS (LAN, Onboard VGA and Sound, USB controllers). My latest actions were to detach the motherboard from the case to rule out any short circuits and to remove all unnecessary devices. At this moment the system is out of the case and consists of the essentials (PSU,motherboard,CPU,RAM,dedicated VGA,HDD). The resets keep happening and almost all of them are described as follows in the Windows Event Viewer:

"BugcheckCode">0
"BugcheckParameter1">0x0
"BugcheckParameter2">0x0
"BugcheckParameter3">0x0
"BugcheckParameter4">0x0
"SleepInProgress">false
"PowerButtonTimestamp">0

Any help would be appreciated. Thanks in advance.

N.B.: I am attaching the logs from SF Diagnostic Tool after the second Windows reinstallation. I could attach the logs from the previous installations if needed.

 

[VistaKing]

Hi Oowead welcome to SevenForums

Which DIMM slot is your memory installed ? Try installing it on the second slot ( furthest away from the CPU )

 

[cipley]

STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!MiAgeWorkingSet+180
828cdb8e 8b0f            mov     ecx,dword ptr [edi]

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!MiAgeWorkingSet+180

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  5147d331

IMAGE_NAME:  [COLOR="Red"]memory_corruption[/COLOR]

FAILURE_BUCKET_ID:  0xA_nt!MiAgeWorkingSet+180

BUCKET_ID:  0xA_nt!MiAgeWorkingSet+180

Chances are your RAM chip(s) are bad...
Check this out: Diagnose RAM using memtest86+
run for at least 7 passes, preferably overnight

 

[Dsprague]

This windows install is counterfeit:

# Copyright (c) 1993-2009 Microsoft Corp.
#
# This is a sample HOSTS file used by Microsoft TCP/IP for Windows.
#
# This file contains the mappings of IP addresses to host names. Each
# entry should be kept on an individual line. The IP address should
# be placed in the first column followed by the corresponding host name.
# The IP address and the host name should be separated by at least one
# space.
#
# Additionally, comments (such as these) may be inserted on individual
# lines or following the machine name denoted by a '#' symbol.
#
# For example:
#
#      102.54.94.97     rhino.acme.com          # source server
#       38.25.63.10     x.acme.com              # x client host

# localhost name resolution is handled within DNS itself.
#	127.0.0.1       localhost
#	::1             localhost
[COLOR="Red"]127.0.0.1 validation.sls.microsoft.com[/COLOR]

Please purchase a legal copy of windows format your drive and install it.

 

[Oowead]

Thank you all for replying.

Hi Oowead welcome to SevenForums

Which DIMM slot is your memory installed ? Try installing it on the second slot ( furthest away from the CPU )

Chances are your RAM chip(s) are bad...
Check this out: Diagnose RAM using memtest86+
run for at least 7 passes, preferably overnight

Prolonged re-testing with Memtest86+ according to your advice revealed errors in both slots after testing both the original RAM module and the known-to-work RAM module (which had been operating in a PC with no BSOD's ever). I also noticed that although both modules are DDR1333 they are both described as DDR1067 in slot2 and as DDR400 in slot1. The default RAM clocking in BIOS is at 1067 MHz. The conclusion from reading the Memtest86+ documentation is that the failure of either the RAM or the CPU or the motherboard could produce errors. Since the known-to-work RAM module is reliable would you agree that this might suggest a faulty motherboard or CPU? I am also attaching pictures of BSOD's and logs from previous testing installations on this PC.

Please purchase a legal copy of windows format your drive and install it.

I have already installed my "real" and "operational" copy of Windows in a machine an older backup PC that replaces the problematic PC temporarily.
This is purely a diagnostic installation on Windows 7 being used in a "decommissioned" PC which is inoperative. I can't afford to buy a licence solely for troubleshooting a machine which is taken apart an its only use is running diagnostics all the time. One option was a 30-day-grace-period "trial" version of Windows or an "emulation" of my legal copy of Windows which is already being used. I have used both options so far according to the frequency of reformatting and the period of time needed for each diagnostic installation. If this violates the ethics of this forum it has not been intentional and I will take it into consideration from now on. I am open to any suggestions concerning this matter.

 

[cipley]

that's it. Any "red lines" of the memtest indicates bad chip RAM, or bad RAM slot on the motherboard.
depends on your memtest result, do the necessary actions (either replace your RAM or Motherboard)