- Dec 16, 2010
- 24
- 0
- 18,520
Since April 10th when i reinstalled windows 8.1 on my pc with a new motherboard, I've got about 100 blue screens. I ran memtest86+ v5.01 & got 7 errors but i dont know what that means :^)
https://www.dropbox.com/s/oz4l662vzbp35yk/2014-06-14%2016.02.45.jpg
my computer specifications:
CPU - AMD Phenom II X4 955 @ 3.2Ghz
Mobo - Asrock 980de3/u3s3
gpu - HD6850
Ram - OCZ DDR3 800Mhz 4gb (2x2gb)
Corsair XT650
here is the last 5 blue screens from the event viewer
It looks like i have bad memory however, on my old motherboard (Asus M4A785TD-M EVO) i could overclock my cpu to 4.0ghz and it was fairly stable with only 1 BSoD a month roughy, but with my current motherboard it crashes after only a few seconds on the desktop @ 3.6ghz. So perhaps the motherboard is causing this?! im not sure & would like some helps ty :^)
https://www.dropbox.com/s/oz4l662vzbp35yk/2014-06-14%2016.02.45.jpg
my computer specifications:
CPU - AMD Phenom II X4 955 @ 3.2Ghz
Mobo - Asrock 980de3/u3s3
gpu - HD6850
Ram - OCZ DDR3 800Mhz 4gb (2x2gb)
Corsair XT650
here is the last 5 blue screens from the event viewer
Fault bucket MEMORY_CORRUPTION_ONE_BIT, type 0
Event Name: BlueScreen
Response: http://wer.microsoft.com/responses/resredir.aspx?sid=603&Bucket=MEMORY_CORRUPTION_ONE_BIT&State=1&ID=91598660-b599-4dd1-a436-c87390329f5a
Cab Id: 91598660-b599-4dd1-a436-c87390329f5a
Problem signature:
P1: 109
P2: a3a01f58d5c2e572
P3: b3b72bdf28417a69
P4: fffff8000e4c687c
P5: 1
P6: 6_3_9600
P7: 0_0
P8: 256_1
P9:
P10:
Attached files:
C:\Windows\Minidump\061414-20781-01.dmp
C:\Users\Peter\AppData\Local\Temp\WER-59875-0.sysdata.xml
C:\Windows\MEMORY.DMP
C:\Users\Peter\AppData\Local\Temp\WER26DC.tmp.WERInternalMetadata.xml
These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_109_9f652086c8638d59f50f31029a64156c1228854_00000000_cab_0d6d4447
Analysis symbol:
Rechecking for solution: 0
Report Id: 061414-20781-01
Report Status: 0
Hashed bucket:
Event Name: BlueScreen
Response: http://wer.microsoft.com/responses/resredir.aspx?sid=603&Bucket=MEMORY_CORRUPTION_ONE_BIT&State=1&ID=91598660-b599-4dd1-a436-c87390329f5a
Cab Id: 91598660-b599-4dd1-a436-c87390329f5a
Problem signature:
P1: 109
P2: a3a01f58d5c2e572
P3: b3b72bdf28417a69
P4: fffff8000e4c687c
P5: 1
P6: 6_3_9600
P7: 0_0
P8: 256_1
P9:
P10:
Attached files:
C:\Windows\Minidump\061414-20781-01.dmp
C:\Users\Peter\AppData\Local\Temp\WER-59875-0.sysdata.xml
C:\Windows\MEMORY.DMP
C:\Users\Peter\AppData\Local\Temp\WER26DC.tmp.WERInternalMetadata.xml
These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_109_9f652086c8638d59f50f31029a64156c1228854_00000000_cab_0d6d4447
Analysis symbol:
Rechecking for solution: 0
Report Id: 061414-20781-01
Report Status: 0
Hashed bucket:
Fault bucket AV_nt!MiCaptureAndResetWorkingSetAccessBits, type 0
Event Name: BlueScreen
Response: http://wer.microsoft.com/responses/resredir.aspx?sid=10&Bucket=AV_nt!MiCaptureAndResetWorkingSetAccessBits&State=1&ID=a849fd1a-c3bd-4b89-bd16-8d10e90670a3
Cab Id: a849fd1a-c3bd-4b89-bd16-8d10e90670a3
Problem signature:
P1: 50
P2: fffffa8003e360b0
P3: 0
P4: fffff8004072fa30
P5: 2
P6: 6_3_9600
P7: 0_0
P8: 256_1
P9:
P10:
Attached files:
C:\Windows\Minidump\061014-19171-01.dmp
C:\Users\Peter\AppData\Local\Temp\WER-49421-0.sysdata.xml
C:\Windows\MEMORY.DMP
C:\Users\Peter\AppData\Local\Temp\WER7990.tmp.WERInternalMetadata.xml
These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_50_fcd2672ccc09bbe84594b1e3b8f9cd381fce_00000000_cab_06259de1
Analysis symbol:
Rechecking for solution: 0
Report Id: 061014-19171-01
Report Status: 0
Hashed bucket:
Event Name: BlueScreen
Response: http://wer.microsoft.com/responses/resredir.aspx?sid=10&Bucket=AV_nt!MiCaptureAndResetWorkingSetAccessBits&State=1&ID=a849fd1a-c3bd-4b89-bd16-8d10e90670a3
Cab Id: a849fd1a-c3bd-4b89-bd16-8d10e90670a3
Problem signature:
P1: 50
P2: fffffa8003e360b0
P3: 0
P4: fffff8004072fa30
P5: 2
P6: 6_3_9600
P7: 0_0
P8: 256_1
P9:
P10:
Attached files:
C:\Windows\Minidump\061014-19171-01.dmp
C:\Users\Peter\AppData\Local\Temp\WER-49421-0.sysdata.xml
C:\Windows\MEMORY.DMP
C:\Users\Peter\AppData\Local\Temp\WER7990.tmp.WERInternalMetadata.xml
These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_50_fcd2672ccc09bbe84594b1e3b8f9cd381fce_00000000_cab_06259de1
Analysis symbol:
Rechecking for solution: 0
Report Id: 061014-19171-01
Report Status: 0
Hashed bucket:
Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0
Problem signature:
P1: a0
P2: 107
P3: a
P4: ffffe0017f616a60
P5: 0
P6: 6_3_9600
P7: 0_0
P8: 256_1
P9:
P10:
Attached files:
C:\Windows\Minidump\060814-17875-01.dmp
C:\Users\Peter\AppData\Local\Temp\WER-51859-0.sysdata.xml
C:\Users\Peter\AppData\Local\Temp\WER517C.tmp.WERInternalMetadata.xml
These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_a0_5da774f2971dfe65a8ba65fdbdac4311aee13_00000000_cab_0bff6d9f
Analysis symbol:
Rechecking for solution: 0
Report Id: 060814-17875-01
Report Status: 100
Hashed bucket:
Event Name: BlueScreen
Response: Not available
Cab Id: 0
Problem signature:
P1: a0
P2: 107
P3: a
P4: ffffe0017f616a60
P5: 0
P6: 6_3_9600
P7: 0_0
P8: 256_1
P9:
P10:
Attached files:
C:\Windows\Minidump\060814-17875-01.dmp
C:\Users\Peter\AppData\Local\Temp\WER-51859-0.sysdata.xml
C:\Users\Peter\AppData\Local\Temp\WER517C.tmp.WERInternalMetadata.xml
These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_a0_5da774f2971dfe65a8ba65fdbdac4311aee13_00000000_cab_0bff6d9f
Analysis symbol:
Rechecking for solution: 0
Report Id: 060814-17875-01
Report Status: 100
Hashed bucket:
Fault bucket AV_nt!MmDeleteKernelStack, type 0
Event Name: BlueScreen
Response: http://wer.microsoft.com/responses/resredir.aspx?sid=10&Bucket=AV_nt!MmDeleteKernelStack&State=1&ID=d11a2701-fd04-4b41-a8cf-d427f60f4db7
Cab Id: d11a2701-fd04-4b41-a8cf-d427f60f4db7
Problem signature:
P1: a
P2: fffffa800409a440
P3: 2
P4: 1
P5: fffff8035d75fcb4
P6: 6_3_9600
P7: 0_0
P8: 256_1
P9:
P10:
Attached files:
C:\Windows\Minidump\060714-20046-01.dmp
C:\Users\Peter\AppData\Local\Temp\WER-62953-0.sysdata.xml
C:\Windows\MEMORY.DMP
C:\Users\Peter\AppData\Local\Temp\WERE555.tmp.WERInternalMetadata.xml
These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_a_bc8d3147fb894c8ecfde3750301c31b4ffa2c3c_00000000_cab_0c771771
Analysis symbol:
Rechecking for solution: 0
Report Id: 060714-20046-01
Report Status: 0
Hashed bucket:
Event Name: BlueScreen
Response: http://wer.microsoft.com/responses/resredir.aspx?sid=10&Bucket=AV_nt!MmDeleteKernelStack&State=1&ID=d11a2701-fd04-4b41-a8cf-d427f60f4db7
Cab Id: d11a2701-fd04-4b41-a8cf-d427f60f4db7
Problem signature:
P1: a
P2: fffffa800409a440
P3: 2
P4: 1
P5: fffff8035d75fcb4
P6: 6_3_9600
P7: 0_0
P8: 256_1
P9:
P10:
Attached files:
C:\Windows\Minidump\060714-20046-01.dmp
C:\Users\Peter\AppData\Local\Temp\WER-62953-0.sysdata.xml
C:\Windows\MEMORY.DMP
C:\Users\Peter\AppData\Local\Temp\WERE555.tmp.WERInternalMetadata.xml
These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_a_bc8d3147fb894c8ecfde3750301c31b4ffa2c3c_00000000_cab_0c771771
Analysis symbol:
Rechecking for solution: 0
Report Id: 060714-20046-01
Report Status: 0
Hashed bucket:
Fault bucket 0x1a_5003_nt!MiAllocateWsle, type 0
Event Name: BlueScreen
Response: http://wer.microsoft.com/responses/resredir.aspx?sid=10&Bucket=0x1a_5003_nt!MiAllocateWsle&State=1&ID=fe48a95f-31f2-4f1d-8cb0-71c8cfc8b240
Cab Id: fe48a95f-31f2-4f1d-8cb0-71c8cfc8b240
Problem signature:
P1: 1a
P2: 5003
P3: fffff58010804000
P4: 1b264
P5: 86660018a60
P6: 6_3_9600
P7: 0_0
P8: 256_1
P9:
P10:
Attached files:
C:\Windows\Minidump\060314-19234-01.dmp
C:\Users\Peter\AppData\Local\Temp\WER-38125-0.sysdata.xml
C:\Windows\MEMORY.DMP
C:\Users\Peter\AppData\Local\Temp\WER85C0.tmp.WERInternalMetadata.xml
These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_1a_9a91925659c619d4fa8f52fb98cb495be8c210a_00000000_cab_0bbaacef
Analysis symbol:
Rechecking for solution: 0
Report Id: 060314-19234-01
Report Status: 0
Hashed bucket:
Event Name: BlueScreen
Response: http://wer.microsoft.com/responses/resredir.aspx?sid=10&Bucket=0x1a_5003_nt!MiAllocateWsle&State=1&ID=fe48a95f-31f2-4f1d-8cb0-71c8cfc8b240
Cab Id: fe48a95f-31f2-4f1d-8cb0-71c8cfc8b240
Problem signature:
P1: 1a
P2: 5003
P3: fffff58010804000
P4: 1b264
P5: 86660018a60
P6: 6_3_9600
P7: 0_0
P8: 256_1
P9:
P10:
Attached files:
C:\Windows\Minidump\060314-19234-01.dmp
C:\Users\Peter\AppData\Local\Temp\WER-38125-0.sysdata.xml
C:\Windows\MEMORY.DMP
C:\Users\Peter\AppData\Local\Temp\WER85C0.tmp.WERInternalMetadata.xml
These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_1a_9a91925659c619d4fa8f52fb98cb495be8c210a_00000000_cab_0bbaacef
Analysis symbol:
Rechecking for solution: 0
Report Id: 060314-19234-01
Report Status: 0
Hashed bucket:
It looks like i have bad memory however, on my old motherboard (Asus M4A785TD-M EVO) i could overclock my cpu to 4.0ghz and it was fairly stable with only 1 BSoD a month roughy, but with my current motherboard it crashes after only a few seconds on the desktop @ 3.6ghz. So perhaps the motherboard is causing this?! im not sure & would like some helps ty :^)
Facebook
Twitter
Instagram