[1903, au] A number of my Win10 devices are restarting after a BUG CHECK!

[kennysarmy]

Would anyone have a scooby how to troubleshoot devices randomly restarting, seems to be affecting our Maths department currently.

 

Event Logs state:

 

Two examples...

 

Log Name: System

Source: Microsoft-Windows-WER-SystemErrorReporting

Date: 07/09/2020 14:07:56

Event ID: 1001

Task Category: None

Level: Error

Keywords: Classic

User: N/A

Computer: 3A100-2017-04.curriculum.local

Description:

The computer has rebooted from a bugcheck. The bugcheck was: 0x0000000a (0x0000005c2967a0a0, 0x0000000000000002, 0x0000000000000000, 0xfffff80412c20486). A dump was saved in: C:\windows\MEMORY.DMP. Report Id: bbc25ef7-abcc-40f4-9612-8574804bb24c.

Event Xml:

1001

0

2

0

0

0x80000000000000

2640

System

3A100-2017-04.curriculum.local

0x0000000a (0x0000005c2967a0a0, 0x0000000000000002, 0x0000000000000000, 0xfffff80412c20486)

C:\windows\MEMORY.DMP

bbc25ef7-abcc-40f4-9612-8574804bb24c

 

 

Log Name: System

Source: Microsoft-Windows-WER-SystemErrorReporting

Date: 07/09/2020 11:04:52

Event ID: 1001

Task Category: None

Level: Error

Keywords: Classic

User: N/A

Computer: 6A100-2017-04.curriculum.local

Description:

The computer has rebooted from a bugcheck. The bugcheck was: 0x0000000a (0x000000b57b8d90a0, 0x0000000000000002, 0x0000000000000000, 0xfffff80581820486). A dump was saved in: C:\windows\MEMORY.DMP. Report Id: faf55618-bfce-4686-bc72-57f1c1296063.

Event Xml:

1001

0

2

0

0

0x80000000000000

2828

System

6A100-2017-04.curriculum.local

0x0000000a (0x000000b57b8d90a0, 0x0000000000000002, 0x0000000000000000, 0xfffff80581820486)

C:\windows\MEMORY.DMP

faf55618-bfce-4686-bc72-57f1c1296063

 

 

The staff are getting no warning and the PC shows a blue screen briefly before restart with the message : "your pc ran into a problem and needs restart"

[kennysarmy]

 

Not sure if this helps?

[BOOT]

If it's just the odd one, test the RAM. If they're all the same model, it's probably driver related.

[southhamster]

Don't know if it's related but we had a teacher laptop do this yesterday. I told her to just keep trying and luckily it's now ok as I'm working from home! Could it be a broken windows update which eventually goes away/fixes itself?

[Katy]

If it's random PCs and random users (rather than the same PC each time) grab a copy of the c:\windows\memory.dmp and analyse it in WinDbg to see if it's a specific driver at fault - I've got the same problem with the Promethean driver causing Win 10 2004 build to BSOD repeatedly

Instructions in my blog post I wrote up the other day https://katystech.blog/2020/09/analysing-bsod-memory-dumps/

[kennysarmy]

If it's random PCs and random users (rather than the same PC each time) grab a copy of the c:\windows\memory.dmp and analyse it in WinDbg to see if it's a specific driver at fault - I've got the same problem with the Promethean driver causing Win 10 2004 build to BSOD repeatedly

Instructions in my blog post I wrote up the other day https://katystech.blog/2020/09/analysing-bsod-memory-dumps/

 

There are 14 PC's in our Maths dept.

 

4 have n't crashed at all - no IWB's.

 

Off the remaining 10, 7 have crashed in the last week - all have Promethean IWB's!

[kennysarmy]

If it's random PCs and random users (rather than the same PC each time) grab a copy of the c:\windows\memory.dmp and analyse it in WinDbg to see if it's a specific driver at fault - I've got the same problem with the Promethean driver causing Win 10 2004 build to BSOD repeatedly

Instructions in my blog post I wrote up the other day https://katystech.blog/2020/09/analysing-bsod-memory-dumps/

 

Hi,

 

Same issue as yourself!

 

Any call raised with Promethean?

[Katy]

Hi,

 

Same issue as yourself!

 

Any call raised with Promethean?

 

Not yet as they are all ancient and out of warranty, I've found this: https://community.prometheanworld.com/forums/topic/update-to-1st-generation-2nd-generation-ab100-ab300-ab500-bsod-windows-10-1903/ which seems to be a "this driver doesn't BSOD" and for the newer boards https://support.prometheanworld.com/article/1779 which is some different firmware to try which puts the boards into HID mode, but changes some functionality.

[Katy]

I've installed the "BSOD proof" driver on a couple of PCs with the old v2 boards, tested one by drawing on the board for 20 minutes (more mind numbing than you'd imagine) and it didn't crash. I've set my boss the challenge to make it crash in his lesson in there tomorrow.

Going to try the firmware on one of the newer boards (either 378 or 578 Pro, forget which) before I go home, set him the same challenge.

[Katy]

I've got some rooms with ancient boards on this "new" unsupported driver (5.18.16), a room with a "new" board (578Pro) on the 5.18.16 driver, and a room with a "new" board with the HID mode firmware but the latest driver (5.18.19) so hopefully will work out which of these no longer crashes tomorrow and be able to report back.

[Katy]

@kennysarmy I'm having good reports from the rooms I put the 5.18.16 driver on, 0 crashes so far today so rolling it out everywhere tonight (and tickets for all the other rooms are coming in fast)

[kennysarmy]

@kennysarmy I'm having good reports from the rooms I put the 5.18.16 driver on, 0 crashes so far today so rolling it out everywhere tonight (and tickets for all the other rooms are coming in fast)

 

We still had crashed with just the driver so are rolling out the firmware on the boards too which seems to make things stable.

Firmware does have some strange behaviour where the board drops off the PC's radar after sleep or logoff etc so teachers are getting into the habit of turning board off and on again at start of lessons.

[minimoo]

tried running verifier.exe on the pc's for a bit ?

[kennysarmy]

tried running verifier.exe on the pc's for a bit ?

 

No. Thanks.

 

The issue seems to be resolved by updating the firmware on the IWB's and putting on the latest drivers for the boards.

[Network_Boy]

We're still struggling with getting our old gen2 serial port activ boards to be recognized. We've installed the 5.18.16 driver as per the instructions (disabling secure boot/driver enforcement). This has worked on a couple of PCs, but doesn't work more often than not. I've also tried updating the board firmware to 2.87, but this had no effect. We're on Win10 build 2004, on dell optiplex 7040 and 9020 PCs. Does anyone have any tips / tricks? We're all pulling our hair out at this point. TIA.

[Network_Boy]

UPDATE: Tried again on another Dell Optiplex 9020 today. Managed to get it to finally recognise the board by first installing Activ driver 5.7.23 (the last version with serial support), restarting, then installing Activ driver 5.18.16 (the special no BSOD driver) over the top, with no uninstall of 5.7.23. For some reason this has worked. Will try and test on some more machines and see if I get the same result.

[Network_Boy]

Tried the overinstall of driver 5.18.16 method again today on a different HP PC, and this didn't work. On this PC you can see the board in device manager, but the Activ driver config panel can't see any board connected. Also, the firmware upgrade utility for the board couldn't see any board connected. Tearing my hair out with this!