BSOD error

B

BipolarAvatar

New member
Local time
2:49 PM
Messages
5
I just can't seem to figure out whats wrong with it myself.
OS is windows 7 ultimate x64, it is the original OS of my system. I installed it onto the system about 6-7 months ago, the system is the same age as well.

this is the error I have in my log, and attacked files for your helping hands! :D

----------------------------------------------------------------------------


Problem signature
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.256.1
Locale ID: 1033

Files that help describe the problem (some files may no longer be available)
012611-32744-01.dmp
sysdata.xml
WERInternalMetadata.xml


Extra information about the problem
BCCode: 1a
BCP1: 0000000000000403
BCP2: FFFFF68000084680
BCP3: F71000004F927847
BCP4: FFFFF68000080080
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1


----------------------------------------------------------------------------
 

My Computer

Computer Manufacturer/Model Number
Custom
OS
Windows 7 Ultimate x64
CPU
AMD Phenom(tm) II x4 965 Processor 3.41 GHz
Motherboard
Asus M4A78T-E
Memory
4gb cruical Ballistix tracer DDR3
Graphics Card(s)
EVGA - Nividia GTX460
Sound Card
motherboard
Monitor(s) Displays
asus 23in and asus 24in lcd displays
Hard Drives
2x WD 1TB caviar green
PSU
700 watt
Case
Antex 900
Cooling
air
BipolarAvatar said:
I just can't seem to figure out whats wrong with it myself.
OS is windows 7 ultimate x64, it is the original OS of my system. I installed it onto the system about 6-7 months ago, the system is the same age as well.

this is the error I have in my log, and attacked files for your helping hands! :D

----------------------------------------------------------------------------


Problem signature
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.256.1
Locale ID: 1033

Files that help describe the problem (some files may no longer be available)
012611-32744-01.dmp
sysdata.xml
WERInternalMetadata.xml


Extra information about the problem
BCCode: 1a
BCP1: 0000000000000403
BCP2: FFFFF68000084680
BCP3: F71000004F927847
BCP4: FFFFF68000080080
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1


----------------------------------------------------------------------------
Click to expand...

The newest one was caused by memory_Corruption. Run memtest for 7-8 passes to confirm.

By the way the date on the most recent is 2080, and either your system clock is set incorrectly or some other odd situation exists.

Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Boot from the CD, and leave it running for at least 5 or 6 passes.


Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot. Test the sticks individually, and if you find a good one, test it in all slots.



Code: 
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\K\Desktop\Windows_NT6_BSOD_jcgriff2\072380-16567-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\Symbols*http://msdl.microsoft.com/download/symbols;srv*e:\symbols
*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02a55000 PsLoadedModuleList = 0xfffff800`02c92e50
Debug session time: Tue Jul 23 20:59:54.938 2080 (GMT-5)
System Uptime: 0 days 0:02:07.624
Loading Kernel Symbols
.

Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.

..............................................................
................................................................
......................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffffc0000005, fffff80002af8382, fffff880031b6608, fffff880031b5e70}

Probably caused by : memory_corruption ( nt!MiGetNextNode+26 )

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

0: 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: fffff80002af8382, The address that the exception occurred at
Arg3: fffff880031b6608, Exception Record Address
Arg4: fffff880031b5e70, 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!MiGetNextNode+26
fffff800`02af8382 488b4908        mov     rcx,qword ptr [rcx+8]

EXCEPTION_RECORD:  fffff880031b6608 -- (.exr 0xfffff880031b6608)
ExceptionAddress: fffff80002af8382 (nt!MiGetNextNode+0x0000000000000026)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: 0000000000000264
Attempt to read from address 0000000000000264

CONTEXT:  fffff880031b5e70 -- (.cxr 0xfffff880031b5e70)
rax=000000000000025c rbx=fffffa80039ffb60 rcx=000000000000025c
rdx=000000000000040e rsi=fffffa8006c4fd48 rdi=fffffa8006a4c180
rip=fffff80002af8382 rsp=fffff880031b6848 rbp=0000000000000001
 r8=000000000000040e  r9=00000000000007ff r10=0000000000000801
r11=0000000000000743 r12=fffff8a008c6e000 r13=0000000000000000
r14=fffff8a008c6e000 r15=0000000000000000
iopl=0         nv up ei pl nz na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010206
nt!MiGetNextNode+0x26:
fffff800`02af8382 488b4908        mov     rcx,qword ptr [rcx+8] ds:002b:00000000`00000264=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  SearchIndexer.

CURRENT_IRQL:  0

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

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cfd0e0
 0000000000000264 

FOLLOWUP_IP: 
nt!MiGetNextNode+26
fffff800`02af8382 488b4908        mov     rcx,qword ptr [rcx+8]

BUGCHECK_STR:  0x7E

DEFAULT_BUCKET_ID:  NULL_CLASS_PTR_DEREFERENCE

LAST_CONTROL_TRANSFER:  from fffff80002e5ec30 to fffff80002af8382

STACK_TEXT:  
fffff880`031b6848 fffff800`02e5ec30 : fffff880`031b6870 fffffa80`039ffb60 fffff880`00000006 fffff8a0`02129600 : nt!MiGetNextNode+0x26
fffff880`031b6850 fffff800`02ea2ae1 : fffffa80`06c4fb30 00000000`00001404 fffffa80`068d5000 00000000`00000002 : nt!MmEnumerateAndReferenceImages+0x160
fffff880`031b68d0 fffff800`02ea2d54 : fffffa80`06c4fb30 fffff800`00000018 fffff800`02ea2b00 fffff880`031b69f0 : nt!EtwpEnumerateImages+0x51
fffff880`031b6920 fffff800`02e5a426 : fffffa80`06c46630 fffffa80`06c4fb30 fffff800`02ea2b80 fffff880`031b69f0 : nt!EtwpProcessEnumCallback+0x1d4
fffff880`031b69a0 fffff800`02ea2ea1 : fffff880`031b6ad8 fffffa80`0439fd01 fffffa80`0439fa00 fffffa80`0439fa00 : nt!PsEnumProcesses+0x26
fffff880`031b69d0 fffff800`02ea2ef7 : 00000000`00000000 00000000`00000002 fffff800`02c69470 fffffa80`0439fa80 : nt!EtwpProcessThreadImageRundown+0x51
fffff880`031b6a20 fffff800`02f0e04c : 00000000`00401802 fffffa80`0439fd28 fffffa80`0439fa80 fffff800`02afb5ac : nt!EtwpKernelTraceRundown+0x47
fffff880`031b6a50 fffff800`02f0e14f : fffffa80`0439fa80 00000000`00000002 fffff8a0`08c4b6d0 fffffa80`0439fa00 : nt!EtwpUpdateLoggerGroupMasks+0x22c
fffff880`031b6b50 fffff800`02d22709 : 00000000`00000000 fffff8a0`08c4b6d0 00000000`00000000 fffff800`02ae6406 : nt!EtwpStopLoggerInstance+0x4f
fffff880`031b6b90 fffff800`02e2a1c0 : 00000000`00000000 00000000`00000002 fffffa80`0439fa80 ffffffff`88ca6c00 : nt!EtwpStopTrace+0x129
fffff880`031b6c00 fffff800`02f35455 : ffffffff`ffffffff 00000000`00000001 ffffffff`000000b4 fffff800`02ccaee0 : nt! ?? ::NNGAKEGL::`string'+0x57c1c
fffff880`031b6c70 fffff800`02ad2861 : fffff800`02db9400 fffff800`02f35290 fffff800`02c6a5f8 fffffa80`039ffb60 : nt!PerfDiagpProxyWorker+0x1c5
fffff880`031b6cb0 fffff800`02d6aa86 : 00000000`00000000 fffffa80`039ffb60 00000000`00000080 fffffa80`03973890 : nt!ExpWorkerThread+0x111
fffff880`031b6d40 fffff800`02aa3b06 : fffff880`02f63180 fffffa80`039ffb60 fffff880`02f6dfc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`031b6d80 00000000`00000000 : fffff880`031b7000 fffff880`031b1000 fffff880`031b66a0 00000000`00000000 : nt!KxStartSystemThread+0x16


SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nt!MiGetNextNode+26

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  4b88cfeb

STACK_COMMAND:  .cxr 0xfffff880031b5e70 ; kb

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  X64_0x7E_nt!MiGetNextNode+26

BUCKET_ID:  X64_0x7E_nt!MiGetNextNode+26

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

My Computer

Computer Manufacturer/Model Number
HP Pavillion dv-7 1005 Tx
OS
Win 8 Release candidate 8400
CPU
[email protected]
Memory
4 gigs
Graphics Card(s)
Nvidia 9600M
Sound Card
HD built-in
Monitor(s) Displays
17" Wxga
Screen Resolution
1440x900
Cooling
none
Internet Speed
45Mb down 5Mb up
You must log in or register to reply here.
Back
Top