BSOD gentagne gange i ny PC med vista 64 (har minidumps)

Jeg har for ganske nyligt købt en ny PC med følgende specs:

Bundkort:  Gigabyte GA-MA770T-UD3P
Processor: AMD Phenom Phenom II x4 955 3.2 GHz
RAM:      4 x 2GB DDR3-1333 Kingston RAM
Harddisk:  HDS 1000GB Hitachi SATAII
Grafikkort:Nvidia GF GTS 250 1GB PCI-E
PSU:      PSU Inter-Tech 500W 120mm
OS:        Vista Home Premium 64-bit DK


Jeg har fået BSOD i alt 15 gange i løbet af de sidste 3 dage, og har Minidumps liggende for alle gange. Jeg har kigget mig omkring på nettet, og har efterhånden fundet ud af hvordan man læser disse filer, men har ingen anelse om hvordan de skal tydes for at finde ud af hvor problemet ligger.
Mine BSOD's forekommer oftest under afvikling af spil, men jeg har også haft en enkelt hvor jeg blot åbnede Internet Explorer. Samtlige drivere burde være opdaterede, medmindre jeg har misset noget.

Håber der er nogle som kan hjælpe mig med at finde frem til en løsning.


Den nyeste minidump:
[code]
Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


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

Symbol search path is: SRV*DownstreamStore*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows Server 2008/Windows Vista Kernel Version 6002 (Service Pack 2) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 6002.18005.amd64fre.lh_sp2rtm.090410-1830
Machine Name:
Kernel base = 0xfffff800`01e53000 PsLoadedModuleList = 0xfffff800`02017dd0
Debug session time: Tue Oct 13 04:00:11.575 2009 (GMT+2)
System Uptime: 0 days 0:18:33.692
Loading Kernel Symbols
...............................................................
................................................................
...................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                            *
*                        Bugcheck Analysis                                    *
*                                                                            *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1E, {ffffffffc0000005, fffff8000210e8b1, 0, ffffffffffffffff}

Probably caused by : ntkrnlmp.exe ( nt!ObpWaitForMultipleObjects+2d1 )

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

0: 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: ffffffffc0000005, The exception code that was not handled
Arg2: fffff8000210e8b1, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: ffffffffffffffff, Parameter 1 of the exception

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - Instruktionen ved 0x%08lx refererede hukommelse ved 0x%08lx. Hukommelsen kunne ikke %s.

FAULTING_IP:
nt!ObpWaitForMultipleObjects+2d1
fffff800`0210e8b1 c3              ret

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  ffffffffffffffff

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff8000207a080
ffffffffffffffff

CUSTOMER_CRASH_COUNT:  3

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x1E

PROCESS_NAME:  ShippingPC-BmGa

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff80001e8fa87 to fffff80001ead450

STACK_TEXT: 
fffffa60`07d84fd8 fffff800`01e8fa87 : 00000000`0000001e ffffffff`c0000005 fffff800`0210e8b1 00000000`00000000 : nt!KeBugCheckEx
fffffa60`07d84fe0 fffff800`01ead2a9 : fffffa60`07d85718 00000000`00000001 fffffa60`07d857c0 00000000`2278f108 : nt! ?? ::FNODOBFM::`string'+0x29117
fffffa60`07d855e0 fffff800`01eabe8d : 00000000`00000001 00000000`00000000 fffffa80`06ffcbb0 fffffa80`0ab2cbb0 : nt!KiExceptionDispatch+0xa9
fffffa60`07d857c0 fffff800`0210e8b1 : f7fff800`02097b92 fffffa80`00000006 fffffa80`0ab2cbb0 00000000`00000001 : nt!KiGeneralProtectionFault+0xcd
fffffa60`07d85958 f7fff800`02097b92 : fffffa80`00000006 fffffa80`0ab2cbb0 00000000`00000001 fffffa60`07d85900 : nt!ObpWaitForMultipleObjects+0x2d1
fffffa60`07d85960 fffffa80`00000006 : fffffa80`0ab2cbb0 00000000`00000001 fffffa60`07d85900 00000000`00000000 : 0xf7fff800`02097b92
fffffa60`07d85968 fffffa80`0ab2cbb0 : 00000000`00000001 fffffa60`07d85900 00000000`00000000 00000000`00000000 : 0xfffffa80`00000006
fffffa60`07d85970 00000000`00000001 : fffffa60`07d85900 00000000`00000000 00000000`00000000 00000000`00000006 : 0xfffffa80`0ab2cbb0
fffffa60`07d85978 fffffa60`07d85900 : 00000000`00000000 00000000`00000000 00000000`00000006 fffffa60`019d8ab0 : 0x1
fffffa60`07d85980 00000000`00000000 : 00000000`00000000 00000000`00000006 fffffa60`019d8ab0 00000000`000006c4 : 0xfffffa60`07d85900


STACK_COMMAND:  kb

FOLLOWUP_IP:
nt!ObpWaitForMultipleObjects+2d1
fffff800`0210e8b1 c3              ret

SYMBOL_STACK_INDEX:  4

SYMBOL_NAME:  nt!ObpWaitForMultipleObjects+2d1

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  49e0237f

FAILURE_BUCKET_ID:  X64_0x1E_nt!ObpWaitForMultipleObjects+2d1

BUCKET_ID:  X64_0x1E_nt!ObpWaitForMultipleObjects+2d1

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

0: kd> lmvm nt
start            end                module name
fffff800`01e53000 fffff800`0236b000  nt        (pdb symbols)          downstreamstore\ntkrnlmp.pdb\98C6BA00FE174241BA3FDB915995EA9C2\ntkrnlmp.pdb
    Loaded symbol image file: ntkrnlmp.exe
    Mapped memory image file: DownstreamStore\ntkrnlmp.exe\49E0237F518000\ntkrnlmp.exe
    Image path: ntkrnlmp.exe
    Image name: ntkrnlmp.exe
    Timestamp:        Sat Apr 11 06:58:39 2009 (49E0237F)
    CheckSum:        00487B94
    ImageSize:        00518000
    File version:    6.0.6002.18005
    Product version:  6.0.6002.18005
    File flags:      0 (Mask 3F)
    File OS:          40004 NT Win32
    File type:        1.0 App
    File date:        00000000.00000000
    Translations:    0409.04b0
    CompanyName:      Microsoft Corporation
    ProductName:      Microsoft® Windows® Operating System
    InternalName:    ntkrnlmp.exe
    OriginalFilename: ntkrnlmp.exe
    ProductVersion:  6.0.6002.18005
    FileVersion:      6.0.6002.18005 (lh_sp2rtm.090410-1830)
    FileDescription:  NT Kernel & System
    LegalCopyright:  © Microsoft Corporation. All rights reserved.
[/code]