Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Saturday, January 9, 2016 4:21 PM | 1 vote
After upgrading to Windows 10, about every 2 minutes the Event 1002 from source Winlogon is being generated. The screen temporarily goes black and the desktop refreshes. Obviously, this prevents stable usage. I had previously researched the screen flashing issue under Windows 10 and followed the suggestions to stop the Problem Reports and Solution Control Panel Support Service and the Windows Error Report Service. The problem is still occurring. I searched for Event 1002 in Windows 10 and did not find any hits. I updated the drivers and BIOS on my HP Pavilion DV7-6157cl laptop prior to upgrading. Any suggestions for debugging this issue?
All replies (6)
Monday, January 11, 2016 5:03 PM ✅Answered | 2 votes
Hi,
First enable app crash dump collection by copying following words into notepad, saving it as dump.reg and importing it:
** Windows Registry Editor Version 5.00**
** [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Windows Error Reporting\localdumps\winlogon.EXE]**
** "DumpFolder"=hex(2):63,00,3a,00,5c,00,63,00,72,00,61,00,73,00,68,00,64,00,75,\**
** 00,6d,00,70,00,73,00,00,00**
** "DumpCount"=dword:00000010**
** "DumpType"=dword:00000001**
** "CustomDumpFlags"=dword:00000000**
Then, repro the issue. If crash issue appeared, please find the crashdump file under c:\
To further help you, please upload this file into Onedrive and shared the link here.
Also, you can try to analyze dump by yourself if you would like to：
How to analyze app crash dump file:
http://blogs.technet.com/b/askperf/archive/2007/05/29/basic-debugging-of-an-application-crash.aspx
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com.
Saturday, January 9, 2016 7:00 PM | 1 vote
Try a How to perform a clean boot in Windows to rule \ find third party software that maybe causing it.
If you have any third party software that does explorer extensions (adds to right click etc) try uninstalling that as a guess.
Search the drive for dmp files. Looking for dump (dmp) file for the crash. From a command prompt (right click start choose Command Prompt) is a relativity quick way to do it;
cd \
(to move to root of the drive)
dir *.dmp /s
(search including subfolders) sorry I am not aware of the specific folders to look in on Windows 10. Looking for recent ones. If you find ones that the times look right for this issue zip up the most recent three and upload to a OneDrive \ Google Drive \ DropBox type of service and post the link (or text of the link) here so they can analysed.
Monday, January 11, 2016 3:04 AM | 1 vote
I will give the clean boot a try. I did not find any .dmp files that have occurred during the time in question.
Thanks for the suggestions.
Wednesday, January 20, 2016 10:14 AM | 1 vote
Hi，
Is there any update on your issue?
Have you taken time to try my suggestions?
Just to clarify current status of your issue, for further research, please upload the log file I mentioned above here.
Wait for your response.
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com.
Friday, January 29, 2016 11:00 PM | 1 vote
Analysing an explorer crash dump file the debugger pointed me to an exception thrown by ODBCCP32. A quick search showed me that similar issues had been experienced after an upgrade from W7 to W8. Copied below is the W8 solution that I found and discovered that it works on W10 too. Explorer was crashing too frequently to rename as described. I had to launch a CMD window and use the command "rename ODBCCP32.CPL ODBCCP32.old". Restart and problem gone!
>>>>
Solved, from Microsoft forum;
The problem may be the ODBCCP32.CPL which is an older control panel applet not native to Windows 8.
Go to the C:\Windows\System32 folder and right-click the ODBCCP32.CPL and rename the ODBCCP32.CPL to ODBCCP32.old
Log out and then log back in.
<<<<<<
Monday, February 8, 2016 1:12 PM | 2 votes
I've tested this reg on my Windows 10 Enterprise and already a couple of times some applications crashed but there no dmp files in C:\