Long time no see guys,

So I just got myself a custom built computer, GTX580, Intel i7 950, 6gb ram yabba yabba yabba...

So on the first day of having this I am getting BSOD's...

everytime whilst gaming. Now I have debugged the minidumps and it keeps saying nvlddmkm.sys is one of the problems and USBPORT.SYS is the other.

Let me try and post some info about some of them. Thanks in advance if you can help.

__________________________________________________ ________________

The computer has rebooted from a bugcheck. The bugcheck was: 0x000000d1 (0x0000000000000749, 0x000000000000000d, 0x0000000000000008, 0x0000000000000749). A dump was saved in: C:\Windows\MEMORY.DMP.

************************************************** *****************************
* *
* 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: 0000000000000749, memory referenced
Arg2: 000000000000000d, IRQL
Arg3: 0000000000000008, value 0 = read operation, 1 = write operation
Arg4: 0000000000000749, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800033010e0
0000000000000749

CURRENT_IRQL: d

FAULTING_IP:
+3930653762363664
00000000`00000749 ?? ???

PROCESS_NAME: System

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0xD1

TRAP_FRAME: fffff880031ab9d0 -- (.trap 0xfffff880031ab9d0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=52255bfe60f24400 rbx=0000000000000000 rcx=0000000000000011
rdx=000000000001f236 rsi=0000000000000000 rdi=0000000000000000
rip=0000000000000749 rsp=fffff880031abb60 rbp=0000000000000000
r8=00000000000250f8 r9=0000000000000000 r10=0000000000000749
r11=0000000000000008 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na po nc
00000000`00000749 ?? ???
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff800030ca469 to fffff800030caf00

FAILED_INSTRUCTION_ADDRESS:
+3930653762363664
00000000`00000749 ?? ???

STACK_TEXT:
fffff880`031ab888 fffff800`030ca469 : 00000000`0000000a 00000000`00000749 00000000`0000000d 00000000`00000008 : nt!KeBugCheckEx
fffff880`031ab890 fffff800`030c90e0 : fffffa80`04efb000 00000000`f63a42c9 fffffa80`07a08010 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`031ab9d0 00000000`00000749 : 00000000`00000008 fffff880`0ff487ec 8fd2f78b`ad20f311 59cc907b`b0391094 : nt!KiPageFault+0x260
fffff880`031abb60 00000000`00000008 : fffff880`0ff487ec 8fd2f78b`ad20f311 59cc907b`b0391094 00000000`00000000 : 0x749
fffff880`031abb68 fffff880`0ff487ec : 8fd2f78b`ad20f311 59cc907b`b0391094 00000000`00000000 00000000`00000000 : 0x8
fffff880`031abb70 8fd2f78b`ad20f311 : 59cc907b`b0391094 00000000`00000000 00000000`00000000 00000000`00000000 : nvlddmkm+0xc27ec
fffff880`031abb78 59cc907b`b0391094 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x8fd2f78b`ad20f311
fffff880`031abb80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x59cc907b`b0391094


STACK_COMMAND: kb

FOLLOWUP_IP:
nvlddmkm+c27ec
fffff880`0ff487ec ?? ???

SYMBOL_STACK_INDEX: 5

SYMBOL_NAME: nvlddmkm+c27ec

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME: nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4d9e7f64

FAILURE_BUCKET_ID: X64_0xD1_CODE_AV_BAD_IP_nvlddmkm+c27ec

BUCKET_ID: X64_0xD1_CODE_AV_BAD_IP_nvlddmkm+c27ec

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

__________________________________________________ ______________________

The computer has rebooted from a bugcheck. The bugcheck was: 0x000000d1 (0x00000000000007e3, 0x000000000000000d, 0x0000000000000008, 0x00000000000007e3). A dump was saved in: C:\Windows\MEMORY.DMP.

************************************************** *****************************
* *
* 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: 00000000000007e3, memory referenced
Arg2: 000000000000000d, IRQL
Arg3: 0000000000000008, value 0 = read operation, 1 = write operation
Arg4: 00000000000007e3, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800032be0e0
00000000000007e3

CURRENT_IRQL: d

FAULTING_IP:
+3930653762363664
00000000`000007e3 ?? ???

PROCESS_NAME: System

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0xD1

TRAP_FRAME: fffff880031ab9d0 -- (.trap 0xfffff880031ab9d0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fe765dcdbfb4b800 rbx=0000000000000000 rcx=0000000000000011
rdx=0000000000019f48 rsi=0000000000000000 rdi=0000000000000000
rip=00000000000007e3 rsp=fffff880031abb60 rbp=0000000000000000
r8=000000000001ee45 r9=0000000000000000 r10=00000000000007e3
r11=0000000000000002 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na po nc
00000000`000007e3 ?? ???
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff80003087469 to fffff80003087f00

FAILED_INSTRUCTION_ADDRESS:
+3930653762363664
00000000`000007e3 ?? ???

STACK_TEXT:
fffff880`031ab888 fffff800`03087469 : 00000000`0000000a 00000000`000007e3 00000000`0000000d 00000000`00000008 : nt!KeBugCheckEx
fffff880`031ab890 fffff800`030860e0 : fffffa80`07a38540 00000000`502384bd fffff880`03183180 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`031ab9d0 00000000`000007e3 : 00000000`00000002 fffff880`10b5cb08 1ec70e53`3fd09e29 b3ad41b9`dda3ade5 : nt!KiPageFault+0x260
fffff880`031abb60 00000000`00000002 : fffff880`10b5cb08 1ec70e53`3fd09e29 b3ad41b9`dda3ade5 00000000`00000000 : 0x7e3
fffff880`031abb68 fffff880`10b5cb08 : 1ec70e53`3fd09e29 b3ad41b9`dda3ade5 00000000`00000000 00000000`00000000 : 0x2
fffff880`031abb70 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : USBPORT!USBPORT_TxCsqFindIrp+0x1c


STACK_COMMAND: kb

FOLLOWUP_IP:
USBPORT!USBPORT_TxCsqFindIrp+1c
fffff880`10b5cb08 4183caff or r10d,0FFFFFFFFh

SYMBOL_STACK_INDEX: 5

SYMBOL_NAME: USBPORT!USBPORT_TxCsqFindIrp+1c

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: USBPORT

IMAGE_NAME: USBPORT.SYS

DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bcc07

FAILURE_BUCKET_ID: X64_0xD1_CODE_AV_BAD_IP_USBPORT!USBPORT_TxCsqFindI rp+1c

BUCKET_ID: X64_0xD1_CODE_AV_BAD_IP_USBPORT!USBPORT_TxCsqFindI rp+1c

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

Seems like a driver issue but I cannot pin point where... I have fresh installed my graphics drivers and still, no luck.

It could also be a memory issue. Please try running different sticks (one at a time) until you've either determined which stick (if any) are giving you problems. Are you sure that you matched them correctly?

Since this is a new build have you tried a reinstall? That more than likely isn't the problem however you can eliminate windows by running a live distribution of linux (such as knoppix or ubuntu) from a cd. If you have problems even doing that then that would be indicative of hardware problems.

Take it back! You should not be having BSOD and driver issues on a new computer. Take it back.

It's more hassle than its worth, they just built it together, nothing came pre installed on it etc.

I fresh installed windows 7 on it and the drivers myself.

I updated windows as others were pointing to this maybe being a problem but im still getting the BSOD's now... :/

It's more hassle than its worth, they just built it together, nothing came pre installed on it etc.

That does not matter. This is pointing to a hardware issue. You need to ensure you have the latest Windows 7 drivers for you hardware, including 32 or 64-bit.