With the blueScreenView I found out that it have to do with 
ntoskrnl.exe+75bc0. In the internet people write that it can be have to 
do with drivers like graphic driver, or with the virus program. I 
exclude the msys folders now from the virus program and I make driver 
updates.
I think not the the blue screen comes because of a stress out, in the 
office we makes many times 3d renderings and then the computers runs 
days with 100% cpu capacity and lots of ram usage. Maybe the writing and 
reading on the HD is a problem, because of the many little files, but 
under msys1 I also don't had that problem. It is not so so often, so is 
not so a big pain.

Have a nice evening!

Jonathan


Am 23.05.2014 01:08, schrieb Ray Donnelly:
> On Thu, May 22, 2014 at 7:35 PM, Alexpux <[email protected]> wrote:
>> 22 мая 2014 г., в 22:15, Jon bae <[email protected]> написал(а):
>>
>>> Hello everybody,
>>> I am not sure that it makes sense to report this, but some times I get
>>> bluescreens when I compile tools. I have not read what was staying on
>>> the bluescreen, next time I will look on it.
>>> But it is not only here on my home computer, it was also in my office.
>>> And both have a lot of ram and good cpus. Here on my home laptop I have
>>> 8 threads and I compile with 6 (24gb ram). I was thinking it is happen
>>> when I have two mintty shells open and compile parallel, but it was now
>>> also happen with only one instance.
>>>
>>> Best Regards!
>>>
>>> Jonathan
>>>
>>>
>> Yeah I’m also often have BSOD’s when build huge packages like Qt.
>> Someone need to debug it who know how to do it. I’m not well with it.
>>
> On the other hand I have never ever had a single BSOD using or
> developing MSYS2 across multiple computers with varying performance
> characteristics, compiling lots of big packages with as many jobs as I
> possibly can, often while running Arch Linux in a VM and often also
> building the packages in a 28GB RAM disk. I honestly couldn't stress
> my machines more if I tried.
>
> BSOD to me means overheating, dodgy drivers or some OS corruption.
>
> Alexey, you run in a VM don't you? Would it be possible to spin up a
> new VM image and try there?
>
> Did you check your Windows Event logs to see if anything gets reported there?
>
>> Regards,
>> Alexey.
>>>
>>>
>>> ------------------------------------------------------------------------------
>>> "Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE
>>> Instantly run your Selenium tests across 300+ browser/OS combos.
>>> Get unparalleled scalability from the best Selenium testing platform 
>>> available
>>> Simple to use. Nothing to install. Get started now for free."
>>> http://p.sf.net/sfu/SauceLabs
>>> _______________________________________________
>>> Msys2-users mailing list
>>> [email protected]
>>> https://lists.sourceforge.net/lists/listinfo/msys2-users
>>
>> ------------------------------------------------------------------------------
>> "Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE
>> Instantly run your Selenium tests across 300+ browser/OS combos.
>> Get unparalleled scalability from the best Selenium testing platform 
>> available
>> Simple to use. Nothing to install. Get started now for free."
>> http://p.sf.net/sfu/SauceLabs
>> _______________________________________________
>> Msys2-users mailing list
>> [email protected]
>> https://lists.sourceforge.net/lists/listinfo/msys2-users


------------------------------------------------------------------------------
"Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE
Instantly run your Selenium tests across 300+ browser/OS combos.
Get unparalleled scalability from the best Selenium testing platform available
Simple to use. Nothing to install. Get started now for free."
http://p.sf.net/sfu/SauceLabs
_______________________________________________
Msys2-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/msys2-users

Reply via email to