BSOD when trying to install windows x64

[chris991jules]

hey guys.
i finally upgraded my com from 300gb sata hard disk to a 1TB WD caviar blue and upgraded my ram to 4gb (1x2GB kingston 800MHZ , 2x1GB kingston 677MHZ). So basiclly, i want to make my 1TB hard disk my main slave,so i have to install window.plus currently(now) im using Windows 7 ultimate x86 and as i know, x86 doesnt support 4GB of Ram. so i fixed everything up, and put in my dvd to install windows. Guess what, windows setup start and BAM! BCOD with error 0x00007E. I read few thread about this error and it mention hardware problem. Well i unplug 1 by 1 hardware and tried installing and i still get the same result. So i tried removing my 2gb ram and tried again, and TADA, its works and fully installs without a nag. when it was finally done, i put back my 2gb and bam, BCOS dead appear after windows splash screen and it keeps on restarting even in safe mode. but when i remove 1x 1gb ram, and run windows x64 on 3gb it work.........
There's the problem I'm having, hope u guys and gals can help me. really want to use windows 7 on 4gb

oh and btw this is my system spec

Operating System: Windows 7 Ultimate 32-bit (trying to use x64)
Asus P5B mobo
BIOS: BIOS Date: 03/09/09 10:13:49 Ver: 08.00.12
Processor: Intel(R) Core(TM)2 Duo CPU E6550 @ 2.33GHz (2 CPUs),
Memory: 4096MB RAM
Available OS Memory: 2048MB RAM
Nvidia Geforce GT 220
Soundmax integrated HD audio
1TB WD caviar blue HDD
300Gb Seagate HDD

 

[DocBrown]

Looks like you have mis-matched ram speeds. Best to have all matched size, speed, & pair od ram

 

[chris991jules]

But when I mix the 2gb 800mhz with a single 1gb 667 mhz, windows detect the 3gb and works fine, it only BSOC whn i i put both the 1gb 667 mhz and the 2gb 800 mhz. thats the part im lost. it cant be the mis-matched ram speeds cause i put the slowest ram speed in the 1st slot, so by right bios should read the 1st one and set the rest to follow the 1st one

 

[chris991jules]

i just did a whocrashed analysis, this is the result

[FONT=Segoe UI, Arial]System Information (local) [/FONT]
[FONT=Segoe UI, Arial]computer name: BLAKESTER
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
CPU: GenuineIntel Intel(R) Core(TM)2 Duo CPU E6550 @ 2.33GHz Intel586, level: 6
2 logical processors, active mask: 3
RAM: 3220365312 total
VM: 2147352576, free: 1990201344
[/FONT]

[FONT=Segoe UI, Arial] Crash Dump Analysis [/FONT]
[FONT=Segoe UI, Arial]Crash dump directory: C:\Windows\Minidump[/FONT]

[FONT=Segoe UI, Arial][FONT=Segoe UI, Arial]Crash dumps are enabled on your computer.
[/FONT][/FONT]

[FONT=Segoe UI, Arial]On Sun 29/05/2011 6:52:35 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\052911-31543-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntfs.sys[/FONT] (Ntfs+0x5A88)
Bugcheck code: 0x24 (0x1904FB, 0xFFFFF880041DF5E8, 0xFFFFF880041DEE40, 0xFFFFF80002EA1AB7)
Error: [FONT=Segoe UI, Arial]NTFS_FILE_SYSTEM[/FONT]
file path: C:\Windows\system32\drivers\ntfs.sys
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
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.
[/FONT]

[FONT=Segoe UI, Arial]On Sun 29/05/2011 6:52:35 AM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntfs.sys[/FONT] (Ntfs+0x5A88)
Bugcheck code: 0x24 (0x1904FB, 0xFFFFF880041DF5E8, 0xFFFFF880041DEE40, 0xFFFFF80002EA1AB7)
Error: [FONT=Segoe UI, Arial]NTFS_FILE_SYSTEM[/FONT]
file path: C:\Windows\system32\drivers\ntfs.sys
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
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.
[/FONT]

[FONT=Segoe UI, Arial]On Sat 28/05/2011 4:41:31 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\052911-20358-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x36396C)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF8000318096C, 0xFFFFF880009A9228, 0xFFFFF880009A8A90)
Error: [FONT=Segoe UI, Arial]SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M[/FONT]
file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: NT Kernel & System
Bug check description: This indicates that a system thread 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.
[/FONT]

[FONT=Segoe UI, Arial]On Sat 28/05/2011 2:10:54 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\052811-14414-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x71F00)
Bugcheck code: 0x19 (0x20, 0xFFFFF88002FEDE98, 0xFFFFF88002FEE968, 0x4AD00FD)
Error: [FONT=Segoe UI, Arial]BAD_POOL_HEADER[/FONT]
file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: NT Kernel & System
Bug check description: This indicates that a pool header is corrupt.
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.
[/FONT]