I’m primary using IBM Clearcase as versioninig system and I have n number of issues ever since I started using with Windows 7. The same issue happened though I copied my source to local folder and debugging from there.

Simply took the dump and attached to WinDBG. !analyze -v had given me following call stack

EXCEPTION_RECORD:  002ad92c -- (.exr 0x2ad92c)
ExceptionAddress: 3fe083d0
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 00000008
   Parameter[1]: 3fe083d0
Attempt to execute non-executable address 3fe083d0

FAULTING_THREAD:  00002718

DEFAULT_BUCKET_ID:  SILENT

PROCESS_NAME:  devenv.exe

ERROR_CODE: (NTSTATUS) 0x80000003 - {EXCEPTION}  Breakpoint  A breakpoint has been reached.

EXCEPTION_CODE: (HRESULT) 0x80000003 (2147483651) - One or more arguments are invalid

NTGLOBALFLAG:  400

APPLICATION_VERIFIER_FLAGS:  0

MANAGED_STACK: !dumpstack -EE
OS Thread Id: 0x2718 (0)
Current frame:
ChildEBP RetAddr  Caller,Callee
002af168 71bc5a99 (MethodDesc 0x714cc250 +0x79 System.Collections.Generic.Dictionary`2+ValueCollection+Enumerator[[System.Int32, mscorlib],[System.__Canon, mscorlib]].MoveNext())

CONTEXT:  002ad948 -- (.cxr 0x2ad948)
eax=59730146 ebx=00000000 ecx=01a72c50 edx=0000001d esi=01a72c50 edi=01a729c8
eip=3fe083d0 esp=002adc2c ebp=002adeb0 iopl=0         nv up ei ng nz na pe nc
cs=001b  ss=0023  ds=0023  es=0023  fs=003b  gs=0000             efl=00010286
3fe083d0 ??              ???
Resetting default scope

WRITE_ADDRESS:  3fe083d0 

FOLLOWUP_IP:
msenv!CDockManager::PruneAllDeadPanes+45
5986cbf6 e97745f8ff      jmp     msenv!CDockManager::PruneAllDeadPanes+0x45 (597f1172)

FAILED_INSTRUCTION_ADDRESS:
+5789952f04fedcac
3fe083d0 ??              ???

PRIMARY_PROBLEM_CLASS:  SILENT

BUGCHECK_STR:  APPLICATION_FAULT_SILENT

LAST_CONTROL_TRANSFER:  from 5986cbf6 to 3fe083d0

IP_ON_HEAP:  3fe083d0
The fault address in not in any loaded module, please check your build's rebase
log at \bin\build_logs\timebuild\ntrebase.log for module which may
contain the address if it were loaded.

IP_IN_FREE_BLOCK: 3fe083d0

STACK_TEXT:
3fe083d0 unknown+0x0
5986cbf6 msenv!CDockManager::PruneAllDeadPanes+0x45
597eef9b msenv!CDockManager::SaveUI+0xb7
598122a5 msenv!CPane::TransitionToDesign+0x46
597f67a9 msenv!CVsShellDebugMgr::m_OnModeChange+0xe6
5976aca3 msenv!CVsUIShell::OnModeChange+0x21
5f4dbfa3 vsdebug!CDebugger::SetShellMode+0x9b
5f4dc04f vsdebug!CDebugger::OnModeChange+0x44
5f4dbeef vsdebug!CDebugger::SetDebugMode+0x69
5f4f2c93 vsdebug!CDebugger::OnExitBreakState+0xaa
5f53cab1 vsdebug!CDebugger::OnDebuggingStopped+0x6e
5f51bcb6 vsdebug!CDebugger::HandleEvent+0x8ae
5f4dbc19 vsdebug!CDebugger::Event+0xef
5f4dbaef vsdebug!sdm::CDebugManager::HandleEvent+0xb5
75eefc8f rpcrt4!Invoke+0x2a
75f54c53 rpcrt4!NdrStubCall2+0x2d6
75e9d936 ole32!CStdStubBuffer_Invoke+0xb6
75e9d9c6 ole32!SyncStubInvoke+0x3c
75e9df1f ole32!StubInvoke+0xb9
75db223c ole32!CCtxComChnl::ContextInvoke+0xfa
75db2131 ole32!MTAInvoke+0x1a
75db30fa ole32!STAInvoke+0x46
75e9de47 ole32!AppInvoke+0xab
75e9dcbb ole32!ComInvokeWithLockAndIPID+0x372
75e9e34c ole32!ComInvoke+0xc5
75db2ed2 ole32!ThreadDispatch+0x23
75db2e91 ole32!ThreadWndProc+0x161
762986ef user32!InternalCallWinProc+0x23
76298876 user32!UserCallWinProcCheckWow+0x14b
762989b5 user32!DispatchMessageWorker+0x35e
76298e9c user32!DispatchMessageW+0xf
75d7d6be ole32!CCliModalLoop::PeekRPCAndDDEMessage+0x4c
75d7d66d ole32!CCliModalLoop::FindMessage+0x30
75d7d57e ole32!CCliModalLoop::HandleWakeForMsg+0x41
75d7d633 ole32!CCliModalLoop::BlockFn+0xc3
75d71117 ole32!CoWaitForMultipleHandles+0xcd
5f513ed6 vsdebug!sdm::CDebugManager::WaitForEvent+0x8a
5f526aa0 vsdebug!CDebugger::WaitForDebuggingToStop+0x51
5f526fed vsdebug!CDebugger::TerminateSession+0x106
5f52711a vsdebug!CDebugger::StopDebugging+0x10a
5f4e8014 vsdebug!CVSDebugPackage::Exec+0x5f9
5974249f msenv!CVSCommandTarget::ExecCmd+0x937
59884617 msenv!FTranslateAcceleratorEx+0x4a3
597581c3 msenv!FTranslateAccelerator+0x49
59758045 msenv!MainFTranslateMessage+0x1a7
59757f2b msenv!CMsoComponent::FPreTranslateMessage+0x72
59757ec0 msenv!SCM_MsoStdCompMgr::FPreTranslateMessage+0xdd
5974152c msenv!EnvironmentMsgLoop+0x159
597fb9bd msenv!CMsoCMHandler::FPushMessageLoop+0x86
597fb94d msenv!SCM::FPushMessageLoop+0xb7
597fb8e9 msenv!SCM_MsoCompMgr::FPushMessageLoop+0x28
597fb8b8 msenv!CMsoComponent::PushMsgLoop+0x28
597fbe4e msenv!VStudioMainLogged+0x482
597f7561 msenv!VStudioMain+0xc1
2f6aaabc devenv!util_CallVsMain+0xff
2f6a78f2 devenv!CDevEnvAppId::Run+0x11fd
2f6a7bf4 devenv!WinMain+0x74
2f6a7c68 devenv!License::GetPID+0x258
765a1114 kernel32!BaseThreadInitThunk+0xe
7791b429 ntdll!__RtlUserThreadStart+0x70
7791b3fc ntdll!_RtlUserThreadStart+0x1b

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  msenv!CDockManager::PruneAllDeadPanes+45

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: msenv

IMAGE_NAME:  msenv.dll

DEBUG_FLR_IMAGE_TIMESTAMP:  488f2b9f

STACK_COMMAND:  .cxr 002AD948 ; kb ; dds 2adc2c ; kb

FAILURE_BUCKET_ID:  SILENT_80000003_msenv.dll!CDockManager::PruneAllDeadPanes

BUCKET_ID:  APPLICATION_FAULT_SILENT_BAD_IP_msenv!CDockManager::PruneAllDeadPanes+45

WATSON_STAGEONE_URL:  http://watson.microsoft.com/StageOne/devenv_exe/9_0_30729_1/488f2b50/unknown/0_0_0_0/bbbbbbb4/80000003/00000000.htm?Retriage=1

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

Luckily a Google search with the call stack has returneda single relevant result about this issue in Microsoft Connect.

Visual Studio 2008 IDE Crashes Returning to Design Mode When Stopping Debugging Native C++ Code

Microsoft has released a patch to resolve this issue. Download

You might have seen the above warning when you open a Visual Studio solution on a mapped network drive. This especially appears when you work with clearcase mapped network drives.

Find for caspol.exe in your Windows\Microsoft.NET\Framework folder.

C:\Windows\Microsoft.NET\Framework\v2.0.50727\CasPol.exe -m -pp off -cg 1.2 FullTrust

This will grant full trust to local intranet code group. Note that caspol tool will apply the security settings for 3.0, 3.5 as well though it’s coming with .NET 2.0

How can I solve this glitch? It’s actually caused by choosing accessibility themes for Gnome. Simply uninstall the accessibility theme and set the standard theme

sudo apt-get remove gnome-accessibility-themes
sudo apt-get install gnome-themes-standard

If you want to tweak your theme further, install Gnome tweak tool

gksudo apt-get install gnome-tweak-tool

Run the tool by entering in terminal window or by pressing Alt+F2

gnome-tweak-tool

I have raised the issues in several forums and being helpless I directly contacted veteran Larry Osterman who leads Windows 7 Audio Development at Microsoft. He promptly responded with the issues with the Dell’s driver issues when working with their class driver. It was back 2009 July. I tried re-installing the driver and it really dint work at that time. But the very same driver when I tried reinstalling of late worked perfectly.

The normal to troubleshoot the problem is to use the Windows Hardware Troubleshooting mechanisms available. But Microsoft troubleshooter wrongly reported that Teefer2 Miniport #8 driver is required to be reinstalled which is actually part of Norton End Point Protection installed in my system. It’s a wrong diagnosis.

Search in Dell website for “SIGMATEL STAC 92XX C-Major HD Audio” and download the latest version of the driver. The one which worked for me can be downloaded from here (Seems it will upgraded automatically on new releases). Thanks Larry for your great help.

The basic process is keep asking “Why” to find the root cause. In a typical case, it’s almost possible to find the root cause within 5 whys. But it doesn’t mean that we’ve to stop analyzing further if we can’t find the root cause within 5 whys. It all depends on the complexity of the problem we’re handling. Here’s a classic example published in business week

A few years ago National Parks managers noticed the Jefferson Memorial was crumbling at an alarming rate. When they asked why, they found out it was being washed far more often than other memorials. For most organizations, the analysis would stop here. The solution is clear, right? Adjust the cleaning schedule to match those of the other memorials.

But they did not stop there. They kept asking why for each problems.

1. This monument is deteriorating faster than any other monuments.
2. Why? – Found that this monument is washed more frequently than other monuments.
3. Why? – The bird droppings are high
4. Why? – There are large population of spiders which the birds were feeding
5. Why? – Increasing of midges in and around the memorial
6. Why? – Midges are mate in a unique quality light between specific timings.
7. Why? – (not really about why midges mate) This unique quality of light created by lighting monument before the dusk.

They reached the real root cause of the problem and preferred the action to change the light timings a bit late. By changing this schedule they were able to reduce the bird droppings by 90%

What we’ve to infer from this example.

• In most of the stages explained above looked like dead end and we felt like to choose trivial solutions but they’ve move forwarded further.
• When we analyze root cause, initially less people will be involved. Participants will increase on exploring more.
• The root cause can’t be found on single stretch. It may take any long depends on the problem, information available and the people involved in it
• The root causes can’t solve the entire problem. It may sometimes solve the entire problem but sometimes it may help us to reduce the damage
• The action we’re taking should be appropriate otherwise it will increase the damage.
• It’s required to make sure that the root cause was right before investing time and money in it.

But before starting all these we’ve to ask the fundamental question, do we really need to solve this problem? To solve the problem, it required to analyze the severity, priority, cost and resources available.

Once we decide proceed, we can employ Fish Bone diagram or Ishikawa diagram to effectively map the whys. The causes are grouped in the main groups and formed through brain storming sessions. For e.g. in the manufacturing industry basically we can classify the causes under 8M’s.

• Machine (technology)
• Method (process)
• Material (Includes Raw Material, Consumables and Information.)
• Man Power (physical work)/Mind Power (brain work): Kaizens, Suggestions
  Measurement (Inspection)
• Milieu/Mother Nature (Environment)
• Management/Money Power
• Maintenance

I am not explaining how to create Fishbone diagram, but it’s really powerful enough to map and find the problems root causes. So keep asking “Why” and when it make sense, stop asking “Why” and proceed to fix the problems.

Somehow I managed to get the Windows 7 boot USB to repair my startup for Windows. Again it had happened. The Master Boot Record wasn’t promptly recognized by Windows. It says no problems at all with your Windows Installation. What’s next. I have tried several options to like Fixing the MBR with command line and exporting and importing the boot record and importing it again to corrupt the MBR and tried the repair again. No ways!

Finally how I had to recreate the MBR. How do we do that? (BTW, do this at your own risk. Don’t blame me later)

1. Insert your bootable DVD/USB or Startup repair disc to your computer.
2. Choose Recovery options.
3. Click on Startup Repair and check if it works.

If doesn’t work

4. Open the command window and enter the following commands

bootrec.exe /fixmbr
bootsect.exe /nt60 all /force
bootrec.exe /rebuildbcd

Now you’re done. Reboot your PC and see if it works. Under Windows Vista, you will have to change to X:\boot\ folder to access bootrec and bootsect executable.

See a list of popular magic debug values (retrieved from Wikipedia)

See Wikipedia for more details – http://en.wikipedia.org/wiki/0xDEADBEEF#Magic_debug_values

Try different USB port

Insert the device in another USB port. Try without USB extenders.

Re-Synchronize the receiver

Check for constant green light on the wireless transmitter/receiver after plugging in. Check the red light under mouse blinks well. Push the reset buttons on both mouse and receiver after connecting it to the power. Remove and insert if necessary. Most of the synchronization problems should be resolved by this step.

Image Taken from Microsoft.com

Remove and Insert batteries again

Remove the undercover and insert the battery again. Also ensure that it’s not a drained battery. Always use good quality batteries with your mouse.

Interference

There’s a chance that other wireless devices, mobile phones, radios etc. interfering wireless signals. Take required steps to avoid them.

Upgrade your software

Especially when working with old version of Windows, the latest drivers may not be available. Download it from product vendor’s website. Windows 7 and Vista support most of the latest hardware. Download the drivers from here, if you’re using Microsoft Wireless Mouse of Keyboard

Try This in different computer

Borrow your friend’s computer for a minute and check if it works!

I’ve received the box pre-installed with Japanese version of Windows 7 Starter Edition. I’ve not opted for an external drive when I purchased. So I had prepared the image file using Magic ISO. Dumping in ISO image format is better as it’s a universally accepted format.

There are two methods to prepare the USB disk.

1. Using USB to DVD tool from Microsoft Store

Microsoft realized your needs and they’ve provided a safe method to prepare the bootable USB from ISO. Prepare the ISO image using magic disc. Download the tool from Microsoft website. Now things are pretty straight forward. Just go through the guided steps to create the bootable USB stick

Once you complete preparing the USB, reboot your computer and press F12 (for Dell Laptops only) in the POST screen to choose the boot device. From that opt for USB Storage Device. Go ahead with the simplest Windows Installation we’ve ever seen in Windows history.

2. Using diskpart and xcopy (or simple windows copying)

This step must be done very carefully as it may damage your own HDD if it used wrong. Do this at your own risk.

First you’ve to plugin the USB stick and open the command line tool diskpart from Run Window or from command prompt.

You can see a similar window as displayed above. Note that Windows Vista or Windows 7 may ask for administrator privilege to run this application. Do the following steps

• list disk – this will list the attached physical disks connected to the system
• select disk # – select the preferred disk. Here you must be very careful. Make sure that you’ve chosen the right disk. Otherwise you may lose your data. replace # the number listed ### column of list disk command
• clean – clear the configuration information
• create partition primary – Create the partition for the stick
• format fs=fat32 quick – note that if you’ve not opted for quick, you will have to wait till the OS finish the true formatting of entire disk.
• assign – assign a drive letter for the drive to access through explorer

You’ve prepared a clean USB device. Now mount the ISO image or using magic disc or insert the DVD. Simply copy paste the contents of the folder to the prepared USB device. You can also use xcopy or robocopy if you’re preferring the command line tools.

You can see a video demonstration of this in Microsoft Technet

The next step was to prepare the bootable USB stick from the and created the using my other personal computer to prepare the bootable USB drive. Reboot your computer and press F12 (for Dell Laptops only) in the POST screen to choose the boot device. From that opt for USB Storage Device.

note that the second method has failed many times even the USB started booting. I don’t know if it was the problem with my USB stick. Always try to it with the first method mention.

The worst thing, is that we can’t know the status of caps lock. This is particularly makes problems when you type password as you can’t see the original text. You have to try the caps lock in some editable windows and back to the password field.

Even those Dell laptops which has all indicators including caps lock, it used to display ON/OFF status in a quick small message text on the right bottom side. With Dell Mini you can make use of this handy tool to know the current capslocks status.

The disadvantage is that it will be popped up only when we hit the caps lock key. It’s hard to know the current caps lock status without changing the current capslock state.

But it’s still better then a total blank

Download the system tools from Dell Mini 10v Driver Download Page. I’ve given direct link to Dell Caps Lock Application (this URL may changed by Dell in Future or on upgrade)

Once you finish installing this, you can see something has below on hitting the caps lock key.

ON –

OFF –