Having trouble with new i5 build

IndieSnob

Limp Gawd
Joined
Jun 21, 2004
Messages
234
After upgrading a couple of my friends to i5 systems, the upgrade but hit me as well. However I am damn near regretting it as the new build has given me nothing but headaches for the past week.

The system specs are:

Intel i5-750 CPU with retail HSF
Gigabyte GA-P55-UD3R motherboard
2x2 Gigs Corsair XMS3 DDR3-1600 RAM
Palit 9600GT PCI-Express video card
Samsung F1 1 TB HD for OS install
Samsung Ecogreen 1.5 TB HD
Hitachi 1 TB HD
WD Green 1 TB HD
Antec Earthwatts 430 Watt PSU
Windows 7 Ultimate X64

I built the system this last Friday and after a day received a BSOD when trying to install some software. During the reboot from the BSOD the system halted during the AHCI phase of detecting harddrives, and it said the Samsung F1 was having a smart error.

I promptly took back the F1 and exchanged it for a new drive.

I came back and did another Windows 7 install and all seemed well. Starting two days ago there were times when the computer would lockup trying to come out of sleep.

I decided then to run Memtest 86 and I ran it for six passes to test my memory. There were no issues with it at all.

After some more testing of stuff, it seemed stable again.

Earlier tonight a friend of mine gifted me AION via Steam, so I downloaded the game. When the game was downloading the patch, every time it tried to patch it would give me an error that it failed. In the middle of one of the numerous retries I got a BSOD. When the system rebooted it ran incredibly slow through the detection of the harddrives, and I had to reboot it a few times until I was able to boot back in Windows 7 again.

I downloaded and installed winDBG with the hopes of reading the minidump, but either I did something wrong when I installed the symbol package, or I have plain forgotten how to read through the whole log it brings up.

I installed all the drivers for my motherboard from the included disc. There is no new drivers for it via the website or from Windows Update.

I have also installed the newest Nvidia drivers for my 9600GT.

Here is a link to my memorydump:

Memory Dump

Thanks in advance for any help!
 
Finally got the symbols problem fixed in the debugger: Here is the full readout:

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff80002ab1b74, Address of the exception record for the exception that caused the bugcheck
Arg3: fffff88008d0ae10, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP:
nt!MiUnlinkFreeOrZeroedPage+1ca
fffff800`02ab1b74 48893cc2 mov qword ptr [rdx+rax*8],rdi

CONTEXT: fffff88008d0ae10 -- (.cxr 0xfffff88008d0ae10)
rax=66000000001b6654 rbx=fffffa800016caa0 rcx=0000000000000007
rdx=fffffa8000000008 rsi=fffffa8003600230 rdi=ffffffffffffffff
rip=fffff80002ab1b74 rsp=fffff88008d0b7f0 rbp=000000000000000e
r8=0000000000000000 r9=fffff880031d3180 r10=fffffa8003600250
r11=fffff88008d0b858 r12=fffffa800016caa0 r13=0000000000000000
r14=0000000000000000 r15=00000000ffffffff
iopl=0 nv up ei pl nz ac pe nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010212
nt!MiUnlinkFreeOrZeroedPage+0x1ca:
fffff800`02ab1b74 48893cc2 mov qword ptr [rdx+rax*8],rdi ds:002b:2ffffa80`00db32a8=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0x3B

PROCESS_NAME: firefox.exe

CURRENT_IRQL: 2

LAST_CONTROL_TRANSFER: from 0000000000000000 to fffff80002ab1b74

STACK_TEXT:
fffff880`08d0b7f0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!MiUnlinkFreeOrZeroedPage+0x1ca


FOLLOWUP_IP:
nt!MiUnlinkFreeOrZeroedPage+1ca
fffff800`02ab1b74 48893cc2 mov qword ptr [rdx+rax*8],rdi

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: nt!MiUnlinkFreeOrZeroedPage+1ca

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc600

STACK_COMMAND: .cxr 0xfffff88008d0ae10 ; kb

IMAGE_NAME: memory_corruption

FAILURE_BUCKET_ID: X64_0x3B_nt!MiUnlinkFreeOrZeroedPage+1ca

BUCKET_ID: X64_0x3B_nt!MiUnlinkFreeOrZeroedPage+1ca

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

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

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff80002ab1b74, Address of the exception record for the exception that caused the bugcheck
Arg3: fffff88008d0ae10, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP:
nt!MiUnlinkFreeOrZeroedPage+1ca
fffff800`02ab1b74 48893cc2 mov qword ptr [rdx+rax*8],rdi

CONTEXT: fffff88008d0ae10 -- (.cxr 0xfffff88008d0ae10)
rax=66000000001b6654 rbx=fffffa800016caa0 rcx=0000000000000007
rdx=fffffa8000000008 rsi=fffffa8003600230 rdi=ffffffffffffffff
rip=fffff80002ab1b74 rsp=fffff88008d0b7f0 rbp=000000000000000e
r8=0000000000000000 r9=fffff880031d3180 r10=fffffa8003600250
r11=fffff88008d0b858 r12=fffffa800016caa0 r13=0000000000000000
r14=0000000000000000 r15=00000000ffffffff
iopl=0 nv up ei pl nz ac pe nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010212
nt!MiUnlinkFreeOrZeroedPage+0x1ca:
fffff800`02ab1b74 48893cc2 mov qword ptr [rdx+rax*8],rdi ds:002b:2ffffa80`00db32a8=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0x3B

PROCESS_NAME: firefox.exe

CURRENT_IRQL: 2

LAST_CONTROL_TRANSFER: from 0000000000000000 to fffff80002ab1b74

STACK_TEXT:
fffff880`08d0b7f0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!MiUnlinkFreeOrZeroedPage+0x1ca


FOLLOWUP_IP:
nt!MiUnlinkFreeOrZeroedPage+1ca
fffff800`02ab1b74 48893cc2 mov qword ptr [rdx+rax*8],rdi

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: nt!MiUnlinkFreeOrZeroedPage+1ca

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc600

STACK_COMMAND: .cxr 0xfffff88008d0ae10 ; kb

IMAGE_NAME: memory_corruption

FAILURE_BUCKET_ID: X64_0x3B_nt!MiUnlinkFreeOrZeroedPage+1ca

BUCKET_ID: X64_0x3B_nt!MiUnlinkFreeOrZeroedPage+1ca

Followup: MachineOwner
 
Download the free version of Everest and make sure your system temps look good. Could be a bad heatsink mount on the processor or just overall system too hot.

Try running a stress test through SuperPI or Prime95 to see if the problem might be computational and related to the CPU instead of just the RAM.

You already had 1 HD problem, maybe you ran into a bad batch if you got an exact replacement. I would try installing to a known good harddrive and then load it up with a bunch of apps to really make use of those platters and see if you get any more failures.

Could ultimately be some manufacturing failure in the motherboard itself causing communication errors between your hardware. This will be hardest to detect and you will probably just have to write off the board if you cant reproduce the error through any other means.

There's even the possibility it's your video card. Technically it could be damn near anything when you are suffering random crashes that never lead anywhere. Just go through piece by piece ruling out one after the other, it's the only way at this point.
 
Download the free version of Everest and make sure your system temps look good. Could be a bad heatsink mount on the processor or just overall system too hot.

Try running a stress test through SuperPI or Prime95 to see if the problem might be computational and related to the CPU instead of just the RAM.

You already had 1 HD problem, maybe you ran into a bad batch if you got an exact replacement. I would try installing to a known good harddrive and then load it up with a bunch of apps to really make use of those platters and see if you get any more failures.

Could ultimately be some manufacturing failure in the motherboard itself causing communication errors between your hardware. This will be hardest to detect and you will probably just have to write off the board if you cant reproduce the error through any other means.

There's even the possibility it's your video card. Technically it could be damn near anything when you are suffering random crashes that never lead anywhere. Just go through piece by piece ruling out one after the other, it's the only way at this point.

Oddly enough, and thanks for bringing that up, but I did notice on the first day of the build that when I stress tested with Prime 95 that my core temps were outrageously high. I reseated the HSF and the temps were fine again. I then ran Prime 95 for another 24 hours and had no problems.

The 9600GT was used in my previous system and I had zero problems with it. That does not mean that it could have gone bad, but was not a problem on the last system.

I may have an old 200 gig IDE harddrive laying around I can test the system out with. I'd use one of my other SATA harddrives, but I have tons of data on them.

It's just really odd to me that it made it through Prime and Mem Test, but yet I still had another BSOD.
 
Didnt notice you brought over some of the same hardware... I'd still be highly suspicious about that HD again. Maybe wherever you got it from just abused their shipment and they're all scrap metal now. If you dont want to sacrifice one of your more recent drives, then back them up to that old 200gig drive (and pray it holds) so you can be certain your good drive has ruled out.
 
Turns out that the memory kit I had doesn't play nicely with that board.

Got some new memory and reformatted and things are much smoother now.
 
The Corsair kit was incompatible? odd... did you try setting the voltage/timings manually? How long did you run Memtest?
 
Back
Top