Windows 7 geeft bsod

[Luukg]

Ik krijg ongeveer per dag 1 bsod. Soms 2 dagen niet. Dan ineens 2 in 5 min. Het verschilt nogal. Ik dacht eerst dat het aan de hardware lag. Ik heb memtest86+ 12 uur gedraaid en geen errors. Verder heb ik geen rare drivers of iets geïnstalleerd wat dit kan veroorzaken. Kan iemand mij helpen?

Mijn hardware:

Veld	Waarde
CPU-Eigenschappen	
CPU Type	DualCore Intel Core 2 Duo E7400
CPU Aanduiding	Wolfdale-3M
CPU stepping	R0
Engineering Sample	Nee
CPUID CPU Naam	Intel(R) Core(TM)2 Duo CPU E7400 @ 2.80GHz
CPUID Revisie	0001067Ah
CPU VID	1.2875 V
	
CPU snelheid	
CPU Klok	2802.7 MHz  (origineel: 2800 MHz)
CPU Multiplier	10.5x
CPU FSB	266.9 MHz  (origineel: 266 MHz)
Geheugenbus	400.4 MHz
DRAM:FSB verhouding	12:8
	
CPU Cache	
L1 Code Cache	32 KB per core
L1 Data cache	32 KB per core
L2 Cache	3 MB  (On-Die, ECC, ASC, Full-Speed)
	
Moederbordeigenschappen	
Moederbord ID 	64-0100-000001-00101111-111108-Bearlake$0AAAA000_A7360IMS V1.10 111108
Moederbordnaam	MSI P35 Neo (MS-7360)  (2 PCI, 3 PCI-E x1, 1 PCI-E x16, 4 DDR2 DIMM, Audio, Gigabit LAN)
	
Chipseteigenschappen	
Moederbord Chipset	Intel Bearlake P35
Geheugeninstellingen	5-5-5-18  (CL-RCD-RP-RAS)
Command Rate (CR)	2T
DIMM2: Kingston "	2 GB DDR2-800 DDR2 SDRAM  (5-5-5-18 @ 400 Mhz)  (4-4-4-12 @ 266 Mhz)  (3-3-3-9 @ 200 Mhz)
DIMM4: Kingston "	2 GB DDR2-800 DDR2 SDRAM  (5-5-5-18 @ 400 Mhz)  (4-4-4-12 @ 266 Mhz)  (3-3-3-9 @ 200 Mhz)
	
BIOS Eigenschappen	
Datum Systeem BIOS	11/11/08
Datum Video BIOS	01/09/08
DMI BIOS Versie	V1.10
	
Grafische Processor Eigenschappen	
Video kaart	nVIDIA GeForce 8800 GT
GPU Codenaam	G92GT  (PCI Express 2.0 x16 10DE / 0611, Rev A2)
GPU Klok (Geometric Domain)	602 Mhz  (origineel: 600 MHz)
GPU Klok (Shader Domain)	1512 Mhz  (origineel: 1500 MHz)
Geheugenklok	900 Mhz  (origineel: 900 MHz)

bron: everest ultimate edition.


Verder heb ik hier de 5 recenste minidumps:
mindump1/////////////////////////////////////////////////////////////////////////////////

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


Loading Dump File [C:\Windows\Minidump\111810-16843-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*your local folder for symbols*[url]http://msdl.microsoft.com/download/symbols[/url]
Executable search path is: 
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02a0b000 PsLoadedModuleList = 0xfffff800`02c48e50
Debug session time: Thu Nov 18 16:47:08.989 2010 (UTC + 1:00)
System Uptime: 0 days 2:07:07.629
Loading Kernel Symbols
...............................................................
................................................................
..................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {fffffa801dbe5c80, 5, 1, fffff88004100197}

Unable to load image \SystemRoot\System32\Drivers\sptd.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for sptd.sys
*** ERROR: Module load completed but symbols could not be loaded for sptd.sys
Probably caused by : sptd.sys ( sptd+41192 )

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: fffffa801dbe5c80, memory referenced
Arg2: 0000000000000005, IRQL
Arg3: 0000000000000001, value 0 = read operation, 1 = write operation
Arg4: fffff88004100197, address which referenced memory

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


WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cb30e0
 fffffa801dbe5c80 

CURRENT_IRQL:  5

FAULTING_IP: 
+3061613762363632
fffff880`04100197 ??              ???

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xD1

PROCESS_NAME:  System

TRAP_FRAME:  fffff88002f1b860 -- (.trap 0xfffff88002f1b860)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=00000000a2128901 rbx=0000000000000000 rcx=fffffa8004b55780
rdx=fffffa80047b5050 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88004100197 rsp=fffff88002f1b9f0 rbp=fffff88003d8f254
 r8=fffff88002f1ba68  r9=0000000000000000 r10=00000000000048f0
r11=fffff880084c5a90 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na po nc
fffff880`04100197 ??              ???
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002a7aca9 to fffff80002a7b740

STACK_TEXT:  
fffff880`02f1b718 fffff800`02a7aca9 : 00000000`0000000a fffffa80`1dbe5c80 00000000`00000005 00000000`00000001 : nt!KeBugCheckEx
fffff880`02f1b720 fffff800`02a79920 : 00000000`00000002 fffffa80`04f84000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`02f1b860 fffff880`04100197 : fffff880`03d8f259 fffff880`01108192 fffffa80`046a6000 fffff880`00db0b34 : nt!KiPageFault+0x260
fffff880`02f1b9f0 fffff880`03d8f259 : fffff880`01108192 fffffa80`046a6000 fffff880`00db0b34 fffff880`02f1ba68 : 0xfffff880`04100197
fffff880`02f1b9f8 fffff880`01108192 : fffffa80`046a6000 fffff880`00db0b34 fffff880`02f1ba68 00000000`00000000 : USBPORT!USBPORT_InterruptService+0x5
fffff880`02f1ba00 fffffa80`046a6000 : fffff880`00db0b34 fffff880`02f1ba68 00000000`00000000 fffffa80`05155200 : sptd+0x41192
fffff880`02f1ba08 fffff880`00db0b34 : fffff880`02f1ba68 00000000`00000000 fffffa80`05155200 fffffa80`04b55780 : 0xfffffa80`046a6000
fffff880`02f1ba10 fffff880`02f1ba68 : 00000000`00000000 fffffa80`05155200 fffffa80`04b55780 00000000`00000000 : ataport!IdePortInterrupt
fffff880`02f1ba18 00000000`00000000 : fffffa80`05155200 fffffa80`04b55780 00000000`00000000 fffffa80`04f8b5d3 : 0xfffff880`02f1ba68


STACK_COMMAND:  kb

FOLLOWUP_IP: 
sptd+41192
fffff880`01108192 ??              ???

SYMBOL_STACK_INDEX:  5

SYMBOL_NAME:  sptd+41192

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: sptd

IMAGE_NAME:  sptd.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4ad24632

FAILURE_BUCKET_ID:  X64_0xD1_sptd+41192

BUCKET_ID:  X64_0xD1_sptd+41192

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

Minidump2////////////////////////////////////////////////////////////////


Loading Dump File [C:\Windows\Minidump\111810-15953-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*your local folder for symbols*[url]http://msdl.microsoft.com/download/symbols[/url]
Executable search path is: 
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02a15000 PsLoadedModuleList = 0xfffff800`02c52e50
Debug session time: Wed Nov 17 23:51:56.978 2010 (UTC + 1:00)
System Uptime: 0 days 2:24:44.619
Loading Kernel Symbols
...............................................................
................................................................
....................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff9600022eb40, fffff8800a31dcc0, 0}

Probably caused by : win32k.sys ( win32k!GreDrawStream+178 )

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

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

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff9600022eb40, Address of the instruction which caused the bugcheck
Arg3: fffff8800a31dcc0, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP: 
win32k!GreDrawStream+178
fffff960`0022eb40 837f1400        cmp     dword ptr [rdi+14h],0

CONTEXT:  fffff8800a31dcc0 -- (.cxr 0xfffff8800a31dcc0)
rax=0000000000000008 rbx=000000000000003c rcx=000000000000003c
rdx=0000000000000000 rsi=fffff900c1b2dbe0 rdi=fffff8800a31e8d4
rip=fffff9600022eb40 rsp=fffff8800a31e690 rbp=fffff900c0000de0
 r8=fffff900c200fc90  r9=0000000000000000 r10=0000000000000001
r11=0000000000000006 r12=fffff900c1b2df20 r13=fffff900c200fc90
r14=fffff900c0000de0 r15=fffff900c0000750
iopl=0         nv up ei ng nz na pe nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00210282
win32k!GreDrawStream+0x178:
fffff960`0022eb40 837f1400        cmp     dword ptr [rdi+14h],0 ds:002b:fffff880`0a31e8e8=????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x3B

PROCESS_NAME:  Game_Maker.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff9600022eb40

STACK_TEXT:  
fffff880`0a31e690 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : win32k!GreDrawStream+0x178


FOLLOWUP_IP: 
win32k!GreDrawStream+178
fffff960`0022eb40 837f1400        cmp     dword ptr [rdi+14h],0

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  win32k!GreDrawStream+178

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: win32k

IMAGE_NAME:  win32k.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4c7dc13c

STACK_COMMAND:  .cxr 0xfffff8800a31dcc0 ; kb

FAILURE_BUCKET_ID:  X64_0x3B_win32k!GreDrawStream+178

BUCKET_ID:  X64_0x3B_win32k!GreDrawStream+178

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

mindump3/////////////////////////////////////////////////////////////////////////////////////


Loading Dump File [C:\Windows\Minidump\111710-18640-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*your local folder for symbols*[url]http://msdl.microsoft.com/download/symbols[/url]
Executable search path is: 
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02a03000 PsLoadedModuleList = 0xfffff800`02c40e50
Debug session time: Wed Nov 17 18:13:04.355 2010 (UTC + 1:00)
System Uptime: 0 days 0:46:23.011
Loading Kernel Symbols
...............................................................
................................................................
....................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c000001d, fffff96000152762, fffff88009c8acc0, 0}

Probably caused by : hardware ( win32k!CalcVisRgn+2 )

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

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

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c000001d, Exception code that caused the bugcheck
Arg2: fffff96000152762, Address of the instruction which caused the bugcheck
Arg3: fffff88009c8acc0, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

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


EXCEPTION_CODE: (NTSTATUS) 0xc000001d - {EXCEPTION}  Illegal Instruction  An attempt was made to execute an illegal instruction.

FAULTING_IP: 
win32k!CalcVisRgn+2
fffff960`00152762 5c              pop     rsp

CONTEXT:  fffff88009c8acc0 -- (.cxr 0xfffff88009c8acc0)
rax=fffff900c06064b0 rbx=fffff900c06064b0 rcx=fffff900c1d3d1e0
rdx=fffff900c06064b0 rsi=fffff900c1d3d1e0 rdi=00000000ffffffff
rip=fffff96000152762 rsp=fffff88009c8b698 rbp=fffff900c00c0010
 r8=fffff900c06064b0  r9=0000000000004411 r10=fffff900c202ba70
r11=fffff900c1d3d140 r12=0000000000000001 r13=fffff900c01ef3a0
r14=0000000000000000 r15=0000000000000001
iopl=0         nv up ei ng nz na pe nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00210282
win32k!CalcVisRgn+0x2:
fffff960`00152762 5c              pop     rsp
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x3B

PROCESS_NAME:  Game_Maker.exe

CURRENT_IRQL:  0

MISALIGNED_IP: 
win32k!CalcVisRgn+2
fffff960`00152762 5c              pop     rsp

LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff96000152762

STACK_TEXT:  
fffff880`09c8b698 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : win32k!CalcVisRgn+0x2


FOLLOWUP_IP: 
win32k!CalcVisRgn+2
fffff960`00152762 5c              pop     rsp

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  win32k!CalcVisRgn+2

FOLLOWUP_NAME:  MachineOwner

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

STACK_COMMAND:  .cxr 0xfffff88009c8acc0 ; kb

MODULE_NAME: hardware

FAILURE_BUCKET_ID:  X64_IP_MISALIGNED

BUCKET_ID:  X64_IP_MISALIGNED

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

minidump 4/////////////////////////////////////////////////////////////

Probably caused by : hardware ( win32k!CalcVisRgn+2 )

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


Loading Dump File [C:\Windows\Minidump\111710-18156-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*your local folder for symbols*[url]http://msdl.microsoft.com/download/symbols[/url]
Executable search path is: 
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02a03000 PsLoadedModuleList = 0xfffff800`02c40e50
Debug session time: Wed Nov 17 17:25:22.355 2010 (UTC + 1:00)
System Uptime: 0 days 0:52:10.011
Loading Kernel Symbols
...............................................................
................................................................
....................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 7F, {8, 80050031, 406f8, fffffa80049e1040}

Probably caused by : ntkrnlmp.exe ( nt!KiDoubleFaultAbort+b2 )

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

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

UNEXPECTED_KERNEL_MODE_TRAP (7f)
This means a trap occurred in kernel mode, and it's a trap of a kind
that the kernel isn't allowed to have/catch (bound trap) or that
is always instant death (double fault).  The first number in the
bugcheck params is the number of the trap (8 = double fault, etc)
Consult an Intel x86 family manual to learn more about what these
traps are. Here is a *portion* of those codes:
If kv shows a taskGate
        use .tss on the part before the colon, then kv.
Else if kv shows a trapframe
        use .trap on that value
Else
        .trap on the appropriate frame will show where the trap was taken
        (on x86, this will be the ebp that goes with the procedure KiTrap)
Endif
kb will then show the corrected stack.
Arguments:
Arg1: 0000000000000008, EXCEPTION_DOUBLE_FAULT
Arg2: 0000000080050031
Arg3: 00000000000406f8
Arg4: fffffa80049e1040

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


BUGCHECK_STR:  0x7f_8

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff80002a72ca9 to fffff80002a73740

STACK_TEXT:  
fffff800`04136d28 fffff800`02a72ca9 : 00000000`0000007f 00000000`00000008 00000000`80050031 00000000`000406f8 : nt!KeBugCheckEx
fffff800`04136d30 fffff800`02a71172 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff800`04136e70 fffffa80`049e1040 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDoubleFaultAbort+0xb2
fffff800`0413e3e8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0xfffffa80`049e1040


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!KiDoubleFaultAbort+b2
fffff800`02a71172 90              nop

SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  nt!KiDoubleFaultAbort+b2

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4c1c44a9

FAILURE_BUCKET_ID:  X64_0x7f_8_nt!KiDoubleFaultAbort+b2

BUCKET_ID:  X64_0x7f_8_nt!KiDoubleFaultAbort+b2

Followup: MachineOwner

Minidump5/////////////////////////////////////////////////////////////////////////////////////


Loading Dump File [C:\Windows\Minidump\111510-17937-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*your local folder for symbols*[url]http://msdl.microsoft.com/download/symbols[/url]
Executable search path is: 
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02a57000 PsLoadedModuleList = 0xfffff800`02c94e50
Debug session time: Mon Nov 15 22:25:43.726 2010 (UTC + 1:00)
System Uptime: 0 days 0:27:21.367
Loading Kernel Symbols
...............................................................
................................................................
....................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {fffff8001bda4fb1, d, 1, fffff80002a21f60}

Unable to load image \SystemRoot\system32\DRIVERS\intelppm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for intelppm.sys
*** ERROR: Module load completed but symbols could not be loaded for intelppm.sys
Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+260 )

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

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

IRQL_NOT_LESS_OR_EQUAL (a)
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 a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: fffff8001bda4fb1, memory referenced
Arg2: 000000000000000d, IRQL
Arg3: 0000000000000001, bitfield :
	bit 0 : value 0 = read operation, 1 = write operation
	bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff80002a21f60, address which referenced memory

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


WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cff0e0
 fffff8001bda4fb1 

CURRENT_IRQL:  d

FAULTING_IP: 
hal!HalpRtcClockInterrupt+0
fffff800`02a21f60 48895c2408      mov     qword ptr [rsp+8],rbx

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  System

TRAP_FRAME:  fffff80004133920 -- (.trap 0xfffff80004133920)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff80004133ac0 rbx=0000000000000000 rcx=fffff80002a3d3c0
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002a21f60 rsp=fffff80004133ab8 rbp=fffff80004133b40
 r8=fffff80002c4fc40  r9=00000000f008072b r10=0000000000016181
r11=fffff80002c41e00 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
hal!HalpRtcClockInterrupt:
fffff800`02a21f60 48895c2408      mov     qword ptr [rsp+8],rbx ss:0018:fffff800`04133ac0=fffffa8005065480
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002ac6ca9 to fffff80002ac7740

STACK_TEXT:  
fffff800`041337d8 fffff800`02ac6ca9 : 00000000`0000000a fffff800`1bda4fb1 00000000`0000000d 00000000`00000001 : nt!KeBugCheckEx
fffff800`041337e0 fffff800`02ac5920 : 00000000`00000057 00000000`00000000 fffffa80`04e4c9f0 fffff880`04d082dc : nt!KiBugCheckDispatch+0x69
fffff800`04133920 fffff800`02a21f60 : fffff800`02ac3c33 fffffa80`05065480 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x260
fffff800`04133ab8 fffff800`02ac3c33 : fffffa80`05065480 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalpRtcClockInterrupt
fffff800`04133ac0 fffff880`03bd69c2 : fffff800`02ad524a 00000000`0029c3d5 fffffa80`051f3598 fffff800`02c4fc40 : nt!KiInterruptDispatchNoLock+0x163
fffff800`04133c58 fffff800`02ad524a : 00000000`0029c3d5 fffffa80`051f3598 fffff800`02c4fc40 00000000`00000001 : intelppm+0x39c2
fffff800`04133c60 fffff800`02acfebc : fffff800`02c41e80 fffff800`00000000 00000000`00000000 fffff880`0481fef8 : nt!PoIdle+0x53a
fffff800`04133d40 00000000`00000000 : fffff800`04134000 fffff800`0412e000 fffff800`04133d00 00000000`00000000 : nt!KiIdleLoop+0x2c


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!KiPageFault+260
fffff800`02ac5920 440f20c0        mov     rax,cr8

SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  nt!KiPageFault+260

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4c1c44a9

FAILURE_BUCKET_ID:  X64_0xA_nt!KiPageFault+260

BUCKET_ID:  X64_0xA_nt!KiPageFault+260

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

Beetje lang bericht.
Als er nog meer informatie nodig is?

 

[pity123]

Ik denk dat het aan deze punten ligt:

* Verkeerde drivers
* Hardware probleem
* Antivirus probleem
* Of een probleem door overclocken.


Kun jij mij even de bestanden die in de map C:\Windows\MiniDump zitten, in een .zip doen en even posten.

B.V.D.

 

[gast0225]

Sorry, het is niet echt offtopic, maar wel komisch:
pity123 : wat jij als mogelijke oorzaken beschrijft is dus eigenlijk de gehele computer.

De 4 oorzaken die je noemt zijn een computer.

 

[dnties]

Je eerste BSOD geeft aan dat mogelijk sptd.sys daarvan de boosdoener is. Of dat verder ook invloed had op de andere BSOD's heb ik zo snel niet bekeken.

Die driver is gerelateerd aan Daemon Tools en/of Alcohol 120% installatie op je pc. Om oorzaken uit te sluiten zou ik dus eerst Daemon Tools/Alcohol 120% deïnstalleren en daarna gaan kijken of de BSOD's terugkomen.

Tijs.

 

[pity123]

Maar, ik heb nog wel de C:\Windows\MiniDump bestanden nodig voor analyse. Het kan eigelijks overal aan liggen.

 

[gast0225]

Ja, idd. en daarom reageerde ik zoals ik reageerde.

 

[dnties]

@pity123: Als je de tekst over de systeeminformatie leest, dan zie je dat daar ook analyses in staan van de minidumps.

Natuurlijk begrijp ik dat je wellicht zelf een betere analyse kunt doen dan !analyze -v in de debugger, maar ik zou als ik jou was even afwachten welke minidumps er ontstaan als Daemon Tools en Alcohol 120% van die pc zijn gedeïnstalleerd (zie mijn vorige posting).

Tijs.

 

[pity123]

Er is een post op Helpmij die dezelfde BSOD error weergeeft als bij de pc van TS.

http://www.helpmij.nl/forum/showthread.php/478227-driver_irql_not_less_or_equal

En ik heb meestal niet veel zin om een hele hoop tekst te lezen.

 

[dnties]

@pity123: als jouw minidump-analyses ook zo kort door de bocht zijn, dan kun je maar beter niet posten:
a. In de startposting staan 5 BSOD's geanalyseerd, en zover ik kan zien hebben die allemaal verschillende bugcheckcodes. (zie b.)
b. Alleen de eerste (die over sptd.sys) is qua bugcheck-code gelijk aan jouw link, maar qua betroffen driver helemaal niet. [In jouw link gaat het om NVLDDMKM.SYS, wat een grafische kaart-driver is van Nvidia.]

Tijs.

 

[pity123]

Je eerste BSOD geeft aan dat mogelijk sptd.sys daarvan de boosdoener is. Of dat verder ook invloed had op de andere BSOD's heb ik zo snel niet bekeken.

Die driver is gerelateerd aan Daemon Tools en/of Alcohol 120% installatie op je pc. Om oorzaken uit te sluiten zou ik dus eerst Daemon Tools/Alcohol 120% deïnstalleren en daarna gaan kijken of de BSOD's terugkomen.

Tijs.

Ik ben er mee eens met dnties.

Sorry voor de verwarring.

 

[Luukg]

Wow bedankt dat jullie zo snel reageren. Ik heb deamon tools van m'n computer afgegooid.

Ik gebruik op dit moment de nieuwste videokaart drivers van nvidia. Forceware 260.99. Kan dit de oorzaak zijn??

Ik heb de minidumps in 2 zip bestanden staan.

 

[dnties]

Ik wijs je erop (had ik al geschreven) dat het zinvoller is om vanaf nu (dus nu de Daemon Tools van je systeem zijn) te gaan kijken of BSOD's terugkomen en wat dáár dan de minidump-bestanden van zijn.

Wellicht heeft pity123 nog zin om je 'oude' minidumps door te nemen. Ik wacht gewoon af of er nog nieuwe BSOD's komen, nu je Daemon Tools niet meer gebruikt.

Tijs.

 

[Luukg]

ja de minidumps waren voor pity ind. Hij vroeg erom.
En ik wacht ind gewoon af. Bedankt voor je hulp:thumb:

 

[pity123]

Ik wacht ook liever...

Als je weer een BSOD krijgt moet je het even zeggen en de code posten hè.

Groetjes,
Pity123

 

[Luukg]

nieuwe bsod

ja het is weer zover

De minidump

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


Loading Dump File [C:\Windows\Minidump\111810-17390-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*your local folder for 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.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02a17000 PsLoadedModuleList = 0xfffff800`02c54e50
Debug session time: Thu Nov 18 20:31:21.988 2010 (UTC + 1:00)
System Uptime: 0 days 3:42:32.628
Loading Kernel Symbols
...............................................................
................................................................
....................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c000001d, fffff960001938c5, fffff880081279e0, 0}

Probably caused by : hardware ( win32k!xxxDCEWindowHitTest2+365 )

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

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

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c000001d, Exception code that caused the bugcheck
Arg2: fffff960001938c5, Address of the instruction which caused the bugcheck
Arg3: fffff880081279e0, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

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


EXCEPTION_CODE: (NTSTATUS) 0xc000001d - {EXCEPTION}  Illegal Instruction  An attempt was made to execute an illegal instruction.

FAULTING_IP: 
win32k!xxxDCEWindowHitTest2+365
fffff960`001938c5 f0897c2450      lock mov dword ptr [rsp+50h],edi

CONTEXT:  fffff880081279e0 -- (.cxr 0xfffff880081279e0)
rax=fffff900c0703dd0 rbx=fffff900c06e63f0 rcx=fffff88008128420
rdx=fffff900c0703dd0 rsi=0000000000000000 rdi=0000000000000000
rip=fffff960001938c5 rsp=fffff880081283b0 rbp=00000000fffffffe
 r8=0000000000000000  r9=0000000000000000 r10=0000028b00000441
r11=000000000000028b r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na pe nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00210202
win32k!xxxDCEWindowHitTest2+0x365:
fffff960`001938c5 f0897c2450      lock mov dword ptr [rsp+50h],edi ss:0018:fffff880`08128400=????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x3B

PROCESS_NAME:  Game_Maker.exe

CURRENT_IRQL:  0

MISALIGNED_IP: 
win32k!xxxDCEWindowHitTest2+365
fffff960`001938c5 f0897c2450      lock mov dword ptr [rsp+50h],edi

LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff960001938c5

STACK_TEXT:  
fffff880`081283b0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : win32k!xxxDCEWindowHitTest2+0x365


FOLLOWUP_IP: 
win32k!xxxDCEWindowHitTest2+365
fffff960`001938c5 f0897c2450      lock mov dword ptr [rsp+50h],edi

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  win32k!xxxDCEWindowHitTest2+365

FOLLOWUP_NAME:  MachineOwner

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

STACK_COMMAND:  .cxr 0xfffff880081279e0 ; kb

MODULE_NAME: hardware

FAILURE_BUCKET_ID:  X64_IP_MISALIGNED

BUCKET_ID:  X64_IP_MISALIGNED

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

Links boven in de bluescreen stond system_service_exception
Ik heb de minidump in de bijlage.
Hopelijk kan iemand mij helpen??

 

[dnties]

Zie hier

Cause

This error has been linked to excessive paged pool usage and may occur due to user-mode graphics drivers crossing over and passing bad data to the kernel code.

In je dump: EXCEPTION_CODE: (NTSTATUS) 0xc000001d - {UITZONDERING} Ongeldige instructie Er is geprobeerd een ongeldige instructie uit te voeren.

Dat het in Win32k plaatsvindt hint ook al naar 'iets grafisch'.

Het is bovendien al de zoveelste BSOD die vanuit game_maker.exe plaatsvindt.
Waar gebruik je dat programma voor? En waarom zo vaak?

Zou er een probleem zijn in je grafische kaart (en/of de driver)?

NB: Dit is een voorlopige analyse.

Tijs.

 

[Luukg]

Ik gebruik gamemaker voor school. Ik moet een game maken voor informatica. Ik dacht inderdaad eerst dat het aan gamemaker lag. Maar ik krijg ook bsod's wanneer ik gamemaker niet gebruik en bijvoorbeeld gewoon op internet zit.

Verder is gamemaker niet bepaald intensief ofzo? Ik maak er een mario game mee.

Verder speel ik ook wel eens mw, mw2 en blackops. En dan is er vaak niks aan de hand.
Is er iets waarmee ik kan testen of het aan mijn videokaart licht? Verder heb ik ook nog nooit artefacts gekregen.

Verder heb ik ook al mijn hardeschijf getest op fouten. Want random crashes worden vaak veroorzaakt door of het geheugen of door de hardeschijf toch??

Ik ben ook hier naartoe gegaan omdat ik het helemaal niet meer weet:d

Woh(als mn leraar nederlands dit bericht zag!!!, hoezo ik gebruik vaak: verder)

 

[dnties]

Nu begrijp ik het niet meer: Ik zie nog steeds sptd.sys geladen staan. Je had toch Daemon Tools gedeïnstalleerd?

fffff880`0100c000 fffff880`01132000 sptd sptd.sys Sun Oct 11 22:55:14 2009 (4AD24632)

Zoek eerst het bestand op in je \windows\system32\drivers map, rechtsklik erop en kies Eigenschappen. Kijk in tabblad Versie. Loop alle Itemnamen even door en kijk of het inderdaad bij Daemon tools hoort.

Download AutoRuns.exe en draai die.
Zodra die klaar is met scannen, zoek (via klikken op het 'verrekijkertje' of Ctrl-f toetscombinatie) naar sptd.sys
Vertel ons in welke sectie je die driver hebt gezien. Een schermafdruk van het bewuste stuk zou nog mooier zijn.

Vind je het in Autoruns terug, en is het inderdaad van Daemon Tools, dan geeft dat wat mij betreft weer voer aan mijn mening dat het een troep-pakket is. Als ze zelfs geen fatsoenlijke deïnstallatie kunnen verzorgen... :evil:

Tijs.

 

[Luukg]

Ok heb weer een bsod gehad.

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


Loading Dump File [C:\Windows\Minidump\111910-16812-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*your local folder for 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.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02a0d000 PsLoadedModuleList = 0xfffff800`02c4ae50
Debug session time: Fri Nov 19 15:30:33.229 2010 (UTC + 1:00)
System Uptime: 0 days 0:05:15.885
Loading Kernel Symbols
...............................................................
................................................................
..................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1E, {ffffffffc000001d, fffff80002a79005, 0, 1f500}

Probably caused by : hardware ( nt!KiChainedDispatch+15 )

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

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

KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: ffffffffc000001d, The exception code that was not handled
Arg2: fffff80002a79005, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 000000000001f500, Parameter 1 of the exception

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


EXCEPTION_CODE: (NTSTATUS) 0xc000001d - {EXCEPTION}  Illegal Instruction  An attempt was made to execute an illegal instruction.

FAULTING_IP: 
nt!KiChainedDispatch+15
fffff800`02a79005 ab              stos    dword ptr [rdi]

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  000000000001f500

ERROR_CODE: (NTSTATUS) 0xc000001d - {EXCEPTION}  Illegal Instruction  An attempt was made to execute an illegal instruction.

BUGCHECK_STR:  0x1E_c000001d

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

EXCEPTION_RECORD:  fffff88002f1b888 -- (.exr 0xfffff88002f1b888)
ExceptionAddress: fffff80002a79005 (nt!KiChainedDispatch+0x0000000000000015)
   ExceptionCode: c000001d (Illegal instruction)
  ExceptionFlags: 00000008
NumberParameters: 0

TRAP_FRAME:  fffff88002f1b930 -- (.trap 0xfffff88002f1b930)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000021696 rbx=0000000000000000 rcx=fffffa8005117a40
rdx=fffffa8005206498 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002a79005 rsp=fffff88002f1bac0 rbp=fffff8800257bb40
 r8=0000000000000000  r9=000000002bfe1d3d r10=000000000001f5a7
r11=fffffa8005aa1300 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up di pl nz ac pe nc
nt!KiChainedDispatch+0x15:
fffff800`02a79005 ab              stos    dword ptr [rdi] ds:7200:00000000`00000000=????????
Resetting default scope

MISALIGNED_IP: 
nt!KiChainedDispatch+15
fffff800`02a79005 ab              stos    dword ptr [rdi]

LAST_CONTROL_TRANSFER:  from fffff80002ab7a39 to fffff80002a7d740

FAILED_INSTRUCTION_ADDRESS: 
nt!KiChainedDispatch+15
fffff800`02a79005 ab              stos    dword ptr [rdi]

STACK_TEXT:  
fffff880`02f1b0b8 fffff800`02ab7a39 : 00000000`0000001e ffffffff`c000001d fffff800`02a79005 00000000`00000000 : nt!KeBugCheckEx
fffff880`02f1b0c0 fffff800`02a7cd82 : fffff880`02f1b888 00000000`00000000 fffff880`02f1b930 fffffa80`04b566c0 : nt!KiDispatchException+0x1b9
fffff880`02f1b750 fffff800`02a7aedf : fffff880`02f1b930 00000000`00000000 00000000`00000000 fffff800`00000000 : nt!KiExceptionDispatch+0xc2
fffff880`02f1b930 fffff800`02a79005 : 00000000`00000000 fffff880`02f1bb40 fffff880`009e8180 00000000`00000001 : nt!KiInvalidOpcodeFault+0x11f
fffff880`02f1bac0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiChainedDispatch+0x15


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!KiChainedDispatch+15
fffff800`02a79005 ab              stos    dword ptr [rdi]

SYMBOL_STACK_INDEX:  4

SYMBOL_NAME:  nt!KiChainedDispatch+15

FOLLOWUP_NAME:  MachineOwner

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MODULE_NAME: hardware

FAILURE_BUCKET_ID:  X64_IP_MISALIGNED

BUCKET_ID:  X64_IP_MISALIGNED

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

dnties, ik heb het programma gedownload en sptd.sys gezocht en hij staat onder het tablad drivers, maar als ik rechtermuisknop doe en dan eigenschappen, zegt hij dat hij hem niet kan vinden?
Ik heb gekeken en er staat wel degelijk sptd.sys in de driver map van windows. Als ik hier naar de eigenschappen ga, staat er niks bij detais over welk programma het gebruikt. Dit komt waarschijnlijk omdat ik deamon tools heb gedeïnstalleerd toch?

in dit forum hebben ze het erover dat:
This problem might not have anything to do with Daemon Tools or SPTD.sys, like what happened to me. I have been wrongly blaming SPTD but it turned out that some malware disabled my safeboot key from the registry. So to make sure that your safeboot is still there, please use regedit and check the following:
HKLM\System\CurrentControlSet\Control\Safeboot
(dit heb ik gecheckt en dit heb ik schijnbaar ook niet, is dit het probleem?)

If the key is missing, you might have been attacked by malware,(ik heb een schone installatie gedaan, om te kijken of het door malware kwam, wel heb ik data d ongeschonden gelaten, kan het virus vanaf daar weer m'n windows in zijn gegaan?) especially if you can't even enable "Show hidden files and folders" from Windows Explorer. To restore safeboot, please visit:
Restoring Safeboot Didier Stevens

Bonne chance!

bron:
http://forum.daemon-tools.cc/f19/sptd-sys-21741/

Moet ik proberen de oplossing uit te voeren? of moet ik sptd.sys verwijderen en kijken of ik nog een bsod krijg? Graag advies.

 

[dnties]

Het is voldoende om sptd.sys uit te vinken in Autoruns.
Daarna File -> Refresh (of F5) doen en na de herscan kijken of het nog steeds is uitgevinkt.
Daarna Autoruns afsluiten en de pc opnieuw opstarten. Dan weer checken in Autoruns of sptd.sys nog steeds uitgeschakeld is.

Hopelijk komen er dan geen bsod's meer, maar 100% zekerheid heb ik daar niet van, natuurlijk.

Tijs.