BSOD using TeamViewer, error 0x00000050

ZosoCoder · 14 Apr 2015

Hello,

I have a Dell XPS 15z with Win7 x64. Lately my laptop startup has been ridiculously slow. Explorer is sometimes slow to respond, and have had hardware issues in the past. (NICs and keyboard, though nothing I think is really related to this BSOD). I'm worried my HDD may be failing soon, and my battery life is around 60% according to Dell's preboot diagnostic tool.

I was using TeamViewer to access my Home PC. I only had Outlook 2013 running and a couple of tabs open on Chrome. While working on remote PC, the BSOD just popped up without warning and the fans started spinning very fast. I held the power button down and restarted. No BSOD for several hours now, though I haven't used TeamViewer since. I was running a VM on the remote machine when my laptop crashed, if that matters.

No new hardware, last BSOD issue I had seemed to be caused by some AV software which I removed then.

I have attached the mini dump file for review. Please let me know what me be causing this or how I can figure this out using mini dump file. I do not know how to read it.

Event-Viewer:

- System

- Provider

[ Name] Microsoft-Windows-Kernel-Power
[ Guid] {331C3B3A-2005-44C2-AC5E-77220C37D6B4}

EventID 41

Version 2

Level 1

Task 63

Opcode 0

Keywords 0x8000000000000002

- TimeCreated

[ SystemTime] 2015-04-14T18:21:44.072023800Z

EventRecordID 115375

Correlation

- Execution

[ ProcessID] 4
[ ThreadID] 8

Channel System

Computer Tony-XPS15z

- Security

[ UserID] S-1-5-18

- EventData

BugcheckCode 80
BugcheckParameter1 0xfffff900c2af7000
BugcheckParameter2 0x0
BugcheckParameter3 0xfffff96000136784
BugcheckParameter4 0x0
SleepInProgress false
PowerButtonTimestamp 0

Thanks!

Arc · 15 Apr 2015

Click on button below ....

It will download the DM log collector. Right click on the application and run as administrator. It will generate a .zip file on your desktop. Upload the .zip.
Screenshots and Files - Upload and Post in Seven Forums

ZosoCoder · 15 Apr 2015

Zip file attached. Thanks!

Arc · 16 Apr 2015

Code:

BugCheck 50, {fffff900c2af7000, 0, fffff96000136784, 0}


Could not read faulting driver name
Probably caused by : win32k.sys ( win32k!memcpy+b4 )

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

Dumps are not very much informative.

Try reducing the startup items? Windows does not need any other program to auto start with it, but the auto start programs often conflicts and causes various problems including BSODs.

Click on the Start button
Type “msconfig (without quotes), click the resulting link. It will open the System Configuration window.
Select the “Startup” tab.
Deselect all items other than the antivirus and CyHidWin.
Apply > OK
Accept then restart.

See it changes anything there or not. Also, failing memory is a major cause of stop 0x50. So have a test. Test your RAM modules for possible errors.

How to Test and Diagnose RAM Issues with Memtest86+

Run memtest86+ for at least 8 consecutive passes.

If it start showing errors/red lines, stop testing. A single error is enough to determine that something is going bad there.

Let us know the result.

ZosoCoder · 22 Apr 2015

Apologies for the late reply. I finally had a chance to run memtest86+ for 9 passes. No errors.

Arc · 23 Apr 2015

Any more BSODs during this time, after cleaning up the startup?

ZosoCoder · 23 Apr 2015

I did get the same BSOD stop error when running TeamViewer again. It has not happened during any other task or when idle.
Seems like it might be TeamViewer related? It doesn't happen every time, though. Only when running a VM on remote machine. Maybe the attached files will shed some light on this? If not, I guess I'll just have to stop using TV to access my VMs on remote machine.

Thanks

Arc · 23 Apr 2015

Crash dumps are not saying anything in this line ....

Code:

BugCheck 50, {fffff900c2a59000, 0, fffff960000d6784, 0}


Could not read faulting driver name
Probably caused by : win32k.sys ( win32k!memcpy+b4 )

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

But it confirms that teh BSOD occurred during teamviewer.

Code:

PROCESS_NAME:  TeamViewer.exe

I will see if I can manage some more help for you.

NoelDP · 23 Apr 2015

STOP 50 errors are often caused by rootkits

I note that the Product Key is consistent with the Key being an MSDN one - from where did you acquire this license/Product Key?Where did you get the install media from?

ZosoCoder · 23 Apr 2015

I got the key and install media through my college a few years back when working on my CS major. We had MSDN accounts where I obtained my Windows and Office programs.