Lockups and BSOD

nixon85 said:

Hello, I have a self-built system which was running fine before I installed Win 7. But a few weeks or months after install the problems started. At first I got lockups and BSOD when playing games. Now I get them a few times a day.
Can someone please check out my .dmp files, I have no idea what's wrong. I reinstalled windows and I thought it worked better for a few weeks. Now it's worse then ever.
I uploaded my three latest .dmp files in the rar.

Thanks in advance.

I want to add that I have following things and found no errors
memtest
sfc /scannow
windows repair harddrive (don't know the english name)

What were the results of the SFC /scannow? These crashes were all caused by a device drive but unfortunately it doesnt say which one.

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\New folder (6)\033110-18187-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*F:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02c1b000 PsLoadedModuleList = 0xfffff800`02e58e50
Debug session time: Wed Mar 31 08:41:58.667 2010 (GMT-4)
System Uptime: 0 days 0:23:36.355
Loading Kernel Symbols
...............................................................
................................................................
.........................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 4A, {74a42dd9, 2, 0, fffff88006fc8ca0}

Probably caused by : ntkrnlmp.exe ( nt!KiSystemServiceExit+245 )

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

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

IRQL_GT_ZERO_AT_SYSTEM_SERVICE (4a)
Returning to usermode from a system call at an IRQL > PASSIVE_LEVEL.
Arguments:
Arg1: 0000000074a42dd9, Address of system function (system call routine)
Arg2: 0000000000000002, Current IRQL
Arg3: 0000000000000000, 0
Arg4: fffff88006fc8ca0, 0

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


PROCESS_NAME:  vsmon.exe

BUGCHECK_STR:  RAISED_IRQL_FAULT

FAULTING_IP: 
+60e3952f03c7d830
00000000`74a42dd9 ??              ???

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff80002c8c469 to fffff80002c8cf00

STACK_TEXT:  
fffff880`06fc8a68 fffff800`02c8c469 : 00000000`0000004a 00000000`74a42dd9 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`06fc8a70 fffff800`02c8c3a0 : 00000000`00000000 fffff800`02fa6dfc fffff880`06fc8ca0 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`06fc8bb0 00000000`74a42dd9 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExit+0x245
00000000`0273eba8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x74a42dd9


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!KiSystemServiceExit+245
fffff800`02c8c3a0 4883ec50        sub     rsp,50h

SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  nt!KiSystemServiceExit+245

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc600

FAILURE_BUCKET_ID:  X64_RAISED_IRQL_FAULT_vsmon.exe_nt!KiSystemServiceExit+245

BUCKET_ID:  X64_RAISED_IRQL_FAULT_vsmon.exe_nt!KiSystemServiceExit+245

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

Code:

033010-27437-01.dmp    3/30/2010 3:20:10 PM    IRQL_GT_ZERO_AT_SYSTEM_SERVICE    0x0000004a    00000000`74782dd9    00000000`00000002    00000000`00000000    fffff880`06c80ca0    ntoskrnl.exe    ntoskrnl.exe+71f00                    x64        C:\Users\K\Desktop\New folder (6)\033010-27437-01.dmp    2    15    7600    
033110-18187-01.dmp    3/31/2010 2:43:18 PM    IRQL_GT_ZERO_AT_SYSTEM_SERVICE    0x0000004a    00000000`74a42dd9    00000000`00000002    00000000`00000000    fffff880`06fc8ca0    ntoskrnl.exe    ntoskrnl.exe+71f00                    x64        C:\Users\K\Desktop\New folder (6)\033110-18187-01.dmp    2    15    7600    
033110-27234-01.dmp    3/31/2010 4:20:24 PM    IRQL_GT_ZERO_AT_SYSTEM_SERVICE    0x0000004a    00000000`73632dd9    00000000`00000002    00000000`00000000    fffff880`06d8bca0    ntoskrnl.exe    ntoskrnl.exe+71f00                    x64        C:\Users\K\Desktop\New folder (6)\033110-27234-01.dmp    2    15    7600

Thanks guys, I will try this and report back tomorrow.
What is "device drive", software or hardware?

zigzag3143 said:

What were the results of the SFC /scannow? These crashes were all caused by a device drive but unfortunately it doesnt say which one.

Is there a log or something?
When I run SFC /scannow it just says Scanning of the system started, Verification status 100%. No integrity flaws found.

That's translated from swedish, sorry if the translation is bad, hope you understand.