Quote:
How about memtest86+?
Problem signature:
Problem Event Name:BlueScreen
OS Version:6.1.7600.2.0.0.256.48
Locale ID:1033
Additional information about the problem:
BCCode:116
BCP1:FFFFFA8007C2C4E0
BCP2:FFFFF8801061923C
BCP3:FFFFFFFFC000009A
BCP4:0000000000000004
OS Version:6_1_7600
Service Pack:0_0
Product:256_1
Files that help describe the problem:
C:\Windows\Minidump\040211-21078-01.dmp
C:\Users\ISWILSON\AppData\Local\Temp\WER-51843-0.sysdata.xml
Read our privacy statement online:
http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409
If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt
How about memtest86+?Originally Posted by aislepathlight;12975578
I also got some new RAM, which has passed the Windows Memory Diagnostic test. A
Problem signature: Problem Event Name:BlueScreen OS Version:6.1.7600.2.0.0.256.48 Locale ID:1033 Additional information about the problem: BCCode:124 BCP1:0000000000000000 BCP2:FFFFFA800844D028 BCP3:00000000FE000000 BCP4:0000000002000182 OS Version:6_1_7600 Service Pack:0_0 Product:256_1 Files that help describe the problem: C:\\Windows\\Minidump\\041811-27656-01.dmp C:\\Users\\Ian\\AppData\\Local\\Temp\\WER-41828-0.sysdata.xml |
Specifies source file and line number information. The high 16 bits (the first four hexadecimal digits after the "0x") identify the source file by its identifier number. The low 16 bits identify the source line in the file where the bug check occurred. |