Instability, corrupt files, and BSOD after clean install

klactose · 07 Oct 2011

System Info
OS: Windows 7 Professional x64 (MSDN Student Alliance download)
System Age: 30 days
OS installed: ~20 hours ago

Additional information:
No perfmon report is included because it failed with an Error:

"The wait for the report generation tool to finish has timed out."

I also ran sfc /scannow immediately after the install and it finished reporting corrupt files that can be seen in the attached sfcdetails.txt file

Getting windows update failures too

The BSOD showed up with "Memory Management" on the screen. When windows restarted it provided the following information about the problem:

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: 1a
BCP1: 0000000000041790
BCP2: FFFFFA800DEBF880
BCP3: 000000000000FFFF
BCP4: 0000000000000000
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1

MvdB · 07 Oct 2011

Hello and welcome to SF!

There are a couple of things to check here. First, please check your Maintenance center and make very sure you run all windows updates. Many log errors on that.

HTML Code:

Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Fri Oct  7 17:56:24.300 2011 (UTC + 2:00)
System Uptime: 0 days 7:40:14.030
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+339d6 )
BUGCHECK_STR:  0x1a_41790
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  Azureus.exe
FAILURE_BUCKET_ID:  X64_0x1a_41790_nt!_??_::FNODOBFM::_string_+339d6
Bugcheck code 0000001A
Arguments 00000000`00041790 fffffa80`0debf880 00000000`0000ffff 00000000`00000000
BiosVersion = 0404   
BiosReleaseDate = 03/02/2011
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
MaxSpeed:     3330
CurrentSpeed: 3464

You are OC-ing, which I would turn off (go back to stock value) until stable.

This crashcode is most frequently caused by bad memory. Is your RAm memory all of identical sticks and settings? As a test go back to 8GB and see if that runs stable. Or if preferred, do memtest86+ tests (runs overnight) to test.

klactose · 07 Oct 2011

Hello and thanks for the response!

I didn't even realize that I was overclocking, I never changed any settings... but I do see that in the report you included where it shows current speed is greater than max speed, so I'll have to look into that.

Regarding Windows Update, it ran overnight but most of the updates failed. I'll let it run again. I'm wondering if it's possible that my version of windows is corrupt, I'm hoping that's not the case.

As far as the memory goes, it's a set of G.SKILL Model F3-12800CL9T2-24GBRL (which comes with six 4GB sticks) so they are definitely matching sticks/setting wise.

I guess I will try to install the updates again and do the memtest86+ tonight and let you know how it goes.

Thanks again for your help!

klactose · 11 Oct 2011

Hi again MvdB,

Running memtest86+ returned 50+ errors! But luckily, after some research I found out that there is actually nothing wrong with my memory and I seem to have fixed the problem.

It turned out that my motherboard's preset bios configuration was setup in a way that is incompatible with my memory. This resulted in my memory being sent 1.6 volts instead of 1.5V and it running at 1333MHz instead of 1600MHz which it is rated at.

Once I enabled XMP in the bios settings, the voltage and speed problems were resolved. I've since reinstalled Windows 7 without any of the problems that I was experiencing previously. So if anyone is using an ASUS Rampage III Black Edition mobo with 24GB of memory, you may want to check that you have XMP enabled!

MvdB · 11 Oct 2011

Good news! Thanks for posting back these results! If you're happy this is solved, please mark it so on any page in the thread? I'll note the check on XMP for this memory... thx.