Loading...
> >

Anyone running onto this error pc ran into...

Philippi_ChildPhilippi_Child Posts: 658
in The Commons

hey folks

has anyone else experienced this error on windows 10 64-bit;

”Your pc ran into a problem and needs to restart we’ll gather some information and then we’ll restart it for you!”

this is the second time I’ve has this error and I don’t think this had happen until that October update. I wasn’t doing anything but surfing the net. Anyone else having this fun?

 

thanks

Comments

  • AtiAti Posts: 9,185

    I've just had this issue with a slightly overheating CPU.

  • Dim ReaperDim Reaper Posts: 687

    As is usual with Windows it could be just about anything and the cryptic and vague error messages are of no help.

    A few months ago I kept getting random freezes where programs would work, but I couldn't save anything or load new programs.  The error that you described also popped up occasionally.  After a LOT of trial and error, I found out that the cause of the crashes was that I use Core Temp on startup, but when using Daz Studio or Vue, I also load up MSI Afterburner to monitor the GPU temperatures and fan speeds.  On my system at least, they don't like each other.  The solution is to close Core Temp shortly after startup and before using MSI Afterburner.  Since then, I've had no crashes.  I'm not saying that is your problem, but just illustrating how random conflicts can be.

    I'd say that your first course of action should be to click the START button, then type view reliability history and then load the view reliability history program.  This gives a detailed timeline of crashes and other events over several days or weeks and might help you to locate what is causing the crashes.

  • frankrblowfrankrblow Posts: 2,052

    I often get this when working with dForce. I think that's what happens when Studio is asked to do something that's not covered by its programming.

  • ColdrakeColdrake Posts: 236

    Try checking your system files.

  • joseftjoseft Posts: 310

    That is the Windows 10 version of the Blue Screen of Death. or BSOD as it is referred to. 

    BSOD's can be tricky to diagnose, there are many many many things that can cause them. Hardware issues and driver issues/conflicts are probably the two most common. The BSOD screen doesnt give you as much information in Windows 10 as it did in prior versions of Windows. What you were doing when the BSOD occured can help point you in the right direction sometimes, but can be harder when doing something simple like surfing the net. 

    I have not used the reliability history function Dim Reaper mentioned above, but the Event Viewer also gives details on crashes. Another alternative that i use is a program called Blue Screen Viewer, it looks for the dump (log) files that windows creates every time it crashes, and reads them in detail. It will tell you the BSOD error code that you can then paste into google to kick off your troubleshooting. It will be a phrase seperated by underscores like this "PAGE_FAULT_IN_NONPAGED_AREA" followed by a 'stop code', which looks something like this: 0x00000050. The phrase and the stop code will vary, depending on the cause of the BSOD. The example i gave is one that i have had a couple of times in the past, and was caused by a faulty stick of RAM. But getting that exact code does not necessarily mean you have a bad stick of ram, that is just a common factor that produces that code. 

    Given you did not have this until a windows update, the problem is probably driver or software related. But you should still get the BSOD codes to point you in the right direction. 

  • Philippi_ChildPhilippi_Child Posts: 658

    When this happened all I had open was the edge browser. When the error got to 100% it hung and never restarted so I just manually restarted the PC and everything booted up like normal.  I'm not a technical person and when reading things like view relability history and all the error codes it's like learning Russian. I did have a graphic driver install that failed a while back but I thought it was cleared up. I broke my rule of not uninstalling all of the older driver. I also think, as many have, that these MS updates mess graphic drivers up and I've read you have to competely uninstall every aspect of the graphic drivers or win 10 just goes back and install the old driver info that was stored in the files of the C:/ drive. 

    The BSOD error was SYSTEM_THREAD_EXCEPTION_NOT_HANDLED 0x0000007E I've read that this error is due to a corrupt driver which from what I've read is most common. Since I had that driver install failure a few months ago maybe this is the issue, the driver or WIN 10 overwritting the driver I had installed during the update. 

    At any rate thanks everyone for your insight.

Sign In or Register to comment.