New workunits that you get after the change will use 0.18.
I looked thru your minidumps, I don't see anything there related to BOINC or the Einstein application. Actually, the first STOP: 0x50 you had back in March shows the same problem.
The ones I looked at look very much like you have bad code running on your system, or bad hardware. I had similar problems a few months ago, when I saw they all occurred when my PC room got hot I checked the motherboard and CPU temperatures. Found that one fan had died, another was running slow; replacing them "fixed" the problems. Motherboard temperature before = 125 degrees (f), after = 100 degrees (f).
What might be happening is a driver is in contol of the system, and is accessing "process memory". Thats private memory that belongs to only one process. The driver sets "IRQL" level high enough so that Windows won't switch to another process. But some other program steps in and does something that causes the current process to get switched anyways. So when the driver tries to continue, its in the wrong process and you get the error.
You see "Stop 0x50" errors from the graphics driver, you see "stop 0xd1" from the network driver and you'd probably see a different "Stop" error from other drivers.
If you're sure you have good hardware, you can concentrate on the software. Make sure you're up to date with Windows and the drivers - especially the graphics drivers.
Also you can check the "utility" software running - Anti-virus, firewall, ad-blockers, file backups, file indexers. These all "hook" in to Windows and often interfere. One thing you can try is to disable them all, then add them back one at a time to see if the problem returns. Like if you start getting "Stop 0x50" errors when you run your firewall, its likely thats part of the problem.
What kind of internet connection do you have? Microsoft as some debugging tools that would help you in figuring out whats going on when the system crashes.
Hi Walt, I have just
)
Hi Walt,
I have just tried to install E@H v.0.18. When I rebooted, it still showed E@H v.0.03. is there an easy walkthrough page ?
I have generated another bluescreen crash, when using Bit Torrent to dl a file.
Was about 17% of a 54mb dl.
Driver_IRQL_NOT_LESS_OR_EQUAL
STOP: 0x000000D1, (0X00000400, 0X00000002, 0x00000000,0xF90E4A96)
NDIS.SYS address base at F90C8000,
datestamp 41107ec3
Yours in puzzlement,
Ivor Cogdell
RE: Hi Walt, I have
)
New workunits that you get after the change will use 0.18.
I looked thru your minidumps, I don't see anything there related to BOINC or the Einstein application. Actually, the first STOP: 0x50 you had back in March shows the same problem.
The ones I looked at look very much like you have bad code running on your system, or bad hardware. I had similar problems a few months ago, when I saw they all occurred when my PC room got hot I checked the motherboard and CPU temperatures. Found that one fan had died, another was running slow; replacing them "fixed" the problems. Motherboard temperature before = 125 degrees (f), after = 100 degrees (f).
What might be happening is a driver is in contol of the system, and is accessing "process memory". Thats private memory that belongs to only one process. The driver sets "IRQL" level high enough so that Windows won't switch to another process. But some other program steps in and does something that causes the current process to get switched anyways. So when the driver tries to continue, its in the wrong process and you get the error.
You see "Stop 0x50" errors from the graphics driver, you see "stop 0xd1" from the network driver and you'd probably see a different "Stop" error from other drivers.
If you're sure you have good hardware, you can concentrate on the software. Make sure you're up to date with Windows and the drivers - especially the graphics drivers.
Also you can check the "utility" software running - Anti-virus, firewall, ad-blockers, file backups, file indexers. These all "hook" in to Windows and often interfere. One thing you can try is to disable them all, then add them back one at a time to see if the problem returns. Like if you start getting "Stop 0x50" errors when you run your firewall, its likely thats part of the problem.
What kind of internet connection do you have? Microsoft as some debugging tools that would help you in figuring out whats going on when the system crashes.
Walt