Hey guys,
Just as an update, I had the guy the shop put in a new mobo. After getting it in and reloading Windows 7 along with drivers and several apps, I received the same issue. I ran verifier.exe and the machine kept BSOD'ing on some sort of driver file. I was able to use system restore and install the debugging tools and according to the analysis of the dump, it appears to be an Avast system file that was causing the BSOD on boot at least.
Consistently, throughout this ordeal, I have been loading Avast each time, so it's possible that it could be the culprit. I think it's safe to say after getting every part replaced in the machine at some point including a new motherboard set up recently, that it was probably some sort of driver causing my random reboots. I ended up switching over to Norton after doing a system restore to an earlier point.
Anyways, here is the text from the analysis of the dump:
Quote:
MODULE_NAME: aswSP
FAULTING_MODULE: e2805000 nt
DEBUG_FLR_IMAGE_TIMESTAMP: 4aaf72a1
BUGCHECK_STR: 0xc9_302
DRIVER_VERIFIER_IO_VIOLATION_TYPE: 302
FAULTING_IP:
nt!NtWriteFile+2579
e2a4562d 8945e0 mov dword ptr [ebp-20h],eax
FOLLOWUP_IP:
aswSP+5fba
cc49cfba 8945e4 mov dword ptr [ebp-1Ch],eax
IRP_ADDRESS: d3c27270
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from e2b39f03 to e28e1d10
STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
c7a64324 e2b39f03 000000c9 00000302 e2a4562d nt!KeBugCheckEx+0x1e
c7a64344 e2b3c2cd e2a4562d c7a64380 00000001 nt!PoSetHiberRange+0xe278
c7a6435c e2b3c63b 00000302 e2a4562d 00000001 nt!PoSetHiberRange+0x10642
c7a643c8 e2b43849 00000302 e2a4562d 00000001 nt!PoSetHiberRange+0x109b0
c7a643e4 e2b3c076 d3c272e0 ca7a59c0 e2a4562d nt!PoSetHiberRange+0x17bbe
c7a643f8 e2b3a3e1 ca1a5690 d3c27270 ca7a59c0 nt!PoSetHiberRange+0x103eb
c7a6445c e2b39d33 d3cac488 d3c27270 c7a6448c nt!PoSetHiberRange+0xe756
c7a6446c e2b34670 ca0fe068 d3e97a30 ca0fe068 nt!PoSetHiberRange+0xe0a8
c7a6448c e2841473 d3c272e0 d3e97a8c ca0fe068 nt!PoSetHiberRange+0x89e5
c7a644a0 e2a4562d e189c514 c7a64648 00000000 nt!IofCallDriver+0x1b
c7a64578 e2a261d7 ca0fe068 845c0d20 ca7b0948 nt!NtWriteFile+0x2579
c7a645f4 e2a4c24d 00000000 c7a64648 00000040 nt!SeOpenObjectAuditAlarm+0x59a
c7a64650 e2a445ab c7a6483c c25c0d20 e284b600 nt!ObOpenObjectByName+0x159
c7a646cc e2a4feb6 c7a64874 80000000 c7a6483c nt!NtWriteFile+0x14f7
c7a64718 e284842a c7a64874 80000000 c7a6483c nt!NtCreateFile+0x34
c7a6474c e2845ecd badb0d00 c7a647c4 d3006280 nt!ZwYieldExecution+0xb56
c7a647f8 cc49cfba c7a64874 80000000 c7a6483c nt!ZwCreateFile+0x11
c7a64894 cc49dba8 00770000 00000000 c7a64a90 aswSP+0x5fba
c7a648b0 cc49fd4b 01457740 c7a64a90 0bed5b1d aswSP+0x6ba8
c7a648fc e2aa3400 00000000 0000001d c7a6499c aswSP+0x8d4b
c7a64970 e2a43a71 0000001d c4788670 c4708e80 nt!CmUnRegisterCallback+0x6fd
c7a649b8 e2a3ca0e 0000001d cb403828 c7a64a70 nt!NtWriteFile+0x9bd
c7a64b48 e2a261d7 c4616250 c25b3f78 d3d79ac8 nt!SePrivilegeCheck+0x1579
c7a64bc4 e2a4c24d 00000000 c7a64c18 00000040 nt!SeOpenObjectAuditAlarm+0x59a
c7a64c20 e2a439a4 001bfa70 c25b3f78 e2a47701 nt!ObOpenObjectByName+0x159
c7a64d00 e2a4771c 001bfacc 0002001d 001bfa70 nt!NtWriteFile+0x8f0
c7a64d20 e284842a 001bfacc 0002001d 001bfa70 nt!TmCurrentTransaction+0x681
c7a64d34 77cd64f4 badb0d00 001bfa58 00000000 nt!ZwYieldExecution+0xb56
c7a64d38 badb0d00 001bfa58 00000000 00000000 0x77cd64f4
c7a64d3c 001bfa58 00000000 00000000 00000000 0xbadb0d00
c7a64d40 00000000 00000000 00000000 00000000 0x1bfa58
STACK_COMMAND: kb
SYMBOL_STACK_INDEX: 11
SYMBOL_NAME: aswSP+5fba
FOLLOWUP_NAME: MachineOwner
IMAGE_NAME: aswSP.SYS
BUCKET_ID: WRONG_SYMBOLS
Followup: MachineOwner
I'm going to monitor the system for several days to see if this random restart issue rears its ugly head again.