"fischermx@gmail.com" wrote:

> Environment:
> Microsoft Visual Studio 2005
> Version 8.0.50727.762 (SP.050727-7600)
> Microsoft .NET Framework
> Version 2.0.50727
> Microsoft Visual Studio 2005 Professional Edition - ENU Service Pack 1
> (KB926601)
> Hotfix for Microsoft Visual Studio 2005 Professional Edition - ENU
> (KB933608)
> Windows XP, SP2.
>
>
>
> I have a Dell computer, Core 2 Duo 2.4Ghz, 2GB of RAM, plenty of hard
> disk space, which I use for development.
> Since May 23, I've been having intermitent BSOD while:
> - Loading Visual Studio 2005 (SP1).
> - Compiling an Asp.Net application in VS 2005.
> - Browsing an asp.net application hosted in localhost.
> - Loading SSMSEE
>
>
> So, I got the dump files pointing to devenv.exe, aspnet_wp.exe,
> mscorsvw.exe or SqlWb.exe.
>
> I have already asked in several places, but I'm not being able to fix
> the problem yet.
> So, far, I already.
> - Ran MemTest86, cycled all night and found no errors. Several times.
> - Ran the Dell 32Bit diagnostics utilities. Full tests, found no
> errors. I ran this several nights during this last 3 weeks.
> - Antivirus is updated, no virus were found.
> - Checked for spyware too, no spyware was found.
> - Hard disk already checked for errors.
> - Already tried removing some hardware, like audio and modem.
> - Memories were moved from one slot pair to another.
> - Tried by disabling page file.
> - I already uinstalled VS2005, SqlServer Express, .Net Framework 2.0
> and reinstalled everything, then applyed patches.
> - Ran chkdsk /f /r, several times.
>
>
> The strange thing, is that I can load the computer to hell, by opening
> PhotoShop, PaintShop Pro, burn a DVD with Nero, compile a project with
> Nero Express, and open any possible software in my computer. The error
> is not raised under this stress. But as soon as I open VS2005 it
> blows !
>
>
> The last minidump output looks like:
>
> Debugging Details:
> ************************************************************************
> Could not read faulting driver name
> READ_ADDRESS: e21de000
>
> FAULTING_IP:
> +ffffffff896993de
> 896993de 668b08 mov cx,word ptr [eax]
> MM_INTERNAL_CODE: 1
> CUSTOMER_CRASH_COUNT: 1
> DEFAULT_BUCKET_ID: DRIVER_FAULT
> BUGCHECK_STR: 0x50
> PROCESS_NAME: SqlWb.exe
> LAST_CONTROL_TRANSFER: from 805ceb54 to 896993de
>
> STACK_TEXT:
> WARNING: Frame IP not in any known module. Following frames may be
> wrong.
> 9429abe0 805ceb54 865a97f8 00000b2c 9429ac20 0x896993de
> 9429ac00 805affdf 865a97f8 00000b2c 9429ac20 nt!
> PsCallImageNotifyRoutines+0x36
> 9429ac48 805b0abc 87b074c8 67af0000 9429ad18 nt!MiMapViewOfImageSection
> +0x4c1
> 9429aca4 805b0e81 00000004 87b07110 9429ad18 nt!MmMapViewOfSection
> +0x13c
> 9429ad34 805409ac 000006dc ffffffff 05b8daac nt!NtMapViewOfSection
> +0x2bd
> 9429ad34 7c90eb94 000006dc ffffffff 05b8daac nt!KiFastCallEntry+0xfc
> 05b8dac8 00000000 00000000 00000000 00000000 0x7c90eb94
>
>
> STACK_COMMAND: kb
> FOLLOWUP_IP:
> nt!PsCallImageNotifyRoutines+36
> 805ceb54 56 push esi
>
> SYMBOL_STACK_INDEX: 1
> SYMBOL_NAME: nt!PsCallImageNotifyRoutines+36
> FOLLOWUP_NAME: MachineOwner
> MODULE_NAME: nt
> IMAGE_NAME: ntkrpamp.exe
> DEBUG_FLR_IMAGE_TIMESTAMP: 45e5484a
> FAILURE_BUCKET_ID: 0x50_nt!PsCallImageNotifyRoutines+36
> BUCKET_ID: 0x50_nt!PsCallImageNotifyRoutines+36
> Followup: MachineOwner
> ************************************************************************
>
>
>
> Previous to that error it was this:
>
> ************************************************************************
> 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: e4b74000, memory referenced.
> Arg2: 00000000, value 0 = read operation, 1 = write operation.
> Arg3: 896943de, If non-zero, the instruction address which referenced
> the bad memory
> address.
> Arg4: 00000001, (reserved)
>
> Debugging Details:
> ------------------
>
> Could not read faulting driver name
> READ_ADDRESS: e4b74000
>
> FAULTING_IP:
> +ffffffff896943de
> 896943de 668b08 mov cx,word ptr [eax]
> MM_INTERNAL_CODE: 1
> CUSTOMER_CRASH_COUNT: 2
> DEFAULT_BUCKET_ID: DRIVER_FAULT
> BUGCHECK_STR: 0x50
> PROCESS_NAME: devenv.exe
> LAST_CONTROL_TRANSFER: from 805ceb54 to 896943de
>
> STACK_TEXT:
> WARNING: Frame IP not in any known module. Following frames may be
> wrong.
> 90aebbe0 805ceb54 8609c9e8 000006b8 90aebc20 0x896943de
> 90aebc00 805affdf 8609c9e8 000006b8 90aebc20 nt!
> PsCallImageNotifyRoutines+0x36
> 90aebc48 805b0abc 89609ad0 6c090000 90aebd18 nt!MiMapViewOfImageSection
> +0x4c1
> 90aebca4 805b0e81 00000004 89b11110 90aebd18 nt!MmMapViewOfSection
> +0x13c
> 90aebd34 805409ac 00000968 ffffffff 001280f4 nt!NtMapViewOfSection
> +0x2bd
> 90aebd34 7c90eb94 00000968 ffffffff 001280f4 nt!KiFastCallEntry+0xfc
> 00128110 00000000 00000000 00000000 00000000 0x7c90eb94
>
> STACK_COMMAND: kb
> FOLLOWUP_IP:
> nt!PsCallImageNotifyRoutines+36
> 805ceb54 56 push esi
>
> SYMBOL_STACK_INDEX: 1
> SYMBOL_NAME: nt!PsCallImageNotifyRoutines+36
> FOLLOWUP_NAME: MachineOwner
> MODULE_NAME: nt
> IMAGE_NAME: ntkrpamp.exe
> DEBUG_FLR_IMAGE_TIMESTAMP: 45e5484a
> FAILURE_BUCKET_ID: 0x50_nt!PsCallImageNotifyRoutines+36
> BUCKET_ID: 0x50_nt!PsCallImageNotifyRoutines+36
> Followup: MachineOwner
> ************************************************************************
>
>
> Some people have pointed me a memory error, but different tests shows
> memory is OK.
> And the main question is why it reboots ONLY on Visual Studio related
> programs?
> May be VS and the .Net 2.0 access memory parts which the other
> programs does not?
>
>
> Please, any advise, but really, ANY advise is very welcome. I have not
> called Dell support yet, because I can't reproduce the error
> outside .Net related programs.
>