Sign in with
Sign up | Sign in
Your question

Blue screens after going to 8GB, ok with some cores disabled

Tags:
  • Gigabyte
  • Motherboards
Last response: in Motherboards
Share
October 26, 2012 7:52:26 AM

I ran into problems after installing new Corsair RAM. I'd like to have 12GB (4+8) but I'm first working on getting the new 8GB to work right alone. In experimenting with this many blue screens have come up, some do not write dump files (see results below).

It seems very strange to me that my best fix so far is to limit the CPU to 7 "processors" in System Configuration.

SYMPTOMS
o First boot: Blue screen before the login came up.
o Bad configs often fail before or at the login screen within 90 seconds.
o Boot from Windows 7 DVD: Blue screen running startup repair.

To get a consistent baseline I used BIOS to Load Fail-Safe Defaults (also tried Optimized Defaults).

I have run/tried the following:
o MemTest86+ 4.20: Ran all night with all 12GB installed overnight (8+ hours), 5+ passes, no errors
o Intel Processor Diagnostic Tool 64 bit v1.22.0.0-14-10, no issues found
o Tried disabling graphics card, audio; reenabled nad installed most current drivers
o Prime95 Torture test/blend run on 7 processors (see below) for 1 hour, no issues, max temp for 4 physical cores 56C, 53C, 52C, 50C
o Using XMP (Extreme Memory Profile) in BIOS (1.6V) as well as normal config; all 9-9-9-24. Tried SPD at 6 to run RAM at 800 MHz, no help.
o Tried disabling all kinds of things in BIOS like USB, USB3, GSATA controllers, Azalia Codec, LAN, serial, parallel, Virtualization, etc.

WORKAROUNDS
o Limit processors to 7 in System Configuration (best bet so far)
o Enable only 2 of 4 cores in BIOS (3 gives BSOD); no issues with TurboBoost or HyperThreading
o Disable Power service in System Configuration AND disable C1E (CPU Enhanced Halt) and C3/C6 (power saving state support)
o Boot into Safe Mode with C1E and C3/C6 disabled (varying luck)
o Use only one 4GB module

SYSTEM SPECS (homebuilt in 2010)
Motherboard: Gigabyte GA-P55A-UD3 (rev. 1.0), F11 BIOS (most current)
CPU: Intel i7-860 w/Evercool Transformer 4, not overclocked
RAM:
new: Corsair CMX8GX3M2A1333C9 (8GB 1333 MHz DDR3 2x4GB)
old: Corsair XMS3 TW3X4G1333C9A G (4GB 1333 MHz DDR3, 2x2GB)
GPU: ATI Radeon 5850 (MSI R5850 Twin Frozr II)
HD: Samsung SpinPoint F3 1TB (HD103SJ)
Optical: Sony 24x DVDRW SATA (OEM)
PSU: Seasonic S12II 430B (430W)
Case: Antec P183
OS: Windows 7 Professional x64
Monitor: Dell U2711 on DisplayPort

CPUID shows ITE IT87 voltages
CPU 1.20-1.30V
VIN1 1.60V
+3.3 3.36-3.38V
+5 4.97-5.00V

CRASH DUMPS
Copied from WhoCrashed v3.03.

On Fri 10/26/2012 05:07:34 GMT your computer crashed
crash dump file: C:\Windows\Minidump\102512-45177-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)
Bugcheck code: 0xA (0xFFFFF880039E7C50, 0x2, 0x0, 0xFFFFF800036938D9)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Fri 10/26/2012 05:07:34 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0xA (0xFFFFF880039E7C50, 0x2, 0x0, 0xFFFFF800036938D9)
Error: IRQL_NOT_LESS_OR_EQUAL
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Fri 10/26/2012 01:39:26 GMT your computer crashed
crash dump file: C:\Windows\Minidump\102512-23556-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x48D8)
Bugcheck code: 0x24 (0x1904FB, 0xFFFFF88009220938, 0xFFFFF88009220190, 0xFFFFF8800182287D)
Error: NTFS_FILE_SYSTEM
file path: C:\Windows\system32\drivers\ntfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT File System Driver
Bug check description: This indicates a problem occurred in the NTFS file system.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.


On Fri 10/26/2012 01:22:19 GMT your computer crashed
crash dump file: C:\Windows\Minidump\102512-30934-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)
Bugcheck code: 0x1A (0x41284, 0x7FEF6263001, 0x0, 0xFFFFF70001080000)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Thu 10/25/2012 23:39:28 GMT your computer crashed
crash dump file: C:\Windows\Minidump\102512-25927-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0x8F4E1)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF9600015F4E1, 0xFFFFF8800A22C0E0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\win32k.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Multi-User Win32 Driver
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.


On Thu 10/25/2012 23:29:34 GMT your computer crashed
crash dump file: C:\Windows\Minidump\102512-27081-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF800036E1E0F, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Thu 10/25/2012 23:25:52 GMT your computer crashed
crash dump file: C:\Windows\Minidump\102512-25459-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)
Bugcheck code: 0x4E (0x2, 0x28573A, 0x31FFFF, 0x1)
Error: PFN_LIST_CORRUPT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that the page frame number (PFN) list is corrupted.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Thu 10/25/2012 23:12:34 GMT your computer crashed
crash dump file: C:\Windows\Minidump\102512-37128-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)
Bugcheck code: 0x1A (0x41790, 0xFFFFFA80060C95A0, 0xFFFF, 0x0)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Thu 10/25/2012 20:03:41 GMT your computer crashed
crash dump file: C:\Windows\Minidump\102512-26910-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)
Bugcheck code: 0x4E (0x2, 0x28A4B2, 0x31FFFF, 0x1)
Error: PFN_LIST_CORRUPT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that the page frame number (PFN) list is corrupted.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Thu 10/25/2012 20:01:01 GMT your computer crashed
crash dump file: C:\Windows\Minidump\102512-27331-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)
Bugcheck code: 0x4E (0x2, 0x2961AA, 0x31FFFF, 0x1)
Error: PFN_LIST_CORRUPT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that the page frame number (PFN) list is corrupted.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Thu 10/25/2012 19:17:57 GMT your computer crashed
crash dump file: C:\Windows\Minidump\102512-32807-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)
Bugcheck code: 0x4E (0x2, 0x2BDED4, 0x31FFFF, 0x1)
Error: PFN_LIST_CORRUPT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that the page frame number (PFN) list is corrupted.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Thu 10/25/2012 19:12:45 GMT your computer crashed
crash dump file: C:\Windows\Minidump\102512-32791-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x48D8)
Bugcheck code: 0x24 (0x1904FB, 0xFFFFF88003BEE5D8, 0xFFFFF88003BEDE30, 0xFFFFF800039C2227)
Error: NTFS_FILE_SYSTEM
file path: C:\Windows\system32\drivers\ntfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT File System Driver
Bug check description: This indicates a problem occurred in the NTFS file system.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.


On Thu 10/25/2012 18:22:43 GMT your computer crashed
crash dump file: C:\Windows\Minidump\102512-35537-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x48D8)
Bugcheck code: 0x24 (0x1904FB, 0xFFFFF88002E44ED8, 0xFFFFF88002E44730, 0xFFFFF80003991227)
Error: NTFS_FILE_SYSTEM
file path: C:\Windows\system32\drivers\ntfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT File System Driver
Bug check description: This indicates a problem occurred in the NTFS file system.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.


On Thu 10/25/2012 18:16:43 GMT your computer crashed
crash dump file: C:\Windows\Minidump\102512-30498-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x48D8)
Bugcheck code: 0x24 (0x1904FB, 0xFFFFF880049515D8, 0xFFFFF88004950E30, 0xFFFFF8000397D227)
Error: NTFS_FILE_SYSTEM
file path: C:\Windows\system32\drivers\ntfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT File System Driver
Bug check description: This indicates a problem occurred in the NTFS file system.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.


On Thu 10/25/2012 17:40:31 GMT your computer crashed
crash dump file: C:\Windows\Minidump\102512-36083-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x48D8)
Bugcheck code: 0x24 (0x1904FB, 0xFFFFF88008F905B8, 0xFFFFF88008F8FE10, 0xFFFFF80003980227)
Error: NTFS_FILE_SYSTEM
file path: C:\Windows\system32\drivers\ntfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT File System Driver
Bug check description: This indicates a problem occurred in the NTFS file system.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.

More about : blue screens 8gb cores disabled

October 26, 2012 8:36:40 AM

Seems to me a bad memory chip or old bios that does not work properly with memory. Ntfs problems arise from BSOD when some programs was still writing to disk. Check disk and should be fine. Update bios and check memory with motherboard compatibility list (or change it).
m
0
l
!