0X00000008E, 0XC0000005, oxBF85FC9E,0xB2171AE4,0x00000000 blue screen

[Battal Gazi]

Quite possibly they could just be incompatible with each other then.

Post the brand/ model #'s of both sticks and I'll look up the specs and see if there's any differences that could cause issues when ran together.

Hello. I am still using same, 10 minutes ago bsod came again......

I was watching video on bs player. Chrome was open in background. Suddenly chrome started to blur. I tried to close and i managed to close it. But screen was blurred. Blurred means, screen was not like now for example. It was like as if while dragging a windows to somwhere else on screen but while dragging, it ffreezes and there are as if a lot of windows. I hope i could tell about it.

I am sending the minidump.

Current Size 2047 MB is paging file. auto by system. Only in c drive.

rams are 1 gb kingston

Amazon.com: Kingston ValueRAM 1 GB 400MHz PC3200 DDR DIMM Desktop Memory (KVR400X64C3A/1G): Electronics

Hi-Level 1GB 400MHz DDR Ram (HLV-PC3200/1G) Fiyatı

both are them 3200. In theory.

system specs:

http://speccy.piriform.com/results/hQXPTHfaprfyJmlwK20YWCg

I removed one so there are now 2rams. the removed one is also hilevel.

 

[carnageX]

Looking at your speccy dump..
I can see that the RAM modules have similar timings/specs...but with DDR (and DDR2 at times), could cause issues with small differences.

Kingston: 200MHz: 3-3-3-8 @ 2.5v / 166.7MHz: 2.5-3-3-7 @ 2.5v
Hi-Level: 200Mhz: 3-4-4-8 @ 2.5v / 166.7MHz: 2.5-3-3-7 @ 2.5v
reports as both running in 200MHz.

BSOD: https://msdn.microsoft.com/en-us/library/windows/hardware/ff557389(v=vs.85).aspx
with Parameter 1 pointing to "The pool block header size is corrupt."

It identifies avkmgr.sys as the faulting driver - which seems to be an Avira driver.

What I suggest doing is: take out the Hi-Level stick, leave only the Kingston.

Disable your page file (so that it gets deleted), reboot, and then re-enable it. Set it to a custom size, and make both the min/max size the same. Set both values to 4096.

See if you still get BSOD's.

 

[Battal Gazi]

Looking at your speccy dump..
I can see that the RAM modules have similar timings/specs...but with DDR (and DDR2 at times), could cause issues with small differences.

What I suggest doing is: take out the Hi-Level stick, leave only the Kingston.

Disable your page file (so that it gets deleted), reboot, and then re-enable it. Set it to a custom size, and make both the min/max size the same. Set both values to 4096.

See if you still get BSOD's.

Thank you for great advices.

I did not get any bsod since that but i will do it. Should i remove avira again like avast?

Page file only on c drive or on external drive or on d , e?

 

[carnageX]

Thank you for great advices.

I did not get any bsod since that but i will do it. Should i remove avira again like avast?

Leave it for now.

Page file only on c drive or on external drive or on d , e?

Doesn't really matter. Just keep it on C: for simplicity sake.

 

[Battal Gazi]

Doesn't really matter. Just keep it on C: for simplicity sake.

I removed and now there is only kingston with 4096 pagefile. It asked to overwrite pagefile so i confirmed.

Yesterday before removing, there happened another bsod. The name was different.

2 datys ago , i was trying to test with memtest. So i changed the slots

http://www.gigabyte.com/fileupload/product/2/1863/492_m.jpg

They were in 3. 4. slots, but 2 days ago i changed to 1. and 2. For becoming dual, they should be in same color slot? Can this be reason?




edit: ram is still on 200 mhz, as you can see in screenshot. Why can this be? It is ddr3200



Type: Dual Channel DDR 400 / 333 / 266 support
Max capacity: 4 GB*
DIMM slots: 4
* Due to standard PC architecture, a certain amount of memory is reserved for system usage and therefore the actual memory size is less than the stated amount.

this is mobo webpage

GIGABYTE - Motherboard - Socket 478 - GA-8IPE1000-G (rev. 4.x)

And you can see, this ram has 400 mhz, not 200 mhz normally.

https://www.google.com.tr/search?nu...msedr...0...1c.1.61.serp..0.8.910._yhVK_jqaV8

But speecify says

Slot #1
Type: DDR
Size: 1024 MBytes
Manufacturer: Kingston
Max Bandwidth: PC3200 (200 MHz)
Part Number: K
Serial Number: 6F20B4FE
Week/year: 51 / 08
JEDEC #2
Frequency: 200,0 MHz
CAS# Latency: 3,0
RAS# To CAS#: 3
RAS# Precharge: 3
tRAS: 8
Voltage: 2,500 V
JEDEC #1
Frequency: 166,7 MHz
CAS# Latency: 2,5
RAS# To CAS#: 3
RAS# Precharge: 3
tRAS: 7
Voltage: 2,500 V


Maybe because of motherboard, or slot?


Another edit: i checked the bios, i am posting the picture of it. When i click auto, there are 3-4 options 2 , 1.5 etc i remember. Bios shows 400 mhz also.

And when i go to

Computer properties -> advanced -> User Profiles.

my main account has 3.87 gb size, while administrator has 3-4 mb. c/document/myuser has 11 gb. The userprofile 's size is normal?

 

[carnageX]

I removed and now there is only kingston with 4096 pagefile. It asked to overwrite pagefile so i confirmed.

Yesterday before removing, there happened another bsod. The name was different.

I'll check your dump file when I have a minute.

2 datys ago , i was trying to test with memtest. So i changed the slots

http://www.gigabyte.com/fileupload/product/2/1863/492_m.jpg

They were in 3. 4. slots, but 2 days ago i changed to 1. and 2. For becoming dual, they should be in same color slot? Can this be reason?

Read the manual for your motherboard to see what config it should be in for dual-channel.

edit: ram is still on 200 mhz, as you can see in screenshot. Why can this be? It is ddr3200

PC3200 = DDR-400 = 200MHz. That's what it's supposed to be running at.

And when i go to

Computer properties -> advanced -> User Profiles.

my main account has 3.87 gb size, while administrator has 3-4 mb. c/document/myuser has 11 gb. The userprofile 's size is normal?

They're normal if you've been taking up that much space and you know it.

You can run WinDirStat from here: https://windirstat.info/

On your C: drive and see what files are taking up space.

 

[carnageX]

Ok, I was able to get to your dump file finally. Ran it through Windbg, and again...it points to memory.

*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000000A, {4, 2, 0, 804e7eb3}

Probably caused by : memory_corruption ( nt!MiRemovePageByColor+6a )

Followup: MachineOwner
---------

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

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 00000004, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: 804e7eb3, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from 805630e8
GetPointerFromAddress: unable to read from 805630e0
GetUlongFromAddress: unable to read from 80567ce8
00000004

CURRENT_IRQL: 2

FAULTING_IP:
nt!MiRemovePageByColor+6a
804e7eb3 8b4804 mov ecx,dword ptr [eax+4]

CUSTOMER_CRASH_COUNT: 2

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0xA

PROCESS_NAME: chrome.exe

ANALYSIS_VERSION: 6.3.9600.17298 (debuggers(dbg).141024-1500) x86fre

LAST_CONTROL_TRANSFER: from 804ea84f to 804e7eb3

STACK_TEXT:
aff6cc70 804ea84f c0039118 00000000 00000001 nt!MiRemovePageByColor+0x6a
aff6cc88 804e92db 0e44693c c0039118 88ec5020 nt!MiResolveDemandZeroFault+0x99
aff6ccf8 804e8e55 00000001 0e44693c c0039118 nt!MiDispatchFault+0x129
aff6cd4c 804e0966 00000001 0e44693c 00000001 nt!MmAccessFault+0xcde
aff6cd4c 1ec0020f 00000001 0e44693c 00000001 nt!KiTrap0E+0xd0
WARNING: Frame IP not in any known module. Following frames may be wrong.
0012ecfc 00000000 00000000 00000000 00000000 0x1ec0020f


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!MiRemovePageByColor+6a
804e7eb3 8b4804 mov ecx,dword ptr [eax+4]

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: nt!MiRemovePageByColor+6a

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP: 51d4e5ec

IMAGE_VERSION: 5.1.2600.6419

IMAGE_NAME: memory_corruption

FAILURE_BUCKET_ID: 0xA_nt!MiRemovePageByColor+6a

BUCKET_ID: 0xA_nt!MiRemovePageByColor+6a

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:0xa_nt!miremovepagebycolor+6a

FAILURE_ID_HASH: {26b8545a-2ffb-f5a3-d4a9-5e14165980c1}

Followup: MachineOwner
---------

Bolded parts indicate memory - seems in line with the other BSOD's you had been receiving.