Every Other Day Startup Issues Win 7 Pro x64

I have a brand new rig that I just built consisting of the following specs:
CPU: Intel Core i7-920 2.66 Quad Core
Mobo: MSI x58 Pro E LGA 1366 Intel X58
RAM: 4gb of Patriot 2GB 240 Pin DDR3 SDRAM 1333
HD: 500 Gigabyte Seagate (second drive used, see below)
OS: Windows 7 Professional 64

My current problem is it seems every other day when I start my computer up in the morning, there is some issue of one sort or another on the computer. Last week it was a corrupt file in the windows directory (an ntsomething.dll, don't recall the full name). This morning it was a corrupt system volume.

I did have a number of corrupt system volume issues when I first put the computer together, but I diagnosed that as a bad hard drive (SeaTools tests detected that pretty quick). After having run Seatools on the brand new hard drive (it came up clean), I reinstalled Windows 7 from a system image. Bad idea, as apparently it copied over the corrupt system volume. I reformatted the hard drive, started from scratch, and got myself back up and running.

This morning I had another corrupt system volume. On bootup, I discovered that it was reading only 2 gb of ram, so I reseated the RAM and ran a Memtest on it. It came out fine with no errors.

I out the SATA cable for the hard drive, and moved it to another connection, just in case I had a bad cable/connection.

Restarted my computer, windows decided to run a system repair (corrupt system volume again), rebooted, and it started up just fine (once it comes up, btw, it works just fine. No problems at all).

I ran sfc /scannow in the past and had no problems, but when I ran it just a few minutes ago it stated "Windows Resource Protection found corrupt files and succesfully repaired them. I do have a log file for it, but it's 5MB in size (I can upload a copy of the entries from just today if that would assist anyone).

The only dump file that I have is from 2 days ago (it didn't create one this morning, I'm unsure of why), but I've included that n case there might be something useful.

Any suggestions as to why I'm constantly getting this problem would be much appreciated. If you need more information, please let me know. I hope I got everything people would need, but there's so much, it's easy to overlook something:)

Thank you.

Jon

PS I'm running burn in tests as we speak, just to verify on more time.

MrH said:

I have a brand new rig that I just built consisting of the following specs:
CPU: Intel Core i7-920 2.66 Quad Core
Mobo: MSI x58 Pro E LGA 1366 Intel X58
RAM: 4gb of Patriot 2GB 240 Pin DDR3 SDRAM 1333
HD: 500 Gigabyte Seagate (second drive used, see below)
OS: Windows 7 Professional 64

My current problem is it seems every other day when I start my computer up in the morning, there is some issue of one sort or another on the computer. Last week it was a corrupt file in the windows directory (an ntsomething.dll, don't recall the full name). This morning it was a corrupt system volume.

I did have a number of corrupt system volume issues when I first put the computer together, but I diagnosed that as a bad hard drive (SeaTools tests detected that pretty quick). After having run Seatools on the brand new hard drive (it came up clean), I reinstalled Windows 7 from a system image. Bad idea, as apparently it copied over the corrupt system volume. I reformatted the hard drive, started from scratch, and got myself back up and running.

This morning I had another corrupt system volume. On bootup, I discovered that it was reading only 2 gb of ram, so I reseated the RAM and ran a Memtest on it. It came out fine with no errors.

I out the SATA cable for the hard drive, and moved it to another connection, just in case I had a bad cable/connection.

Restarted my computer, windows decided to run a system repair (corrupt system volume again), rebooted, and it started up just fine (once it comes up, btw, it works just fine. No problems at all).

I ran sfc /scannow in the past and had no problems, but when I ran it just a few minutes ago it stated "Windows Resource Protection found corrupt files and succesfully repaired them. I do have a log file for it, but it's 5MB in size (I can upload a copy of the entries from just today if that would assist anyone).

The only dump file that I have is from 2 days ago (it didn't create one this morning, I'm unsure of why), but I've included that n case there might be something useful.

Any suggestions as to why I'm constantly getting this problem would be much appreciated. If you need more information, please let me know. I hope I got everything people would need, but there's so much, it's easy to overlook something:)

Thank you.

Jon

PS I'm running burn in tests as we speak, just to verify on more time.

Hi and welcome. there are several different things that can couse this type of crash. they are Device driver, System DLL corruption, Faulty hardware in I/O path (a disk error, faulty RAM, or a corrupted page file), BIOS

I would update the BIOS,
re-run the sfc /scannow
Run Hd drive diagnostics from here HD Diagnostic

If you are overclocking stop
If you have a raid update its driver

Ken J+

Code:

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\K\Desktop\011510-18515-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*d:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02806000 PsLoadedModuleList = 0xfffff800`02a43e50
Debug session time: Fri Jan 15 06:14:54.000 2010 (GMT-5)
System Uptime: 0 days 0:00:08.296
Loading Kernel Symbols
..................................................
Loading User Symbols
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck C0000221, {fffff8a00020c4e0, 0, 0, 0}

Probably caused by : ntkrnlmp.exe ( nt!ExpSystemErrorHandler2+5ff )

Followup: MachineOwner
---------

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Unknown bugcheck code (c0000221)
Unknown bugcheck description
Arguments:
Arg1: fffff8a00020c4e0
Arg2: 0000000000000000
Arg3: 0000000000000000
Arg4: 0000000000000000

Debugging Details:
------------------


BUGCHECK_STR:  0xc0000221

ERROR_CODE: (NTSTATUS) 0xc0000221 - {Bad Image Checksum}  The image %hs is possibly corrupt. The header checksum does not match the computed checksum.

EXCEPTION_CODE: (NTSTATUS) 0xc0000221 - {Bad Image Checksum}  The image %hs is possibly corrupt. The header checksum does not match the computed checksum.

EXCEPTION_PARAMETER1:  fffff8a00020c4e0

EXCEPTION_PARAMETER2:  0000000000000000

EXCEPTION_PARAMETER3:  0000000000000000

EXCEPTION_PARAMETER4: 0

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff80002ac409f to fffff80002877f00

STACK_TEXT:  
fffff880`009a91e8 fffff800`02ac409f : 00000000`0000004c 00000000`c0000221 fffff880`009a9288 fffffa80`028081a0 : nt!KeBugCheckEx
fffff880`009a91f0 fffff800`028c4544 : 7ff00000`00000000 00000000`00000000 00000000`00000000 fffff700`01080000 : nt!ExpSystemErrorHandler2+0x5ff
fffff880`009a9420 fffff800`02ca74b1 : 00000000`c0000221 00000000`00000001 00000000`00000001 00000000`004a0000 : nt!ExpSystemErrorHandler+0xd4
fffff880`009a9460 fffff800`02ca78b6 : fffffa80`c0000221 00000000`00000001 fffffa80`00000001 00000000`004a0000 : nt!ExpRaiseHardError+0xe1
fffff880`009a9790 fffff800`02ca8d66 : fffff8a0`c0000221 00000000`00000001 00000000`00000001 fffff880`009a9988 : nt!ExRaiseHardError+0x1d6
fffff880`009a9890 fffff800`02cbbf6f : 00000000`c0000221 00000000`08000000 fffff800`02d42828 ffffffff`80000084 : nt!NtRaiseHardError+0x1e4
fffff880`009a9930 fffff800`02cbc2c9 : 00000000`002a0028 00000000`00000000 00000000`00000001 fffff800`02d729f0 : nt!PspLocateSystemDll+0xbf
fffff880`009a9a00 fffff800`02da597d : fffff800`00812740 00000000`00000002 00000000`00000000 fffff800`029f0e80 : nt!PsLocateSystemDlls+0x69
fffff880`009a9a40 fffff800`02da8b20 : 00000000`00000000 00000000`00000010 ffffffff`80000028 fffff800`00812740 : nt!IoInitSystem+0x85d
fffff880`009a9b40 fffff800`02cf9419 : 00000000`00000000 fffffa80`01894040 00000000`00000080 fffffa80`01834990 : nt!Phase1InitializationDiscard+0x1290
fffff880`009a9d10 fffff800`02b1b166 : 00000000`00000000 00000000`00000080 00000000`00000000 fffff800`02856479 : nt!Phase1Initialization+0x9
fffff880`009a9d40 fffff800`02856486 : fffff800`029f0e80 fffffa80`01894040 fffff800`029fec40 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`009a9d80 00000000`00000000 : fffff880`009aa000 fffff880`009a4000 fffff880`009a93f0 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!ExpSystemErrorHandler2+5ff
fffff800`02ac409f cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!ExpSystemErrorHandler2+5ff

FOLLOWUP_NAME:  MachineOwner

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc600

FAILURE_BUCKET_ID:  X64_0xc0000221_nt!ExpSystemErrorHandler2+5ff

BUCKET_ID:  X64_0xc0000221_nt!ExpSystemErrorHandler2+5ff

Followup: MachineOwner
---------

zigzag3143 said:

Hi and welcome. there are several different things that can couse this type of crash. they are Device driver, System DLL corruption, Faulty hardware in I/O path (a disk error, faulty RAM, or a corrupted page file), BIOS

I would update the BIOS,
re-run the sfc /scannow
Run Hd drive diagnostics from here HD Diagnostic

If you are overclocking stop
If you have a raid update its driver

Ken J+

Ken,

Thanks for the quick response.

I've gone in and updated the BIOS (I was on 8.6, the latest was 8.7).
Ran sfc /scannow and it did not find any problems right now.
I've run the hardware diagnostics, no problems reported.

Not overclocking.
No Raid to worry about.

I've rebooted several times today and there doesn't seem to be a problem yet, but it does seem to be an every other day type thing, so I'll keep an eye on it.

Thanks for the suggestions :)
Jon