Rainmeter crashes on opening

[Paladinz]

I've used Rainmeter on Windows 10 Pro for many months but the past couple of days it crashes on opening.

I've followed all the steps from https://forum.rainmeter.net/viewtopic.php?f=103&t=27981 and totally uninstalled Rainmeter and deleted all the folders. I've then updated my video driver to the latest and installed both 4.3 Beta Release - 3279 & 4.2 Final Release - r3111 of Rainmeter, both crash on opening with no skins apart from the default.

System Info

Operating System: Windows 10 Pro 64-bit (10.0, Build 17134) (17134.rs4_release.180410-1804)
Language: English (Regional Setting: English)
System Manufacturer: Gigabyte Technology Co., Ltd.
System Model: H81M-S2H
BIOS: F2 (type: UEFI)
Processor: Intel(R) Core(TM) i7-4790 CPU @ 3.60GHz (8 CPUs), ~3.6GHz
Memory: 16384MB RAM
Available OS Memory: 16282MB RAM
Page File: 9983MB used, 22298MB available
Windows Dir: C:\WINDOWS
DirectX Version: DirectX 12
Card name: NVIDIA GeForce GTX 1060 6GB
Manufacturer: NVIDIA
Chip type: GeForce GTX 1060 6GB
DAC type: Integrated RAMDAC
Device Type: Full Device (POST)
Device Key: Enum\PCI\VEN_10DE&DEV_1C03&SUBSYS_371A1458&REV_A1
Device Status: 0180200A [DN_DRIVER_LOADED|DN_STARTED|DN_DISABLEABLE|DN_NT_ENUMERATOR|DN_NT_DRIVER]
Device Problem Code: No Problem
Driver Problem Code: Unknown
Display Memory: 14193 MB
Dedicated Memory: 6052 MB
Shared Memory: 8141 MB
Current Mode: 1920 x 1080 (32 bit) (60Hz)

Event viewer shows

Faulting application name: Rainmeter.exe, version: 4.3.0.3279, time stamp: 0x5c45ce26
Faulting module name: D3D10Warp.dll, version: 10.0.17134.112, time stamp: 0x4d6afe37
Exception code: 0xc0000005
Fault offset: 0x0000000000139f40
Faulting process ID: 0x176c
Faulting application start time: 0x01d4ba25174691c7
Faulting application path: C:\Program Files\Rainmeter\Rainmeter.exe
Faulting module path: C:\WINDOWS\SYSTEM32\D3D10Warp.dll
Report ID: 0c402926-d83c-48c4-a651-902df3ee7040
Faulting package full name:
Faulting package-relative application ID:

Fault bucket 1642102632496811872, type 4
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: Rainmeter.exe
P2: 4.3.0.3279
P3: 5c45ce26
P4: D3D10Warp.dll
P5: 10.0.17134.112
P6: 4d6afe37
P7: c0000005
P8: 0000000000139f40
P9:
P10:

[balala]

These kind of issues are probably caused (in most cases) by some not properly written skins. Especially that:

both crash on opening with no skins apart from the default.

So, unless I didn't understand something wrong, the default skins doesn't crash Rainmeter. So probably one of the installed skins is guilty. You have to figure out which one. Here is a description of how to do this.

[jsmorley]

I have a similar issue. It crashes after the latest Windows 10 update. I guess it may be somehow connected. I've found one more thread with the same issue. No solution mentioned though. I tried to rename and delete Rainmeter. Didn't help.

Just out of curiosity, are you by any chance getting "insider Preview" updates to Windows 10? If so, are you in the "Fast", "Slow", or "Release Preview" ring? If not, then I assume your About / Version in Rainmeter looks something like:

Rainmeter 4.3.0.3296 beta (64-bit)
Language: English (1033)
Build time: 2019-03-07 7:50:54
Commit Hash: 8bd98683
Windows 10 Pro 1809 64-bit (build 17763) - English (1033)
Path: C:\Program Files\Rainmeter\
SkinPath: C:\Users\Jeffrey\Documents\Rainmeter\Skins\
SettingsPath: C:\Users\Jeffrey\AppData\Roaming\Rainmeter\
IniFile: C:\Users\Jeffrey\AppData\Roaming\Rainmeter\Rainmeter.ini

And if you display the Properties of D3D10Warp.dll in C:\Windows\System32, it will look like:

2.jpg

Anyway, assuming you have a clean installation of Rainmeter, and are running only the default skins that come with Rainmeter, then it feels to me like you have some kind of issue with your system.

1) Install the latest drivers for your video card. Where you get these will vary depending on the video card / chipset that you have in your computer.
Reboot and see if that fixes the issue. If not...

2) Open a Command Prompt or Powershell window "as administrator" and run sfc /scannow. This will take a few minutes to run and will fix any corruption of any system files. If it finds and fixes anything, reboot and run it again. Do this until it comes back clean.
Reboot and see if that fixes the issue. If not...

3) Open a Command Prompt or Powershell window "as administrator" and run DISM /Online /Cleanup-Image /RestoreHealth. This will take some time, maybe 10-20 minutes to run, and will correct anything that wasn't correctly installed by a Windows update, or that has been subsequently changed. If it finds and fixes anything, reboot and run it again. Do this until it comes back clean.

1.jpg

If my initial assumptions were in fact true, I'm betting one of these actions corrects the problem.