Author Topic: Win 10 crash  (Read 4650 times)

0 Members and 1 Guest are viewing this topic.

Offline flyingnurse

  • Newbie
  • *
  • Join Date: Jan 2017
  • Posts: 5
  • Karma: 0
    • View Profile
Win 10 crash
« on: January 10, 2017, 10:16:32 AM »
I just installed Windows 10 insider version 15002 and I get a BSOD (green  now), When I try to run  Windows Repair Pro.  I tried to update and it also happens when I try to install the latest version. This is the first time this has happened.
« Last Edit: January 10, 2017, 10:36:53 AM by flyingnurse »

Offline Boggin

  • Global Moderator
  • Hero Member
  • *****
  • Join Date: Jul 2014
  • Posts: 7210
  • Location: UK
  • Karma: 106
    • View Profile
Re: Win 10 crash
« Reply #1 on: January 10, 2017, 02:13:31 PM »
Are you able to download BlueScreenView to see if it created a Memory Dump file ?

http://www.nirsoft.net/utils/blue_screen_view.html

Most BSODs are caused by driver conflicts.

Are you able to revert back to the previous build or is this your first install into the Insider Ring ?

WR as far as I know has only been tested on the current release of 1607.14393.576.

Offline coover

  • Newbie
  • *
  • Join Date: Jul 2012
  • Posts: 44
  • Karma: 0
    • View Profile
Re: Win 10 crash
« Reply #2 on: January 10, 2017, 05:00:02 PM »
Yes, version 3.9.22 (portable) also blue screens my Windows 10 preview build 15002. I doubt it's the fault of the Windows Repair software, but something added by Microsoft (not intentionally) that will not allow it to work. I suspect that the Tweaking.com guys need to look into this, as I doubt that Microsoft will make a change so that this one application will work. Of course there are no problems with the present version of Windows 10, but I suspect that the changes made in 15002 will make it into one of the Windows updates someday soon.

If the techs from tweaking.com wishes to do some testing using my computer with the preview software, a Lenovo T420 Laptop with an i7 CPU and 6 GB RAM, they are welcome to contact me. I do have the latest version of Teamviewer installed. 

Offline Boggin

  • Global Moderator
  • Hero Member
  • *****
  • Join Date: Jul 2014
  • Posts: 7210
  • Location: UK
  • Karma: 106
    • View Profile
Re: Win 10 crash
« Reply #3 on: January 11, 2017, 12:49:57 AM »
I'll ask Shane but as 15002 will probably evolve into something else before being released, this may not be relevant at the moment for the evolution of the program.

Have you notified MS on the feed back.

Have you downloaded BlueScreenView to see if it can tell you what caused the BSOD ?

The TH2 update in November 2015 broke the WR apps reset in the released Win 10 version so that Shane had to take out that repair and it took MS 5 months to resolve that one.

Offline Boggin

  • Global Moderator
  • Hero Member
  • *****
  • Join Date: Jul 2014
  • Posts: 7210
  • Location: UK
  • Karma: 106
    • View Profile
Re: Win 10 crash
« Reply #4 on: January 11, 2017, 01:24:27 AM »
Came across this article which tells you what 15002 has improved upon as well as known issues.

https://blogs.windows.com/windowsexperience/2017/01/09/announcing-windows-10-insider-preview-build-15002-pc/#qOAMBEgu64mKLE0t.97

Offline flyingnurse

  • Newbie
  • *
  • Join Date: Jan 2017
  • Posts: 5
  • Karma: 0
    • View Profile
Re: Win 10 crash
« Reply #5 on: January 11, 2017, 08:23:26 AM »
This is a copy of the crash dump.

Offline Boggin

  • Global Moderator
  • Hero Member
  • *****
  • Join Date: Jul 2014
  • Posts: 7210
  • Location: UK
  • Karma: 106
    • View Profile
Re: Win 10 crash
« Reply #6 on: January 11, 2017, 08:45:09 AM »
I'll PM satrow to see if he can have a look at it who has more experience in BSODs.

Offline satrow

  • Jr. Member
  • **
  • Join Date: Nov 2016
  • Posts: 79
  • Location: Cymru
  • Karma: 2
    • View Profile
Re: Win 10 crash
« Reply #7 on: January 11, 2017, 09:20:29 AM »
I'm not familiar with 0x13a bugchecks (or W8>10), but as far as I can tell, it roughly means: "Memory in the kernel (Windows' core) was fatally overwritten. The kernel allocates a block of heap memory of a given size and *some buggy driver* writes to memory beyond the allocated size of the heap block."

It seems to have been triggered by the graphics subsection (win32kfull.sys default (no compatibility 'fix' needed) Windows graphics driver), though that might also use a 3rd party driver from the GPU/iGPU maker, AMD/ATI, nVidia, Intel etc., which might have been the real trigger.

If you can copy C:\Windows\Minidump\011017-8953-01.dmp to your Desktop, zip it (right-click it and select Send to > Compressed folder) and attach the resulting zip here, I could dig a little deeper.

If you can access W10's Repair options, a System Restore point would be a workaround, or if you can get access by another route and Rollback the graphics driver from Device Manager, that might also 'fix' it.


Offline Shane

  • Top Geek, err uh Dog.
  • Administrator
  • Hero Member
  • *****
  • Join Date: Sep 2011
  • Posts: 9274
  • Location: USA
  • Karma: 136
  • "Knowledge should be shared not hidden."
    • View Profile
    • Tweaking.com
Re: Win 10 crash
« Reply #8 on: January 11, 2017, 09:33:02 AM »
Do you get the blue screen as soon as you try to open my program?

The insider builds normally have a lot of things missing, I have seen problems on insider builds before. I also dont test on the insider builds because of this, but every time a final build comes out there is never any trouble.

The file you posted shows that the system file win32kfull.sys is causing the crash, but it isnt very detailed. I use a program called WhoCrashed to try and get more info on the crash, use that if you are able.

Do me a fav and download and try running my registry backup program. If my Windows repair is crashing when you open it and my registry backup program crashes when you open it then I know it is most likly an API that does the drawing of the icons and graphics in the program, which would be a fault in the OS itself. :wink:

Shane
PLEASE EDIT YOUR TOPIC AND PUT (SOLVED) IF YOU ARE ALL FIXED.

(My weekends belong to my wife and kids, I will try my best to answer all posts daily during the work week)

(About Shane)
Site Owner, Top Admin, Lead Programmer, Wife & 5 kids, Needs a lot more coffee.

When people ask "Why fix what isn't broken?" I reply "To make it better."
"Only a life lived for others is a life worthwhile"
Honor & Respect is all that matters.

Owner & Programmer of: www.pcwintech.com & www.tweaking.com

Offline flyingnurse

  • Newbie
  • *
  • Join Date: Jan 2017
  • Posts: 5
  • Karma: 0
    • View Profile
Re: Win 10 crash
« Reply #9 on: January 12, 2017, 08:59:58 AM »
Trid the reg backup. Had no problem. Heres a copy of the dump.

Offline sadhra

  • Newbie
  • *
  • Join Date: Jan 2017
  • Posts: 1
  • Karma: 0
    • View Profile
Re: Win 10 crash
« Reply #10 on: January 12, 2017, 02:52:48 PM »
Hi There,

I had the same issue after updating to the latest insider build and using the latest windows repair tool.
Found version 3.50 works on the windows insider build 15002

Offline Boggin

  • Global Moderator
  • Hero Member
  • *****
  • Join Date: Jul 2014
  • Posts: 7210
  • Location: UK
  • Karma: 106
    • View Profile
Re: Win 10 crash
« Reply #11 on: January 13, 2017, 05:49:21 AM »
Has anyone updated to 15007 yet to see if the same problem occurs ?

Offline flyingnurse

  • Newbie
  • *
  • Join Date: Jan 2017
  • Posts: 5
  • Karma: 0
    • View Profile
Re: Win 10 crash
« Reply #12 on: January 13, 2017, 11:32:18 AM »
Working on it now.

Offline flyingnurse

  • Newbie
  • *
  • Join Date: Jan 2017
  • Posts: 5
  • Karma: 0
    • View Profile
Re: Win 10 crash
« Reply #13 on: January 14, 2017, 12:36:49 PM »
Installed in version 15007. No problems, works great.  :cheesy:

Offline Boggin

  • Global Moderator
  • Hero Member
  • *****
  • Join Date: Jul 2014
  • Posts: 7210
  • Location: UK
  • Karma: 106
    • View Profile
Re: Win 10 crash
« Reply #14 on: January 14, 2017, 01:34:29 PM »
They break some and then they fix some :D