Overclock.net banner

Weird behavior after reinstall of OS and addition of RAM

386 Views 7 Replies 6 Participants Last post by  Quantum Reality
Hey all,

My rig was running happily until about a week ago, when I decided that I should clean it out as a part of my spring cleaning. I also got some new RAM, which has passed the Windows Memory Diagnostic test. Anyway, the hardware setup is the same as it was before I cleaned it out, when it was working stably and had no issues (Minus the RAM, which is fine, according to tests).

After I reinstalled the OS, the computer has been working mostly stably, but it seems that whenever I am away from it after a while, it will tell me that it BSOD'ed. I have no idea what I have done wrong. My roommate looked through everything I've done, and he said that he wouldn't have done anything differently.

I copied the BSOD and pasted it in below. I tried to search the internet to see what my issue was, and I couldn't find any info about my specific BSOD was about.
Quote:
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
1 - 8 of 8 Posts
Quote:
Originally Posted by aislepathlight;12975578
I also got some new RAM, which has passed the Windows Memory Diagnostic test. A
How about memtest86+?
run memtest. windows diagnostic is a complete failure.
Sorry to dig this up, keep having issues

Quote:


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

I checked here, and it sees that for the BCCode 124 suggest that there are "NTFS_FILE_SYSTEM" issues

Quote:


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.

Wait. I'm confused now. When checking the bug check code, I'm assuming that you need the 0X24, and then the leading 1 is the parameter for the issue, right? Because otherwise, I have an "uncorrectable_error" (0x124) which sees like a really bad thing

One other edit--I've got a thumb drive formatted Fat32 in to run MemTest86, and thats acting up thats plugged in to the computer now
See less See more
Are your timings and voltages correct and running at advertised speeds? Start up CPU-z and take a picture of the memory and SPD tabs.
1 - 8 of 8 Posts
This is an older thread, you may not receive a response, and could be reviving an old thread. Please consider creating a new thread.
Top