Constant BSODs, various errors.

I don't see a dumpfile in your zipfile at all. Post the contents of your c:\windows\minidump folder please.. Thanks.

event3horizon said:

I don't see a dumpfile in your zipfile at all. Post the contents of your c:\windows\minidump folder please.. Thanks.

My dumpfile is 500mb. Would you still like it?

No, useless. You'll need to set it to small memory dump before the next time it crashes. It's in the system control panel , advanced.

Otherwise without info, you'll just have to do the basics like memory test, hard drive test, sfc /scannow, check CPU temps, reinstall video/audio drivers.., stress test with prim95/intel burner etc.

I just attached the latest memory dump file.

Another one.

Please help?

Come on. Someone? Anyone?

Are you serious. Help!

you'll need to be patient, no one is paid to do this. That being said here are the excerpts from the bsod analysis

first dump

Code:

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


Loading Dump File [C:\Users\dimeigna\Desktop\051712-39655-01\051712-39655-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\Program Files\Debugging Tools for Windows (x86)\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17803.amd64fre.win7sp1_gdr.120330-1504
Machine Name:
Kernel base = 0xfffff800`03001000 PsLoadedModuleList = 0xfffff800`03245670
Debug session time: Wed May 16 23:13:41.804 2012 (UTC - 4:00)
System Uptime: 0 days 0:02:18.021
Loading Kernel Symbols
...............................................................
................................................................
....................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {fffffa80273db0f0, 2, 0, fffff880015060f9}

Probably caused by : NETIO.SYS ( NETIO!RtlGetNextExpiredTimerWheelEntry+ea )

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

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

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: fffffa80273db0f0, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff880015060f9, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800032af100
 fffffa80273db0f0 

CURRENT_IRQL:  2

FAULTING_IP: 
NETIO!RtlGetNextExpiredTimerWheelEntry+ea
fffff880`015060f9 8b4210          mov     eax,dword ptr [rdx+10h]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xD1

PROCESS_NAME:  mscorsvw.exe

TRAP_FRAME:  fffff88002f224b0 -- (.trap 0xfffff88002f224b0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffa80073db0e0 rbx=0000000000000000 rcx=fffffa80073db0e0
rdx=fffffa80273db0e0 rsi=0000000000000000 rdi=0000000000000000
rip=fffff880015060f9 rsp=fffff88002f22648 rbp=0000000000000000
 r8=0000000000003607  r9=fffffa80073db000 r10=fffff880009eb180
r11=0000000000000006 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na pe nc
NETIO!RtlGetNextExpiredTimerWheelEntry+0xea:
fffff880`015060f9 8b4210          mov     eax,dword ptr [rdx+10h] ds:fffffa80`273db0f0=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff8000307f769 to fffff800030801c0

STACK_TEXT:  
fffff880`02f22368 fffff800`0307f769 : 00000000`0000000a fffffa80`273db0f0 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`02f22370 fffff800`0307e3e0 : fffff880`01695560 00000000`00000000 00000001`00000014 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`02f224b0 fffff880`015060f9 : fffff880`016b0a2f fffffa80`06980260 00000000`0000360c fffffa80`073d2088 : nt!KiPageFault+0x260
fffff880`02f22648 fffff880`016b0a2f : fffffa80`06980260 00000000`0000360c fffffa80`073d2088 fffff880`016b2422 : NETIO!RtlGetNextExpiredTimerWheelEntry+0xea
fffff880`02f22650 fffff880`016b0f5d : fffffa80`0742bbc8 fffff880`02f22830 00000000`002e1702 00000000`00000000 : tcpip!TcpProcessExpiredTcbTimers+0x7f
fffff880`02f22720 fffff800`0308ae4c : fffff880`02f22830 fffffa80`00001adf 00000000`00000000 00000000`00000001 : tcpip!TcpPeriodicTimeoutHandler+0x265
fffff880`02f227a0 fffff800`0308ace6 : fffffa80`09e0ec58 fffffa80`09e0ec58 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x6c
fffff880`02f22810 fffff800`0308abce : 00000000`52447165 fffff880`02f22e88 00000000`0000228f fffff880`009ee768 : nt!KiProcessExpiredTimerList+0xc6
fffff880`02f22e60 fffff800`0308a9b7 : fffff880`009eb1c2 fffff880`0000228f 00000000`00000001 00000000`0000008f : nt!KiTimerExpiration+0x1be
fffff880`02f22f00 fffff800`03083315 : 00000000`00000000 fffffa80`06d31060 00000000`00000000 fffff800`03198170 : nt!KiRetireDpcList+0x277
fffff880`02f22fb0 fffff800`0308312c : fffff880`009eb180 fffff800`0308b7b8 00000000`00000000 00000000`0269d967 : nt!KxRetireDpcList+0x5
fffff880`0a864aa0 fffff800`030cb1d3 : fffff800`0308b54c fffff800`0308b5b8 00000000`0000004e fffff880`0a864b60 : nt!KiDispatchInterruptContinue
fffff880`0a864ad0 fffff800`0308b5b8 : 00000000`0000004e fffff880`0a864b60 00000000`00000000 00000000`0000004e : nt!KiDpcInterruptBypass+0x13
fffff880`0a864ae0 000007fe`f6631566 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSecondaryClockInterrupt+0x1a8
00000000`0012c6c0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7fe`f6631566


STACK_COMMAND:  kb

FOLLOWUP_IP: 
NETIO!RtlGetNextExpiredTimerWheelEntry+ea
fffff880`015060f9 8b4210          mov     eax,dword ptr [rdx+10h]

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  NETIO!RtlGetNextExpiredTimerWheelEntry+ea

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: NETIO

IMAGE_NAME:  NETIO.SYS

DEBUG_FLR_IMAGE_TIMESTAMP:  4ce79381

FAILURE_BUCKET_ID:  X64_0xD1_NETIO!RtlGetNextExpiredTimerWheelEntry+ea

BUCKET_ID:  X64_0xD1_NETIO!RtlGetNextExpiredTimerWheelEntry+ea

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

the second dump is the same.

NETIO.SYS is crashing due to mscorsvw.exe which is some .NET runtime optimizer.

I would start by uninstall/reinstall of network drivers. I know you've re-done windows as you stated but you'll need to do process of elimination. If you've already done this, find an older version of the drivers and test. You may need to stop mscorsvw or reinstall it somehow, i'm not sure to which .net version it is link there's a whole lot of .NET versions. Do you have latest updates for Win?