Formula IV new build issues

[Unholyskorn86]

Please help.

I just built this system, and am having some issues.

Once in a while when windows loads. It will get to the desktop and the circle windows 7 icon will show up and then everything will freeze. No mouse or keyboard functions.

Also the computer will just die if I go out for the night. When i come back the mouse, keyboard and monitor have no signal to them. (power lights on mouse and keyboard gone, monitor no signal.) I can not wake the computer up. I have to hold power button down for 5 seconds and restart, and it will run fine. This has happened at least 3 or 4 times. But I just built it the other day.

Here is a minidump I happened to find.


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


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

Symbol search path is: SRV*C:\Symbols*
msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02a0c000 PsLoadedModuleList = 0xfffff800`02c49e50
Debug session time: Tue Nov 9 02:34:30.601 2010 (UTC - 5:00)
System Uptime: 0 days 0:16:10.959
Loading Kernel Symbols
...............................................................
................................................................
..............................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {ffffffff90909090, 2, 1, fffff80002a89c7f}

Probably caused by : USBPORT.SYS ( USBPORT!USBPORT_Core_IncIoRequestCount+c3 )

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

5: 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: ffffffff90909090, memory referenced
Arg2: 0000000000000002, 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: fffff80002a89c7f, address which referenced memory

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


WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cb40e0
ffffffff90909090

CURRENT_IRQL: 2

FAULTING_IP:
nt!KeReleaseSpinLock+2f
fffff800`02a89c7f c3 ret

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0xA

PROCESS_NAME: System

TRAP_FRAME: fffff880030af9c0 -- (.trap 0xfffff880030af9c0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=fffffa800468e3a0
rdx=fffffa800468e302 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002a89c7f rsp=fffff880030afb58 rbp=0000000070616ceb
r8=fffffa8004738400 r9=0000000000000000 r10=fffffa800468e100
r11=0000000000000002 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na po cy
nt!KeReleaseSpinLock+0x2f:
fffff800`02a89c7f c3 ret
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff80002a7bca9 to fffff80002a7c740

STACK_TEXT:
fffff880`030af878 fffff800`02a7bca9 : 00000000`0000000a ffffffff`90909090 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`030af880 fffff800`02a7a920 : 00000000`00000000 fffffa80`05b22e20 fffff880`057c4388 fffffa80`04353f20 : nt!KiBugCheckDispatch+0x69
fffff880`030af9c0 fffff800`02a89c7f : 00000000`ffffff02 fffffa80`0468e1a0 fffffa80`0468e1a0 fffffa80`0468e050 : nt!KiPageFault+0x260
fffff880`030afb58 00000000`ffffff02 : fffffa80`0468e1a0 fffffa80`0468e1a0 fffffa80`0468e050 fffff880`05049dd7 : nt!KeReleaseSpinLock+0x2f
fffff880`030afb60 fffffa80`0468e1a0 : fffffa80`0468e1a0 fffffa80`0468e050 fffff880`05049dd7 fffffa80`0468f5f8 : 0xffffff02
fffff880`030afb68 fffffa80`0468e1a0 : fffffa80`0468e050 fffff880`05049dd7 fffffa80`0468f5f8 fffff880`0504554a : 0xfffffa80`0468e1a0
fffff880`030afb70 fffffa80`0468e050 : fffff880`05049dd7 fffffa80`0468f5f8 fffff880`0504554a fffffa80`04738480 : 0xfffffa80`0468e1a0
fffff880`030afb78 fffff880`05049dd7 : fffffa80`0468f5f8 fffff880`0504554a fffffa80`04738480 fffffa80`0468e050 : 0xfffffa80`0468e050
fffff880`030afb80 fffff880`05048378 : fffffa80`0468e050 00000000`00000000 fffffa80`0468ed20 fffffa80`04738480 : USBPORT!USBPORT_Core_IncIoRequestCount+0xc3
fffff880`030afbc0 fffff880`05045e86 : fffffa80`0468e050 fffffa80`0468e050 fffffa80`05af0c20 fffffa80`0468e1a0 : USBPORT!USBPORT_Core_iMapTransfer+0x94
fffff880`030afc40 fffff880`05036f89 : fffffa80`0468e050 00000000`00000000 fffffa80`0468ed02 fffffa80`0468ed20 : USBPORT!USBPORT_Core_UsbMapDpc_Worker+0x296
fffff880`030afca0 fffff800`02a87bfc : fffff880`03087180 fffffa80`0468ed20 fffffa80`0468ed38 00000000`00000000 : USBPORT!USBPORT_Xdpc_Worker+0x1d9
fffff880`030afcd0 fffff800`02a84eea : fffff880`03087180 fffff880`03092040 00000000`00000000 fffff880`05036db0 : nt!KiRetireDpcList+0x1bc
fffff880`030afd80 00000000`00000000 : fffff880`030b0000 fffff880`030aa000 fffff880`030afd40 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND: kb

FOLLOWUP_IP:
USBPORT!USBPORT_Core_IncIoRequestCount+c3
fffff880`05049dd7 418b842408020000 mov eax,dword ptr [r12+208h]

SYMBOL_STACK_INDEX: 8

SYMBOL_NAME: USBPORT!USBPORT_Core_IncIoRequestCount+c3

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: USBPORT

IMAGE_NAME: USBPORT.SYS

DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bcc07

FAILURE_BUCKET_ID: X64_0xA_USBPORT!USBPORT_Core_IncIoRequestCount+c3

BUCKET_ID: X64_0xA_USBPORT!USBPORT_Core_IncIoRequestCount+c3

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

 

[Jonathan King]

That dump points to USBPORT.SYS, the Windows USB driver. Don't bother trying to fix that; it is just an indication of another problem.

Do you have any USB devices attached? Try removing them and see what happens.

Also, we could use some more info. Could you upload a jcgriff2 report for us? Follow the directions here: http://www.jcgriff2.com/BSODpostinstructions.html

Zip up the output folder, and upload it to Rapidshare.

 

[Unholyskorn86]

Issues are...

Ok, I have a WD 2tb external drive USB. Other then that I cannot think of anything else.

These lockups I think might have been coming from my RAM frequencies etc running too high. I know I set it to 2000 because thats what my ram is, Corsair XMS 2000. I got a few game crashes after posting this and was just ticked off so I set everything to automatic. We will see. Still need help tho. Was told AMD only runs my 2000 ram at 1600 max...odd and unfair but it should still be stable I hope...

Could that be why?

I would literally use the PC for hours and it be fine. Then leave and get a call from my wife hours later that the pc is not responding...no keyboard or mouse lights, and the monitor obviously wouldn't come back on.

I have seen it myself too. Just, computer in limbo basically.

Here is the dumbs etc you requested.

Please note now that this was just run with all the settings and voltages ETC at stock....it's even putting the cpu below 3.2...

rapidshare.com/files/430479658/Windows7_Vista_jcgriff2.zip


I ALSO NOTE

The ram when it was run at 2000mhz was giving me 1 error per full pass on Memtest86+...
As soon as I set it all to auto in bios and restarted, tested 2 more passes....0 errors....

 

[Unholyskorn86]

Another DUMP

Here is another dump from today.


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


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

Symbol search path is: SRV*C:\Symbols*
msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02a4f000 PsLoadedModuleList = 0xfffff800`02c8ce50
Debug session time: Fri Nov 12 01:25:02.463 2010 (UTC - 5:00)
System Uptime: 0 days 0:17:23.743
Loading Kernel Symbols
...............................................................
................................................................
...................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffff180cac61750, 0, fffff96000116bc8, 7}


Could not read faulting driver name
Probably caused by : win32k.sys ( win32k!xxxInternalDoSyncPaint+c8 )

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

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

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except,
it must be protected by a Probe. Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: fffff180cac61750, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff96000116bc8, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000007, (reserved)

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


Could not read faulting driver name

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cf70e0
fffff180cac61750

FAULTING_IP:
win32k!xxxInternalDoSyncPaint+c8
fffff960`00116bc8 488b742460 mov rsi,qword ptr [rsp+60h]

MM_INTERNAL_CODE: 7

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0x50

PROCESS_NAME: utorrent.exe

CURRENT_IRQL: 0

TRAP_FRAME: fffff880086d1dc0 -- (.trap 0xfffff880086d1dc0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff900c258f7a0 rbx=0000000000000000 rcx=fffff900c2a6b6e0
rdx=fffff960003b0440 rsi=0000000000000000 rdi=0000000000000000
rip=fffff96000116bc8 rsp=fffff880086d1f50 rbp=fffff900c1a10c30
r8=0000000000000000 r9=0000000000000001 r10=0000000050210000
r11=0000000000020804 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na po nc
win32k!xxxInternalDoSyncPaint+0xc8:
fffff960`00116bc8 488b742460 mov rsi,qword ptr [rsp+60h] ss:0018:fffff880`086d1fb0=0000000000000004
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff80002b3e849 to fffff80002abf740

STACK_TEXT:
fffff880`086d1c58 fffff800`02b3e849 : 00000000`00000050 fffff180`cac61750 00000000`00000000 fffff880`086d1dc0 : nt!KeBugCheckEx
fffff880`086d1c60 fffff800`02abd82e : 00000000`00000000 fffff900`c258f7c8 fffffa80`07c4cb00 fffff960`00194e4a : nt! ?? ::FNODOBFM::`string'+0x40e0b
fffff880`086d1dc0 fffff960`00116bc8 : fffff900`c2a6b700 fffff900`c1a10c30 00000000`00000004 fffff900`c258f7a0 : nt!KiPageFault+0x16e
fffff880`086d1f50 fffff960`00116ba4 : fffff900`c258f7c8 fffff900`c1a10c30 00000000`00000004 00000000`00000004 : win32k!xxxInternalDoSyncPaint+0xc8
fffff880`086d1fa0 fffff960`00116ae5 : fffff900`c0647ca0 00000000`00000000 00000000`00000000 00000000`00000002 : win32k!xxxInternalDoSyncPaint+0xa4
fffff880`086d1ff0 fffff960`001693a9 : fffff960`003b0120 00000000`00000000 00000000`00000001 00000000`00000000 : win32k!xxxDoSyncPaint+0x51
fffff880`086d2020 fffff960`00168fe6 : fffff900`00000001 fffff900`c0648940 00000000`00000002 fffff800`00000000 : win32k!xxxEndDeferWindowPosEx+0x381
fffff880`086d20e0 fffff960`001a746d : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : win32k!xxxSetWindowPos+0x156
fffff880`086d2160 fffff800`02abe993 : fffffa80`092f7b60 fffff880`086d22e0 00000000`0008cb08 fffff880`086d2208 : win32k!NtUserSetWindowPos+0x1e5
fffff880`086d21f0 00000000`74dffe0a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0008cae8 fffff800`02ab7080 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x74dffe0a
fffff880`086d2670 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000202 : nt!KiCallUserMode


STACK_COMMAND: kb

FOLLOWUP_IP:
win32k!xxxInternalDoSyncPaint+c8
fffff960`00116bc8 488b742460 mov rsi,qword ptr [rsp+60h]

SYMBOL_STACK_INDEX: 3

SYMBOL_NAME: win32k!xxxInternalDoSyncPaint+c8

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: win32k

IMAGE_NAME: win32k.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4c7dc13c

FAILURE_BUCKET_ID: X64_0x50_win32k!xxxInternalDoSyncPaint+c8

BUCKET_ID: X64_0x50_win32k!xxxInternalDoSyncPaint+c8

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

 

[Unholyskorn86]

Here is my build info, please let me know if anything doesn't look right.

1 x ASUS VE276Q Black 27" Full HD HDMI Widescreen LCD Monitor w/Display Port & Speakers
1 x CORSAIR XMS 8GB (2 x 4GB) 240-Pin DDR3 SDRAM DDR3 2000 (PC3 16000) Desktop Memory Model CMX8GX3M2A2000C9
1 x ASUS Crosshair IV Formula AM3 AMD 890FX SATA 6Gb/s USB 3.0 ATX AMD Motherboard
1 x Microsoft Explorer Mouse
1 x Link Depot C6M-10-GYB 10 ft. Cat 6 Gray Network Cable
1 x CORSAIR CMPSU-850TX 850W ATX12V 2.2 / EPS12V 2.91 SLI Ready CrossFire Ready Active PFC Power Supply
1 x AMD Phenom II X6 1090T Black Edition Thuban 3.2GHz Socket AM3 125W Six-Core Desktop Processor HDT90ZFBGRBOX
1 x Arctic Silver 5 Thermal Compound - OEM
1 x CyberPower CP1350AVRLCD 1350 VA 810 Watts UPS
1 x Rosewill 6 feet High Speed HDMI Cable with Ethernet Model RC-6-HDMI-HSE-MM-BK
1 x OCZ Vertex 2 OCZSSD3-2VTX120G 3.5" 120GB SATA II MLC Internal Solid State Drive (SSD)
1 x SAPPHIRE DVI to VGA adapter for Twin-View video cards Model DVI-2-VGA - OEM
1 x VisionTek 900338 Radeon HD 6870 1GB 256-bit GDDR5 PCI Express 2.0 x16 HDCP Ready CrossFireX Support Video Card with Eyefinity
1 x AMC 15 ft. Black VGA Male to Female Monitor Extension Cable Model CSV-F15MF - OEM

 

[Jonathan King]

Go ahead and remove that Western Digital drive for now. At least, remove the software that came with it.

wdcsam.sys      Wed Apr 16 04:39:08 2008 (4805BB2C)

Other than that, all I can see from a software side is your old Marvell Yukon and JMicron SATA drivers.

yk62x64.sys     Mon Feb 15 10:46:41 2010 (4B796C61) -- http://extranet.marvell.com/drivers/
jraid.sys       Thu Oct 29 04:14:20 2009 (4AE94EDC) -- ftp://driver.jmicron.com.tw/../../SATA_Controller/Windows/JMB36X_WinDrv_R1.17.59_WHQL.zip

If the BSODs persist, enable driver verifier: http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html

...Summary of the dumps

Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Fri Nov 12 01:25:02.463 2010 (UTC - 5:00)
System Uptime: 0 days 0:17:23.743
Probably caused by : win32k.sys ( win32k!xxxInternalDoSyncPaint+c8 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x50
PROCESS_NAME:  utorrent.exe
FAILURE_BUCKET_ID:  X64_0x50_win32k!xxxInternalDoSyncPaint+c8
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Thu Nov 11 05:37:10.066 2010 (UTC - 5:00)
System Uptime: 0 days 1:31:42.346
Probably caused by : Ntfs.sys ( Ntfs!NtfsAcquireFcbWithPaging+12d )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
BUGCHECK_STR:  0x24
FAILURE_BUCKET_ID:  X64_0x24_Ntfs!NtfsAcquireFcbWithPaging+12d
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Tue Nov  9 02:34:30.601 2010 (UTC - 5:00)
System Uptime: 0 days 0:16:10.959
Probably caused by : USBPORT.SYS ( USBPORT!USBPORT_Core_IncIoRequestCount+c3 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xA_USBPORT!USBPORT_Core_IncIoRequestCount+c3
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

 

[Unholyskorn86]

So do you think this is software/driver related? Hardware that I have to RMA? Or ??

This is my first advanced system, upgraded from a simple P4 so I am new to some aspects of this.

Also I went and updated my drivers on both those links you posted. I think I did it correctly.

 

[Unholyskorn86]

OK I set it to lower on the ram and it hasn't skipped a beat in two days. Thanks. DDR3 2000 on a amd is a lie. Thanks corsair.....