BSOD at random times, losing work!

Pauly said:

Try copying the file to your desktop to work with should let you compress from there

Pauly, this is what I did but now I can't do anything with the file. I managed to zip the folder with the .dmp in it but now I'm stuck with this .dmp on my desktop! It's cursed. I tried taking permission. I am the administrator! Frustration. Thanks for your help though.

zjwillie said:

I managed to compress the folder for it and it is attached. But the one I copied to my desktop I can't delete or more. It says it belongs to my user but still can't do anything with it!!

Hi and welcome

this one is pretty straight forward. Memory corruption

I would download memtestx86 and run it for 5 passes.

If you are overclocking STOP

I would also run a system file check
type cmd in search>right click and run as adxmin>sfc /dcannow

Ken J+

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\011710-25178-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*d:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02a1f000 PsLoadedModuleList = 0xfffff800`02c5ce50
Debug session time: Sun Jan 17 04:23:13.281 2010 (GMT-5)
System Uptime: 0 days 1:26:39.873
Loading Kernel Symbols
...............................................................
................................................................
..................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {28, 2, 0, fffff80002ad3090}

Probably caused by : memory_corruption ( nt!MiFindNodeOrParent+0 )

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

1: 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: 0000000000000028, 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: fffff80002ad3090, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cc70e0
 0000000000000028 

CURRENT_IRQL:  2

FAULTING_IP: 
nt!MiFindNodeOrParent+0
fffff800`02ad3090 48f7412800ffffff test    qword ptr [rcx+28h],0FFFFFFFFFFFFFF00h

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  SearchProtocol

TRAP_FRAME:  fffff880082e7260 -- (.trap 0xfffff880082e7260)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000001 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002ad3090 rsp=fffff880082e73f8 rbp=0000000000000000
 r8=fffff880082e7440  r9=0000000000000000 r10=fffffa800372b3d0
r11=fffffa8005f783d0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
nt!MiFindNodeOrParent:
fffff800`02ad3090 48f7412800ffffff test    qword ptr [rcx+28h],0FFFFFFFFFFFFFF00h ds:00000000`00000028=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002a90469 to fffff80002a90f00

STACK_TEXT:  
fffff880`082e7118 fffff800`02a90469 : 00000000`0000000a 00000000`00000028 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`082e7120 fffff800`02a8f0e0 : 78800001`0b362921 fffffa80`0372b418 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`082e7260 fffff800`02ad3090 : fffff800`02ad6e17 fffffa80`05048720 00000000`00000004 00000000`00000001 : nt!KiPageFault+0x260
fffff880`082e73f8 fffff800`02ad6e17 : fffffa80`05048720 00000000`00000004 00000000`00000001 fffff700`01080488 : nt!MiFindNodeOrParent
fffff880`082e7400 fffff800`02ad6d9d : 00000014`00000000 00000000`6bbb0000 00000000`6bb60000 00000000`00534000 : nt!MiLocateAddressInTree+0x17
fffff880`082e7430 fffff800`02ad6ea8 : 00000000`00000000 00000000`00000000 fffffa80`052ce0e8 fffffa80`0372b488 : nt!MiGetSharedProtosAtDpcLevel+0xbd
fffff880`082e7480 fffff800`02a2d19b : 00000000`06652000 00000000`06651000 00000000`6c4c3000 00000000`6c49a000 : nt!MiGetSharedProtos+0x18
fffff880`082e74b0 fffff800`02b95810 : 00000000`00000000 fffffa80`0372b410 b2f00001`07a4ac46 b3100000`204d8c46 : nt! ?? ::FNODOBFM::`string'+0x92bb
fffff880`082e74e0 fffff800`02b959f0 : fffffa80`03ee5370 00000003`00000000 fffffa80`0372b3d0 fffffa80`0372b488 : nt!MiEmptyPageAccessLog+0x160
fffff880`082e7550 fffff800`02b95bf6 : fffffa80`04299000 00000000`0000034c fffff680`003be3c8 00000000`00000041 : nt!MiAllocateAccessLog+0x80
fffff880`082e7580 fffff800`02b61705 : 00000003`00000000 00000000`00000001 00000000`00000003 00000000`0000034c : nt!MiLogPageAccess+0x46
fffff880`082e75d0 fffff800`02b61908 : 00000000`00000211 00000000`00000b85 00000000`0000087e 00000000`00000000 : nt!MiTrimWorkingSet+0x125
fffff880`082e7680 fffff800`02cd7797 : ffffffff`ffffffff fffffa80`03ee5708 fffffa80`0434a420 00000000`00000032 : nt!MiReduceWs+0x48
fffff880`082e76b0 fffff800`02ee1c3d : 00000000`00000001 fffff880`082e7c60 00000000`00000000 00000000`021ee500 : nt!MmAdjustWorkingSetSizeEx+0x397
fffff880`082e7740 fffff800`02de928b : 00000000`00000008 00000000`00000000 00000000`00000001 00000000`021ee530 : nt!PspSetQuotaLimits+0x32d
fffff880`082e7890 fffff800`02a90153 : 00000000`00000000 00000000`022daad0 fffff880`082e7b01 fffffa80`060609d0 : nt! ?? ::NNGAKEGL::`string'+0x4adf0
fffff880`082e7be0 00000000`77ac007a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`021ee4f8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77ac007a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!MiFindNodeOrParent+0
fffff800`02ad3090 48f7412800ffffff test    qword ptr [rcx+28h],0FFFFFFFFFFFFFF00h

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  nt!MiFindNodeOrParent+0

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc600

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  X64_0xA_nt!MiFindNodeOrParent+0

BUCKET_ID:  X64_0xA_nt!MiFindNodeOrParent+0

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

zjwillie said:

Opened Command as Administrator and deleted the file! Phew, that was annoying. Sorry for all the posts, but please can someone help with the BSOD?

Thanks for posting!

In what way can we help?

zigzag3143 said:

zjwillie said:

Opened Command as Administrator and deleted the file! Phew, that was annoying. Sorry for all the posts, but please can someone help with the BSOD?

Thanks for posting!

In what way can we help?

You did I'm sorry, didn't refresh my page while I was working on the problem. I'm doing as you suggested. Thank you for your help!

No problem. I thought you may have needed help with the things I suggested

zigzag3143 said:

No problem. I thought you may have needed help with the things I suggested

Now I do. Okay, I ran the slc test, nothing found. But here is where it gets weird. I put memtest86x on a disk (got the new one) and ran it. It crashes and my computer restarts at about 45% of the first test! So I thought must be the memory. Well so I tested each stick individually in each slot and they both pass. But together I can't even get it through the test. I'm leaving just one stick in there for now but that makes me sad.

Any suggestions?

Thanks!!!!

zjwillie said:

zigzag3143 said:

No problem. I thought you may have needed help with the things I suggested

Now I do. Okay, I ran the slc test, nothing found. But here is where it gets weird. I put memtest86x on a disk (got the new one) and ran it. It crashes and my computer restarts at about 45% of the first test! So I thought must be the memory. Well so I tested each stick individually in each slot and they both pass. But together I can't even get it through the test. I'm leaving just one stick in there for now but that makes me sad.

Any suggestions?

Thanks!!!!

You may also want to chek BIOS for a setting called Max Memory. It should be unchecked if you have it.


Ken J+

Pauly said:

zjwillie said:

zigzag3143 said:

No problem. I thought you may have needed help with the things I suggested

Now I do. Okay, I ran the slc test, nothing found. But here is where it gets weird. I put memtest86x on a disk (got the new one) and ran it. It crashes and my computer restarts at about 45% of the first test! So I thought must be the memory. Well so I tested each stick individually in each slot and they both pass. But together I can't even get it through the test. I'm leaving just one stick in there for now but that makes me sad.

Any suggestions?

Thanks!!!!

Have you tried sticks in different slots on the MB
Could be a MB issue, one of the slots could be faulty
Hopefully not but you never know
Also check your ram settings in bios, check they are set to the right voltage/timings/speed etc

Yeah, tried the sticks alone, work great in any of the slots. Together, Memtest won't run. I checked the stats in BIOS and all are correct. Will try this MAX thing next. Thanks guys!

The funny thing is, when I was running Windows 7 RC I had no problems at all...