Problems with new CPU Installation

[Moochmaker]

God I hate crashes. There always seems to be problems with this computer whenever I install something or something goes wrong. Anyways...to the point. My bro helped me tonight change from the old AMD X2 3800+ CPU to an AMD X2 5200+. It is the right part, that we are sure of. After removing the old CPU, we cleaned out the heat sync, applied new thermal paste to the heat sync, and put in the new CPU. Not sure if we may have used too much of the paste, but I don't think we did. After this, we started up the computer normally, passed the login screen, and got to the desktop. It immediately installed drivers for the CPU and asked for a restart. Around 30 seconds or so after that restart, the computer crashed and a bsod popped up. Again, it restarted, got to the same point and crashed again. We started in safe mode and encountered no problems. The event viewer displayed a power-kernal error (almost always the problem I encounter) I believe as ID:41 Task:63 or the other way around. After numerous restarts and crashes, we tried taking out the graphics card to see if that was an issue and it crashed just the same. The only things we think it could be are the RAM and/or the new CPU itself. Not sure what the problem is and it is virtually impossible to get a dump file as the computer crashes near instantly after a boot. Perhaps in safe mode I can get a dump and get that if possible. Need a how to on how to get a dump file, though. Any thoughts on what it could be?

 

[Moochmaker]

Here are the three dump files I could retrieve.

 

[ttran]

I'm guessing that AVG is the cause of the problem (see the highlighted), please remove them completely, using the uninstall tool > Info > Tool (32bit) - Tool (64 bit)

Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
Copyright (c) Microsoft Corporation. All rights reserved.
 
Loading Dump File [C:\Users\TUANTR~1\AppData\Local\Temp\Rar$DI00.533\062410-32276-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*e:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02a02000 PsLoadedModuleList = 0xfffff800`02c3fe50
Debug session time: Thu Jun 24 16:13:10.809 2010 (UTC + 7:00)
System Uptime: 0 days 0:02:08.822
Loading Kernel Symbols
...............................................................
................................................................
................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 24, {1904fb, fffff880076c6728, fffff880076c5f90, fffff80002a880ba}
Probably caused by : Ntfs.sys ( Ntfs!NtfsOpenExistingPrefixFcb+123 )
Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
NTFS_FILE_SYSTEM (24)
    If you see NtfsExceptionFilter on the stack then the 2nd and 3rd
    parameters are the exception record and context record. Do a .cxr
    on the 3rd parameter and then kb to obtain a more informative stack
    trace.
Arguments:
Arg1: 00000000001904fb
Arg2: fffff880076c6728
Arg3: fffff880076c5f90
Arg4: fffff80002a880ba
Debugging Details:
------------------
 
EXCEPTION_RECORD:  fffff880076c6728 -- (.exr 0xfffff880076c6728)
ExceptionAddress: fffff80002a880ba (nt!ExAcquireFastMutex+0x000000000000001a)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff
CONTEXT:  fffff880076c5f90 -- (.cxr 0xfffff880076c5f90)
rax=0000000000000001 rbx=ff00fa8004ef2758 rcx=ff00fa8004ef2758
rdx=0000000000000001 rsi=fffffa8003d6ec10 rdi=0000000000000000
rip=fffff80002a880ba rsp=fffff880076c6960 rbp=0000000000000000
 r8=fffff880076c69e4  r9=fffff8a0003f8938 r10=fffffa80066956f0
r11=0000000000000000 r12=0000000000000001 r13=0000000000000000
r14=fffffa80066956f0 r15=0000000000000024
iopl=0         nv up ei ng nz na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010286
nt!ExAcquireFastMutex+0x1a:
fffff800`02a880ba f00fba3100      lock btr dword ptr [rcx],0 ds:002b:ff00fa80`04ef2758=????????
Resetting default scope
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  [COLOR=red]avgwdsvc.exe[/COLOR]
CURRENT_IRQL:  1
ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
EXCEPTION_PARAMETER1:  0000000000000000
EXCEPTION_PARAMETER2:  ffffffffffffffff
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002caa0e0
 ffffffffffffffff 
FOLLOWUP_IP: 
Ntfs!NtfsOpenExistingPrefixFcb+123
fffff880`012dce33 ff83c0000000    inc     dword ptr [rbx+0C0h]
FAULTING_IP: 
nt!ExAcquireFastMutex+1a
fffff800`02a880ba f00fba3100      lock btr dword ptr [rcx],0
BUGCHECK_STR:  0x24
LAST_CONTROL_TRANSFER:  from fffff880012dce33 to fffff80002a880ba
STACK_TEXT:  
fffff880`076c6960 fffff880`012dce33 : fffff8a0`003f8d10 00000000`00000000 fffffa80`03d6ec10 fffff880`05977390 : nt!ExAcquireFastMutex+0x1a
fffff880`076c6990 fffff880`012ede76 : fffffa80`066956f0 fffffa80`03d6ec10 fffff8a0`003f8d10 00000000`00000701 : Ntfs!NtfsOpenExistingPrefixFcb+0x123
fffff880`076c6a80 fffff880`012e828d : fffffa80`066956f0 fffffa80`03d6ec10 fffff880`076c6c60 fffff880`076c6ca8 : Ntfs!NtfsFindStartingNode+0x5e6
fffff880`076c6b50 fffff880`01251c0d : fffffa80`066956f0 fffffa80`03d6ec10 fffff880`05977390 fffffa80`04edc700 : Ntfs!NtfsCommonCreate+0x3dd
fffff880`076c6d30 fffff800`02a6a487 : fffff880`05977300 00000000`0056e810 00000000`7efad000 00000000`00e7ff08 : Ntfs!NtfsCommonCreateCallout+0x1d
fffff880`076c6d60 fffff800`02a6a441 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KySwitchKernelStackCallout+0x27
fffff880`059771d0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSwitchKernelStackContinue
 
SYMBOL_STACK_INDEX:  1
SYMBOL_NAME:  Ntfs!NtfsOpenExistingPrefixFcb+123
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: Ntfs
IMAGE_NAME:  Ntfs.sys
DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc14f
STACK_COMMAND:  .cxr 0xfffff880076c5f90 ; kb
FAILURE_BUCKET_ID:  X64_0x24_Ntfs!NtfsOpenExistingPrefixFcb+123
BUCKET_ID:  X64_0x24_Ntfs!NtfsOpenExistingPrefixFcb+123
Followup: MachineOwner
---------

You have these old drivers (conexant modem drivers):

fffff880`0445c000 fffff880`04527000   CAX_CNXT CAX_CNXT.sys Thu Jun 21 02:29:12 2007 (46798008)
fffff880`04235000 fffff880`043a7000   CAX_DPV  CAX_DPV.sys  Thu Jun 21 02:32:53 2007 (467980E5)
fffff880`04000000 fffff880`0406f000   CAXHWBS2 CAXHWBS2.sys Thu Jun 21 02:30:20 2007 (4679804C)

~Tuan

 

[Moochmaker]

Haven't tried using the remover tool you suggested yet. Tried doing an uninstall normally. After a reboot, the computer ended up crashing for different reasons. More dump files to come...

Edit: Again, it works fine in safe mode. It could be the new CPU using too much power along with the memory that causes any app that starts up first to cause the computer to crash. Any chance this CPU is eating up too much voltage?

 

[ttran]

It would be best if you can get all trace of AVG out by using that tool
Yes, please upload more minidump files so we can see what else can cause BSODs

~Tuan

 

[Moochmaker]

Here are some more dumps. Any chance a re-installation of windows would work?

 

[ttran]

I want to ask you again this, Can you boot into normal mode? If it keep crashing while you attempt to reboot the computer, I guess the problems is due to system services somehow caused BSODs (My guess). Because in the 2 minidump files you posted, 1 indicated stop code error 3B, which usually caused by system services, drivers..or memory and stop code FC, which is usually driver.
Can you please go to Run-->type in msconfig-->choose startup tab-->uncheck every services that chosen at startup-->apply and reboot

Bugcheck:

BugCheck 3B, {c000001d, fffff88001245cd5, fffff88005d77c80, 0}
Probably caused by : Ntfs.sys ( Ntfs!NtfsReleaseForCreateSection+55 )
Followup: MachineOwner
---------
BugCheck FC, {fffff880009e6180, 80000000002f1963, fffff88002f1bbf0, 0}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+40a65 )
Followup: MachineOwner
---------

Let us know how it goes

~Tuan

 

[Moochmaker]

I did like you said and turned off all the startup apps. The computer booted up to the login screen in normal mode. I typed in my password after and waited for the desktop to pop up. Instead, the screen went black and a command prompt comes on on the screen. Soon after a crash follows. What now? Safe mode seems to work fine, but normal startup will not go at all.

 

[ttran]

How about doing this:
How to troubleshoot a problem by performing a clean boot in Windows Vista or in Windows 7

~Tuan

 

[Moochmaker]

Still no dice. I don't think the clean boot will work when every time I login, a black screen comes up with a command prompt and crashes. I'll need to get by that initial part first to see if I can get a clean boot in then.

 

[ttran]

Guess what...I think I would suggest you to do clean install of window 7.
http://www.sevenforums.com/tutorials/1649-clean-install-windows-7-a.html
Because the situaltion that you get rightnow, sounds to me your OS is messed up

~Tuan

 

[Lordbob75]

Hello MoochMaker,

Since you can't boot normally, lets try to fix that.
Boot into safe mode. Open an elevated command prompt (right click, run as admin) and type sfc /scannow. What does it say?

Second option is to attempt a repair install. Boot into your Windows installation disk, and click repair your computer. Just let it check for problems and then fix them.

If none of this works, then a clean install might be the best option. It could be that your CPU is not compatible, or another hardware problem. Before doing a clean install I would recommend trying to boot into a Linux Live CD to see if that crashes. You can also run Memtest86+ - Advanced Memory Diagnostic Tool.

~Lordbob

 

[Moochmaker]

Well, before I read that post, we went ahead and threw the old CPU back in there just to see if it still worked. Luckily, it did. There are a couple of things we've narrowed it down to for the problem. 1) The CPU (as you suggested, bob) could be incompatible and therefore not usable on the mother board or 2) the BIOS wasn't up-to-date and therefore was also not compatible with the new CPU. The OS also could be rejecting the CPU as well (for what reason I have no idea). I will mention that some of our attempts at the things you suggested like the clean install and other ideas met with the computer freezing up which called for a restart. It could be we got the wrong CPU and will just have to make d*** sure we find the right one to use if this one isn't the appropriate one.

 

[Lordbob75]

Well, before I read that post, we went ahead and threw the old CPU back in there just to see if it still worked. Luckily, it did. There are a couple of things we've narrowed it down to for the problem. 1) The CPU (as you suggested, bob) could be incompatible and therefore not usable on the mother board or 2) the BIOS wasn't up-to-date and therefore was also not compatible with the new CPU. The OS also could be rejecting the CPU as well (for what reason I have no idea). I will mention that some of our attempts at the things you suggested like the clean install and other ideas met with the computer freezing up which called for a restart. It could be we got the wrong CPU and will just have to make d*** sure we find the right one to use if this one isn't the appropriate one.

Definitely check your motherboard documentation to double check that it is compatible. Make sure to look for a new BIOS update that might add compatibility.

~Lordbob

 

[Moochmaker]

One more question. Where can I find a lit of compatible upgrades for my processor? Check "My System Specs."

 

[stormy13]

Motherboard in that gateway,

Gateway Support - Specifications

can find the full specs here,

Gateway Support - 1014914R Gateway GT5637E Desktop Computer

There is no reason for the new CPU to not be compatible with that motherboard except for it is in a Gateway computer (same applies to Dell's, HP's, etc), other than the small fact that they would much rather sell you a new computer with a faster CPU than allow for a simple CPU upgrade. This is the latest bios from Gatewat for it,

BIOS ECS-MCP61PM-AM MotherboardVersion 61G114GS

Despite the motherboard being made by ESC, it is a custom OEM made for Gateway and as such they are in complete control of any bios updates for it and what it will support.

If it turns out that the problems with the new CPU come down to a lack of support for it in the bios, you aren't the first and definitely won't be the last to not be able to upgrade the CPU because of it (there are more than a few threads in the hardware forum where it has happened to others).

 

[Moochmaker]

Alright. Well, I'll try updating the bios and see if that helps. As of now, I'm going back to school and don't really want to tinker with my desktop for the rest of the year, but I'll get back to you if the BIOS update ends up working out or not. Guess I'll be SOL until I either get a new computer for the BIOS allows for an upgrade.

 

[cable]

My bro helped me tonight change from the old AMD X2 3800+ CPU to an AMD X2 5200+. After this, we started up the computer normally, passed the login screen, and got to the desktop. It immediately installed drivers for the CPU and asked for a restart. Around 30 seconds or so after that restart, the computer crashed and a bsod popped up.

Looks like you didn't format/reinstall Windows after you installed your CPU- or at least a repair install. It is always recommended (or more so required) to reinstall your Windows after CPU swap. The best way is to reinstall your Windows so it can build the registry and profiles the clean way. Backup, format, and reinstall will be your best bet.
Oh, and the way it keeps restarting, that's how I lost an HDD I/O when I didn't know I had to do a clean install after swapping a CPU.

** I just noticed that Tuan already said what I was going to say lol. Anyways, yes. Please reinstall your Windows = happy system.

 

[Moochmaker]

Still, seems like there should be an easier option than just a reinstall. Shouldn't you just be able to pop in the piece and move on? Just seems like more trouble to get a new CPU unless it's compatible and will just run once it's been put in. But I guess that's just me.

 

[cable]

It is because your windows needs to develop new databases and assign different instructions after a new cpu is introduced to the installation. It is recommended that you wipe and reinstall, but a workaround would be installing your windows as an "upgrade", basically updating your windows files while keeping your program files. Nevertheless, your problem will probably be solved after windows installation.