Getting BSODs randomly

[Arma]

I've been getting recently strange BSODs occuring randomly.. Sometimes none a day sometimes 3 a day..

Event Type: Error
Event Source: System Error
Event Category: (102)
Event ID: 1003
Date: 2009.12.22
Time: 15:23:21

Description:
Error code 1000008e, parameter1 c0000005, parameter2 80569243, parameter3 b99f1bb0, parameter4 00000000.

Event Type: Error
Event Source: System Error
Event Category: (102)
Event ID: 1003
Date: 2009.12.21
Time: 22:37:41

Description:
Error code 0000007f, parameter1 0000000d, parameter2 00000000, parameter3 00000000, parameter4 00000000.

Event Type: Error
Event Source: System Error
Event Category: (102)
Event ID: 1003
Date: 2009.12.21
Time: 22:37:07

Description:
Error code 1000008e, parameter1 c0000005, parameter2 bf202600, parameter3 b9bcaa98, parameter4 00000000.

Event Type: Error
Event Source: System Error
Event Category: (102)
Event ID: 1003
Date: 2009.12.21
Time: 15:24:04

Description:
Error code 1000008e, parameter1 c0000005, parameter2 804de9a4, parameter3 b9d5d7c0, parameter4 00000000.

Event Type: Error
Event Source: System Error
Event Category: (102)
Event ID: 1003
Date: 2009.12.20
Time: 19:40:26

Description:
Error code 000000c1, parameter1 90dc8fd8, parameter2 90dc8c20, parameter3 007bc028, parameter4 00000023.

Event Type: Error
Event Source: System Error
Event Category: (102)
Event ID: 1003
Date: 2009.12.20
Time: 11:51:36

Description:
Error code 000000c9, parameter1 00000226, parameter2 f85e159c, parameter3 00000000, parameter4 00000000.

Event Type: Error
Event Source: System Error
Event Category: (102)
Event ID: 1003
Date: 2009.12.18
Time: 15:20:00

Description:
Error code 000000c4, parameter1 00000053, parameter2 81ed65b8, parameter3 81ed65e8, parameter4 00000000.

Event Type: Error
Event Source: System Error
Event Category: (102)
Event ID: 1003
Date: 2009.12.17
Time: 20:30:20

Description:
Error code 000000cc, parameter1 94914f10, parameter2 00000000, parameter3 804eca2b, parameter4 00000000.

Attached few dmp files. Waiting for a response. Thanks.

 

[Route44]

Your issue is memory corruption. Two of three minidumps specifically cited this as the issue. The other said hardware and this error was 0x8E and these are almost always caused by hardware and are paricularly a strong indicator of corrupted memory.

You need to run Memtest onj your RAM to determine if one or all your sticks are bad.

See the link below and follow the instructions. There is a newer version than what is listed but either one should work. If you need to see what the Memtest screen looks like go to reply #21. The third screen is the Memtest screen.

Let it run for a LONG time. The rule is a minimum of 7 Passes; the more Passes after 7 so much the better. There are 8 individual tests per Pass, i.e 8 individual test = 1 Pass. Many people will start this test before going to bed and check it the next day.

If you have errors you have corrupted memory and it needs to be replaced.

Also, with errors you need to run this test per stick of RAM. Take out one and run the test. Then take that one out and put the other in and run the test. If you start getting errors before 7 Passes you know that stick is corrupted and you don’t need to run the test any further on that stick.


Link: https://www.techspot.com/vb/topic62524.html


* Get back to us with the results.

 

[Arma]

Thanks for the advice ;]
Tried memtest on all 3 ram sticks, all went well and then after i put all 3 back in it was all ok and didnt crash once in 2days.. strange.

 

[Route44]

It could be that one or more of your sticks were not properly seated.