mIRC Home    About    Download    Register    News    Help

Print Thread
v7.56 about crash #265735 10/07/19 07:50 PM
Joined: Jan 2007
Posts: 16
C
chili_beta Offline OP
Pikka bird
OP Offline
Pikka bird
C
Joined: Jan 2007
Posts: 16
I don't know if it's just me, but after upgrading to v7.56 mirc crashes with no message when you hit "continue" in the about window.
On windows 10:
[Linked Image]

Re: v7.56 about crash [Re: chili_beta] #265739 11/07/19 08:56 AM
Joined: Dec 2002
Posts: 4,563
Khaled Offline
Hoopy frood
Offline
Hoopy frood
Joined: Dec 2002
Posts: 4,563
Thanks for your bug report. I have not been able to reproduce this issue yet.

Are you using anti-virus software? If so, which anti-virus software is it? If you disable it, or add an exception for mIRC, does it resolve the issue?

If you install a clean copy of mIRC to an empty folder in your Windows Documents folder, using the "portable" option in the installer, with no scripts or addons, and then test this copy of mIRC, do you see the same issue?

Re: v7.56 about crash [Re: Khaled] #265741 11/07/19 06:07 PM
Joined: Jan 2007
Posts: 16
C
chili_beta Offline OP
Pikka bird
OP Offline
Pikka bird
C
Joined: Jan 2007
Posts: 16
I use windows' own av, defender. I tried turning it off, same result. Also with a portable installation, same result.

I actually went back a few mirc versions and I still get it, so I guess it's something that came from a windows update? I can say for sure how long ago was the last time I checked the about page.

If it helps, windows' event journal had two logs each time it crashes:
Code
Nom du journal :Application
Source :       Application Error
Date :         11/07/2019 19:48:58
ID de l’événement :1000
Catégorie de la tâche :(100)
Niveau :       Erreur
Mots clés :    Classique
Utilisateur :  N/A
Ordinateur :   AlienwareM17xR4
Description :
Nom de l’application défaillante mirc.exe, version : 7.56.0.0, horodatage : 0x5d205a39
Nom du module défaillant : d3d10warp.dll, version : 10.0.18362.1, horodatage : 0xa01dbf92
Code d’exception : 0xc0000005
Décalage d’erreur : 0x002870c3
ID du processus défaillant : 0xda8
Heure de début de l’application défaillante : 0x01d53810d8c44b93
Chemin d’accès de l’application défaillante : D:\downloads\Nouveau dossier\mIRC\mirc.exe
Chemin d’accès du module défaillant: C:\WINDOWS\SYSTEM32\d3d10warp.dll
ID de rapport : a561402d-9f78-49db-9948-7032d464a866
Nom complet du package défaillant : 
ID de l’application relative au package défaillant : 
XML de l’événement :
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Application Error" />
    <EventID Qualifiers="0">1000</EventID>
    <Level>2</Level>
    <Task>100</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2019-07-11T17:48:58.795226800Z" />
    <EventRecordID>11985</EventRecordID>
    <Channel>Application</Channel>
    <Computer>AlienwareM17xR4</Computer>
    <Security />
  </System>
  <EventData>
    <Data>mirc.exe</Data>
    <Data>7.56.0.0</Data>
    <Data>5d205a39</Data>
    <Data>d3d10warp.dll</Data>
    <Data>10.0.18362.1</Data>
    <Data>a01dbf92</Data>
    <Data>c0000005</Data>
    <Data>002870c3</Data>
    <Data>da8</Data>
    <Data>01d53810d8c44b93</Data>
    <Data>D:\downloads\Nouveau dossier\mIRC\mirc.exe</Data>
    <Data>C:\WINDOWS\SYSTEM32\d3d10warp.dll</Data>
    <Data>a561402d-9f78-49db-9948-7032d464a866</Data>
    <Data>
    </Data>
    <Data>
    </Data>
  </EventData>
</Event>


Code
Nom du journal :Application
Source :       Windows Error Reporting
Date :         11/07/2019 19:49:03
ID de l’événement :1001
Catégorie de la tâche :Aucun
Niveau :       Information
Mots clés :    Classique
Utilisateur :  N/A
Ordinateur :   AlienwareM17xR4
Description :
Détecteur d'erreurs 1498719732580720412, type 1
Nom d’événement : APPCRASH
Réponse : Non disponible
ID de CAB : 0

Signature du problème : 
P1 : mirc.exe
P2 : 7.56.0.0
P3 : 5d205a39
P4 : d3d10warp.dll
P5 : 10.0.18362.1
P6 : a01dbf92
P7 : c0000005
P8 : 002870c3
P9 : 
P10 : 

Fichiers joints :
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER15FD.tmp.mdmp
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1746.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1776.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1784.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER17B4.tmp.txt

Ces fichiers sont peut-être disponibles ici :
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_mirc.exe_a02ac2a543ddcad8451e9fe1de85b79a31e6bea8_3fa46f5d_8c091ac5-2840-4caa-b50f-124d51eb08d5

Symbole d’analyse : 
Nouvelle recherche de la solution : 0
ID de rapport : a561402d-9f78-49db-9948-7032d464a866
Statut du rapport : 268435456
Récipient avec hachage : 2d157e9fd59f3a7fb4cc85a7fe579f1c
GUID CAB :0
XML de l’événement :
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Windows Error Reporting" />
    <EventID Qualifiers="0">1001</EventID>
    <Level>4</Level>
    <Task>0</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2019-07-11T17:49:03.170615800Z" />
    <EventRecordID>11986</EventRecordID>
    <Channel>Application</Channel>
    <Computer>AlienwareM17xR4</Computer>
    <Security />
  </System>
  <EventData>
    <Data>1498719732580720412</Data>
    <Data>1</Data>
    <Data>APPCRASH</Data>
    <Data>Non disponible</Data>
    <Data>0</Data>
    <Data>mirc.exe</Data>
    <Data>7.56.0.0</Data>
    <Data>5d205a39</Data>
    <Data>d3d10warp.dll</Data>
    <Data>10.0.18362.1</Data>
    <Data>a01dbf92</Data>
    <Data>c0000005</Data>
    <Data>002870c3</Data>
    <Data>
    </Data>
    <Data>
    </Data>
    <Data>
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER15FD.tmp.mdmp
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1746.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1776.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1784.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER17B4.tmp.txt</Data>
    <Data>\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_mirc.exe_a02ac2a543ddcad8451e9fe1de85b79a31e6bea8_3fa46f5d_8c091ac5-2840-4caa-b50f-124d51eb08d5</Data>
    <Data>
    </Data>
    <Data>0</Data>
    <Data>a561402d-9f78-49db-9948-7032d464a866</Data>
    <Data>268435456</Data>
    <Data>2d157e9fd59f3a7fb4cc85a7fe579f1c</Data>
    <Data>0</Data>
  </EventData>
</Event>

Re: v7.56 about crash [Re: chili_beta] #265742 11/07/19 07:11 PM
Joined: Dec 2002
Posts: 4,563
Khaled Offline
Hoopy frood
Offline
Hoopy frood
Joined: Dec 2002
Posts: 4,563
Thanks for the logs. If it is affecting older versions of mIRC as well, this may indicate an issue with something else on your system.

I am also using Windows 10 and have the same d3d10warp.dll 10.0.18362.1 on my system. That said, mIRC does not use d3d10warp.dll and, as far as I know, does not load any DLLs that use it.

Are you running many other applications in the background? If you exit as many other applications as you can, and then run mIRC, do you still see the same issue?

Update: I may have found a potential cause of this issue, however I have not been able able to reproduce it. I am going to make a change to the next beta version to see if it resolves the issue for you.

Last edited by Khaled; 11/07/19 08:22 PM.
Re: v7.56 about crash [Re: chili_beta] #265749 12/07/19 12:21 PM
Joined: Dec 2002
Posts: 4,563
Khaled Offline
Hoopy frood
Offline
Hoopy frood
Joined: Dec 2002
Posts: 4,563
I have made changes in the latest beta that affect how the about dialog handles a number of events after the continue button is pressed.

This has the potential to either 1) resolve your issue, or 2) make the issue worse for everyone else :-]

Tested here under Windows 10 and XP and am unable to reproduce any issues with either the beta or previous versions.

Please let me know how it works out for you.

Re: v7.56 about crash [Re: Khaled] #265750 12/07/19 01:21 PM
Joined: Mar 2008
Posts: 87
B
BhaaL Offline
Babel fish
Offline
Babel fish
B
Joined: Mar 2008
Posts: 87
WARP usually means the thing is running the software rasterizer; either because the application is flagged to run as such (which is usually a developer-only option by running dxcpl.exe and entering it in a list) or because no display adapter is active, so the whole system is running using the Microsoft Basic Display Adapter.

Have you tried any of those to see if you can reproduce the crash?

Also @OP: are your GPU drivers up2date and working?

Re: v7.56 about crash [Re: Khaled] #265751 12/07/19 06:38 PM
Joined: Jan 2007
Posts: 16
C
chili_beta Offline OP
Pikka bird
OP Offline
Pikka bird
C
Joined: Jan 2007
Posts: 16
Originally Posted by Khaled
I have made changes in the latest beta that affect how the about dialog handles a number of events after the continue button is pressed.

This has the potential to either 1) resolve your issue, or 2) make the issue worse for everyone else :-]

Tested here under Windows 10 and XP and am unable to reproduce any issues with either the beta or previous versions.

Please let me know how it works out for you.

Sadly, it still crashes:
Code
Nom du journal :Application
Source :       Application Error
Date :         12/07/2019 20:20:42
ID de l’événement :1000
Catégorie de la tâche :(100)
Niveau :       Erreur
Mots clés :    Classique
Utilisateur :  N/A
Ordinateur :   AlienwareM17xR4
Description :
Nom de l’application défaillante mirc.exe, version : 7.56.71.0, horodatage : 0x5d2855a0
Nom du module défaillant : d3d10warp.dll, version : 10.0.18362.1, horodatage : 0xa01dbf92
Code d’exception : 0xc0000005
Décalage d’erreur : 0x002870c3
ID du processus défaillant : 0x34a8
Heure de début de l’application défaillante : 0x01d538de757d9ae7
Chemin d’accès de l’application défaillante : D:\downloads\mircb75671\mirc.exe
Chemin d’accès du module défaillant: C:\WINDOWS\SYSTEM32\d3d10warp.dll
ID de rapport : e368a062-73f7-4fe7-a5b2-c696d18d46ea
Nom complet du package défaillant : 
ID de l’application relative au package défaillant : 
XML de l’événement :
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Application Error" />
    <EventID Qualifiers="0">1000</EventID>
    <Level>2</Level>
    <Task>100</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2019-07-12T18:20:42.680878200Z" />
    <EventRecordID>12404</EventRecordID>
    <Channel>Application</Channel>
    <Computer>AlienwareM17xR4</Computer>
    <Security />
  </System>
  <EventData>
    <Data>mirc.exe</Data>
    <Data>7.56.71.0</Data>
    <Data>5d2855a0</Data>
    <Data>d3d10warp.dll</Data>
    <Data>10.0.18362.1</Data>
    <Data>a01dbf92</Data>
    <Data>c0000005</Data>
    <Data>002870c3</Data>
    <Data>34a8</Data>
    <Data>01d538de757d9ae7</Data>
    <Data>D:\downloads\mircb75671\mirc.exe</Data>
    <Data>C:\WINDOWS\SYSTEM32\d3d10warp.dll</Data>
    <Data>e368a062-73f7-4fe7-a5b2-c696d18d46ea</Data>
    <Data>
    </Data>
    <Data>
    </Data>
  </EventData>
</Event>

Code
Nom du journal :Application
Source :       Windows Error Reporting
Date :         12/07/2019 20:20:56
ID de l’événement :1001
Catégorie de la tâche :Aucun
Niveau :       Information
Mots clés :    Classique
Utilisateur :  N/A
Ordinateur :   AlienwareM17xR4
Description :
Détecteur d'erreurs 2004728798278720012, type 1
Nom d’événement : APPCRASH
Réponse : Non disponible
ID de CAB : 0

Signature du problème : 
P1 : mirc.exe
P2 : 7.56.71.0
P3 : 5d2855a0
P4 : d3d10warp.dll
P5 : 10.0.18362.1
P6 : a01dbf92
P7 : c0000005
P8 : 002870c3
P9 : 
P10 : 

Fichiers joints :
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER7E0C.tmp.mdmp
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER809D.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER80BD.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER80CB.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER80FB.tmp.txt

Ces fichiers sont peut-être disponibles ici :
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_mirc.exe_584fda8a7065edbc140f3c1285afb28523d4d2_aa062bb0_70332bf1-0b4b-4ab7-86c5-8ce35f568fcb

Symbole d’analyse : 
Nouvelle recherche de la solution : 0
ID de rapport : e368a062-73f7-4fe7-a5b2-c696d18d46ea
Statut du rapport : 268435456
Récipient avec hachage : 28c1f8d21a56bc8b7bd23a3874661a0c
GUID CAB :0
XML de l’événement :
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Windows Error Reporting" />
    <EventID Qualifiers="0">1001</EventID>
    <Level>4</Level>
    <Task>0</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2019-07-12T18:20:56.174786200Z" />
    <EventRecordID>12405</EventRecordID>
    <Channel>Application</Channel>
    <Computer>AlienwareM17xR4</Computer>
    <Security />
  </System>
  <EventData>
    <Data>2004728798278720012</Data>
    <Data>1</Data>
    <Data>APPCRASH</Data>
    <Data>Non disponible</Data>
    <Data>0</Data>
    <Data>mirc.exe</Data>
    <Data>7.56.71.0</Data>
    <Data>5d2855a0</Data>
    <Data>d3d10warp.dll</Data>
    <Data>10.0.18362.1</Data>
    <Data>a01dbf92</Data>
    <Data>c0000005</Data>
    <Data>002870c3</Data>
    <Data>
    </Data>
    <Data>
    </Data>
    <Data>
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER7E0C.tmp.mdmp
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER809D.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER80BD.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER80CB.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER80FB.tmp.txt</Data>
    <Data>\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_mirc.exe_584fda8a7065edbc140f3c1285afb28523d4d2_aa062bb0_70332bf1-0b4b-4ab7-86c5-8ce35f568fcb</Data>
    <Data>
    </Data>
    <Data>0</Data>
    <Data>e368a062-73f7-4fe7-a5b2-c696d18d46ea</Data>
    <Data>268435456</Data>
    <Data>28c1f8d21a56bc8b7bd23a3874661a0c</Data>
    <Data>0</Data>
  </EventData>
</Event>


Originally Posted by BhaaL
WARP usually means the thing is running the software rasterizer; either because the application is flagged to run as such (which is usually a developer-only option by running dxcpl.exe and entering it in a list) or because no display adapter is active, so the whole system is running using the Microsoft Basic Display Adapter.

Have you tried any of those to see if you can reproduce the crash?

Also @OP: are your GPU drivers up2date and working?


I use a 7-year old laptop. It has both Intel HD4000 (last updated in may) and Nvidia Geoforce GTX 675M which is sadly no longer supported and last updated last year. I tried running mIRC on both and it still crashes.

Re: v7.56 about crash [Re: chili_beta] #265753 12/07/19 09:31 PM
Joined: Dec 2002
Posts: 4,563
Khaled Offline
Hoopy frood
Offline
Hoopy frood
Joined: Dec 2002
Posts: 4,563
Thanks for the feedback.

I am afraid I am not sure what else to suggest. I tested mIRC on seven different Windows XP, 8.1, and 10 installations and could not reproduce the issue.

If I Google this issue, there are quite a few similar reports such as here, here, here, here, and here. Unfortunately, there do not seem to be any obvious solutions, eg. it could be due to a corrupted installation of DirectX, in which case you could run "dxdiag" to see if any errors are reported and/or reinstall DirectX or your graphics drivers. You could try shutting down all background applications first eg. MSI Afterburner, since they might be interferring. Some reports indicate that disabling anti-virus software resolved the issue. You could also try running the System File Checker tool.

If you do find a solution, please let us know.

Re: v7.56 about crash [Re: Khaled] #265756 13/07/19 08:22 AM
Joined: Jan 2007
Posts: 16
C
chili_beta Offline OP
Pikka bird
OP Offline
Pikka bird
C
Joined: Jan 2007
Posts: 16
Thanks for all the help, but I think I’ll leave it at that.

I did reinstall both the intel and nvidia cards, but that wasn’t it. I did a sfc check and the log says d3d10warp hash does not match the windows update one, with sfc not being able to fix it. But MS doesn’t not allow reinstalling dx12, since it’s merged into w10, so other than reinstalling w10, there’s no fix for me. And that doesn’t even guarantee it would fix the issue.

Since my issue is only about closing the about window (which I went to for the silly animations), I’ll wait it out and recheck in a couple of months.

Thanks again.

Re: v7.56 about crash [Re: chili_beta] #265757 13/07/19 10:09 AM
Joined: Apr 2004
Posts: 841
Sat Offline
Hoopy frood
Offline
Hoopy frood
Joined: Apr 2004
Posts: 841
Originally Posted by chili_beta
[..] closing the about window (which I went to for the silly animations), [..]

FWIW: you can close the first screen, without continuing to the second, by pressing Esc.


Saturn, QuakeNet staff