Some .dmp analysis, pourquoi?

noobvious said:

Kari said:

It means you have uploaded an empty ZIP archive

*Sigh* I'll try it again later when I'm not aggravated. Thanks for looking, Kari.:)

When ever you feel like trying it again here is the instructions.https://www.sevenforums.com/crash-loc...d-problem.html


Let us know if you need help

Ken

noobvious said:

zigzag3143 said:

noobvious said:

*Sigh* I'll try it again later when I'm not aggravated. Thanks for looking, Kari.:)

When ever you feel like trying it again here is the instructions.https://www.sevenforums.com/crash-loc...d-problem.html


Let us know if you need help

Ken

OK, one more try. In this case, things appeared to be running normally, then I got a different blue screen.....more like one I used to see on the old XP machine. It said, and I'm paraphrasing, "Windows has been shut to to prevent (something or other)" and then went on to advise checking into anything recently installed, etc.

And it just stayed on that blue screen, I had to manually power down from there, as opposed to the full-out BSOD's where everything just died, a couple weeks ago.

This was the only file in the minidump folder.....perhaps I didn't zip it properly before, but the filesize is different this time, so maybe now something useful is there.

Thanks Ken:)

This one war probably caused by memory management. Sidebar was op at the time of the crash. This may just be a one off but you should download memtestx86 for at least 5 passes to test it.

Let us know if you need help

Ken

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\051410-14726-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 (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02854000 PsLoadedModuleList = 0xfffff800`02a91e50
Debug session time: Fri May 14 19:53:12.242 2010 (GMT-4)
System Uptime: 0 days 2:33:42.756
Loading Kernel Symbols
...............................................................
................................................................
.............................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

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

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

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

1: 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: fffffa80028cf440
Arg3: 000000000000ffff
Arg4: 0000000000000000

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


BUGCHECK_STR:  0x1a_41790

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  sidebar.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff80002937ede to fffff800028c4600

STACK_TEXT:  
fffff880`08e96638 fffff800`02937ede : 00000000`0000001a 00000000`00041790 fffffa80`028cf440 00000000`0000ffff : nt!KeBugCheckEx
fffff880`08e96640 fffff800`028f7cc9 : fffff880`00000000 00000000`0222ffff 00000000`00000000 fffff800`02a53888 : nt! ?? ::FNODOBFM::`string'+0x33946
fffff880`08e96800 fffff800`02897734 : ffffffff`ffffffff fffff880`00000000 fffffa80`06ae7f90 fffffa80`06ae7f90 : nt!MiRemoveMappedView+0xd9
fffff880`08e96920 fffff800`02baac4f : fffff8a0`09cc1060 fffff880`08e96c20 00000000`00000000 fffffa80`0433ab60 : nt!MmCleanProcessAddressSpace+0x228
fffff880`08e96970 fffff800`02b834d1 : 00000000`000000ff fffffa80`0433ab01 000007ff`fffaa000 fffffa80`06d6a060 : nt!PspExitThread+0x92f
fffff880`08e96a30 fffff800`028a10e3 : 00000000`00000000 fffffa80`06b17060 00000000`05effbe0 fffff880`08e96be0 : nt!PsExitSpecialApc+0x1d
fffff880`08e96a60 fffff800`028a1520 : 00000000`773f4298 fffff880`08e96ae0 fffff800`02b835dc 00000000`00000001 : nt!KiDeliverApc+0x2eb
fffff880`08e96ae0 fffff800`028c38f7 : fffffa80`0433ab60 00000000`773f4270 fffff880`000000c0 00000000`00000000 : nt!KiInitiateUserApc+0x70
fffff880`08e96c20 00000000`773417ba : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExit+0x9c
00000000`05eff9f8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x773417ba


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+33946
fffff800`02937ede cc              int     3

SYMBOL_STACK_INDEX:  1

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

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4b88cfeb

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

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

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