A bunch of Issues

Hi there!

I'm new here and was just wondering if the kind people here could help me out. i have recently just purchased a new computer, i bought the parts and put it together myself. I have put windows 7 professional OEM on it.

Everything seemed fine. I installed everything etc. I then downloaded a dodgy torrent, which i cleaned up and got rid of the viruses. The computer was working fine, i came back after a holidya, put in a new sound card, installed the drivers and whatnot and figured out that software as well as some programs (ie 32 bit, firefox) wouldnt open, although it said they were running under task manager > processes. I looked everywhere, ran all the malware stuff here (which is when i got rid of the viruses). basically that didnt help.

i ended up doing a clean install of windows 7 pro oem. I downloaded everything from scratch again, and ive just gotten everything i needed downloaded again, but i have just suffered a BSOD.

i think the previous issues were rectified by the clean install, but i was wondering if someone could tell me how to upload the minidump and tell me why it just BSOD.

i believe this shouldnt be happening with a brand new pc and i am concered for it

Thanks,

Wip

 

Hi Wip

First you have to make sure W7 is set for saving minidumps. If it is already, then the C:\Windows\Minidump folder should hold a *.dmp, copy it to your Desktop then zip it, attach the resulting zip file to your post. If you had to set it to save minidumps, you'll need to wait until after you get the next BSOD.

 

No worries, here we go

 

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 24, {1904fb, fffff8800aea42b8, fffff8800aea3b20, fffff88001050366}

Unable to load image \SystemRoot\system32\DRIVERS\AVGIDSFilter.Sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for AVGIDSFilter.Sys
*** ERROR: Module load completed but symbols could not be loaded for AVGIDSFilter.Sys
Probably caused by : Ntfs.sys ( Ntfs!NtfsExtendedCompleteRequestInternal+114 )

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

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

NTFS_FILE_SYSTEM (24)
    If you see NtfsExceptionFilter on the stack then the 2nd and 3rd
    parameters are the exception record and context record. Do a .cxr
    on the 3rd parameter and then kb to obtain a more informative stack
    trace.
Arguments:
Arg1: 00000000001904fb
Arg2: fffff8800aea42b8
Arg3: fffff8800aea3b20
Arg4: fffff88001050366

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


EXCEPTION_RECORD:  fffff8800aea42b8 -- (.exr 0xfffff8800aea42b8)
ExceptionAddress: fffff88001050366 (fltmgr!TreeUnlinkNoBalance+0x0000000000000006)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

CONTEXT:  fffff8800aea3b20 -- (.cxr 0xfffff8800aea3b20)
rax=fffffa800a9cbb60 rbx=4000000000000000 rcx=4000000000000000
rdx=ffffffffffffffff rsi=fffffa800736a850 rdi=0000000000000000
rip=fffff88001050366 rsp=fffff8800aea44f0 rbp=fffffa800736a858
 r8=ffffffffffffffff  r9=ffffffffffffffff r10=fffff80002a49000
r11=00000000000004b6 r12=ffffffffffffffff r13=fffffa8009373e90
r14=0000000000002000 r15=0000000000000001
iopl=0         nv up ei ng nz na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010286
fltmgr!TreeUnlinkNoBalance+0x6:
fffff880`01050366 488b5118        mov     rdx,qword ptr [rcx+18h] ds:002b:40000000`00000018=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  chrome.exe

CURRENT_IRQL:  0

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

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

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  ffffffffffffffff

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cf10e0
 ffffffffffffffff 

FOLLOWUP_IP: 
Ntfs!NtfsExtendedCompleteRequestInternal+114
fffff880`01237cb4 488b5c2450      mov     rbx,qword ptr [rsp+50h]

FAULTING_IP: 
fltmgr!TreeUnlinkNoBalance+6
fffff880`01050366 488b5118        mov     rdx,qword ptr [rcx+18h]

BUGCHECK_STR:  0x24

LAST_CONTROL_TRANSFER:  from fffff8800104c238 to fffff88001050366

STACK_TEXT:  
fffff880`0aea44f0 fffff880`0104c238 : fffff8a0`043c7750 00000000`00000000 00000000`00000001 00000000`00004000 : fltmgr!TreeUnlinkNoBalance+0x6
fffff880`0aea4520 fffff880`0106a46f : ffffffff`ffffffff fffffa80`09373800 00000000`6e664d46 fffff880`0106ade0 : fltmgr!TreeUnlinkMulti+0x148
fffff880`0aea4570 fffff880`0106ae34 : ffffffff`ffffffff fffffa80`06fda820 fffffa80`09373800 fffffa80`0736a7d0 : fltmgr!DeleteNameCacheNodes+0x9f
fffff880`0aea45b0 fffff880`0107a2af : fffffa80`06fda820 fffffa80`0736a7d0 00000000`00000000 00000000`00000000 : fltmgr!PurgeStreamNameCache+0xc4
fffff880`0aea45f0 fffff880`01071a30 : fffffa80`07138700 fffffa80`09373800 00000000`00000000 fffffa80`072e8960 : fltmgr!FltpPurgeVolumeNameCache+0x7f
fffff880`0aea4630 fffff880`0106ad4b : fffffa80`09373800 00000000`00000000 fffffa80`06ffc660 00000000`00000000 : fltmgr! ?? ::NNGAKEGL::`string'+0x1a04
fffff880`0aea4670 fffff880`0104d06a : fffffa80`073e4b60 fffffa80`07cf9870 00740073`0069004c 006e006f`00630049 : fltmgr!FltpReinstateNameCachingAllFrames+0x4b
fffff880`0aea46a0 fffff800`02abbd26 : fffff880`0ae9c000 fffff880`0104c0a2 fffffa80`073e4c10 00000000`00000000 : fltmgr!FltpPassThroughCompletion+0x8a
fffff880`0aea46e0 fffff880`01237cb4 : fffffa80`09058dc0 00000000`00000001 00000000`00000000 00000000`00000000 : nt!IopfCompleteRequest+0x3a6
fffff880`0aea47c0 fffff880`012beeda : fffff8a0`0eaf8bc0 fffffa80`07bba180 00000000`00000000 00000000`00000701 : Ntfs!NtfsExtendedCompleteRequestInternal+0x114
fffff880`0aea4800 fffff880`01230ba0 : fffffa80`09058dc0 fffffa80`072e85c0 fffff880`0aea4901 fffff880`0aea4900 : Ntfs!NtfsCommonSetInformation+0xef1
fffff880`0aea48e0 fffff880`0104a23f : fffffa80`072e89a8 fffffa80`072e85c0 fffffa80`09058dc0 fffff880`0aea4908 : Ntfs!NtfsFsdSetInformation+0x11c
fffff880`0aea4960 fffff880`010486df : fffffa80`07cf9870 fffffa80`0a870820 fffffa80`07cf9800 fffffa80`072e85c0 : fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x24f
fffff880`0aea49f0 fffff880`054745b4 : fffffa80`072e85c0 fffffa80`0a870820 fffffa80`06ffc660 00000000`0000000a : fltmgr!FltpDispatch+0xcf
fffff880`0aea4a50 fffffa80`072e85c0 : fffffa80`0a870820 fffffa80`06ffc660 00000000`0000000a fffffa80`06ffc660 : AVGIDSFilter+0x35b4
fffff880`0aea4a58 fffffa80`0a870820 : fffffa80`06ffc660 00000000`0000000a fffffa80`06ffc660 fffffa80`071d1d20 : 0xfffffa80`072e85c0
fffff880`0aea4a60 fffffa80`06ffc660 : 00000000`0000000a fffffa80`06ffc660 fffffa80`071d1d20 00000000`00000000 : 0xfffffa80`0a870820
fffff880`0aea4a68 00000000`0000000a : fffffa80`06ffc660 fffffa80`071d1d20 00000000`00000000 fffff800`02d9a31d : 0xfffffa80`06ffc660
fffff880`0aea4a70 fffffa80`06ffc660 : fffffa80`071d1d20 00000000`00000000 fffff800`02d9a31d 00000000`000000b6 : 0xa
fffff880`0aea4a78 fffffa80`071d1d20 : 00000000`00000000 fffff800`02d9a31d 00000000`000000b6 fffffa80`072e85c0 : 0xfffffa80`06ffc660
fffff880`0aea4a80 00000000`00000000 : fffff800`02d9a31d 00000000`000000b6 fffffa80`072e85c0 00000000`00000000 : 0xfffffa80`071d1d20


SYMBOL_STACK_INDEX:  9

SYMBOL_NAME:  Ntfs!NtfsExtendedCompleteRequestInternal+114

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: Ntfs

IMAGE_NAME:  Ntfs.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4d79996d

STACK_COMMAND:  .cxr 0xfffff8800aea3b20 ; kb

FAILURE_BUCKET_ID:  X64_0x24_Ntfs!NtfsExtendedCompleteRequestInternal+114

BUCKET_ID:  X64_0x24_Ntfs!NtfsExtendedCompleteRequestInternal+114

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

Your loaded drivers all look pretty much up to date but there's a touch of suspicion regarding the AVG file:

I'd run chkdsk /f /r then a SFC/scannow and check the resulting onscreen messages and logs before deciding whether to remove AVG. You can also check the hard drive with the makers diagnostics. Disk/file corruption can also be from a bad or loose cable, check that all connections are tight and replace any that you suspect.

 

Oh sorry for my nubness but how do i do those checks you mentioned?

 

To run Chkdsk, try the Windows method first, right-click the hard drive you want to check in Explorer and choose Properties > Tools > Error checking Check now > check both boxes and click Start > you must allow Windows to reboot for this to work as it can't check files that are loaded. See attachment.

To run SFC, see Caliban's tutorial.

 

i will be running those test tonight, i didnt realise how long they took, so i had to cancel it after a few minutes of trying a dskchk.

also another bluescreen minidump is attached below (another BSOD happened)

I will post the results of the dskchk/sfc scan

 

Another Blue screen, so maybe not caused by avg, which i uninstalled.

3rd bluescreen minidump is attached below. can anyone tell me what the second one was all about aswell?

 

Most recent dump is a 0x1A MEMORY_MANAGEMENT, the earlier one is a 0x50 PAGE_FAULT_IN_NONPAGED_AREA, Invalid system memory was referenced.

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {41287, 58000000000, 0, 0}

[B]Probably caused by : hardware[/B] ( nt! ?? ::FNODOBFM::`string'+46585 )

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

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

MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000041287, The subtype of the bugcheck.
Arg2: 0000058000000000
Arg3: 0000000000000000
Arg4: 0000000000000000

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


BUGCHECK_STR:  0x1a_41287

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  vegas100.exe

CURRENT_IRQL:  0

TRAP_FRAME:  fffff8800aa69920 -- (.trap 0xfffff8800aa69920)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000058000000000 rbx=0000000000000000 rcx=fffffa8002209350
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002a9eee1 rsp=fffff8800aa69ab8 rbp=fffff8800aa69b40
 r8=0000000000000000  r9=0000098000000000 r10=0000000000000000
r11=fffff8800aa69c20 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
nt!MmAccessFault+0x2d1:
fffff800`02a9eee1 3006            xor     byte ptr [rsi],al ds:109c:00000000`00000000=??
Resetting default scope

MISALIGNED_IP: 
nt!MmAccessFault+2d1
fffff800`02a9eee1 3006            xor     byte ptr [rsi],al

LAST_CONTROL_TRANSFER:  from fffff80002a24dce to fffff80002a91d00

STACK_TEXT:  
fffff880`0aa697b8 fffff800`02a24dce : 00000000`0000001a 00000000`00041287 00000580`00000000 00000000`00000000 : nt!KeBugCheckEx
fffff880`0aa697c0 fffff800`02a8fe2e : 00000000`00000001 00000580`00000000 fffff880`0aa69b00 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x46585
fffff880`0aa69920 fffff800`02a9eee1 : 00000000`00000053 00000000`00000000 00000000`00000000 fffff700`01080000 : nt!KiPageFault+0x16e
fffff880`0aa69ab8 fffff880`0aa69ca0 : fffff800`02a8fe2e 00000000`00000001 00000000`85239ff8 00000000`00000001 : nt!MmAccessFault+0x2d1
fffff880`0aa69c18 fffff800`02a8fe2e : 00000000`00000001 00000000`85239ff8 00000000`00000001 00000000`091a4868 : 0xfffff880`0aa69ca0
fffff880`0aa69c20 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+46585
fffff800`02a24dce cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+46585

FOLLOWUP_NAME:  MachineOwner

[B]IMAGE_NAME:  hardware[/B]

DEBUG_FLR_IMAGE_TIMESTAMP:  0

[B]MODULE_NAME: hardware[/B]

FAILURE_BUCKET_ID:  X64_IP_MISALIGNED

BUCKET_ID:  X64_IP_MISALIGNED

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

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {ffffffffffffffff, 1, fffff80002aac9e6, 0}


Could not read faulting driver name
[B]Probably caused by : hardware[/B] ( nt! ?? ::FNODOBFM::`string'+4621f )

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

5: 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: ffffffffffffffff, memory referenced.
Arg2: 0000000000000001, value 0 = read operation, 1 = write operation.
Arg3: fffff80002aac9e6, If non-zero, the instruction address which referenced the bad memory
	address.
Arg4: 0000000000000000, (reserved)

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


Could not read faulting driver name

WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cd00e8
 ffffffffffffffff 

FAULTING_IP: 
nt!MmAccessFault+3c6
fffff800`02aac9e6 100f            adc     byte ptr [rdi],cl

MM_INTERNAL_CODE:  0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x50

[B]PROCESS_NAME:  avgchsva.exe[/B]

CURRENT_IRQL:  0

TRAP_FRAME:  fffff880047cf930 -- (.trap 0xfffff880047cf930)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffa8009a51b30 rbx=0000000000000000 rcx=00000000000012b5
rdx=0000000008418000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002aac9e6 rsp=fffff880047cfac0 rbp=fffff880047cfb40
 r8=fffffa8009007ca8  r9=fffffa800378a440 r10=0000000000000001
r11=fffff70001080488 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na po nc
nt!MmAccessFault+0x3c6:
fffff800`02aac9e6 100f            adc     byte ptr [rdi],cl ds:00000000`00000000=??
Resetting default scope

MISALIGNED_IP: 
nt!MmAccessFault+3c6
fffff800`02aac9e6 100f            adc     byte ptr [rdi],cl

LAST_CONTROL_TRANSFER:  from fffff80002a4b2ac to fffff80002a9f640

STACK_TEXT:  
fffff880`047cf7c8 fffff800`02a4b2ac : 00000000`00000050 ffffffff`ffffffff 00000000`00000001 fffff880`047cf930 : nt!KeBugCheckEx
fffff880`047cf7d0 fffff800`02a9d76e : 00000000`00000001 ffffffff`ffffffff ab500001`2836c800 fffff680`000420c0 : nt! ?? ::FNODOBFM::`string'+0x4621f
fffff880`047cf930 fffff800`02aac9e6 : fffff880`00000073 ff800000`00ffffff fffff6fb`7da00000 00000000`00000000 : nt!KiPageFault+0x16e
fffff880`047cfac0 fffff800`02a9d76e : 00000000`00000001 00000000`08418038 00000000`00000301 00000000`08418038 : nt!MmAccessFault+0x3c6
fffff880`047cfc20 000007fe`ff8acfb5 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e
00000000`0941f218 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7fe`ff8acfb5


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+4621f
fffff800`02a4b2ac cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+4621f

FOLLOWUP_NAME:  MachineOwner

[B]IMAGE_NAME:  hardware[/B]

DEBUG_FLR_IMAGE_TIMESTAMP:  0

[B]MODULE_NAME: hardware[/B]

FAILURE_BUCKET_ID:  X64_IP_MISALIGNED

BUCKET_ID:  X64_IP_MISALIGNED

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

Check the BIOS settings for your RAM are correct against the data supplied by the manufacturers website and the website of the motherboard you're using. Make sure the RAM is inserted correctly, has clean contacts and the slots are clean.

Check for memory errors with Memtest86+, there's a tutorial here, Caliban has a tutorial on creating CD's from ISO's here if you need it.

 

Ok a 4th bluescreen added here.

Thanks for your help so far.

Are all the blue-screens related to memory issues? (including this one?)

i have 8gb of ram, but the exact type of ram that i got it not specifically listed in the motherboard's manafacturers site... so i have a feeling the ram isnt quite fully certified as being tested to run with this motherboard. so is the ram causing all these problems?

 

will the memtest86 work for my 64 bit version of windows? the 86 has me thinking this is for 32 bit OS

 

It's unfortunate that they named it the way they did. Not to worry, memtest86+ doesn't run under windows at all. It's got it's own little environment to run in.

 

MemTest is NOT testing windows. It runs before windows is loaded so it has nothing to do with the OS you are running (software). This program is testing hardware.
http://www.memtest.org/
Read the history section.

 

also do i just run this test or do i do the thing where i remove all ram and only plug one in at a time and run it? i have 4 x 2GB sticks...

 

You just run the test. If an error comes up, then you start testing the memory modules individually.

 

Ran a memtest, after 7 passes, no errors.

This seems to be a doozy of a case

Im still concerned as the specific type of memory i have isnt listen on the motherboards webiste in the list of compatible memory... but its working fine

anyway 4 bluescreens happened pretty quickly in succession (all seem to be different errors)

I have attached these.

Thanks for your continued help with my tempremental computer!

 

The BSOD's seem to be of a random nature, this would normally lead me to thinking that RAM or possibly a weak PSU are to blame.

Code:

STOP 0x0000000A: IRQL_NOT_LESS_OR_EQUAL
Usual causes:  [B]Kernel mode driver, System Service, BIOS, Windows, Virus scanner, Backup tool, compatibility[/B]

STOP 0x0000003B: SYSTEM_SERVICE_EXCEPTION
Usual causes:  [B]System service, Device driver, graphics driver, ?memory[/B]

STOP 0x00000109: CRITICAL_STRUCTURE_CORRUPTION
Usual causes:  [B]Device driver, Breakpoint set with no debugger attached, Hardware (Memory in particular)[/B]


*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff880048b829f, fffff88003d5edf0, 0}

Probably caused by : atikmdag.sys ( atikmdag+2c29f )

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: fffff880048b829f, Address of the instruction which caused the bugcheck
Arg3: fffff88003d5edf0, 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: 
atikmdag+2c29f
fffff880`048b829f cac348          retf    48C3h

CONTEXT:  fffff88003d5edf0 -- (.cxr 0xfffff88003d5edf0)
rax=fffff88004d0f500 rbx=fffffa8008c0f300 rcx=0000000000000000
rdx=0000000000000000 rsi=fffff88003d5f950 rdi=fffffa8009388a90
rip=fffff880048b829f rsp=fffff88003d5f7d0 rbp=fffffa8007d50180
 r8=fffff88003d5f810  r9=0000000000000000 r10=0000000000000001
r11=fffffa80094a8000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010246
atikmdag+0x2c29f:
fffff880`048b829f cac348          retf    48C3h
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x3B

PROCESS_NAME:  LogonUI.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff880048b829f

STACK_TEXT:  
fffff880`03d5f7d0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : atikmdag+0x2c29f


FOLLOWUP_IP: 
atikmdag+2c29f
fffff880`048b829f cac348          retf    48C3h

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  atikmdag+2c29f

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: atikmdag

IMAGE_NAME:  atikmdag.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4dae3c99

STACK_COMMAND:  .cxr 0xfffff88003d5edf0 ; kb

FAILURE_BUCKET_ID:  X64_0x3B_atikmdag+2c29f

BUCKET_ID:  X64_0x3B_atikmdag+2c29f

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

0: kd> lmvm atikmdag
start             end                 module name
fffff880`0488c000 fffff880`051c0000   atikmdag T (no symbols)           
    Loaded symbol image file: atikmdag.sys
    Image path: \SystemRoot\system32\DRIVERS\atikmdag.sys
    Image name: atikmdag.sys
    Timestamp:        Wed Apr 20 02:53:29 2011 (4DAE3C99)
    CheckSum:         008E91DD
    ImageSize:        00934000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4



*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {8, 2, 0, fffff80002ffd33e}

Probably caused by : USBPORT.SYS ( USBPORT!USBPORT_Core_iCompleteDoneTransfer+45f )

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: 0000000000000008, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, 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: fffff80002ffd33e, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cc1100
 0000000000000008 

CURRENT_IRQL:  2

FAULTING_IP: 
hal!HalpDmaFreeMapRegisters+1a
fffff800`02ffd33e 488b5a08        mov     rbx,qword ptr [rdx+8]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  System

TRAP_FRAME:  fffff880030b0890 -- (.trap 0xfffff880030b0890)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff880030b09c0 rbx=0000000000000000 rcx=fffffa8008abdac8
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002ffd33e rsp=fffff880030b0a20 rbp=0000000000000400
 r8=fffff880030b09c0  r9=fffff80003027c60 r10=003c003e00330027
r11=0000000000000002 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na pe nc
hal!HalpDmaFreeMapRegisters+0x1a:
fffff800`02ffd33e 488b5a08        mov     rbx,qword ptr [rdx+8] ds:00000000`00000008=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002a912a9 to fffff80002a91d00

STACK_TEXT:  
fffff880`030b0748 fffff800`02a912a9 : 00000000`0000000a 00000000`00000008 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`030b0750 fffff800`02a8ff20 : fffffa80`08839050 fffff880`0517c9b9 00000000`00000008 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`030b0890 fffff800`02ffd33e : 00000000`000003e8 fffff800`02ffd69a fffffa80`08abda50 fffffa80`09909400 : nt!KiPageFault+0x260
fffff880`030b0a20 fffff800`02fffb82 : fffffa80`08abda50 00000000`00000000 fffffa80`08abda50 00000000`00000000 : hal!HalpDmaFreeMapRegisters+0x1a
fffff880`030b0a50 fffff800`02fff825 : fffffa80`07ce4170 00000000`00000498 00000000`00000000 fffffa80`06e033c0 : hal!IoFreeMapRegisters+0x62
fffff880`030b0ac0 fffff880`0518007b : fffffa80`088441a0 fffffa80`0737ed30 fffffa80`08844050 fffffa80`088441a0 : hal!HalPutScatterGatherList+0xd5
fffff880`030b0b20 fffff880`05180b0f : fffffa80`0737e902 fffffa80`075eb930 00000000`ffffffff fffffa80`08844eb0 : USBPORT!USBPORT_Core_iCompleteDoneTransfer+0x45f
fffff880`030b0c00 fffff880`0517e66f : fffffa80`08844eb0 fffffa80`088441a0 fffffa80`08845050 00000000`00000000 : USBPORT!USBPORT_Core_iIrpCsqCompleteDoneTransfer+0x3a7
fffff880`030b0c60 fffff880`0516ff89 : fffffa80`08844050 00000000`00000000 fffffa80`08844e02 fffffa80`08844eb0 : USBPORT!USBPORT_Core_UsbIocDpc_Worker+0xf3
fffff880`030b0ca0 fffff800`02a9d10c : fffff880`03088180 fffffa80`08844eb0 fffffa80`08844ec8 00000000`00000000 : USBPORT!USBPORT_Xdpc_Worker+0x1d9
fffff880`030b0cd0 fffff800`02a89a2a : fffff880`03088180 fffff880`03093040 00000000`00000000 fffff880`0516fdb0 : nt!KiRetireDpcList+0x1bc
fffff880`030b0d80 00000000`00000000 : fffff880`030b1000 fffff880`030ab000 fffff880`030b0d40 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
USBPORT!USBPORT_Core_iCompleteDoneTransfer+45f
fffff880`0518007b 4533c0          xor     r8d,r8d

SYMBOL_STACK_INDEX:  6

SYMBOL_NAME:  USBPORT!USBPORT_Core_iCompleteDoneTransfer+45f

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: USBPORT

IMAGE_NAME:  USBPORT.SYS

DEBUG_FLR_IMAGE_TIMESTAMP:  4d8c0c08

FAILURE_BUCKET_ID:  X64_0xA_USBPORT!USBPORT_Core_iCompleteDoneTransfer+45f

BUCKET_ID:  X64_0xA_USBPORT!USBPORT_Core_iCompleteDoneTransfer+45f

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

5: kd> lmvm USBPORT
start             end                 module name
fffff880`0516d000 fffff880`051c3000   USBPORT    (pdb symbols)          c:\symbols\usbport.pdb\47451B86B21D42BDADD411F6892B8A0D1\usbport.pdb
    Loaded symbol image file: USBPORT.SYS
    Mapped memory image file: c:\symbols\USBPORT.SYS\4D8C0C0856000\USBPORT.SYS
    Image path: \SystemRoot\system32\DRIVERS\USBPORT.SYS
    Image name: USBPORT.SYS
    Timestamp:        Fri Mar 25 03:29:12 2011 (4D8C0C08)
    CheckSum:         00056970
    ImageSize:        00056000
    File version:     6.1.7601.17586
    Product version:  6.1.7601.17586
    File flags:       0 (Mask 3F)
    File OS:          40004 NT Win32
    File type:        2.0 Dll
    File date:        00000000.00000000
    Translations:     0409.04b0
    CompanyName:      Microsoft Corporation
    ProductName:      Microsoft® Windows® Operating System
    InternalName:     usbport.sys
    OriginalFilename: usbport.sys
    ProductVersion:   6.1.7601.17586
    FileVersion:      6.1.7601.17586 (win7sp1_gdr.110324-1501)
    FileDescription:  USB 1.1 & 2.0 Port Driver
    LegalCopyright:   © Microsoft Corporation. All rights reserved.






*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 109, {a3a039d898e6c66b, 0, b1d38fa4cac417e2, 101}

Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )

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

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

CRITICAL_STRUCTURE_CORRUPTION (109)
This bugcheck is generated when the kernel detects that critical kernel code or
data have been corrupted. There are generally three causes for a corruption:
1) A driver has inadvertently or deliberately modified critical kernel code
 or data. See http://www.microsoft.com/whdc/driver/kernel/64bitPatching.mspx
2) A developer attempted to set a normal kernel breakpoint using a kernel
 debugger that was not attached when the system was booted. Normal breakpoints,
 "bp", can only be set if the debugger is attached at boot time. Hardware
 breakpoints, "ba", can be set at any time.
3) A hardware corruption occurred, e.g. failing RAM holding kernel code or data.
Arguments:
Arg1: a3a039d898e6c66b, Reserved
Arg2: 0000000000000000, Reserved
Arg3: b1d38fa4cac417e2, Failure type dependent information
Arg4: 0000000000000101, Type of corrupted region, can be
	0 : A generic data region
	1 : Modification of a function or .pdata
	2 : A processor IDT
	3 : A processor GDT
	4 : Type 1 process list corruption
	5 : Type 2 process list corruption
	6 : Debug routine modification
	7 : Critical MSR modification

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


BUGCHECK_STR:  0x109

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff80002ae1d00

STACK_TEXT:  
fffff880`031685d8 00000000`00000000 : 00000000`00000109 a3a039d8`98e6c66b 00000000`00000000 b1d38fa4`cac417e2 : nt!KeBugCheckEx


STACK_COMMAND:  kb

SYMBOL_NAME:  ANALYSIS_INCONCLUSIVE

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: Unknown_Module

IMAGE_NAME:  Unknown_Image

DEBUG_FLR_IMAGE_TIMESTAMP:  0

BUCKET_ID:  BAD_STACK

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

2: kd> lmvm Unknown_Module
start             end                 module name




*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {1b, 2, 0, fffff80002ad5d52}

Probably caused by : ntkrnlmp.exe ( nt!KiDeferredReadyThread+32 )

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: 000000000000001b, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, 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: fffff80002ad5d52, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cff100
 000000000000001b 

CURRENT_IRQL:  2

FAULTING_IP: 
nt!KiDeferredReadyThread+32
fffff800`02ad5d52 4c8b6918        mov     r13,qword ptr [rcx+18h]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  vegas100.exe

TRAP_FRAME:  fffff880075a5940 -- (.trap 0xfffff880075a5940)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ffffc0b3891b269d rbx=0000000000000000 rcx=0000000000000003
rdx=fffffa800a27ec68 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002ad5d52 rsp=fffff880075a5ad0 rbp=0000000000000000
 r8=fffffa800a27eb60  r9=fffffa800970ab70 r10=fffff80002a50000
r11=00000000001f0003 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe nc
nt!KiDeferredReadyThread+0x32:
fffff800`02ad5d52 4c8b6918        mov     r13,qword ptr [rcx+18h] ds:f168:00000000`0000001b=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002acf2a9 to fffff80002acfd00

STACK_TEXT:  
fffff880`075a57f8 fffff800`02acf2a9 : 00000000`0000000a 00000000`0000001b 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`075a5800 fffff800`02acdf20 : 00000000`00004000 fffffa80`09a7f060 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`075a5940 fffff800`02ad5d52 : fffff880`009e9180 fffffa80`0a4d2720 00000000`00000000 fffffa80`09a7f060 : nt!KiPageFault+0x260
fffff880`075a5ad0 fffff800`02ad3d90 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000001 : nt!KiDeferredReadyThread+0x32
fffff880`075a5b50 fffff800`02db8210 : fffff880`00000000 00000000`00000001 fffffa80`06c9f900 fffffa80`0a27ec68 : nt!KeSetEvent+0x190
fffff880`075a5bc0 fffff800`02acef93 : fffffa80`09a7f060 00000000`00002710 fffff880`00000000 fffffa80`0957ae10 : nt!NtSetEvent+0x90
fffff880`075a5c20 00000000`77bb13fa : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0b7df588 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77bb13fa


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!KiDeferredReadyThread+32
fffff800`02ad5d52 4c8b6918        mov     r13,qword ptr [rcx+18h]

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  nt!KiDeferredReadyThread+32

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4d9fdd5b

FAILURE_BUCKET_ID:  X64_0xA_nt!KiDeferredReadyThread+32

BUCKET_ID:  X64_0xA_nt!KiDeferredReadyThread+32

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

5: kd> lmvm nt
start             end                 module name
fffff800`02a50000 fffff800`03039000   nt         (pdb symbols)          c:\symbols\ntkrnlmp.pdb\962458112DE04DEBBFB6761B710924452\ntkrnlmp.pdb
    Loaded symbol image file: ntkrnlmp.exe
    Mapped memory image file: c:\symbols\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
    Image path: ntkrnlmp.exe
    Image name: ntkrnlmp.exe
    Timestamp:        Sat Apr 09 05:15:23 2011 (4D9FDD5B)
    CheckSum:         0054E319
    ImageSize:        005E9000
    File version:     6.1.7601.17592
    Product version:  6.1.7601.17592
    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.1.7601.17592
    FileVersion:      6.1.7601.17592 (win7sp1_gdr.110408-1631)
    FileDescription:  NT Kernel & System
    LegalCopyright:   © Microsoft Corporation. All rights reserved.

Are you using the latest BIOS for the motherboard? If you gave the full details of all the hardware, it could help us think this through and be on the lookout for any potential compatibility issues.

I think the best you can do for the next few days/week, is to remove some hardware; start by removing 2x sticks of RAM and uninstall and remove the Xonar card, if you have (or can borrow) a known good graphics card, you could try that too. If you uninstall and remove your CD/DVD drives and don't connect any USB device that doesn't have it's own power supply, it should stress the PSU less.

Then use the PC as normal, if there are any further crashes, please let us know what the PC was doing at the time and upload any further minidumps.

 

Alright.

The PSU is a 750W (tp-750)
8 GB of geil ram (4 x 2gb)
M4A87TD/USB3 mobo
phenom II x6 3.2ghz processor 1090T black edition i think
xfx radeon 6950 1gb graphics
asus xonar essence stx
have a logitech g500 via usb
and a microsoft x4 keyboard via usb
asus 21.5 inch monitor

 

as for the latest bios, i dont think so. (how do i upgrade and should i upgrade?)

The specific type of ram, although the mobo supports some geil, this specific one wasnt on the list the website gave me (possible problem?)

and i also notice like the computer making struggle noises but i think these are normal.... any way of stopping those noises or finding out if they are normal?

additionally i also have a usb mic from logitech so another usb thingy.

is 750w enough? also got a 1TB western digital HD i think along with some generic non special asus cd drive thing.

 

I'm seeing others making comments on RAM incompatibilities with this 'board; checking the ASUS QVL list, I see that there are very few recommended sets of 4x sticks for it, in fact, there are many more compatible sets of 3x sticks listed! This makes me think that trying to get 4x non-QVL sticks running is going to be pretty difficult, if not impossible.

You could try manually setting the RAM timings but I'd pull 1 or 2 sticks and test that for a few days.

 

Just as i expected. Ill look into compatible ram and possibly replace it too.

Another BSOD

 

another one straight after lol

Also would it be better to find a better mobo that supports this ram and processor instead of finding new ram?

 

a third in 30 mins lol. sorry.

 

another BSOD, even after removing 4gb of ram to be left with 4... (in proper slots (1 and 3)

not sure if its related to ram

but should i get new ram/mobo or what? (maybe not caused by the ram?)

 

The last dump was caused by Hardware (USB?), according to Windbg:

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {8a93a, 2, 1, fffff88004811f5b}

Probably caused by : hardware ( USBPORT!USBPORT_Core_UsbHcIntDpc_Worker+a7 )

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

5: 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: 000000000008a93a, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, value 0 = read operation, 1 = write operation
Arg4: fffff88004811f5b, address which referenced memory

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


WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002d09100
 000000000008a93a 

CURRENT_IRQL:  2

FAULTING_IP: 
USBPORT!USBPORT_Core_UsbHcIntDpc_Worker+a7
fffff880`04811f5b 4a204103        and     byte ptr [rcx+3],al

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xD1

PROCESS_NAME:  System

TRAP_FRAME:  fffff880030afaa0 -- (.trap 0xfffff880030afaa0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=00000000ffffffff rbx=0000000000000000 rcx=000000000008a937
rdx=fffffa80057051a0 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88004811f5b rsp=fffff880030afc38 rbp=fffffa80057051a0
 r8=fffffa80057051a0  r9=fffff8800746b080 r10=00000000ffffffff
r11=fffffa80057051a0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         ov up ei ng nz na po nc
USBPORT!USBPORT_Core_UsbHcIntDpc_Worker+0xa7:
fffff880`04811f5b 4a204103        and     byte ptr [rcx+3],al ds:00000000`0008a93a=??
Resetting default scope

MISALIGNED_IP: 
USBPORT!USBPORT_Core_UsbHcIntDpc_Worker+a7
fffff880`04811f5b 4a204103        and     byte ptr [rcx+3],al

LAST_CONTROL_TRANSFER:  from fffff80002ad92a9 to fffff80002ad9d00

STACK_TEXT:  
fffff880`030af958 fffff800`02ad92a9 : 00000000`0000000a 00000000`0008a93a 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`030af960 fffff800`02ad7f20 : 00000000`00000000 fffff800`02ad5947 fffffa80`059caf08 fffffa80`05705050 : nt!KiBugCheckDispatch+0x69
fffff880`030afaa0 fffff880`04811f5b : 00000000`0ff0c78a fffffa80`05705050 fffffa80`075b5010 fffffa80`075b8c20 : nt!KiPageFault+0x260
fffff880`030afc38 fffffa80`05705a18 : fffff880`04802f89 fffffa80`05705050 00000000`00000000 fffffa80`05705a02 : USBPORT!USBPORT_Core_UsbHcIntDpc_Worker+0xa7
fffff880`030afc98 fffff880`04802f89 : fffffa80`05705050 00000000`00000000 fffffa80`05705a02 fffffa80`05705a18 : 0xfffffa80`05705a18
fffff880`030afca0 fffff800`02ae510c : fffff880`03087180 fffffa80`05705a18 fffffa80`05705a30 00000000`00000000 : USBPORT!USBPORT_Xdpc_Worker+0x1d9
fffff880`030afcd0 fffff800`02ad1a2a : fffff880`03087180 fffff880`03092040 00000000`00000000 fffff880`04802db0 : 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_UsbHcIntDpc_Worker+a7
fffff880`04811f5b 4a204103        and     byte ptr [rcx+3],al

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  USBPORT!USBPORT_Core_UsbHcIntDpc_Worker+a7

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
---------

USB problems are another commonly described shortcoming on this 'board. But - checkout this MSFT page.

Check the BIOS settings for your RAM are correct against the data supplied by the manufacturers (Geil) website, manually set the RAM timings and voltage if needed/possible. CPU-Z should give the currently loaded memory timings.

Ultimately, new RAM or a new 'board that suits the current RAM looks like the best way out of this problem.

 

another one, curious as if to this is still caused by the same thing:

 

Still looks like it's hardware or hardware-related (BIOS or BIOS settings, overheating, ... ) to me:

Code:

STOP 0x0000000A: IRQL_NOT_LESS_OR_EQUAL
Usual causes:  Kernel mode driver, System Service, BIOS, Windows, Virus scanner, Backup tool, compatibility


*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {fffff8800aeb56cb, 0, 1, fffff80002aa9c24}

Probably caused by : ntkrnlmp.exe ( nt!KiSecondaryClockInterrupt+14 )

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: fffff8800aeb56cb, memory referenced
Arg2: 0000000000000000, 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: fffff80002aa9c24, address which referenced memory

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


WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002ccd100
 fffff8800aeb56cb 

CURRENT_IRQL:  0

FAULTING_IP: 
nt!KiSecondaryClockInterrupt+14
fffff800`02aa9c24 c645ab00        mov     byte ptr [rbp-55h],0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  BFBC2Game.exe

TRAP_FRAME:  fffff8800ae65510 -- (.trap 0xfffff8800ae65510)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000017550003 rbx=0000000000000000 rcx=fffff70001080488
rdx=0000000000000002 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002aa9c24 rsp=fffff8800ae656a0 rbp=fffff8800aeb5720
 r8=0000000000000003  r9=0000000000000001 r10=0000000017550003
r11=fffff680000baa98 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up di ng nz na po nc
nt!KiSecondaryClockInterrupt+0x14:
fffff800`02aa9c24 c645ab00        mov     byte ptr [rbp-55h],0 ss:0018:fffff880`0aeb56cb=??
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002a9d2a9 to fffff80002a9dd00

STACK_TEXT:  
fffff880`0ae653c8 fffff800`02a9d2a9 : 00000000`0000000a fffff880`0aeb56cb 00000000`00000000 00000000`00000001 : nt!KeBugCheckEx
fffff880`0ae653d0 fffff800`02a9bf20 : 00000000`00000001 fffff880`0aeb56cb 00000000`00000000 00000000`17554048 : nt!KiBugCheckDispatch+0x69
fffff880`0ae65510 fffff800`02aa9c24 : 00000000`00000000 fffffa80`03df9ec8 00000000`00001000 fffff800`02bc990e : nt!KiPageFault+0x260
fffff880`0ae656a0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSecondaryClockInterrupt+0x14


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!KiSecondaryClockInterrupt+14
fffff800`02aa9c24 c645ab00        mov     byte ptr [rbp-55h],0

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  nt!KiSecondaryClockInterrupt+14

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4d9fdd5b

FAILURE_BUCKET_ID:  X64_0xA_nt!KiSecondaryClockInterrupt+14

BUCKET_ID:  X64_0xA_nt!KiSecondaryClockInterrupt+14

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

 

She defs aint overheating. Ive adjust the ram fequency to its proper 1600 in bios so hopefully that rids the errors!

 

Another 4 in quick succession. Still hardware related?

Looking at getting a gigabyte mobo and new ram

 

I have a feeling it's hardware related. Power supply, memory, or hard drive.

 

Another 2. Starting to suspect hard drive maybe?

Also is there anything from EventViewer i can post to help?

 

just had a wierd error... it was kinda like a BSOD... the music i was listening to started to skip/make the repeating sound it usually does before bluescreening but the screen just went black and the computer kept running...

what could that be?

 

I see EPU.exe (ASUS) as running during one of the recent crashes, try to uninstall anything that isn't strictly driver-related yet tied to hardware, like any monitoring software, etc.

The audio problem reads like the beginnings of a TDR type of problem, which would, without Windows recovering it (which is the cause of that 'lag'), lead to a BSOD (with the TDR-related problem, it would be pointing to the graphics subsystem).

Next time you hit any little lags/bugs like that, check the System and Application logs. Yes, if you can pinpoint the time of the crashes, look at any entries within a few minutes of them, any extra clues will help.