Skip to Content

Register Login

Industry Online Support

Technical Forum

Navigation

WinCC 5.1 SCADA PC Rebooting Issue...

Created by: KD... at: 6/2/2008 1:41 PM (6 Replies)

Rating (0)

Thanks 0

7 Entries

6/2/2008 1:41 PM	Rate (0)
KD... Posts: 27 Rating: (2)	Problem Summery: The SCADA was running fine since past four years. We have not changed any Hardware or Software. WinCC SCADA Rebooted automatically on following instances. 1) Time 22.08 pm – Date 19^th May 2008 2) Time 22.22 pm – Date 16^th May 2008 3) Time 11.00 AM – Date 31^st May 2008 PC:Manufacturer: Dell CorporationFreeHard Drive Space: 44.8 GBProcessor: Intel 4 CPU 3.00 GhzRAM: 512MB OS: Windows 2000 Version 5.0 SP4 SCADA: WinCC 5.1 SP2 , with 64K RT Licence Simatic Net: Software Version:V6.2 - SP1 Confuigured SCADA Connections: Profibus Speed - 1.5 Mbps DH+ Speed - 57.6 kbps PCI Cards: CP5613 PKTX I have attached following for your Ref. 1. Diagnose Folder 2. RA setup Files 3. S7 Files 4. ALMSR_SP.txt 5. Citamis.str 6. Event Log.txt 7. Event Logs.evt 8. Mini051608-01.dmp 9. System Information.txt Thanks in Advance, KD... Attachment SCADA PC Information.zip (29 Downloads)
KD... Posts: 27 Rating: (2)
Suggestion To thank Quote Answer

6/2/2008 11:46 PM	Rate (0)
billwest Posts: 510 Rating: (117)	I ran the mini dump file through WinDbg.exe. I did not have all of the symbols for Win2K, so the output did not contain any more than "Probably caused by : cp5613_wdm.sys ( cp5613_wdm+593f )." I have attached the output from WinDbg in case there is some one more knowledgeable than I am at reading it. You could try updating the driver for the CP5613. If that does not fix the problem you may have a 5613 that is dying. BTW it was very helpful that you provided all of the information in your zip file. Bill Attachment minidump_output.pdf (31 Downloads)
billwest Posts: 510 Rating: (117)
Suggestion To thank Quote Answer

6/3/2008 10:13 AM	Rate (0)
KD... Posts: 27 Rating: (2)	Thanks Bill, Your comment looks very logical, I must appreciate that. But I still can't believe why the driver started creating problem if it was running fine since past four years. As you said it could be that the card is dying. But Iwould be very difficult to prove that to the end user. Can we check the healthiness of the driver by any means? I.e. is there any tool by which can conclude that the card is faulty. Regards, KD…
KD... Posts: 27 Rating: (2)
Suggestion To thank Quote Answer

6/3/2008 1:22 PM	Rate (0)
billwest Posts: 510 Rating: (117)	The bugcheck section of the analysis contained this statement: DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1) An attempt was made to access a pageable (or completely invalid) address at an interrupt request level (IRQL) that is too high. This is usually caused by drivers using improper addresses. If kernel debugger is available get stack backtrace. Arguments: Arg1: f94ce000, memory referenced Arg2: 00000002, IRQL Arg3: 00000001, value 0 = read operation, 1 = write operation Arg4: bfd8893f, address which referenced memory I don't have a kernel debugger so I can't do a stack backtrace. Hardware can be damagedif the systemis subjected to power surges.This can take many forms including damaging system RAM or the RAM on the CP5613.Likewise, improper shutdown of the operating system through loss of power can lead to software corruption.At this point Ican't definitively say what the problem. If you could post the other two mini dump files I could ook at them. Bill.
billwest Posts: 510 Rating: (117)
Suggestion To thank Quote Answer

6/4/2008 10:16 AM	Rate (0)
KD... Posts: 27 Rating: (2)	Hi Bill, Sorry for replying late and thanksfor your prompt reply and your time. I searched in the PC we could not find the anything like "kernel de*" but locally what ever I felt I have uploaded them. In addition to that I have uploaded all the mini files created in the PC. Hope this is what you are looking for. Thanks again for you kind help. KD... PS: If you specify the path of the Kernel de* files in your reply, I can upload them. Attachment Mini Dump File & Kernel Files.zip (28 Downloads)
KD... Posts: 27 Rating: (2)	Last edited by: KD... at: 6/4/2008 10:23 AM Failed to upload the attachment...
Suggestion To thank Quote Answer

6/4/2008 1:55 PM	Rate (0)
billwest Posts: 510 Rating: (117)	I looked at all of the mini dump files: 11 were the 5613 2 were due to kmixer.sys 5/1 and 5/18 1 was due to portcls.sys 5/8 1 was due to the Kernel (ntoskrnl.exe) 5/5 The 5613 started having problems on 2/24 Between 2/24 and 4/20 there were 3 crashes Between 5/1 and 5/31 there were 11 crashes Any crashes are too many, butsomehting changed inthe system in May to accelerate the number of crashes. Were there any significantevents, hardware or software? If every crash was due to the 5613, you would normally conclude the 5613 was the problem. Since there were 4 other crashes, the root casue may not be the 5613. I would reload the driver for the 5613. I would also do a memory check on the RAM in the computer. There aremany programs you can use to test the memory. Here is a link to Microsoft's memory diagnostic test. http://oca.microsoft.com/en/windiag.asp Bill
billwest Posts: 510 Rating: (117)
Suggestion To thank Quote Answer

6/4/2008 4:50 PM	Rate (0)
KD... Posts: 27 Rating: (2)	Hi Bill, Thanks a lot for your help...I will work on your sugegstion and willkeep you informed how its goes. I must appreciate your helping attitude and through knowledge about windows stuff. Thanks again for your help. Regards, KD...
KD... Posts: 27 Rating: (2)
Suggestion To thank Quote Answer

|

Share this page:

Share this page on...

Follow us on