|
|
You're in the
visual studio .net debugging
group:Minidumps available !
visual studio .net debugging:
[quoted text, click to view] "Skybuck Flying" <spam@hotmail.com> wrote in message
news:faumd8$2ae$1@news3.zwoll1.ov.home.nl... >I am definetly no expert... > > Seems like something did a try except where that is not allowed, also > seems resource related ????: > > Microsoft (R) Windows Debugger Version 6.6.0007.5 > Copyright (c) Microsoft Corporation. All rights reserved. > > > Loading Dump File [C:\WINDOWS\Minidump\Mini082707-01.dmp] > Mini Kernel Dump File: Only registers and stack trace are available > > Symbol search path is: > SRV*c:\Tools\WinDbg\WebSymbols*http://msdl.microsoft.com/download/symbols > Executable search path is: > Windows Server 2003 Kernel Version 3790 (Service Pack 2) MP (2 procs) Free > x64 > Product: WinNt, suite: TerminalServer SingleUserTS > Built by: 3790.srv03_sp2_rtm.070216-1710 > Kernel base = 0xfffff800`01000000 PsLoadedModuleList = 0xfffff800`011d5100 > Debug session time: Mon Aug 27 15:17:04.640 2007 (GMT+2) > System Uptime: 0 days 0:27:21.571 > Loading Kernel Symbols > ........................................................................................................................................... > Loading User Symbols > Loading unloaded module list > .................................................. > ******************************************************************************* > * * > * Bugcheck Analysis * > * * > ******************************************************************************* > > Use !analyze -v to get detailed debugging information. > > BugCheck 50, {fffffa8804c21090, 0, fffff97fff0a7742, 5} > > > Could not read faulting driver name > Probably caused by : win32k.sys ( win32k!HmgAllocateDcAttr+1b6 ) > > Followup: MachineOwner > --------- > > 1: 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: fffffa8804c21090, memory referenced. > Arg2: 0000000000000000, value 0 = read operation, 1 = write operation. > Arg3: fffff97fff0a7742, If non-zero, the instruction address which > referenced the bad memory > address. > Arg4: 0000000000000005, (reserved) > > Debugging Details: > ------------------ > > > Could not read faulting driver name > > READ_ADDRESS: fffffa8804c21090 > > FAULTING_IP: > win32k!HmgAllocateDcAttr+1b6 > fffff97f`ff0a7742 488b4cc118 mov rcx,qword ptr [rcx+rax*8+18h] > > MM_INTERNAL_CODE: 5 > > CUSTOMER_CRASH_COUNT: 1 > > DEFAULT_BUCKET_ID: DRIVER_FAULT > > BUGCHECK_STR: 0x50 > > PROCESS_NAME: bds.exe > > CURRENT_IRQL: 0 > > TRAP_FRAME: fffffadfc478e990 -- (.trap fffffadfc478e990) > NOTE: The trap frame does not contain all registers. > Some register values may be zeroed. > rax=00000000ffffffff rbx=0000000000000888 rcx=fffffa8004c21080 > rdx=fffffa8004c21080 rsi=fffffa80051f6280 rdi=fffff97fff0cda0e > rip=fffff97fff0a7742 rsp=fffffadfc478eb20 rbp=fffffadfc478ecf0 > r8=fffffa8004b9b0c0 r9=5000984210000000 r10=500098421117001d > r11=00000000000007ff r12=0000000000000000 r13=0000000000000000 > r14=0000000000000000 r15=0000000000000000 > iopl=0 nv up ei ng nz ac po nc > win32k!HmgAllocateDcAttr+0x1b6: > fffff97f`ff0a7742 488b4cc118 mov rcx,qword ptr [rcx+rax*8+18h] > ds:fffffa88`04c21090=???????????????? > Resetting default scope > > LAST_CONTROL_TRANSFER: from fffff800010a5416 to fffff8000102e950 > > STACK_TEXT: > fffffadf`c478e8b8 fffff800`010a5416 : 00000000`00000050 fffffa88`04c21090 > 00000000`00000000 fffffadf`c478e990 : nt!KeBugCheckEx > fffffadf`c478e8c0 fffff800`0102d519 : fffffa80`00cad9e0 00000000`00000009 > 00000000`00000000 fffffa80`05009b50 : nt!MmAccessFault+0x395 > fffffadf`c478e990 fffff97f`ff0a7742 : 00000000`00000000 fffff97f`ff0ce249 > fffffa80`0445f780 fffffadf`c478ecf0 : nt!KiPageFault+0x119 > fffffadf`c478eb20 fffff97f`ff0ce004 : 00000000`00000888 00000000`00000000 > 00000000`1e011591 fffffa80`051f6280 : win32k!HmgAllocateDcAttr+0x1b6 > fffffadf`c478eb60 fffff97f`ff0cdf0e : fffffa80`051f6280 fffffa80`051f6280 > fffffadf`cba85cd0 fffffa80`0133b000 : win32k!GreSetupDCAttributes+0x34 > fffffadf`c478eba0 fffff97f`ff0a36c6 : fffffa80`01351010 fffff97f`ff0ced20 > 00000000`00000000 00000000`7efdb000 : win32k!GreCreateDisplayDC+0x1c4 > fffffadf`c478ec30 fffff800`0102e3fd : 00000000`7d814cc6 fffff97f`ff0ced20 > 00000000`7d814cc6 00000000`7d814c30 : win32k!GreCreateCompatibleDC+0x77 > fffffadf`c478ec70 00000000`78b842d9 : 00000000`00000000 00000000`00000000 > 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x3 > 00000000`0012edf8 00000000`00000000 : 00000000`00000000 00000000`00000000 > 00000000`00000000 00000000`00000000 : 0x78b842d9 > > > STACK_COMMAND: kb > > FOLLOWUP_IP: > win32k!HmgAllocateDcAttr+1b6 > fffff97f`ff0a7742 488b4cc118 mov rcx,qword ptr [rcx+rax*8+18h] > > SYMBOL_STACK_INDEX: 3 > > SYMBOL_NAME: win32k!HmgAllocateDcAttr+1b6 > > FOLLOWUP_NAME: MachineOwner > > MODULE_NAME: win32k > > IMAGE_NAME: win32k.sys > > DEBUG_FLR_IMAGE_TIMESTAMP: 45e6f310 > > FAILURE_BUCKET_ID: X64_0x50_win32k!HmgAllocateDcAttr+1b6 > > BUCKET_ID: X64_0x50_win32k!HmgAllocateDcAttr+1b6 > > Followup: MachineOwner > --------- > > Bye, > Skybuck. > > P.S.: I followed instructions on this link to setup WinDBG properly for > symbol support ;) > > http://forums.majorgeeks.com/showthread.php?t=35246 > > Simply add something like: > > SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols > > to symbol path. > > Then symbols will be downloaded... > > (I set mine to C:\Tools\WinDBG\WebSymbols :) ) > > >
File purpose and description:
Bds.exe is a program file which you would have installed yourself on your own computer. The exact disk location is also shown below to verfiy it is not spyware, as many spyware programs use similiar names and just locate them elsewhere on your hard drive. Always check the proper disk location of your programs if you are suspicious. Bds.exe is a common name, short names like this can often be used by many companies, this one is most often associated with Borland Software (not Codegear software) and the Delphi installation. The BDS.exe is for the Borland Database Engine (as it used to be called), and this will be a running task if you install Delphi software. This file is considered safe and is not spyware. (See the details below for the actual location of this file.) Actual file or task name: bds.exe File type: This is an executable program. File or folder location: This file will be found on your disk drive at C:\Documents and Settings\All Users\Application Data\{AB3EC276-D261-4943-A921-1CC1C6799AED}\corex\B2284239\1CC39CF2 and also at C:\Program Files\CodeGear\RAD Studio\5.0\bin General information: Be aware that many tasks will be similiar names to existing tasks or processes. You can always view the running tasks on your computer by pressing ctrl-alt-del to view the windows "task manager", and then view the "processes" tab. This will show you all tasks running or currently active on your PC. Although this shows you all running tasks, it does not show dll file thats are loaded, as they get loaded as part of other processes. Many spyware writers attempt to hide their files on your computer, for example, bds.exe may be intentionally misspelled to look like a similiar task, or spyware may be named very similiar to a Windows system task. The reason they do this is so you cannot easily recognize the name in your tasklist as I have mentioned above. Make sure always check the location of the file if you are concerned. You can always find the location of bds.exe on your computer by using your Windows search options, but I will also try to list the file location of every file described on this website, so you can verify the correct location. You can view the entire tasklist directory with the link below. Tasklist Directory Main Page Software Downloads Page Spyware and Adware Removal Tips Lookup other processes below. icq.exe icqlite.exe ie4uinit.exe iedkcs32.dll ieexplorer.exe iegr32.exe iehelper.dll iehost.exe iel2cde8.dll iesdpb.dll iesdsg.dll ietie.dll ieudinit.exe iexplore.exe iexplores.exe ifrmewrk.exe igdctrl.exe igfxpers igfxtray.exe igowdkka.dll ikeymain.exe imekrmig.exe imjpmig.exe imscinst.exe incd.exe incdsrv.exe incmail.exe indexsearch.exe inicio.exe inkmonitor.exe intel32.exe intelmem.exe internat.exe intmonp.exe iopengl.exe iphsend.exe ipmon32.exe ipodwatcher.exe ipv6monl.dll isadd.dll isaddon.dll isamntr.exe isamonitor.exe issch.exe isstart.exe isuspm.exe itouch.exe ituneshelper.exe jaaste.dll jawa32.exe [quoted text, click to view] Paul Russell wrote:
> what is PROCESS_NAME: bds.exe > > > "Skybuck Flying" <spam@hotmail.com> wrote in message > news:faumd8$2ae$1@news3.zwoll1.ov.home.nl... >> I am definetly no expert... >> >> Seems like something did a try except where that is not allowed, also >> seems resource related ????: >> >> Microsoft (R) Windows Debugger Version 6.6.0007.5 >> Copyright (c) Microsoft Corporation. All rights reserved. >> >> >> Loading Dump File [C:\WINDOWS\Minidump\Mini082707-01.dmp] >> Mini Kernel Dump File: Only registers and stack trace are available >> >> Symbol search path is: >> SRV*c:\Tools\WinDbg\WebSymbols*http://msdl.microsoft.com/download/symbols >> Executable search path is: >> Windows Server 2003 Kernel Version 3790 (Service Pack 2) MP (2 procs) >> Free x64 >> Product: WinNt, suite: TerminalServer SingleUserTS >> Built by: 3790.srv03_sp2_rtm.070216-1710 >> Kernel base = 0xfffff800`01000000 PsLoadedModuleList = >> 0xfffff800`011d5100 >> Debug session time: Mon Aug 27 15:17:04.640 2007 (GMT+2) >> System Uptime: 0 days 0:27:21.571 >> Loading Kernel Symbols >> ........................................................................................................................................... >> >> Loading User Symbols >> Loading unloaded module list >> .................................................. >> ******************************************************************************* >> >> * * >> * Bugcheck Analysis * >> * * >> ******************************************************************************* >> >> >> Use !analyze -v to get detailed debugging information. >> >> BugCheck 50, {fffffa8804c21090, 0, fffff97fff0a7742, 5} >> >> >> Could not read faulting driver name >> Probably caused by : win32k.sys ( win32k!HmgAllocateDcAttr+1b6 ) >> >> Followup: MachineOwner >> --------- >> >> 1: 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: fffffa8804c21090, memory referenced. >> Arg2: 0000000000000000, value 0 = read operation, 1 = write operation. >> Arg3: fffff97fff0a7742, If non-zero, the instruction address which >> referenced the bad memory >> address. >> Arg4: 0000000000000005, (reserved) >> >> Debugging Details: >> ------------------ >> >> >> Could not read faulting driver name >> >> READ_ADDRESS: fffffa8804c21090 >> >> FAULTING_IP: >> win32k!HmgAllocateDcAttr+1b6 >> fffff97f`ff0a7742 488b4cc118 mov rcx,qword ptr [rcx+rax*8+18h] >> >> MM_INTERNAL_CODE: 5 >> >> CUSTOMER_CRASH_COUNT: 1 >> >> DEFAULT_BUCKET_ID: DRIVER_FAULT >> >> BUGCHECK_STR: 0x50 >> >> PROCESS_NAME: bds.exe >> >> CURRENT_IRQL: 0 >> >> TRAP_FRAME: fffffadfc478e990 -- (.trap fffffadfc478e990) >> NOTE: The trap frame does not contain all registers. >> Some register values may be zeroed. >> rax=00000000ffffffff rbx=0000000000000888 rcx=fffffa8004c21080 >> rdx=fffffa8004c21080 rsi=fffffa80051f6280 rdi=fffff97fff0cda0e >> rip=fffff97fff0a7742 rsp=fffffadfc478eb20 rbp=fffffadfc478ecf0 >> r8=fffffa8004b9b0c0 r9=5000984210000000 r10=500098421117001d >> r11=00000000000007ff r12=0000000000000000 r13=0000000000000000 >> r14=0000000000000000 r15=0000000000000000 >> iopl=0 nv up ei ng nz ac po nc >> win32k!HmgAllocateDcAttr+0x1b6:
Hello,
Windows XP Professional x64 Edition has crashed many times the last year and two months. I have made available 27 minidumps that were made during the crashes ! Not all minidumps might be complete, sometimes I resetted the system because I didn't want to wait, so some minidumps might be truncated. Also the Win 64 Debugger doesn't show that much information but some command line tool did show much more information... which can be seen in the two output.txt samples. (Can't remember which command line tool it was, maybe output.txt has hints ! ;) ) I have uploaded these minidumps to my webdrive for you to download in case you want to improve WinXPx64Pro ! Hope this helps ! (I also hope no passwords are in there or something like that LOL ! ;) gjez) Webdrive is located at: http://members.home.nl/hbthouppermans/ Specifically: http://members.home.nl/hbthouppermans/WinXPx64ProMinidumps/ I hope you have some fun with them ! I will inspect the latest myself: 27 august 2007. I was debugging, developing with Delphi 2007 with themed support enabled and then first system hang and the second time system crashed ! Nasty ! (win32k.sys bug ?) Bye, Skybuck.
Oh shit,
I just noticed all the date/time on the webdrive have be changed to the day I uploaded them SHIT. The minidump for today/themed crash is: Mini082707-01.dm Bye, Skybuck.
I am definetly no expert...
Seems like something did a try except where that is not allowed, also seems resource related ????: Microsoft (R) Windows Debugger Version 6.6.0007.5 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\WINDOWS\Minidump\Mini082707-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*c:\Tools\WinDbg\WebSymbols*http://msdl.microsoft.com/download/symbols Executable search path is: Windows Server 2003 Kernel Version 3790 (Service Pack 2) MP (2 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 3790.srv03_sp2_rtm.070216-1710 Kernel base = 0xfffff800`01000000 PsLoadedModuleList = 0xfffff800`011d5100 Debug session time: Mon Aug 27 15:17:04.640 2007 (GMT+2) System Uptime: 0 days 0:27:21.571 Loading Kernel Symbols ............................................................................................................................................ Loading User Symbols Loading unloaded module list ................................................... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 50, {fffffa8804c21090, 0, fffff97fff0a7742, 5} Could not read faulting driver name Probably caused by : win32k.sys ( win32k!HmgAllocateDcAttr+1b6 ) Followup: MachineOwner --------- 1: 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: fffffa8804c21090, memory referenced. Arg2: 0000000000000000, value 0 = read operation, 1 = write operation. Arg3: fffff97fff0a7742, If non-zero, the instruction address which referenced the bad memory address. Arg4: 0000000000000005, (reserved) Debugging Details: ------------------ Could not read faulting driver name READ_ADDRESS: fffffa8804c21090 FAULTING_IP: win32k!HmgAllocateDcAttr+1b6 fffff97f`ff0a7742 488b4cc118 mov rcx,qword ptr [rcx+rax*8+18h] MM_INTERNAL_CODE: 5 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: DRIVER_FAULT BUGCHECK_STR: 0x50 PROCESS_NAME: bds.exe CURRENT_IRQL: 0 TRAP_FRAME: fffffadfc478e990 -- (.trap fffffadfc478e990) NOTE: The trap frame does not contain all registers. Some register values may be zeroed. rax=00000000ffffffff rbx=0000000000000888 rcx=fffffa8004c21080 rdx=fffffa8004c21080 rsi=fffffa80051f6280 rdi=fffff97fff0cda0e rip=fffff97fff0a7742 rsp=fffffadfc478eb20 rbp=fffffadfc478ecf0 r8=fffffa8004b9b0c0 r9=5000984210000000 r10=500098421117001d r11=00000000000007ff r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei ng nz ac po nc win32k!HmgAllocateDcAttr+0x1b6: fffff97f`ff0a7742 488b4cc118 mov rcx,qword ptr [rcx+rax*8+18h] ds:fffffa88`04c21090=???????????????? Resetting default scope LAST_CONTROL_TRANSFER: from fffff800010a5416 to fffff8000102e950 STACK_TEXT: fffffadf`c478e8b8 fffff800`010a5416 : 00000000`00000050 fffffa88`04c21090 00000000`00000000 fffffadf`c478e990 : nt!KeBugCheckEx fffffadf`c478e8c0 fffff800`0102d519 : fffffa80`00cad9e0 00000000`00000009 00000000`00000000 fffffa80`05009b50 : nt!MmAccessFault+0x395 fffffadf`c478e990 fffff97f`ff0a7742 : 00000000`00000000 fffff97f`ff0ce249 fffffa80`0445f780 fffffadf`c478ecf0 : nt!KiPageFault+0x119 fffffadf`c478eb20 fffff97f`ff0ce004 : 00000000`00000888 00000000`00000000 00000000`1e011591 fffffa80`051f6280 : win32k!HmgAllocateDcAttr+0x1b6 fffffadf`c478eb60 fffff97f`ff0cdf0e : fffffa80`051f6280 fffffa80`051f6280 fffffadf`cba85cd0 fffffa80`0133b000 : win32k!GreSetupDCAttributes+0x34 fffffadf`c478eba0 fffff97f`ff0a36c6 : fffffa80`01351010 fffff97f`ff0ced20 00000000`00000000 00000000`7efdb000 : win32k!GreCreateDisplayDC+0x1c4 fffffadf`c478ec30 fffff800`0102e3fd : 00000000`7d814cc6 fffff97f`ff0ced20 00000000`7d814cc6 00000000`7d814c30 : win32k!GreCreateCompatibleDC+0x77 fffffadf`c478ec70 00000000`78b842d9 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x3 00000000`0012edf8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x78b842d9 STACK_COMMAND: kb FOLLOWUP_IP: win32k!HmgAllocateDcAttr+1b6 fffff97f`ff0a7742 488b4cc118 mov rcx,qword ptr [rcx+rax*8+18h] SYMBOL_STACK_INDEX: 3 SYMBOL_NAME: win32k!HmgAllocateDcAttr+1b6 FOLLOWUP_NAME: MachineOwner MODULE_NAME: win32k IMAGE_NAME: win32k.sys DEBUG_FLR_IMAGE_TIMESTAMP: 45e6f310 FAILURE_BUCKET_ID: X64_0x50_win32k!HmgAllocateDcAttr+1b6 BUCKET_ID: X64_0x50_win32k!HmgAllocateDcAttr+1b6 Followup: MachineOwner --------- Bye, Skybuck. P.S.: I followed instructions on this link to setup WinDBG properly for symbol support ;) http://forums.majorgeeks.com/showthread.php?t=35246 Simply add something like: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols to symbol path. Then symbols will be downloaded... (I set mine to C:\Tools\WinDBG\WebSymbols :) )
Make that 28 !
System just crashed again while using internet explorer and surfing to the weblog of the guy that wrote the themed delphi stuff ?! The irony ?! Coincendence ?! or this guy one serious bug !? :) Me think coincedence ! ;) Latest crash analysis: Microsoft (R) Windows Debugger Version 6.6.0007.5 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\WINDOWS\Minidump\Mini082707-02.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*c:\Tools\WinDbg\WebSymbols*http://msdl.microsoft.com/download/symbols Executable search path is: Windows Server 2003 Kernel Version 3790 (Service Pack 2) MP (2 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 3790.srv03_sp2_rtm.070216-1710 Kernel base = 0xfffff800`01000000 PsLoadedModuleList = 0xfffff800`011d5100 Debug session time: Mon Aug 27 17:39:39.484 2007 (GMT+2) System Uptime: 0 days 2:21:02.411 Loading Kernel Symbols ............................................................................................................................................ Loading User Symbols Loading unloaded module list ................................................... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 1000007E, {ffffffffc0000005, fffff80001011ebd, fffffadfc9086a90, fffffadfc90864a0} Probably caused by : ntkrnlmp.exe ( nt!CmpDelayCloseWorker+494 ) Followup: MachineOwner --------- 1: 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: fffff80001011ebd, The address that the exception occurred at Arg3: fffffadfc9086a90, Exception Record Address Arg4: fffffadfc90864a0, 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!CmpDelayCloseWorker+494 fffff800`01011ebd 488b4008 mov rax,qword ptr [rax+8] EXCEPTION_RECORD: fffffadfc9086a90 -- (.exr fffffadfc9086a90) ExceptionAddress: fffff80001011ebd (nt!CmpDelayCloseWorker+0x0000000000000494) ExceptionCode: c0000005 (Access violation) ExceptionFlags: 00000000 NumberParameters: 2 Parameter[0]: 0000000000000000 Parameter[1]: 0000000000000008 Attempt to read from address 0000000000000008 CONTEXT: fffffadfc90864a0 -- (.cxr fffffadfc90864a0) rax=0000000000000000 rbx=fffffa8003281c68 rcx=000000000000132f rdx=0000000000000008 rsi=00000000ffffffff rdi=fffffa80028bd588 rip=fffff80001011ebd rsp=fffffadfc9086cb0 rbp=fffffa800412b920 r8=00000000da81d47a r9=fffffa80028bd590 r10=0000000000000000 r11=00000000000007ff r12=000000000000132f r13=00000000000001c1 r14=0000000000000000 r15=0000000000000001 iopl=0 nv up ei pl nz na pe cy cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010203 nt!CmpDelayCloseWorker+0x494: fffff800`01011ebd 488b4008 mov rax,qword ptr [rax+8] ds:002b:00000000`00000008=0000000000000000 Resetting default scope CUSTOMER_CRASH_COUNT: 2 CURRENT_IRQL: 0 ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s". READ_ADDRESS: 0000000000000008 BUGCHECK_STR: 0x7E DEFAULT_BUCKET_ID: NULL_CLASS_PTR_DEREFERENCE EXCEPTION_STR: 0x0 LAST_CONTROL_TRANSFER: from fffff8000103768a to fffff80001011ebd STACK_TEXT: fffffadf`c9086cb0 fffff800`0103768a : 00000000`00000000 fffff800`011defe0 fffff800`01012070 fffffadf`cecd3bf0 : nt!CmpDelayCloseWorker+0x494 fffffadf`c9086d00 fffff800`0124b972 : fffffadf`cecd3bf0 00000000`00000080 fffffadf`cecd3bf0 fffffadf`c8c83680 : nt!ExpWorkerThread+0x13b fffffadf`c9086d70 fffff800`010202d6 : fffffadf`c8c7b180 fffffadf`cecd3bf0 fffffadf`c8c83680 fffff800`011b5dc0 : nt!PspSystemThreadStartup+0x3e fffffadf`c9086dd0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16 FOLLOWUP_IP: nt!CmpDelayCloseWorker+494 fffff800`01011ebd 488b4008 mov rax,qword ptr [rax+8] SYMBOL_STACK_INDEX: 0 FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe DEBUG_FLR_IMAGE_TIMESTAMP: 45d69ab4 SYMBOL_NAME: nt!CmpDelayCloseWorker+494 STACK_COMMAND: .cxr 0xfffffadfc90864a0 ; kb FAILURE_BUCKET_ID: X64_0x7E_nt!CmpDelayCloseWorker+494 BUCKET_ID: X64_0x7E_nt!CmpDelayCloseWorker+494 Followup: MachineOwner --------- 1: kd> ml *** WARNING: Unable to verify timestamp for nv4_disp.dll *** ERROR: Module load completed but symbols could not be loaded for nv4_disp.dll *** WARNING: Unable to verify timestamp for CTEDSPSY.DLL *** ERROR: Module load completed but symbols could not be loaded for CTEDSPSY.DLL *** WARNING: Unable to verify timestamp for dump_nvata64.sys *** ERROR: Module load completed but symbols could not be loaded for dump_nvata64.sys *** WARNING: Unable to verify timestamp for vmm.sys *** ERROR: Module load completed but symbols could not be loaded for vmm.sys *** WARNING: Unable to verify timestamp for kl1.sys *** ERROR: Module load completed but symbols could not be loaded for kl1.sys *** WARNING: Unable to verify timestamp for klif.sys *** ERROR: Module load completed but symbols could not be loaded for klif.sys *** WARNING: Unable to verify timestamp for CTEXFIFX.DLL *** ERROR: Module load completed but symbols could not be loaded for CTEXFIFX.DLL *** WARNING: Unable to verify timestamp for CT20XUT.DLL *** ERROR: Module load completed but symbols could not be loaded for CT20XUT.DLL *** WARNING: Unable to verify timestamp for ctac32k.sys *** ERROR: Module load completed but symbols could not be loaded for ctac32k.sys
Just for the record here is the link and the source of the website that
crashed my system (might be internet explorer 7 related, one internet explorer didn't start quickly enough so I terminated it, then later the new instance crashed): The crash might have been caused by the internet explorere I terminated, maybe it wasn't terminated properly ;) (No website was loaded for the terminated explorer, since I have blank by default, but it still loaded slowly ? strange) Still website full of crap: <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html> <head> <title>Delphi 2007 VCL Designer Theme Support</title> <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> <meta http-equiv="Content-Language" content="EN" /> <meta name="DC.title" content="The Blog of Steve Trefethen" /> <meta name="ICBM" content="37.0517349243164, -122.031608581543" /> <meta name="geo.position" content="37.0517349243164, -122.031608581543" /> <meta content="Delphi, ASP.NET, Google, Computer, .NET, C#, Trefethen, Steve, Weblog, Scotts Valley, California, stevetrefethen.com - Steve Trefethen's Weblog" name="KEYWORDS" /> <meta content="Blogging on development related topics particularly internet applications, ASP.NET, C#, Delphi, Windows API, Win32 and other items of personal interest" name="DESCRIPTION" /> <meta name="author" content="Steve Trefethen" /> <meta name="copyright" content="2006-2007 Steve Trefethen Creative Commons Attribution 2.5 License Some rights reserved" /> <meta name="verify-v1" content="4u+6jnGkp0dk/ers2rvpg9D+2Q6PbIYlEZ+9EgVvO5E=" /> <link rel="openid.server" href="http://www.myopenid.com/server" /> <link rel="openid.delegate" href="http://stevetrefethen.myopenid.com/" /> <link media="all" rel="stylesheet" type="text/css" href="http://www.stevetrefethen.com/blog/themes/SteveWhite/allstyles.css"></link> <link rel="shortcut icon" href="/favicon.ico" /> <link rel="meta" type="application/rdf+xml" title="FOAF" href="/blog/foaf.rdf" /> <!--[if IE 6]> <style type="text/css"> body { width: 990px; } pre { font-size: smaller; } #centercolumn { float: left; margin-left: 0px; margin-right: 0px; width: 590px;} #rightcolumn { width: 185px; } </style> <![endif]--> <!--[if lt IE 7.]> <script defer type="text/javascript" src="/blog/themes/stevewhite/scripts/pngfix.js"></script> <![endif]--> <link rel="stylesheet" type="text/css" href="http://www.google.com/uds/css/gsearch.css"></link> <style type="text/css"> gs-result, gs-webResult { width: 575px; } </style> <!--[if gte IE 7.]> <style type="text/css"> body { width: 990px; } pre { font-size: smaller; } #centercolumn { float: left; margin-left: 0px; margin-right: 0px; width: 605px;} #rightcolumn { width: 190px; } gs-result, gs-webResult { width: 575px; } </style> <![endif]--> <script src="http://www.google.com/uds/api?file=uds.js&v=1.0&key=ABQIAAAAxdzra1SUiRgCxlxV65C7ThQxZfWLYgQ1RrGbkJQBJQpJyHPXGRRLpHQp7SERGgRo929bmsPGrg4zFw" type="text/javascript"></script> <script language="Javascript" type="text/javascript"> //<![CDATA[ function OnLoad() { // Create a search control var searchControl = new GSearchControl(); // Set options var options = new GsearcherOptions(); options.setExpandMode(GSearchControl.EXPAND_MODE_OPEN); options.setRoot(document.getElementById("search_results")); // site restricted web search with custom label // and class suffix var siteSearch = new GwebSearch(); siteSearch.setUserDefinedLabel("stevetrefethen.com"); siteSearch.setUserDefinedClassSuffix("siteSearch"); siteSearch.setSiteRestriction("stevetrefethen.com"); searchControl.addSearcher(siteSearch, options); // Tell the searcher to draw itself and tell it where to attach searchControl.draw(document.getElementById("searchcontrol")); // Execute an inital search //searchControl.execute("Google"); } GSearch.setOnLoadCallback(OnLoad); //]]> </script> <base href="http://www.stevetrefethen.com/blog/"></base> <link rel="alternate" type="application/rss+xml" title="Steve Trefethen's Weblog" href="http://feeds.feedburner.com/SteveTrefethensWeblog" /> <link rel="alternate" type="application/atom+xml" title="Steve Trefethen's Weblog" href="http://feeds.feedburner.com/SteveTrefethensWeblog" /> <link rel="EditURI" type="application/rsd+xml" title="RSD" href="http://www.stevetrefethen.com/blog/EditService.asmx/GetRsd" /><link rel="microsummary" type="application/x.microsummary+xml" href="http://www.stevetrefethen.com/blog/Microsummary.ashx" /></head> <body><form name="mainForm" method="post" action="/blog/CommentView.aspx?title=Delphi2007VCLDesignerThemeSupport" id="mainForm"> <input type="hidden" name="__EVENTTARGET" id="__EVENTTARGET" value="" /> <input type="hidden" name="__EVENTARGUMENT" id="__EVENTARGUMENT" value="" /> <input type="hidden" name="__VIEWSTATE" id="__VIEWSTATE" value="/wEPDwUKMTM2MTcxNzAwMA9kFgJmD2QWAgIFD2QWBAIFDzwrAAoBAA8WAh4KVG9kYXlzRGF0ZQYAgHdYVLbJCGRkAhUPZBYCZg8PFgIeB2VudHJ5SWQFJDEwYzQ1NGRhLTIyMTgtNDZlZi1hNjk1LTE4NzBhNjc5MzVmYmQWAmYPZBYGAgMPFgIeB1Zpc2libGVnFgICAQ8PFgIeBFRleHQFFENvbW1lbnRzIGFyZSBjbG9zZWQuZGQCBA8WAh8CaBYCAgEPDxYCHwMFS0FsbCBjb21tZW50cyByZXF1aXJlIHRoZSBhcHByb3ZhbCBvZiB0aGUgc2l0ZSBvd25lciBiZWZvcmUgYmVpbmcgZGlzcGxheWVkLmRkAgYPFgIfAmgWEGYPZBYCZg9kFgRmDw8WAh8DBQROYW1lZGQCAg8PFgIeDEVycm9yTWVzc2FnZQUxWW91IG11c3QgZW50ZXIgeW91ciBuYW1lIC0gb3IgYXQgbGVhc3Qgc29tZSBuYW1lLmRkAgEPZBYEZg9kFgRmDw8WAh8DBQZFLW1haWxkZAICDw8WAh8EBUpUaGUgZS1tYWlsIGFkZHJlc3MgaXMgb3B0aW9uYWwsIGJ1dCBpZiB5b3UgcHJvdmlkZSBpdCwgaXQgc2hvdWxkIGJlIHZhbGlkLmRkAgEPZBYCAgMPFgIfAmgWAgIBDw8WAh8DBVQod2lsbCBzaG93IHlvdXIgPGEgaHJlZj0iaHR0cDovL3d3dy5ncmF2YXRhci5jb20iIHRhcmdldD0iX2JsYW5rIj5ncmF2YXRhcjwvYT4gaWNvbilkZAICD2QWAmYPZBYCZg8PFgIfAwUJSG9tZSBwYWdlZGQCBA9kFgICAQ9kFgICAQ8QDxYCHwMFC1JlbWVtYmVyIE1lZGRkZAIFD2QWAmYPZBYGZg8PFgQfAwUaQ29tbWVudCAoSFRNTCBub3QgYWxsb3dlZCkfAmhkZAICDw8WAh8DBdMBQ29tbWVudCAoU29tZSBodG1sIGlzIGFsbG93ZWQ6IDxjb2RlPmFAaHJlZkB0aXRsZSwgYiwgYmxvY2txdW90ZUBjaXRlLCBlbSwgaSwgc3Ryb25nPC9jb2RlPikgd2hlcmUgdGhlIEAgbWVhbnMgImF0dHJpYnV0ZS4iIEZvciBleGFtcGxlLCB5b3UgY2FuIHVzZSAmbHQ7YSBocmVmPSIiIHRpdGxlPSIiJmd0OyBvciAmbHQ7YmxvY2txdW90ZSBjaXRlPSJTY290dCImZ3Q7LmRkAgQPDxYCHwQFHkVtcHR5IGNvbW1lbnRzIGFyZW4ndCBhbGxvd2VkLmRkAgYPZBYCZg9kFgICBQ8PFgIfBAUbUGxlYXNlIGVudGVyIHRoZSBjb2RlIHNob3duZGQCBw9kFgJmD2QWAmYPDxYCHwMFFExpdmUgQ29tbWVudCBQcmV2aWV3ZGQCCQ9kFgJmD2QWAgIDDw8WAh8DBQxTYXZlIENvbW1lbnRkZGQ=" /> <script type="text/javascript"> <!--
what were you programming at the time of crash?
I have seen this kind of crash happen in some apps our test guys were doing to stress GDI ... [quoted text, click to view] "Skybuck Flying" <spam@hotmail.com> wrote in message
news:favvsa$d2b$1@news4.zwoll1.ov.home.nl... > Hi, > > It's Delphi 2007 from the file's description: > > "CodeGear RAD Studio for Windows" > > BDS.EXE is what I believe is the Delphi 2007 IDE. > > Integrated Development Environment for Rapid Application Development for > Windows. > > So far no more crashes, play with it a bit more... > > Bye, > Skybuck. > > "Paul Russell" <no_spam@nospam.com> wrote in message > news:4A21A8D0-6A4C-42DF-A0DF-10DE6DDA7838@microsoft.com... >> what is PROCESS_NAME: bds.exe >> >> >> "Skybuck Flying" <spam@hotmail.com> wrote in message >> news:faumd8$2ae$1@news3.zwoll1.ov.home.nl... >>>I am definetly no expert... >>> >>> Seems like something did a try except where that is not allowed, also >>> seems resource related ????: >>> >>> Microsoft (R) Windows Debugger Version 6.6.0007.5 >>> Copyright (c) Microsoft Corporation. All rights reserved. >>> >>> >>> Loading Dump File [C:\WINDOWS\Minidump\Mini082707-01.dmp] >>> Mini Kernel Dump File: Only registers and stack trace are available >>> >>> Symbol search path is: >>> SRV*c:\Tools\WinDbg\WebSymbols*http://msdl.microsoft.com/download/symbols >>> Executable search path is: >>> Windows Server 2003 Kernel Version 3790 (Service Pack 2) MP (2 procs) >>> Free x64 >>> Product: WinNt, suite: TerminalServer SingleUserTS >>> Built by: 3790.srv03_sp2_rtm.070216-1710 >>> Kernel base = 0xfffff800`01000000 PsLoadedModuleList = >>> 0xfffff800`011d5100 >>> Debug session time: Mon Aug 27 15:17:04.640 2007 (GMT+2) >>> System Uptime: 0 days 0:27:21.571 >>> Loading Kernel Symbols >>> ........................................................................................................................................... >>> Loading User Symbols >>> Loading unloaded module list >>> .................................................. >>> ******************************************************************************* >>> * * >>> * Bugcheck Analysis * >>> * * >>> ******************************************************************************* >>> >>> Use !analyze -v to get detailed debugging information. >>> >>> BugCheck 50, {fffffa8804c21090, 0, fffff97fff0a7742, 5} >>> >>> >>> Could not read faulting driver name >>> Probably caused by : win32k.sys ( win32k!HmgAllocateDcAttr+1b6 ) >>> >>> Followup: MachineOwner >>> --------- >>> >>> 1: 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: fffffa8804c21090, memory referenced. >>> Arg2: 0000000000000000, value 0 = read operation, 1 = write operation. >>> Arg3: fffff97fff0a7742, If non-zero, the instruction address which >>> referenced the bad memory >>> address. >>> Arg4: 0000000000000005, (reserved) >>> >>> Debugging Details: >>> ------------------ >>> >>> >>> Could not read faulting driver name >>> >>> READ_ADDRESS: fffffa8804c21090 >>> >>> FAULTING_IP: >>> win32k!HmgAllocateDcAttr+1b6 >>> fffff97f`ff0a7742 488b4cc118 mov rcx,qword ptr [rcx+rax*8+18h] >>> >>> MM_INTERNAL_CODE: 5 >>> >>> CUSTOMER_CRASH_COUNT: 1 >>> >>> DEFAULT_BUCKET_ID: DRIVER_FAULT >>> >>> BUGCHECK_STR: 0x50 >>> >>> PROCESS_NAME: bds.exe >>> >>> CURRENT_IRQL: 0 >>> >>> TRAP_FRAME: fffffadfc478e990 -- (.trap fffffadfc478e990) >>> NOTE: The trap frame does not contain all registers. >>> Some register values may be zeroed. >>> rax=00000000ffffffff rbx=0000000000000888 rcx=fffffa8004c21080 >>> rdx=fffffa8004c21080 rsi=fffffa80051f6280 rdi=fffff97fff0cda0e >>> rip=fffff97fff0a7742 rsp=fffffadfc478eb20 rbp=fffffadfc478ecf0 >>> r8=fffffa8004b9b0c0 r9=5000984210000000 r10=500098421117001d >>> r11=00000000000007ff r12=0000000000000000 r13=0000000000000000 >>> r14=0000000000000000 r15=0000000000000000 >>> iopl=0 nv up ei ng nz ac po nc >>> win32k!HmgAllocateDcAttr+0x1b6: >>> fffff97f`ff0a7742 488b4cc118 mov rcx,qword ptr [rcx+rax*8+18h] >>> ds:fffffa88`04c21090=???????????????? >>> Resetting default scope >>> >>> LAST_CONTROL_TRANSFER: from fffff800010a5416 to fffff8000102e950 >>> >>> STACK_TEXT: >>> fffffadf`c478e8b8 fffff800`010a5416 : 00000000`00000050 >>> fffffa88`04c21090 00000000`00000000 fffffadf`c478e990 : nt!KeBugCheckEx >>> fffffadf`c478e8c0 fffff800`0102d519 : fffffa80`00cad9e0 >>> 00000000`00000009 00000000`00000000 fffffa80`05009b50 : >>> nt!MmAccessFault+0x395 >>> fffffadf`c478e990 fffff97f`ff0a7742 : 00000000`00000000 >>> fffff97f`ff0ce249 fffffa80`0445f780 fffffadf`c478ecf0 : >>> nt!KiPageFault+0x119 >>> fffffadf`c478eb20 fffff97f`ff0ce004 : 00000000`00000888 >>> 00000000`00000000 00000000`1e011591 fffffa80`051f6280 : >>> win32k!HmgAllocateDcAttr+0x1b6 >>> fffffadf`c478eb60 fffff97f`ff0cdf0e : fffffa80`051f6280 >>> fffffa80`051f6280 fffffadf`cba85cd0 fffffa80`0133b000 : >>> win32k!GreSetupDCAttributes+0x34 >>> fffffadf`c478eba0 fffff97f`ff0a36c6 : fffffa80`01351010 >>> fffff97f`ff0ced20 00000000`00000000 00000000`7efdb000 : >>> win32k!GreCreateDisplayDC+0x1c4 >>> fffffadf`c478ec30 fffff800`0102e3fd : 00000000`7d814cc6 >>> fffff97f`ff0ced20 00000000`7d814cc6 00000000`7d814c30 : >>> win32k!GreCreateCompatibleDC+0x77 >>> fffffadf`c478ec70 00000000`78b842d9 : 00000000`00000000 >>> 00000000`00000000 00000000`00000000 00000000`00000000 : >>> nt!KiSystemServiceCopyEnd+0x3 >>> 00000000`0012edf8 00000000`00000000 : 00000000`00000000 >>> 00000000`00000000 00000000`00000000 00000000`00000000 : 0x78b842d9 >>> >>> >>> STACK_COMMAND: kb >>> >>> FOLLOWUP_IP: >>> win32k!HmgAllocateDcAttr+1b6 >>> fffff97f`ff0a7742 488b4cc118 mov rcx,qword ptr [rcx+rax*8+18h] >>> >>> SYMBOL_STACK_INDEX: 3 >>> >>> SYMBOL_NAME: win32k!HmgAllocateDcAttr+1b6 >>> >>> FOLLOWUP_NAME: MachineOwner >>> >>> MODULE_NAME: win32k >>> >>> IMAGE_NAME: win32k.sys >>> >>> DEBUG_FLR_IMAGE_TIMESTAMP: 45e6f310 >>> >>> FAILURE_BUCKET_ID: X64_0x50_win32k!HmgAllocateDcAttr+1b6 >>> >>> BUCKET_ID: X64_0x50_win32k!HmgAllocateDcAttr+1b6 >>> >>> Followup: MachineOwner >>> --------- >>> >>> Bye, >>> Skybuck. >>> >>> P.S.: I followed instructions on this link to setup WinDBG properly for >>> symbol support ;) >>> >>> http://forums.majorgeeks.com/showthread.php?t=35246 >>> >>> Simply add something like:
It is not my job to fixes these bugs.
Somebody made a bug somewhere. These minidumps can provide hints. That's why I am providing these minidumps, in case some developer is reading or happens to read this message and finds it interesting and thinks hmmm I am gonna look into the mentioned code to see if there is something that could have caused it. Alternatively recreate the situation debug it and see what happens. Might be difficult to recreate this problem, or maybe not... time will tell. Bye, Skybuck.
On Tue, 28 Aug 2007 08:50:01 +0200, "Skybuck Flying" <spam@hotmail.com>
[quoted text, click to view] wrote: >It is not my job to fixes these bugs. > >Somebody made a bug somewhere. > >These minidumps can provide hints. But why dump then here? Get in touch with the right people for support, contact Delphi, or go to their forums. Over there they are much cleverer.
Hi,
It's Delphi 2007 from the file's description: "CodeGear RAD Studio for Windows" BDS.EXE is what I believe is the Delphi 2007 IDE. Integrated Development Environment for Rapid Application Development for Windows. So far no more crashes, play with it a bit more... Bye, Skybuck. [quoted text, click to view] "Paul Russell" <no_spam@nospam.com> wrote in message news:4A21A8D0-6A4C-42DF-A0DF-10DE6DDA7838@microsoft.com... > what is PROCESS_NAME: bds.exe > > > "Skybuck Flying" <spam@hotmail.com> wrote in message > news:faumd8$2ae$1@news3.zwoll1.ov.home.nl... >>I am definetly no expert... >> >> Seems like something did a try except where that is not allowed, also >> seems resource related ????: >> >> Microsoft (R) Windows Debugger Version 6.6.0007.5 >> Copyright (c) Microsoft Corporation. All rights reserved. >> >> >> Loading Dump File [C:\WINDOWS\Minidump\Mini082707-01.dmp] >> Mini Kernel Dump File: Only registers and stack trace are available >> >> Symbol search path is: >> SRV*c:\Tools\WinDbg\WebSymbols*http://msdl.microsoft.com/download/symbols >> Executable search path is: >> Windows Server 2003 Kernel Version 3790 (Service Pack 2) MP (2 procs) >> Free x64 >> Product: WinNt, suite: TerminalServer SingleUserTS >> Built by: 3790.srv03_sp2_rtm.070216-1710 >> Kernel base = 0xfffff800`01000000 PsLoadedModuleList = >> 0xfffff800`011d5100 >> Debug session time: Mon Aug 27 15:17:04.640 2007 (GMT+2) >> System Uptime: 0 days 0:27:21.571 >> Loading Kernel Symbols >> ........................................................................................................................................... >> Loading User Symbols >> Loading unloaded module list >> .................................................. >> ******************************************************************************* >> * * >> * Bugcheck Analysis * >> * * >> ******************************************************************************* >> >> Use !analyze -v to get detailed debugging information. >> >> BugCheck 50, {fffffa8804c21090, 0, fffff97fff0a7742, 5} >> >> >> Could not read faulting driver name >> Probably caused by : win32k.sys ( win32k!HmgAllocateDcAttr+1b6 ) >> >> Followup: MachineOwner >> --------- >> >> 1: 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: fffffa8804c21090, memory referenced. >> Arg2: 0000000000000000, value 0 = read operation, 1 = write operation. >> Arg3: fffff97fff0a7742, If non-zero, the instruction address which >> referenced the bad memory >> address. >> Arg4: 0000000000000005, (reserved) >> >> Debugging Details: >> ------------------ >> >> >> Could not read faulting driver name >> >> READ_ADDRESS: fffffa8804c21090 >> >> FAULTING_IP: >> win32k!HmgAllocateDcAttr+1b6 >> fffff97f`ff0a7742 488b4cc118 mov rcx,qword ptr [rcx+rax*8+18h] >> >> MM_INTERNAL_CODE: 5 >> >> CUSTOMER_CRASH_COUNT: 1 >> >> DEFAULT_BUCKET_ID: DRIVER_FAULT >> >> BUGCHECK_STR: 0x50 >> >> PROCESS_NAME: bds.exe >> >> CURRENT_IRQL: 0 >> >> TRAP_FRAME: fffffadfc478e990 -- (.trap fffffadfc478e990) >> NOTE: The trap frame does not contain all registers. >> Some register values may be zeroed. >> rax=00000000ffffffff rbx=0000000000000888 rcx=fffffa8004c21080 >> rdx=fffffa8004c21080 rsi=fffffa80051f6280 rdi=fffff97fff0cda0e >> rip=fffff97fff0a7742 rsp=fffffadfc478eb20 rbp=fffffadfc478ecf0 >> r8=fffffa8004b9b0c0 r9=5000984210000000 r10=500098421117001d >> r11=00000000000007ff r12=0000000000000000 r13=0000000000000000 >> r14=0000000000000000 r15=0000000000000000 >> iopl=0 nv up ei ng nz ac po nc >> win32k!HmgAllocateDcAttr+0x1b6: >> fffff97f`ff0a7742 488b4cc118 mov rcx,qword ptr [rcx+rax*8+18h] >> ds:fffffa88`04c21090=???????????????? >> Resetting default scope >> >> LAST_CONTROL_TRANSFER: from fffff800010a5416 to fffff8000102e950 >> >> STACK_TEXT: >> fffffadf`c478e8b8 fffff800`010a5416 : 00000000`00000050 fffffa88`04c21090 >> 00000000`00000000 fffffadf`c478e990 : nt!KeBugCheckEx >> fffffadf`c478e8c0 fffff800`0102d519 : fffffa80`00cad9e0 00000000`00000009 >> 00000000`00000000 fffffa80`05009b50 : nt!MmAccessFault+0x395 >> fffffadf`c478e990 fffff97f`ff0a7742 : 00000000`00000000 fffff97f`ff0ce249 >> fffffa80`0445f780 fffffadf`c478ecf0 : nt!KiPageFault+0x119 >> fffffadf`c478eb20 fffff97f`ff0ce004 : 00000000`00000888 00000000`00000000 >> 00000000`1e011591 fffffa80`051f6280 : win32k!HmgAllocateDcAttr+0x1b6 >> fffffadf`c478eb60 fffff97f`ff0cdf0e : fffffa80`051f6280 fffffa80`051f6280 >> fffffadf`cba85cd0 fffffa80`0133b000 : win32k!GreSetupDCAttributes+0x34 >> fffffadf`c478eba0 fffff97f`ff0a36c6 : fffffa80`01351010 fffff97f`ff0ced20 >> 00000000`00000000 00000000`7efdb000 : win32k!GreCreateDisplayDC+0x1c4 >> fffffadf`c478ec30 fffff800`0102e3fd : 00000000`7d814cc6 fffff97f`ff0ced20 >> 00000000`7d814cc6 00000000`7d814c30 : win32k!GreCreateCompatibleDC+0x77 >> fffffadf`c478ec70 00000000`78b842d9 : 00000000`00000000 00000000`00000000 >> 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x3 >> 00000000`0012edf8 00000000`00000000 : 00000000`00000000 00000000`00000000 >> 00000000`00000000 00000000`00000000 : 0x78b842d9 >> >> >> STACK_COMMAND: kb >> >> FOLLOWUP_IP: >> win32k!HmgAllocateDcAttr+1b6 >> fffff97f`ff0a7742 488b4cc118 mov rcx,qword ptr [rcx+rax*8+18h] >> >> SYMBOL_STACK_INDEX: 3 >> >> SYMBOL_NAME: win32k!HmgAllocateDcAttr+1b6 >> >> FOLLOWUP_NAME: MachineOwner >> >> MODULE_NAME: win32k >> >> IMAGE_NAME: win32k.sys >> >> DEBUG_FLR_IMAGE_TIMESTAMP: 45e6f310 >> >> FAILURE_BUCKET_ID: X64_0x50_win32k!HmgAllocateDcAttr+1b6 >> >> BUCKET_ID: X64_0x50_win32k!HmgAllocateDcAttr+1b6 >> >> Followup: MachineOwner >> --------- >> >> Bye, >> Skybuck. >> >> P.S.: I followed instructions on this link to setup WinDBG properly for >> symbol support ;) >> >> http://forums.majorgeeks.com/showthread.php?t=35246 >> >> Simply add something like: >> >> SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols >> >> to symbol path. >> >> Then symbols will be downloaded... >> >> (I set mine to C:\Tools\WinDBG\WebSymbols :) ) >> >> >> >
I dunno. . .I notice this: PAGE_FAULT_IN_NONPAGED_AREA
perhaps you should read this article here: http://www.osronline.com/article.cfm?id=335 it is (may be?) helpfull in many ways. This amount of errors and warnings actually tells me there is one error that is triggering most of all the rest. Otherwise that machine would NEVER have booted. I think you have a bad installation of something or other, if the 'dumps' isn't teaching you anything, I would start un-installing things - one at a time, until you find. . .whatever. I think that is much faster - memory dumps are specialist info of the most extreme kind, most of us ordinary mortals fall asleep while trying to read them. Things that are listed by name, isn't automatically where the trouble is located, that is just where the system finds the error or where the error surfaces, it may well be happening somewhere else entirely - in fact, the more errors you have, the less is the chance of the origin being named there. Tony. . . [quoted text, click to view] "Skybuck Flying" <spam@hotmail.com> wrote in message .............................................................................news:faumd8$2ae$1@news3.zwoll1.ov.home.nl... > I am definetly no expert... > > Seems like something did a try except where that is not allowed, also seems > resource related ????: > > Microsoft (R) Windows Debugger Version 6.6.0007.5 > Copyright (c) Microsoft Corporation. All rights reserved. > > > Loading Dump File [C:\WINDOWS\Minidump\Mini082707-01.dmp] > Mini Kernel Dump File: Only registers and stack trace are available > > Symbol search path is: > SRV*c:\Tools\WinDbg\WebSymbols*http://msdl.microsoft.com/download/symbols > Executable search path is: > Windows Server 2003 Kernel Version 3790 (Service Pack 2) MP (2 procs) Free > x64 > Product: WinNt, suite: TerminalServer SingleUserTS > Built by: 3790.srv03_sp2_rtm.070216-1710 > Kernel base = 0xfffff800`01000000 PsLoadedModuleList = 0xfffff800`011d5100 > Debug session time: Mon Aug 27 15:17:04.640 2007 (GMT+2) > System Uptime: 0 days 0:27:21.571 > Loading Kernel Symbols > ................................................................ [quoted text, click to view] > Loading User Symbols ****************************************************************************> Loading unloaded module list > .................................................. > *** [quoted text, click to view] > * ****************************************************************************> * > * Bugcheck Analysis > * > * > * > *** [quoted text, click to view] > ****************************************************************************> Use !analyze -v to get detailed debugging information. > > BugCheck 50, {fffffa8804c21090, 0, fffff97fff0a7742, 5} > > > Could not read faulting driver name > Probably caused by : win32k.sys ( win32k!HmgAllocateDcAttr+1b6 ) > > Followup: MachineOwner > --------- > > 1: kd> !analyze -v > *** [quoted text, click to view] > * ****************************************************************************> * > * Bugcheck Analysis > * > * > * > *** [quoted text, click to view] >
> 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: fffffa8804c21090, memory referenced. > Arg2: 0000000000000000, value 0 = read operation, 1 = write operation. > Arg3: fffff97fff0a7742, If non-zero, the instruction address which > referenced the bad memory > address. > Arg4: 0000000000000005, (reserved) > > Debugging Details: > ------------------ > > > Could not read faulting driver name > > READ_ADDRESS: fffffa8804c21090 > > FAULTING_IP: > win32k!HmgAllocateDcAttr+1b6 > fffff97f`ff0a7742 488b4cc118 mov rcx,qword ptr [rcx+rax*8+18h] > > MM_INTERNAL_CODE: 5 > > CUSTOMER_CRASH_COUNT: 1 > > DEFAULT_BUCKET_ID: DRIVER_FAULT > > BUGCHECK_STR: 0x50 > > PROCESS_NAME: bds.exe > > CURRENT_IRQL: 0 > > TRAP_FRAME: fffffadfc478e990 -- (.trap fffffadfc478e990) > NOTE: The trap frame does not contain all registers. > Some register values may be zeroed. > rax=00000000ffffffff rbx=0000000000000888 rcx=fffffa8004c21080 > rdx=fffffa8004c21080 rsi=fffffa80051f6280 rdi=fffff97fff0cda0e > rip=fffff97fff0a7742 rsp=fffffadfc478eb20 rbp=fffffadfc478ecf0 > r8=fffffa8004b9b0c0 r9=5000984210000000 r10=500098421117001d > r11=00000000000007ff r12=0000000000000000 r13=0000000000000000 > r14=0000000000000000 r15=0000000000000000 > iopl=0 nv up ei ng nz ac po nc > win32k!HmgAllocateDcAttr+0x1b6: > fffff97f`ff0a7742 488b4cc118 mov rcx,qword ptr [rcx+rax*8+18h] > ds:fffffa88`04c21090=???????????????? > Resetting default scope > > LAST_CONTROL_TRANSFER: from fffff800010a5416 to fffff8000102e950 > > STACK_TEXT: > fffffadf`c478e8b8 fffff800`010a5416 : 00000000`00000050 fffffa88`04c21090 > 00000000`00000000 fffffadf`c478e990 : nt!KeBugCheckEx > fffffadf`c478e8c0 fffff800`0102d519 : fffffa80`00cad9e0 00000000`00000009 > 00000000`00000000 fffffa80`05009b50 : nt!MmAccessFault+0x395 > fffffadf`c478e990 fffff97f`ff0a7742 : 00000000`00000000 fffff97f`ff0ce249 > fffffa80`0445f780 fffffadf`c478ecf0 : nt!KiPageFault+0x119 > fffffadf`c478eb20 fffff97f`ff0ce004 : 00000000`00000888 00000000`00000000 > 00000000`1e011591 fffffa80`051f6280 : win32k!HmgAllocateDcAttr+0x1b6 > fffffadf`c478eb60 fffff97f`ff0cdf0e : fffffa80`051f6280 fffffa80`051f6280 > fffffadf`cba85cd0 fffffa80`0133b000 : win32k!GreSetupDCAttributes+0x34 > fffffadf`c478eba0 fffff97f`ff0a36c6 : fffffa80`01351010 fffff97f`ff0ced20 > 00000000`00000000 00000000`7efdb000 : win32k!GreCreateDisplayDC+0x1c4 > fffffadf`c478ec30 fffff800`0102e3fd : 00000000`7d814cc6 fffff97f`ff0ced20 > 00000000`7d814cc6 00000000`7d814c30 : win32k!GreCreateCompatibleDC+0x77 > fffffadf`c478ec70 00000000`78b842d9 : 00000000`00000000 00000000`00000000 > 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x3 > 00000000`0012edf8 00000000`00000000 : 00000000`00000000 00000000`00000000 > 00000000`00000000 00000000`00000000 : 0x78b842d9 > > > STACK_COMMAND: kb > > FOLLOWUP_IP: > win32k!HmgAllocateDcAttr+1b6 > fffff97f`ff0a7742 488b4cc118 mov rcx,qword ptr [rcx+rax*8+18h] > > SYMBOL_STACK_INDEX: 3 > > SYMBOL_NAME: win32k!HmgAllocateDcAttr+1b6 > > FOLLOWUP_NAME: MachineOwner > > MODULE_NAME: win32k > > IMAGE_NAME: win32k.sys > > DEBUG_FLR_IMAGE_TIMESTAMP: 45e6f310 > > FAILURE_BUCKET_ID: X64_0x50_win32k!HmgAllocateDcAttr+1b6 > > BUCKET_ID: X64_0x50_win32k!HmgAllocateDcAttr+1b6 > > Followup: MachineOwner > --------- > > Bye, > Skybuck. > > P.S.: I followed instructions on this link to setup WinDBG properly for > symbol support ;) > > http://forums.majorgeeks.com/showthread.php?t=35246 > > Simply add something like: > > SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
What if they don't have the time for it, or are not interested ?
When they get fired at least somebody else can continue thanks to these posts in history ! :) Bye, Skybuck.
[quoted text, click to view] "Skybuck Flying" <spam@hotmail.com> wrote in message news:fb0ldc$385$1@news4.zwoll1.ov.home.nl... > It is not my job to fixes these bugs. > Sure, it is. Unless you give them your machine and pay them to solve it - it's nobody else's job. [quoted text, click to view] > Somebody made a bug somewhere. > So far, I've seen nothing that suggest this has to be a bug, just as I've seen nothing to suggest it couldn't be your own doing. [quoted text, click to view] > These minidumps can provide hints. > Sure, they can. [quoted text, click to view] > That's why I am providing these minidumps, in case some developer is reading > or happens to read this message and finds it interesting and thinks hmmm I > am gonna look into the mentioned code to see if there is something that > could have caused it. > Developers usually aren't allowed to debug code, because they write code and they are pre-determined to believe the code. Debugging is handed over to people who can think like an analytical archeologist, and unless anything essential on your system is Open Source - there is no code to look at. If it is OS then this is not the forum anyway. [quoted text, click to view] > Alternatively recreate the situation debug it and see what happens. > Wonderfull! They would have to do this on the actual machine - publishing a memory dump is practically useless for anything other than guess-work, unless you happen to draw attention to someone who studied a near duplicate yesterday! In which case it would still contain a lot of guess-work. [quoted text, click to view] > Might be difficult to recreate this problem, or maybe not... time will tell. > If for nothing else - it will depend on how much learning you pick up from the event. If you don't care - nobody else will, too. Tony. . .
It's not the job of anyone *here* either to hunt down bugs you're seeing on
your system. Besides, what do you expect any of *us* here to do about them? Nobody here has the source or can release a hotfix. Submit your dumps to MS. If it's somebody's job at all to look after these submissions, they won't claim they don't have time or inclination. It's not up to the individual developers at MS to make those kind of decisions.
[quoted text, click to view] "Skybuck Flying" <spam@hotmail.com> wrote in message news:fb1dtu$ddm$1@news6.zwoll1.ov.home.nl... > What if they don't have the time for it, or are not interested ? > > When they get fired at least somebody else can continue thanks to these > posts in history ! :) > Sorry, but this is not how it works. You can submit the dumps to Microsoft, IIRC the cost is $250 per dump. This is a newsgroup where people try to help one another, but not do their work. -- Don Burn (MVP, Windows DDK) Windows 2k/XP/2k3 Filesystem and Driver Consulting Website: http://www.windrvr.com Blog: http://msmvps.com/blogs/WinDrvr Remove StopSpam to reply
On Wed, 29 Aug 2007 20:39:19 +0200, "Skybuck Flying" <spam@hotmail.com>
[quoted text, click to view] wrote: >Very strange, > >This is a newsgroup hosted by microsoft ? Yes, more or less so, but maybe not the right place (microsoft.public.windows.64bit) to get a specific answer to your problem. That's why I suggested to go to Delphi, if you think it's a Delphi problem. They have a Knowledge Base, newsgroups on Usetnet etc etc. The concentration of specialists which can help you, is much higher there, that's what I'm on about :-)
Very strange,
This is a newsgroup hosted by microsoft ? Bye, Skybuck.
SF> This is a newsgroup hosted by microsoft ?
This is a newsgroup hosted by anyone who decides to carry it in xyr news spool.
Hi, Skybuck.
"Hosted" is the key word. Microsoft just makes it easy (possible?) for us users to communicate with each other. With rare exceptions, Softies don't hang out in these newsgroups, or do so quietly on their own time. Unless you see something like [MS] or [MSFT] in their Sig, they probably are not posting in any official capacity. MVPs are NOT Microsoft employees; we are just volunteers who enjoy helping when we can. It's just us, talking among ourselves, trying to help each other. Like reminding each other when it is time to contact the official Tech Support staff, who ARE paid to help us solve problems with Microsoft products. RC -- R. C. White, CPA San Marcos, TX rc@grandecom.net Microsoft Windows MVP (Running Windows Live Mail beta in Vista Ultimate x64) [quoted text, click to view] "Skybuck Flying" <spam@hotmail.com> wrote in message
news:fb4jb4$bsc$1@news4.zwoll1.ov.home.nl... > Very strange, > > This is a newsgroup hosted by microsoft ? > > Bye, > Skybuck.
I am experiencing a similar error, but the crash occurs whenever various,
unconnected folders crash the Windows Explorer. I have just recently installed an upgrade to Windows Vista Business and this was not occuring before then. [quoted text, click to view] "Skybuck Flying" wrote:
> Make that 28 ! > > System just crashed again while using internet explorer and surfing to the > weblog of the guy that wrote the themed delphi stuff ?! > > The irony ?! Coincendence ?! or this guy one serious bug !? :) Me think > coincedence ! ;) > > Latest crash analysis: > > Microsoft (R) Windows Debugger Version 6.6.0007.5 > Copyright (c) Microsoft Corporation. All rights reserved. > > > Loading Dump File [C:\WINDOWS\Minidump\Mini082707-02.dmp] > Mini Kernel Dump File: Only registers and stack trace are available > > Symbol search path is: > SRV*c:\Tools\WinDbg\WebSymbols*http://msdl.microsoft.com/download/symbols > Executable search path is: > Windows Server 2003 Kernel Version 3790 (Service Pack 2) MP (2 procs) Free > x64 > Product: WinNt, suite: TerminalServer SingleUserTS > Built by: 3790.srv03_sp2_rtm.070216-1710 > Kernel base = 0xfffff800`01000000 PsLoadedModuleList = 0xfffff800`011d5100 > Debug session time: Mon Aug 27 17:39:39.484 2007 (GMT+2) > System Uptime: 0 days 2:21:02.411 > Loading Kernel Symbols > ............................................................................................................................................ > Loading User Symbols > Loading unloaded module list > ................................................... > ******************************************************************************* > * > * > * Bugcheck Analysis > * > * > * > ******************************************************************************* > > Use !analyze -v to get detailed debugging information. > > BugCheck 1000007E, {ffffffffc0000005, fffff80001011ebd, fffffadfc9086a90, > fffffadfc90864a0} > > Probably caused by : ntkrnlmp.exe ( nt!CmpDelayCloseWorker+494 ) > > Followup: MachineOwner > --------- > > 1: 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: fffff80001011ebd, The address that the exception occurred at > Arg3: fffffadfc9086a90, Exception Record Address > Arg4: fffffadfc90864a0, 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!CmpDelayCloseWorker+494 > fffff800`01011ebd 488b4008 mov rax,qword ptr [rax+8] > > EXCEPTION_RECORD: fffffadfc9086a90 -- (.exr fffffadfc9086a90) > ExceptionAddress: fffff80001011ebd > (nt!CmpDelayCloseWorker+0x0000000000000494) > ExceptionCode: c0000005 (Access violation) > ExceptionFlags: 00000000 > NumberParameters: 2 > Parameter[0]: 0000000000000000 > Parameter[1]: 0000000000000008 > Attempt to read from address 0000000000000008 > > CONTEXT: fffffadfc90864a0 -- (.cxr fffffadfc90864a0) > rax=0000000000000000 rbx=fffffa8003281c68 rcx=000000000000132f > rdx=0000000000000008 rsi=00000000ffffffff rdi=fffffa80028bd588 > rip=fffff80001011ebd rsp=fffffadfc9086cb0 rbp=fffffa800412b920 > r8=00000000da81d47a r9=fffffa80028bd590 r10=0000000000000000 > r11=00000000000007ff r12=000000000000132f r13=00000000000001c1 > r14=0000000000000000 r15=0000000000000001 > iopl=0 nv up ei pl nz na pe cy > cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b > efl=00010203 > nt!CmpDelayCloseWorker+0x494: > fffff800`01011ebd 488b4008 mov rax,qword ptr [rax+8] > ds:002b:00000000`00000008=0000000000000000 > Resetting default scope > > CUSTOMER_CRASH_COUNT: 2 > > CURRENT_IRQL: 0 > > ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced > memory at "0x%08lx". The memory could not be "%s". > > READ_ADDRESS: 0000000000000008 > > BUGCHECK_STR: 0x7E > > DEFAULT_BUCKET_ID: NULL_CLASS_PTR_DEREFERENCE > > EXCEPTION_STR: 0x0 > > LAST_CONTROL_TRANSFER: from fffff8000103768a to fffff80001011ebd > > STACK_TEXT: > fffffadf`c9086cb0 fffff800`0103768a : 00000000`00000000 fffff800`011defe0 > fffff800`01012070 fffffadf`cecd3bf0 : nt!CmpDelayCloseWorker+0x494 > fffffadf`c9086d00 fffff800`0124b972 : fffffadf`cecd3bf0 00000000`00000080 > fffffadf`cecd3bf0 fffffadf`c8c83680 : nt!ExpWorkerThread+0x13b > fffffadf`c9086d70 fffff800`010202d6 : fffffadf`c8c7b180 fffffadf`cecd3bf0 > fffffadf`c8c83680 fffff800`011b5dc0 : nt!PspSystemThreadStartup+0x3e > fffffadf`c9086dd0 00000000`00000000 : 00000000`00000000 00000000`00000000 > 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16 > > > FOLLOWUP_IP: > nt!CmpDelayCloseWorker+494 > fffff800`01011ebd 488b4008 mov rax,qword ptr [rax+8] > > SYMBOL_STACK_INDEX: 0 > > FOLLOWUP_NAME: MachineOwner > > MODULE_NAME: nt > > IMAGE_NAME: ntkrnlmp.exe > > DEBUG_FLR_IMAGE_TIMESTAMP: 45d69ab4 > > SYMBOL_NAME: nt!CmpDelayCloseWorker+494 > > STACK_COMMAND: .cxr 0xfffffadfc90864a0 ; kb > > FAILURE_BUCKET_ID: X64_0x7E_nt!CmpDelayCloseWorker+494 > > BUCKET_ID: X64_0x7E_nt!CmpDelayCloseWorker+494 > > Followup: MachineOwner > --------- > > 1: kd> ml > *** WARNING: Unable to verify timestamp for nv4_disp.dll > *** ERROR: Module load completed but symbols could not be loaded for > nv4_disp.dll > *** WARNING: Unable to verify timestamp for CTEDSPSY.DLL > *** ERROR: Module load completed but symbols could not be loaded for > CTEDSPSY.DLL > *** WARNING: Unable to verify timestamp for dump_nvata64.sys > *** ERROR: Module load completed but symbols could not be loaded for > dump_nvata64.sys > *** WARNING: Unable to verify timestamp for vmm.sys > *** ERROR: Module load completed but symbols could not be loaded for vmm.sys > *** WARNING: Unable to verify timestamp for kl1.sys
Opened log file 'c:\debuglog.txt'
Microsoft (R) Windows Debugger Version 6.7.0005.1 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Windows\MEMORY.DMP] Kernel Complete Dump File: Full address space is available ************************************************************ WARNING: Dump file has been truncated. Data may be missing. ************************************************************ Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols Executable search path is: C:\Windows;C:\Windows\system32;C:\Windows\system32\drivers ************************************************************************** THIS DUMP FILE IS PARTIALLY CORRUPT. KdDebuggerDataBlock is not present or unreadable. ************************************************************************** Unable to read PsLoadedModuleList ************************************************************************** THIS DUMP FILE IS PARTIALLY CORRUPT. KdDebuggerDataBlock is not present or unreadable. ************************************************************************** KdDebuggerData.KernBase < SystemRangeStart Windows XP Kernel Version 2600 MP (2 procs) Free x86 compatible Product: WinNt, suite: TerminalServer SingleUserTS Kernel base = 0x00000000 PsLoadedModuleList = 0x8055c700 Debug session time: Tue Sep 18 06:34:07.937 2007 (GMT+1) System Uptime: 0 days 2:59:32.620 ************************************************************************** THIS DUMP FILE IS PARTIALLY CORRUPT. KdDebuggerDataBlock is not present or unreadable. ************************************************************************** Unable to read PsLoadedModuleList ************************************************************************** THIS DUMP FILE IS PARTIALLY CORRUPT. KdDebuggerDataBlock is not present or unreadable. ************************************************************************** KdDebuggerData.KernBase < SystemRangeStart Loading Kernel Symbols Unable to read PsLoadedModuleList GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 CS descriptor lookup failed GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 Unable to get program counter GetContextState failed, 0x80004002 Unable to get current machine context, HRESULT 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 8E, {c0000005, 804ef15f, acfe6b54, 0} ***** Debugger could not find nt in module list, module list might be corrupt, error 0x80070057. GetContextState failed, 0x80004002 Unable to get current machine context, HRESULT 0x80004002 GetContextState failed, 0x80004002 Unable to read selector for PCR for processor 0 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 Unable to get current machine context, HRESULT 0x80004002 GetContextState failed, 0x80004002 Unable to get current machine context, HRESULT 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 Unable to get current machine context, HRESULT 0x80004002 GetContextState failed, 0x80004002 Unable to get current machine context, HRESULT 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 Unable to get current machine context, HRESULT 0x80004002 GetContextState failed, 0x80004002 Unable to get current machine context, HRESULT 0x80004002 GetContextState failed, 0x80004002 Unable to get current machine context, HRESULT 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 Unable to get current machine context, HRESULT 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 Unable to get current machine context, HRESULT 0x80004002 GetContextState failed, 0x80004002 Unable to get current machine context, HRESULT 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 Unable to get current machine context, HRESULT 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 Unable to get current machine context, HRESULT 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002
Don't see what you're looking for? Try a search.
|
June 2003
July 2003
August 2003
September 2003
October 2003
November 2003
December 2003
January 2004
February 2004
March 2004
April 2004
May 2004
June 2004
July 2004
August 2004
September 2004
October 2004
November 2004
December 2004
January 2005
February 2005
March 2005
April 2005
May 2005
June 2005
July 2005
August 2005
September 2005
October 2005
November 2005
December 2005
January 2006
February 2006
March 2006
April 2006
May 2006
June 2006
July 2006
August 2006
September 2006
October 2006
November 2006
December 2006
January 2007
February 2007
March 2007
April 2007
May 2007
June 2007
July 2007
August 2007
September 2007
October 2007
| home · blog · groups | Questions? Comments? Contact the dn |