Windows 7 Forums

Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: Getting a new set of BSOD's

14 Oct 2010   #1
Reime

Windows 7 Ultimate x64
 
 
Getting a new set of BSOD's

Hello again. Computer has BSOD'd like 3 times or more so far, My computer randomly froze a bit earlier, nothing was responding, so i just ended up turning it off, and when i started it back up, both the broadcom and the Bigfoot " Killer Xeno Pro " stopped working resulting in me not being able to get internet. Besides that, everything else relating to installing / uninstalling drivers and etc seems to have slowed down drastically, or even just times out instead. I had the broadcom working in safe mode and could get on the net, but while trying to scan the computer for viruses and what not in safe mode, it soon then BSOD'd. I'll edit my post with the mini dumps and etc when i can get the computer working.. [ Posting Via Macbook Pro. ]


My System SpecsSystem Spec
.
14 Oct 2010   #2
CarlTR6

Windows 7 Ultimate 32 bit
 
 

Sorry to learn you are having problems. Read this tutorial, follow the instructions, upload the files and we will be glad to help you.

https://www.sevenforums.com/crashes-debugging/96879-blue-screen-death-bsod-posting-instructions.html
My System SpecsSystem Spec
14 Oct 2010   #3
Reime

Windows 7 Ultimate x64
 
 

Here it is. Also hello again Carl. Had to boot into safe mode with Networking. Weird, computer wouldnt even notice that i plugged in a USB card, so it woulda been impossible to reply with the dumps and perfmon stuff. Yeah. I don't really know what happened this time. I'm really considering just doing another re-install of OS. Though. Might just pull up the same problems..
My System SpecsSystem Spec
.

14 Oct 2010   #4
CarlTR6

Windows 7 Ultimate 32 bit
 
 

Hi Reime. I looked at the six most recent dumps. All but one of the occurred after several hour of uptime, the longest being 17 hours. They are all hardware/hardware related errors and five of the six indicate memory corruption.
Quote:
Error code 24, NTFS_FILE_SYSTEM. Usual causes: Disk corruption, insufficient physical memory, Device driver, Indexing, Resident antivirus, backup, defrag programs, Disk/Drive failing/failure.

Error code 1A (2X), MEMORY_MANAGEMENT. Usual causes: Device driver, memory, kernel.

Error code 3B, SYSTEM_SERVICE_EXCEPTION. Usual causes: System service, Device driver, graphics driver, ?memory.

Error code 7E, SYSTEM_THREAD_EXCEPTION_NOT_HANDLED. Usual causes: Insufficient disk space, Device driver, Video card, BIOS, Breakpoint with no debugger attached, Hardware incompatibility, Faulty system service, Memory, 3rd party remote control.

Error code A, IRQL_NOT_LESS_OR_EQUAL. Usual causes: Kernel mode driver, System Service, BIOS, Windows, Virus scanner, Backup tool, compatibility.
Code:
Kernel base = 0xfffff800`0201d000 PsLoadedModuleList = 0xfffff800`0225ae50
Debug session time: Thu Oct 14 18:37:45.250 2010 (GMT-4)
System Uptime: 0 days 0:19:12.138
Loading Kernel Symbols
...............................................................
..........................................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 24, {1904fb, fffff88002521758, fffff88002520fc0, fffff880014c56c5}

Probably caused by : Ntfs.sys ( Ntfs!NtfsDeleteInternalAttributeStream+c5 )

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

4: 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: fffff88002521758
Arg3: fffff88002520fc0
Arg4: fffff880014c56c5

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


EXCEPTION_RECORD:  fffff88002521758 -- (.exr 0xfffff88002521758)
ExceptionAddress: fffff880014c56c5 (Ntfs!NtfsDeleteInternalAttributeStream+0x00000000000000c5)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

CONTEXT:  fffff88002520fc0 -- (.cxr 0xfffff88002520fc0)
rax=0000000000000001 rbx=fffff8a023a74140 rcx=fffffa800734e880
rdx=0000000000000000 rsi=1000000000000000 rdi=0000000000000000
rip=fffff880014c56c5 rsp=fffff88002521990 rbp=fffff80002232500
 r8=0000000000000000  r9=0000000000000000 r10=fffff8a023a74010
r11=fffff88002521b52 r12=fffffa800eb78600 r13=0000000000000000
r14=0000000000000702 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=00010202
Ntfs!NtfsDeleteInternalAttributeStream+0xc5:
fffff880`014c56c5 66897e5a        mov     word ptr [rsi+5Ah],di ds:002b:10000000`0000005a=????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

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

FOLLOWUP_IP: 
Ntfs!NtfsDeleteInternalAttributeStream+c5
fffff880`014c56c5 66897e5a        mov     word ptr [rsi+5Ah],di

FAULTING_IP: 
Ntfs!NtfsDeleteInternalAttributeStream+c5
fffff880`014c56c5 66897e5a        mov     word ptr [rsi+5Ah],di

BUGCHECK_STR:  0x24

LAST_CONTROL_TRANSFER:  from fffff8800149a956 to fffff880014c56c5

STACK_TEXT:  
fffff880`02521990 fffff880`0149a956 : 00000000`00000000 fffff800`02232500 00000000`00000001 fffff8a0`23a74140 : Ntfs!NtfsDeleteInternalAttributeStream+0xc5
fffff880`025219e0 fffff880`0140dcb4 : fffff8a0`23a74040 fffff8a0`23a74140 fffff800`02232500 00000000`00000003 : Ntfs!NtfsRemoveScb+0xe2
fffff880`02521a20 fffff880`014982dc : fffff8a0`23a74010 fffff800`022325a0 fffff880`02521b52 fffffa80`0eb786e0 : Ntfs!NtfsPrepareFcbForRemoval+0x50
fffff880`02521a50 fffff880`01416882 : fffffa80`0eb786e0 fffffa80`0eb786e0 fffff8a0`23a74010 00000000`00000000 : Ntfs!NtfsTeardownStructures+0xdc
fffff880`02521ad0 fffff880`014af813 : fffffa80`0eb786e0 fffff800`022325a0 fffff8a0`23a74010 00000000`00000009 : Ntfs!NtfsDecrementCloseCounts+0xa2
fffff880`02521b10 fffff880`0148938f : fffffa80`0eb786e0 fffff8a0`23a74140 fffff8a0`23a74010 fffffa80`0734e180 : Ntfs!NtfsCommonClose+0x353
fffff880`02521be0 fffff800`0209a961 : 00000000`00000000 fffff880`01489200 fffff800`02294100 02290229`00000005 : Ntfs!NtfsFspClose+0x15f
fffff880`02521cb0 fffff800`02331c06 : dbc0dbc0`dbc0dbc0 fffffa80`0614ab60 00000000`00000080 fffffa80`061366f0 : nt!ExpWorkerThread+0x111
fffff880`02521d40 fffff800`0206bc26 : fffff880`0245d180 fffffa80`0614ab60 fffff880`024681c0 5d335d33`5d335d33 : nt!PspSystemThreadStartup+0x5a
fffff880`02521d80 00000000`00000000 : fffff880`02522000 fffff880`0251c000 fffff880`025219f0 00000000`00000000 : nt!KxStartSystemThread+0x16


SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  Ntfs!NtfsDeleteInternalAttributeStream+c5

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: Ntfs

IMAGE_NAME:  Ntfs.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc14f

STACK_COMMAND:  .cxr 0xfffff88002520fc0 ; kb

FAILURE_BUCKET_ID:  X64_0x24_Ntfs!NtfsDeleteInternalAttributeStream+c5

BUCKET_ID:  X64_0x24_Ntfs!NtfsDeleteInternalAttributeStream+c5

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

Kernel base = 0xfffff800`02c0b000 PsLoadedModuleList = 0xfffff800`02e48e50
Debug session time: Tue Oct  5 05:44:12.030 2010 (GMT-4)
System Uptime: 0 days 14:00:47.123
Loading Kernel Symbols
...............................................................
................................................................
........................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {41790, fffffa8004cfa280, ffff, 0}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+33906 )

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

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

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

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


BUGCHECK_STR:  0x1a_41790

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  SearchIndexer.

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff80002ceef9e to fffff80002c7b740

STACK_TEXT:  
fffff880`0d0f67a8 fffff800`02ceef9e : 00000000`0000001a 00000000`00041790 fffffa80`04cfa280 00000000`0000ffff : nt!KeBugCheckEx
fffff880`0d0f67b0 fffff800`02caedf9 : 00000000`00000000 000007fe`fd3fdfff 00000000`00000000 00000000`77011000 : nt! ?? ::FNODOBFM::`string'+0x33906
fffff880`0d0f6970 fffff800`02c4e81c : ffffffff`ffffffff 00000000`00000000 00000000`00000000 00000000`00000000 : nt!MiRemoveMappedView+0xd9
fffff880`0d0f6a90 fffff800`02f60dcf : fffff8a0`02da2060 00000000`00000001 00000000`00000000 fffffa80`0c00cad0 : nt!MmCleanProcessAddressSpace+0x228
fffff880`0d0f6ae0 fffff800`02f3885b : 00000000`00000000 00000000`00000001 000007ff`fffde000 00000000`00000000 : nt!PspExitThread+0x92f
fffff880`0d0f6ba0 fffff800`02c7a993 : fffffa80`0c00b390 00000000`00000000 00000000`001e3c01 fffffa80`0c00cad0 : nt!NtTerminateProcess+0x25b
fffff880`0d0f6c20 00000000`76fe001a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0011f728 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x76fe001a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+33906
fffff800`02ceef9e cc              int     3

SYMBOL_STACK_INDEX:  1

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

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4c1c44a9

FAILURE_BUCKET_ID:  X64_0x1a_41790_nt!_??_::FNODOBFM::_string_+33906

BUCKET_ID:  X64_0x1a_41790_nt!_??_::FNODOBFM::_string_+33906

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

Kernel base = 0xfffff800`02c19000 PsLoadedModuleList = 0xfffff800`02e56e50
Debug session time: Tue Sep 28 06:53:11.402 2010 (GMT-4)
System Uptime: 0 days 5:09:27.883
Loading Kernel Symbols
...............................................................
................................................................
...................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff80002f83fe6, fffff88002b68e90, 0}

Probably caused by : ntkrnlmp.exe ( nt!RtlEqualUnicodeString+26 )

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

10: 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: fffff80002f83fe6, Address of the exception record for the exception that caused the bugcheck
Arg3: fffff88002b68e90, 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: 
nt!RtlEqualUnicodeString+26
fffff800`02f83fe6 488b02          mov     rax,qword ptr [rdx]

CONTEXT:  fffff88002b68e90 -- (.cxr 0xfffff88002b68e90)
rax=0000000000000010 rbx=fffff8a000e394a0 rcx=fffff88002b69970
rdx=effff8a00587d4e0 rsi=fffff8a0001e31d0 rdi=fffffa800e7e2678
rip=fffff80002f83fe6 rsp=fffff88002b69860 rbp=0000000000910097
 r8=0000000000000001  r9=fffff8a003950800 r10=0000000000000010
r11=fffff8a003950810 r12=fffff88002b69970 r13=0000000000000001
r14=fffff8a00000b498 r15=fffff8a00000b430
iopl=0         nv up ei pl nz ac pe nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010212
nt!RtlEqualUnicodeString+0x26:
fffff800`02f83fe6 488b02          mov     rax,qword ptr [rdx] ds:002b:effff8a0`0587d4e0=????????????????
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 fffff80002f83fe6

STACK_TEXT:  
fffff880`02b69860 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!RtlEqualUnicodeString+0x26


FOLLOWUP_IP: 
nt!RtlEqualUnicodeString+26
fffff800`02f83fe6 488b02          mov     rax,qword ptr [rdx]

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nt!RtlEqualUnicodeString+26

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4c1c44a9

STACK_COMMAND:  .cxr 0xfffff88002b68e90 ; kb

FAILURE_BUCKET_ID:  X64_0x3B_nt!RtlEqualUnicodeString+26

BUCKET_ID:  X64_0x3B_nt!RtlEqualUnicodeString+26

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

Kernel base = 0xfffff800`02c55000 PsLoadedModuleList = 0xfffff800`02e92e50
Debug session time: Sat Sep 25 10:23:42.514 2010 (GMT-4)
System Uptime: 0 days 17:02:41.606
Loading Kernel Symbols
...............................................................
................................................................
...................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffffc0000005, fffff80002cb99eb, fffff880037c5908, fffff880037c5170}

Probably caused by : ntkrnlmp.exe ( nt!ExpScanGeneralLookasideList+a0 )

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

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

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
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.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff80002cb99eb, The address that the exception occurred at
Arg3: fffff880037c5908, Exception Record Address
Arg4: fffff880037c5170, Context Record Address

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


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

FAULTING_IP: 
nt!ExpScanGeneralLookasideList+a0
fffff800`02cb99eb 418b40d8        mov     eax,dword ptr [r8-28h]

EXCEPTION_RECORD:  fffff880037c5908 -- (.exr 0xfffff880037c5908)
ExceptionAddress: fffff80002cb99eb (nt!ExpScanGeneralLookasideList+0x00000000000000a0)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

CONTEXT:  fffff880037c5170 -- (.cxr 0xfffff880037c5170)
rax=0000000000000000 rbx=fffff80002e6a760 rcx=0000000000000000
rdx=0000000000000000 rsi=fffffa800610c040 rdi=000000000000ffff
rip=fffff80002cb99eb rsp=fffff880037c5b40 rbp=0000000000000001
 r8=effffa800ad9ff80  r9=0000000000000004 r10=0000000000000000
r11=0000000000000100 r12=0000000000000000 r13=fffff80002e6a750
r14=0000000000000000 r15=fffff880009b7140
iopl=0         nv up ei ng nz na pe cy
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010283
nt!ExpScanGeneralLookasideList+0xa0:
fffff800`02cb99eb 418b40d8        mov     eax,dword ptr [r8-28h] ds:002b:effffa80`0ad9ff58=????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  2

ERROR_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 fffff80002efd0e0
 ffffffffffffffff 

FOLLOWUP_IP: 
nt!ExpScanGeneralLookasideList+a0
fffff800`02cb99eb 418b40d8        mov     eax,dword ptr [r8-28h]

BUGCHECK_STR:  0x7E

LAST_CONTROL_TRANSFER:  from fffff80002cd90e0 to fffff80002cb99eb

STACK_TEXT:  
fffff880`037c5b40 fffff800`02cd90e0 : 00000000`00000001 00000000`00000008 00000000`00000001 fffff800`02efd900 : nt!ExpScanGeneralLookasideList+0xa0
fffff880`037c5ba0 fffff800`02cda16e : 00000000`00000008 fffff880`037c5c10 00000000`00000001 fffffa80`00000000 : nt!ExAdjustLookasideDepth+0x40
fffff880`037c5bd0 fffff800`02f69c06 : fffffa80`06139860 00000000`00000080 fffffa80`0610c040 00000000`00000001 : nt!KeBalanceSetManager+0x1be
fffff880`037c5d40 fffff800`02ca3c26 : fffff880`009b2180 fffffa80`06139860 fffff880`009bd1c0 1163116d`13149163 : nt!PspSystemThreadStartup+0x5a
fffff880`037c5d80 00000000`00000000 : fffff880`037c6000 fffff880`037c0000 fffff880`037c5710 00000000`00000000 : nt!KxStartSystemThread+0x16


SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nt!ExpScanGeneralLookasideList+a0

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4c1c44a9

STACK_COMMAND:  .cxr 0xfffff880037c5170 ; kb

FAILURE_BUCKET_ID:  X64_0x7E_nt!ExpScanGeneralLookasideList+a0

BUCKET_ID:  X64_0x7E_nt!ExpScanGeneralLookasideList+a0

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

Kernel base = 0xfffff800`02c5d000 PsLoadedModuleList = 0xfffff800`02e9ae50
Debug session time: Sat Sep 25 16:37:16.707 2010 (GMT-4)
System Uptime: 0 days 6:12:07.188
Loading Kernel Symbols
...............................................................
................................................................
...................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {b8000000b0, 2, 1, fffff80002cd6365}

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

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

2: 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: 000000b8000000b0, 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: fffff80002cd6365, address which referenced memory

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


WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002f050e0
 000000b8000000b0 

CURRENT_IRQL:  2

FAULTING_IP: 
nt!KeAcquireSpinLockRaiseToDpc+55
fffff800`02cd6365 f0480fba2900    lock bts qword ptr [rcx],0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  msnmsgr.exe

TRAP_FRAME:  fffff8800dfbe740 -- (.trap 0xfffff8800dfbe740)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000002 rbx=0000000000000000 rcx=000000b8000000b0
rdx=fffffa800b4a7380 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002cd6365 rsp=fffff8800dfbe8d0 rbp=000000b8000000b0
 r8=000000000000ffff  r9=0000000000000000 r10=0000000000000000
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na pe nc
nt!KeAcquireSpinLockRaiseToDpc+0x55:
fffff800`02cd6365 f0480fba2900    lock bts qword ptr [rcx],0 ds:5100:000000b8`000000b0=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002cccca9 to fffff80002ccd740

STACK_TEXT:  
fffff880`0dfbe5f8 fffff800`02cccca9 : 00000000`0000000a 000000b8`000000b0 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`0dfbe600 fffff800`02ccb920 : fffffa80`0611e570 00000000`00000002 00000000`0000027f 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`0dfbe740 fffff800`02cd6365 : fffffa80`0611e570 fffffa80`09ff5220 00000000`00000000 fffff880`052fd3ca : nt!KiPageFault+0x260
fffff880`0dfbe8d0 fffff880`0530149a : fffffa80`0b4a7380 fffffa80`0b4a7380 000000b8`00000000 fffffa80`0b4a7380 : nt!KeAcquireSpinLockRaiseToDpc+0x55
fffff880`0dfbe920 fffffa80`0b4a7380 : fffffa80`0b4a7380 000000b8`00000000 fffffa80`0b4a7380 fffffa80`0ba72570 : Xeno7x64+0x949a
fffff880`0dfbe928 fffffa80`0b4a7380 : 000000b8`00000000 fffffa80`0b4a7380 fffffa80`0ba72570 00000000`9c40244f : 0xfffffa80`0b4a7380
fffff880`0dfbe930 000000b8`00000000 : fffffa80`0b4a7380 fffffa80`0ba72570 00000000`9c40244f fffffa80`09b35180 : 0xfffffa80`0b4a7380
fffff880`0dfbe938 fffffa80`0b4a7380 : fffffa80`0ba72570 00000000`9c40244f fffffa80`09b35180 00000000`00000000 : 0xb8`00000000
fffff880`0dfbe940 fffffa80`0ba72570 : 00000000`9c40244f fffffa80`09b35180 00000000`00000000 fffffa80`0a36c1a0 : 0xfffffa80`0b4a7380
fffff880`0dfbe948 00000000`9c40244f : fffffa80`09b35180 00000000`00000000 fffffa80`0a36c1a0 fffff880`052fb991 : 0xfffffa80`0ba72570
fffff880`0dfbe950 fffffa80`09b35180 : 00000000`00000000 fffffa80`0a36c1a0 fffff880`052fb991 00000000`9c402437 : 0x9c40244f
fffff880`0dfbe958 00000000`00000000 : fffffa80`0a36c1a0 fffff880`052fb991 00000000`9c402437 00000000`00000000 : 0xfffffa80`09b35180


STACK_COMMAND:  kb

FOLLOWUP_IP: 
Xeno7x64+949a
fffff880`0530149a ??              ???

SYMBOL_STACK_INDEX:  4

SYMBOL_NAME:  Xeno7x64+949a

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: Xeno7x64

IMAGE_NAME:  Xeno7x64.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a25b2a4

FAILURE_BUCKET_ID:  X64_0xA_Xeno7x64+949a

BUCKET_ID:  X64_0xA_Xeno7x64+949a

Followup: MachineOwner
---------
I find some out of date drivers on your system Older drivers can and do cause memory corruption and crashes. Update the following drivers.
Quote:
mcdbus.sys Tue Feb 24 05:34:07 2009 - MagicISO SCSI Host Controller belongs to the software MagicDisc or Driver for MagicISO SCSI Host Controller by MagicISO, Inc. See if there is an updated driver for MagicDisc.

k57nd60a.sys Sun Jun 07 03:36:34 2009 - This driver was indicated in one of your dumps as being involved in the crash. Broadcom NetLink Gigabit Ethernet NDIS6.x Unified Driver. Broadcom.com - Downloads & Support

intelsmb.sys Wed May 13 03:31:00 2009 - System Management Bus 2.0 (SMBus) Driver is a driver file from Intel Corporation belonging to Intel(R) SMBus Controller. http://downloadcenter.intel.com/Default.aspx

AWOPFilterDriver.sys Thu Jun 25 09:54:47 2009 - Alienware Optical Drive Filter Driver, Alienware/Dell Inc. Go to the Dell site and see if you can update this driver.
Update these drivers. Report back and we will start on testing hardware.

Download and install Speedfan. Monitor your temps during heavy useage.

Test your RAM with Memetest86. Follow the instructions in this tutorial: RAM - Test with Memtest86+
Post your results.
My System SpecsSystem Spec
15 Oct 2010   #5
Reime

Windows 7 Ultimate x64
 
 

Ive updated the broadcom, i cant get updating or anything to really work right anymore normally outside of safe mode. Im considering doing another OS re-install.. But ugh, this is pretty upsetting. Thanks for helping again though Carl, ya helped me before if ya don't remember.
Also, firefox doesnt seem to wanna work right with the automatic updater, i'm trying with Internet explorer for intel's auto update, but the page is loading very very slowly..
Edit : It doesnt even come up with an update for the SMBUS controller thing.. I believe i tried to look for that before with no luck..
My System SpecsSystem Spec
15 Oct 2010   #6
Reime

Windows 7 Ultimate x64
 
 

So like before the memtest really even started, it says i got 103 Errors.. =/
Do i stop? or do the errors somehow i unno.. get fixed by pass 7?

Edit : Well, i just started to retest with just one ram card in the first slot. 0 Errors.. Yay. but i gotta let that run for 7 passes. Blah. gonna take forever..

Edit #2 : I noticed before, but Does having the ram cards split up, instead of being inserted right next to each other have any type of effect on them in general? I've got room to insert 6 Ram cards on the mother board, and each 2gb card was inserted in every other slot.

Edit #3: So far it seems like the 3rd slot is the biggest problem. I've tested two cards on it. One card was pulling like 13,000+ Errors before i reset it, and the 3rd was pulling like 2,000+ before i reset the computer. So far, slot one seems fine with the first card i tried, i didnt have any problem with that slot, after testing the other two in slot 3 like how they were first inserted, i decided to test slot 2. So far no errors yet with that slot. So it seems two cards are working just fine so far. No passes yet.. But i dont know if i should bother with the first card since it works perfect in slot 1..

Edit #4: Actually, does it matter which slots they are in, if they are split up among the 6 slots? Because i asked a friend, and she said that they work better when split up, but now im just curious if they have to be evenly placed among the slots, or not.

Thanks.
My System SpecsSystem Spec
15 Oct 2010   #7
CarlTR6

Windows 7 Ultimate 32 bit
 
 

It looks as though you definitely have a RAM problem. It could be a bad RAM stick, a bad RAM slot, or incompatible RAM. It does matter what slots the sticks are in. I am not a hardware guy. I am going to ask the the hardware gurus to look at this thread and give you guidance. How does your computer run with the just the one stick of RAM? Do you have the manual that came with your motherboard? If so, it will tell you how to slot your RAM.
My System SpecsSystem Spec
15 Oct 2010   #8
pebbly

win 7 ultimate32bit, Win8.1pro wmc 32bit
 
 

reime, the mobo is a gigabyte ga-ex58-udr3, looking at the board there are 4 ram slots #2slot [from the cpu side] is colour coded blue ,that slot should be empty , so your ram chips should be in slots 1,3 & 4
My System SpecsSystem Spec
15 Oct 2010   #9
CarlTR6

Windows 7 Ultimate 32 bit
 
 

Thank you, Pebbly. That definitely answers one of his questions.

Reime, I believe you tested slot 3 with two known good RAM sticks and got errors with both, is this correct? That may indicate that slot is bad.
My System SpecsSystem Spec
15 Oct 2010   #10
Reime

Windows 7 Ultimate x64
 
 

Yeah, i believe the slot is bad, i didnt test it with the first ram card, because i had left that alone in the first slot.
@Pebbly Uhm.. They're white and black colored, and theres 3 white, 3 black.. I've got them split apart among the 6 slots. I ran memtest last night, it did 10 passes with no errors. And MSN seems to be working just fine using the broadcom adaptor. I haven't tried using the Killer Xeno yet.

Edit: Well the computer in general seems to be working just fine right now.
Should i post any scanner or run a program like perfmon or something? Oh. Im going to run sfc /scannow
Would the log for that help any?
My System SpecsSystem Spec
Reply

 Getting a new set of BSOD's




Thread Tools



Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 21:35.
Twitter Facebook Google+ Seven Forums iOS App Seven Forums Android App