Windows 7: Random BSOD while develloping with VS2010

Washu · 03 Feb 2015

Hello All

I have an random BSOD while develloping with Visual Studio 2010, please note that I'm using a virtual computer (Vmware) with Kaspersky and Windows 7 Pro.

Can you help me please ?

Aurélien.

essenbe · 03 Feb 2015

Hello, Washu. I'll try to help you, although I don't use or know much about VS although I do know some about VMware Player and Workstation. What I am getting from your dump files is

Code:

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: fffff96000177663, memory referenced.
Arg2: 0000000000000008, value 0 = read operation, 1 = write operation.
Arg3: fffff96000177663, If non-zero, the instruction address which referenced the bad memory
 address.
Arg4: 0000000000000007, (reserved)

and

Code:

STACK_COMMAND:  kb
FOLLOWUP_IP: 
win32k!fnHkINLPMSG+1d3
fffff960`00177663 488905e6002400  mov     qword ptr [win32k!gptiCurrent (fffff960`003b7750)],rax
SYMBOL_STACK_INDEX:  3
SYMBOL_NAME:  win32k!fnHkINLPMSG+1d3
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: win32k
IMAGE_NAME:  win32k.sys
DEBUG_FLR_IMAGE_TIMESTAMP:  52f4357b
IMAGE_VERSION:  6.1.7601.18388
FAILURE_BUCKET_ID:  X64_0x50_BAD_IP_win32k!fnHkINLPMSG+1d3
BUCKET_ID: X64_0x50_BAD_IP_win32k!fnHkINLPMSG+1d3
ANALYSIS_SOURCE:  KM
FAILURE_ID_HASH_STRING:  km:x64_0x50_bad_ip_win32k!fnhkinlpmsg+1d3

And from the other one

Code:

Use !analyze -v to get detailed debugging information.
BugCheck 50, {fffff960000b5464, 8, fffff960000b5464, 7}
*** WARNING: Unable to verify timestamp for klif.sys
*** ERROR: Module load completed but symbols could not be loaded for klif.sys
Could not read faulting driver name
Probably caused by : memory_corruption
Followup: memory_corruption

The memory corruption is the more serious one because it can make everything else in the dump files not trustworthy. So, to begin with,

Please Run Memtest86+

Information

Please download from this site only http://www.memtest.org/ in the middle of the page are the Download links, you can download the ISO.zip or the Auto USB Flash Drive installer.zip

Extract the Zip file. If you chose the ISO image, burn it to a CD using Windows Disk Image Burner or any Image burner you may have. If you downloaded the Auto USB installer, extract it, insert your USB 2.0 Flash Drive and take note of the drive letter. Run the installer, select the Flash Drive Letter, check the format box and press next. It will install memtest86+ to a flash drive. You can use either V4.20 or V5.01. Boot from your selected media. If you use V5.01 it will tell you to press certain buttons at the start, please press no buttons. The test will begin on it's own and continue to run until you stop it. It needs to run for 8 complete passes or until you receive an error. If you receive an error, stop the test. Even 1 error is a fail. Each pass tests a different part of the ram and each of the 10 tests in each pass tests something different. It takes a minimum of 8 passes to completely test the ram, more passes are better. It is quite a long test and will take several hours depending on how much ram you have. Due to the time length it is best to run overnight. If you have any questions, please do not hesitate to ask

Washu · 04 Feb 2015

First of all, thank you for your quick answer.

The VM is hosted on a ESXi server with other VM which don't have this problem, so I suppose this is not a memory issue no ?

What do you think about the following message ? Do you think it's problem with the IP stack ?
"X64_0x50_BAD_IP_win32k!fnHkINLPMSG+1d3"

essenbe · 04 Feb 2015

I've never seen that issue, but it looks like what you said, a problem with the IP or IP Stack, would be my guess. Are you sure you have it installed correctly?

Washu · 04 Feb 2015

Yes and driver are uptodate, but I'm using Kaspersky and I think he is protecting the IP stack by installing his own driver, so maybe there is problem or a conflict with him.