PCIe PCAN force PC to restart

[Ales1000]

Hello,

In my company we have PC with Windows 10 Ent., driver:4.3.0.16563 PCAN-Basic: 4.6.0.600. HW is PCAN-PCI Express FD. Pinnout on CANON: 2-CAN-LOW, 7-CAN-HIGH, 5 and 9 are supply (it is designed to not collide with PCAN pinnout).

When unitialize is called on PCIe channel with bus erros (BUS PASSIVE channel) it immediatelly turns PC off (black screen) and then starts it normally. (The bus errors may be subject of another topic, but this cannot make such a thing.)

If same thing is made with USB PCAN pro FD, its ok.

My suggestion is, that it is due to fact that PCAN PCIe is connected directly to PC motherboard and USB PCAN is via USB interface. Due to this fact, PCIe PCAN can theoretically make "bad" things on the motherboard and do such a thing.

How can I resolve this?

Thank you in advance for your answer.

BR
Aleš

[M.Maidhof]

Hi,

which application is running in that moment? Does the same reboot occur when you work with PCAN-View? If the PC restarts automatically, please diasable the "automatic restart" option in the Windows System settings, to see if there is a BSOD. Next step, please check the BIOS for updates and use the PCIe setting "Gen1" for the used PCIe slot of the PCAN card.

regards

Michael

[Ales1000]

Hello Michael,

in that momment is running PCANBasic based application for sending CAN-FD messages. I am not sure if we are possible to update BIOS, this is forbidden in my organization and it has to be done complicated via IT dep. Is BIOS update really what may help?

I will check for BSOD and let you know.

Aleš

[Ales1000]

BSOD have not occured after mentioned settings.

[Ales1000]

In eventvwr.msc was approximatelly corresponding number of critical Kernel-Power 41

Mostly, the Kernel-Power 41 error is caused by the wrong device drivers on your computer, especially an old or corrupted sound card driver. So you can try to update all the available drivers on your computer to solve this problem.Sep 15, 2022

This can be, what it caused.

It should be noted, that the restarts are observed on many PCs.

[M.Maidhof]

Hi,

after changing the restart option in the Windows settings, you have to restart once, so that the BSOD will be displayed instead of a reboot.

Did you test with PCAN-View only? How about used BIOS settings?

regards

Michael

[Ales1000]

Hello Michael,

no, after PC restart BSOD not occured.

Why to test PCAN-View only??? The driver and the PCIe PCAN CARD should be robust enough to avoid doing bad things on the PCIe interface on the motherboard. It is nonsense to blame app using PCAN-Basic interface to do such bad things. (Kernel-Power 41 is something with driver or power supply (normal power supply embedded in PC, I would not expect problem here))

What BIOS settings?

BR
Aleš

[M.Maidhof]

Hi,

I just want to help you with your problem, so please stay friendly with your answers in a forum.

I want to see a test with PCAN-View to checkif the problem is PC/hardware/PCIe related or software based. I don't know your application and cannot say how it could produce a reboot of a PC when using our hardware without showing a BSOD!

BIOS settings: see info in my first answer to this post regarding "GEN1"

To be sure the latest drivers and dlls are used on your PC, please download the SysInfo tool from the following URL:

http://www.peak-system.com/fileadmin/me ... ysInfo.zip

Unzip it and start the *.exe (no installation required), then make a system analysis from the system (avoid the quick scan function), save the result as a XML file and send the XML file to our support[at]peak-system.com email address.

regards

Michael

[Ales1000]

Hello Michael,

I am very friendly, I am patiently trying to explain you (several times, more and more straight), that the app used for generating periodic messages is based on your PCAN-BASIC API. ACCESSING HW ONLY USING THIS API. I used this straight approach to explain you that the problem is related to HW/supply/driver because the app is accessing the PCIe via PEAK System SW. I hope that it is now clear. Thus, it cannot be caused by the app.

I have sent you the XML. We have updated the driver to newest, restarted PC and the bug is still present.

BSOD is not showing, only the Kernel 41 event described before.

I will contact our IT to update BIOS and set GEN1 but it will take some time.

Can you please tell me another possible solution of this where IT is not needed? Or want you some another log/data file?

BR
Aleš

[Ales1000]

“solved” by updating the latest firmware version.