BSOD Possibly Related to Memory

N

NachoFoot

New member
Joined
Jan 10, 2017
Posts
4
OS - Windows 10 x64 upgraded from Windows 7
Its a home-built computer I bought off of craigslist about 6 years ago.
CPU: AMD Phenom II X6 1100T
Mainboard: GA-890FXA-UD5
Memory: 2x8gb PNY part #8GBH2X04E99927-15
GPU: ASUS Nvidia GeForce GTX 770
PS: Antec 650W

Hi. I'm experiencing multiple BSODs since I upgraded the memory and video card last year. I get the occasional BSOD usually while completely idle. I Bought two sticks of memory from Best Buy and one of them produced errors. Exchanged them and the current memory reports no errors on multiple passes from Memtest86+. The computer is almost 6 years old and I thought maybe it was the motherboard, memory, or both...or maybe its just something I can't pinpoint myself. Any help is greatly appreciated! Thanks!

I did run a chkdsk /r /f /x and this is what I got:


Checking file system on C:
The type of the file system is NTFS.


A disk check has been scheduled.
Windows will now check the disk.


Stage 1: Examining basic file system structure ...
843520 file records processed. File verification completed.
26589 large file records processed. 0 bad file records processed.
Stage 2: Examining file name linkage ...
Unable to locate the file name attribute of index entry 3ce9bce9b0beb249_h.bundle
of index $I30 with parent 0xd05e in file 0x5030f.
Deleting index entry 3ce9bce9b0beb249_h.bundle in index $I30 of file 53342.
Unable to locate the file name attribute of index entry HomeBusinessR_OEM_Perp4-ul-phn.ørm-ms
of index $I30 with parent 0x12445 in file 0x7dbc2.
Deleting index entry HomeBusinessR_OEM_Perp4-ul-phn.ørm-ms in index $I30 of file 74821.
The index bitmap $I30 is missing in file 0x9650f.
Correcting error in index $I30 for file 615695.
1022284 index entries processed. Index verification completed.
CHKDSK is scanning unindexed files for reconnect to their original directory.
Recovering orphaned file HomeBusinessR_OEM_Perp3-ppd.xrm-ms (514994) into directory file 74821.
2 unindexed files scanned. Recovering orphaned file HomeBusinessR_OEM_Perp4-ul-phn.xrm-ms (515010) into directory file 74821.
2 unindexed files recovered to original directory.
0 unindexed files recovered to lost and found.
Stage 3: Examining security descriptors ...
Cleaning up 1632 unused index entries from index $SII of file 0x9.
Cleaning up 1632 unused index entries from index $SDH of file 0x9.
Cleaning up 1632 unused security descriptors.
CHKDSK is compacting the security descriptor stream
Security descriptor verification completed.
89383 data files processed. CHKDSK is verifying Usn Journal...
Usn Journal verification completed.


Stage 4: Looking for bad clusters in user file data ...
843504 files processed. File data verification completed.


Stage 5: Looking for bad, free clusters ...
274125043 free clusters processed. Free space verification is complete.
Correcting errors in the master file table's (MFT) BITMAP attribute.
Correcting errors in the Volume Bitmap.


Windows has made corrections to the file system.
No further action is required.


1952559103 KB total disk space.
854763172 KB in 576141 files.
319864 KB in 89386 indexes.
0 KB in bad sectors.
975895 KB in use by the system.
65536 KB occupied by the log file.
1096500172 KB available on disk.


4096 bytes in each allocation unit.
488139775 total allocation units on disk.
274125043 allocation units available on disk.


Internal Info:
00 df 0c 00 76 25 0a 00 62 5f 12 00 00 00 00 00 ....v%..b_......
c7 26 00 00 f0 90 00 00 00 00 00 00 00 00 00 00 .&..............


Windows has finished checking your disk.
Please wait while your computer restarts.
 

Attachments

Hi, your dumps show heavy mem-problems

Code: 
BugCheck 12B, {ffffffffc00002c4, 56b, 2d6bd0, ffffdf01bc303000}

*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : memory_corruption

Followup:     [COLOR=#ff0000]memory_corruption[/COLOR]
---------

5: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

FAULTY_HARDWARE_CORRUPTED_PAGE (12b)
This bugcheck indicates that a single bit error was found in this page.  This is a hardware memory error.
Arguments:
Arg1: ffffffffc00002c4, virtual address mapping the corrupted page
Arg2: 000000000000056b, physical page number
Arg3: 00000000002d6bd0, zero
Arg4: ffffdf01bc303000, zero

Debugging Details:
------------------


DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING:  10.0.14393.447 (rs1_release_inmarket.161102-0100)

SYSTEM_MANUFACTURER:  Gigabyte Technology Co., Ltd.

SYSTEM_PRODUCT_NAME:  GA-890FXA-UD5

BIOS_VENDOR:  Award Software International, Inc.

BIOS_VERSION:  FEf

BIOS_DATE:  12/24/2012

BASEBOARD_MANUFACTURER:  Gigabyte Technology Co., Ltd.

BASEBOARD_PRODUCT:  GA-890FXA-UD5

DUMP_TYPE:  2

BUGCHECK_P1: ffffffffc00002c4

BUGCHECK_P2: 56b

BUGCHECK_P3: 2d6bd0

BUGCHECK_P4: ffffdf01bc303000

BUGCHECK_STR:  0x12B_c00002c4_[COLOR=#ff0000]StCtDecompressFailed
[/COLOR]
CPU_COUNT: 6

CPU_MHZ: cf3

CPU_VENDOR:  AuthenticAMD

CPU_FAMILY: 10

CPU_MODEL: a

CPU_STEPPING: 0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  [COLOR=#ff0000]CODE_CORRUPTION[/COLOR]

PROCESS_NAME:  [COLOR=#ff0000]MemCompression[/COLOR]

CURRENT_IRQL:  0

ANALYSIS_SESSION_HOST:  SKYLAKE1

ANALYSIS_SESSION_TIME:  01-16-2017 10:24:25.0834

ANALYSIS_VERSION: 10.0.14321.1024 amd64fre

LAST_CONTROL_TRANSFER:  from fffff80106ea76f7 to fffff80106dd7510

STACK_TEXT:  
ffffdf01`c1ea62f8 fffff801`06ea76f7 : 00000000`0000012b ffffffff`c00002c4 00000000`0000056b 00000000`002d6bd0 : nt!KeBugCheckEx
ffffdf01`c1ea6300 fffff801`06e000fc : 00000000`00000200 00000000`00000003 00000000`002d6bd0 ffffdf01`bc303000 : nt!ST_STORE<SM_TRAITS>::StDmPageError+0x117
ffffdf01`c1ea6350 fffff801`06d97563 : 00000000`00000000 ffffaa03`8de12050 00000000`00000000 00000000`00006bd0 : nt! ?? ::FNODOBFM::`string'+0x1975c
ffffdf01`c1ea6430 fffff801`06d978f1 : 00000000`00000001 00000000`00001a58 00000000`00000001 ffffdf01`00004000 : nt!ST_STORE<SM_TRAITS>::StDmSinglePageTransfer+0x7b
ffffdf01`c1ea6480 fffff801`06d97a7d : 00000000`ffffffff ffffaa03`8f0ab000 ffffdf01`c1ea6568 ffffaa03`91528090 : nt!ST_STORE<SM_TRAITS>::StDmpSinglePageRetrieve+0x199
ffffdf01`c1ea6520 fffff801`06d98852 : ffff8844`00000000 ffffaa03`91528090 ffffaa03`90ef4060 ffffaa03`91528090 : nt!ST_STORE<SM_TRAITS>::StDmPageRetrieve+0xe5
ffffdf01`c1ea65e0 fffff801`06d98999 : ffffaa03`8de12000 ffffdf01`c1ea66f0 fffff801`06d98978 fffff801`06d98978 : nt!SMKM_STORE<SM_TRAITS>::SmStDirectReadIssue+0x52
ffffdf01`c1ea6630 fffff801`06d1b325 : ffffaa03`96ecd080 ffffdf01`c1ea66f0 ffffaa03`90ef4060 fffff801`06c90c2c : nt!SMKM_STORE<SM_TRAITS>::SmStDirectReadCallout+0x21
ffffdf01`c1ea6660 fffff801`06d91bbd : 00000000`00000003 ffffaa03`8f0ab000 ffffaa03`8de12000 00000000`00000000 : nt!KeExpandKernelStackAndCalloutInternal+0x85
ffffdf01`c1ea66b0 fffff801`06d94fbc : ffffdf01`c1ea67b0 ffffdf01`c1ea68f0 ffffaa03`8de12000 fffff801`06d91d96 : nt!SMKM_STORE<SM_TRAITS>::SmStDirectRead+0xad
ffffdf01`c1ea6780 fffff801`06d94ca7 : ffffaa03`8de12000 ffffaa03`91528090 fffff801`07048a40 ffffdf01`c1ea68f0 : nt!SMKM_STORE<SM_TRAITS>::SmStWorkItemQueue+0x1a4
ffffdf01`c1ea67d0 fffff801`06d91a53 : 00000000`0000000c ffffaa03`90ef4110 ffffaa03`91528090 00000000`00000004 : nt!SMKM_STORE_MGR<SM_TRAITS>::SmIoCtxQueueWork+0xbf
ffffdf01`c1ea6850 fffff801`06d98972 : ffffaa03`00000004 ffffaa03`90ef4110 ffffdf01`00000000 ffffaa03`8de12000 : nt!SMKM_STORE_MGR<SM_TRAITS>::SmPageRead+0x16b
ffffdf01`c1ea68c0 fffff801`06d479d9 : 00000000`80000000 ffffaa03`88aed580 0000011e`3e187000 ffff8b00`10804310 : nt!SmPageRead+0x2e
ffffdf01`c1ea6910 fffff801`06d47d5d : 00000000`00000002 ffffdf01`c1ea6c40 ffffaa03`90ef4010 00000000`00000000 : nt!MiIssueHardFaultIo+0x145
ffffdf01`c1ea69a0 fffff801`06d358b0 : 00000000`c0033333 ffffdf01`c1ea6c40 00000000`00000004 ffffdf01`c1ea6c40 : nt!MiIssueHardFault+0x15d
ffffdf01`c1ea6a40 fffff801`06de0afc : ffffaa03`96ecd080 00000000`00000000 00000000`00000000 00000000`00000000 : nt!MmAccessFault+0xca0
ffffdf01`c1ea6c40 00007fff`6e1710bd : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x13c
0000000a`d29fc790 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007fff`6e1710bd


STACK_COMMAND:  kb

CHKIMG_EXTENSION: !chkimg -lo 50 -d !nt
    fffff80106d345e2-fffff80106d345e3  2 bytes - nt!MiGetFreeOrZeroPage+2e2
    [ 80 fa:00 a2 ]
    fffff80106d34638-fffff80106d34639  2 bytes - nt!MiGetFreeOrZeroPage+338 (+0x56)
    [ 80 fa:00 a2 ]
    fffff80106d47dfe-fffff80106d47dff  2 bytes - nt!MiIssueHardFault+1fe (+0x137c6)
    [ 80 f6:00 88 ]
6 errors : !nt (fffff80106d345e2-fffff80106d47dff)

MODULE_NAME: [COLOR=#ff0000]memory_corruption[/COLOR]

IMAGE_NAME:  memory_corruption

FOLLOWUP_NAME:  memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MEMORY_CORRUPTOR:  LARGE

FAILURE_BUCKET_ID:  MEMORY_CORRUPTION_LARGE

BUCKET_ID:  MEMORY_CORRUPTION_LARGE

PRIMARY_PROBLEM_CLASS:  MEMORY_CORRUPTION_LARGE

TARGET_TIME:  2017-01-13T16:03:47.000Z

OSBUILD:  14393

OSSERVICEPACK:  447

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK:  272

PRODUCT_TYPE:  1

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

OSEDITION:  Windows 10 WinNt TerminalServer SingleUserTS

OS_LOCALE:  

USER_LCID:  0

OSBUILD_TIMESTAMP:  2016-11-02 11:17:03

BUILDDATESTAMP_STR:  161102-0100

BUILDLAB_STR:  rs1_release_inmarket

BUILDOSVER_STR:  10.0.14393.447

ANALYSIS_SESSION_ELAPSED_TIME: 122a

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:memory_corruption_large

FAILURE_ID_HASH:  {e29154ac-69a4-0eb8-172a-a860f73c0a3c}

Followup:     memory_corruption

Bios is the latest, but Beta?

unsure if the populated Slots are right for an AMD-CPU, the manual i found show only population for intel CPUs.

The RAM is not in the compatibility list, reseat them into the first Slots and try again.
 
It seems that one of the first slots is inoperable. Would using the second slots affect the stability of the RAM?
 
Hi NachoFoot. :welcome:

Your MB manual "says" you can use both the white slots or both the blue slots, for your RAM sticks.

Rivatuner: known bsods with windows (7).
gdrv.sys: gigabyte easytuner (other possible culprit)
 
Well, tried to put ram back into the white slots. The computer had trouble loading Windows and kept freezing at Performing Automatic Repair. Tried using a recovery disk and it still froze. Reseated the ram just in case and now it won't post. I don't think it's the ram. Will probably be able to salvage the gpu and hard drives. I am afraid to try the ram in a new build though.
 
Try to seat only one of the sticks, first in DDR3_3, then in DDR3_1.
DDR3_3 is the third (white) slot starting from the cpu.
DDR3_1 is the first (blue) slot.
If that won't work, try the other stick.
 
Last edited:
Ok, so it wasn't the memory after all. Seems like Phenom IIs don't like to go above 1,333 mhz. I had to put in some old memory just to get it to post then revert. I brought it back down to 1,333 and tightened the timings to 7,7,7,21. I'll try for awhile and see if I get anymore blue screens.
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top