[SOLVED] BSOD after CPU upgrade - Windows 7 x64

T

Teamow

New member
Joined
May 29, 2015
Posts
3
Hi!

I have installed a new CPU on my mobo. During the first boot my mobo notified me of the newly placed CPU and the startup that followed was all fine. Windows recognised the new CPU and installed the necessary drivers. After a while I received a first BSOD, I restarted hoping it was an incident, unfortunately it wasnt.

In a first attempt to fix it I deleted the drivers of the old cpu in the device manager but that didn't make any difference. Later on the BSOD shows up almost immediately after starting up windows and reaching the desktop. Next I tried to reset the mobo and update to the latest bios version, again no result.

Because I started to get despreate I took out the cpu and installed it again to be sure that the installation was right. As you might guess, nothing changed.

Looking around the internet I found a thread on this website with the same BSOD as I have after installing a new CPU, unfortunately that solution didn't work for me but hopefully someone has another idea for me.


Specs:
Os: Windows 7 x64
Motherboard: Asus M5A78L-M LE
Old CPU: AMD phenom II x4 955
New CPU: AMD FX-6300
GPU: Asus HD7790


BSOD Dump file: https://drive.google.com/open?id=0B-O017kkFtLvTmMzYlhfS2VGUTg&authuser=0



WhoCrashed analysis:
On Fri 29-5-2015 8:52:21 GMT your computer crashed
crash dump file: C:\Windows\Minidump\052915-28095-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x101 (0x21, 0x0, 0xFFFFF88002F65180, 0x2)
Error: CLOCK_WATCHDOG_TIMEOUT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an expected clock interrupt on a secondary processor, in a multi-processor system, was not received within the allocated interval.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
 

Attachments

Your Google Drive account is locked, I'm assuming you've uploaded the file to a Private folder?

Is the file on your Google Drive a Kernel Memory Dump?
 
To debug 0x101s, we'll need a Kernel memory dump.

Go the Start
Right click My Computer
Select Properties
Click Advanced system settings
Click on the Advanced tab
Select Settings under Startup and Recovery
Then under Write debugging information select Kernel memory dump.

Once a dump is created go to:
C:/Windows/memory.dmp
Copy the file to the desktop, zip it up and upload it to a file sharing site like Onedrive. After the upload is done post the download link in your next reply.

Harry beat me to it by a few minutes!
 
My bad, was my first time using google drive, the link below should be better.

https://onedrive.live.com/redir?resid=FD21E40B83311B7D!144&authkey=!APUQFtld8HQaRC0&ithint=file,rar


In the mean time I have been trying to solve the problems by doing a clean install. My system still has the same issues although the analysis from WhoCrashed has changed:

[FONT=Segoe UI, Arial]On Sat 5/30/2015 10:11:04 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\053015-28017-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x4A63CC)
Bugcheck code: 0x124 (0x0, 0xFFFFFA8004C19218, 0x0, 0x0)
Error: [FONT=Segoe UI, Arial]WHEA_UNCORRECTABLE_ERROR[/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 bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.


I just put in my old CPU and my system is stable again. Which is pretty ironic since my motherboard doesn't support this cpu, which was the entire reason for me to get a supported CPU [/FONT]:huh:
[FONT=Segoe UI, Arial]

[/FONT]
 
Code: 
4: kd> [COLOR=#008000]lmvm P17[/COLOR]
Browse full module list
start             end                 module name
fffff880`07678000 fffff880`077fd000   P17        (no symbols)           
    Loaded symbol image file: P17.sys
    Image path: \SystemRoot\system32\drivers\P17.sys
    Image name: P17.sys
    Browse all global symbols  functions  data
    Timestamp:        [COLOR=#ff0000]Fri Oct 16 07:44:53 2009[/COLOR] (4AD81665)
    CheckSum:         0013FE04
    ImageSize:        00185000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

This driver does seem rather old, start of the Windows 7 era? I would suggest looking for updates from the driver page here - Creative Worldwide Support > Sound Blaster 5.1 VX


----------------------------------------
----------------------------------------

Code: 
[COLOR=#ff0000]BugCheck 101[/COLOR], {21, 0, [COLOR=#ff8c00]fffff88002f65180[/COLOR], [COLOR=#0000cd]2[/COLOR]}

Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )

Code: 
2: kd> [COLOR=#008000]!prcb[/COLOR]
PRCB for Processor 2 at fffff88002f65180:
Current IRQL -- 0
Threads--  Current fffff88002f70040 Next fffffa8008dfb440 Idle fffff88002f70040
Processor Index 2 Number (0, 2) GroupSetMember 4
Interrupt Count -- 0000dfa0
Times -- Dpc    0000000b Interrupt 00000005 
         Kernel 00000cff User      00000018

It appears that a clock interrupt hasn't been serviced by the processor.

Code: 
2: kd> [COLOR=#008000]!running[/COLOR]

System Processors:  (000000000000003f)
  Idle Processors:  (0000000000000022) (0000000000000000) (0000000000000000) (0000000000000000)

       Prcbs             Current         (pri) Next            (pri) Idle
  0    fffff80004852e80  fffffa8006bad040 (15)                       fffff80004860cc0  ................
  [COLOR=#0000cd]2[/COLOR]    [COLOR=#ff8c00]fffff88002f65180[/COLOR]  [COLOR=#ff0000]fffff88002f70040[/COLOR] ( 0) fffffa8008dfb440 (30) fffff88002f70040  ................
  3    fffff88002fd7180  fffff88002fe2040 ( 0) fffffa80096eb060 (22) fffff88002fe2040  ................
  4    fffff880009b3180  fffffa8006b91b50 (13)                       fffff880009be040  ................

The Interrupt Flag hasn't been set either, indicating that the processor isn't able to service interrupts properly.

Code: 
2: kd> [COLOR=#008000]r @if[/COLOR]
if=[COLOR=#ff0000]0[/COLOR]

The Clock Interrupt is usually followed with a IPI:

Code: 
0: kd> [COLOR=#008000]!ipi[/COLOR]
IPI State for Processor 0

    As a sender, awaiting IPI completion from processor(s) 2, 3.

    TargetCount          2  PacketBarrier        1  IpiFrozen     0 [Running]


IPI State for Processor 1
    TargetCount          0  PacketBarrier        0  IpiFrozen     2 [Frozen]


IPI State for [COLOR=#ff0000]Processor 2[/COLOR]

    As a receiver, unhandled requests are pending from processor(s) 0, 4.

    TargetCount          0  PacketBarrier        0  IpiFrozen     5 [Target Freeze]

    From processor 0, active request of type: flush multiple range
        Flush Count 1  Flush List fffff88003374638  (dp fffff88003374638 l1)
    From processor 4, active request of type: packet ready
        WorkerRoutine fffff800046c8e10 (nt!FsRtlpNopStackOverflowRoutine)
        Parameter[0] 0  Parameter[1] 0  Parameter[2] 0

IPI State for Processor 3

    As a receiver, unhandled requests are pending from processor(s) 0, 4.

    TargetCount          0  PacketBarrier        0  IpiFrozen     5 [Target Freeze]

    From processor 0, active request of type: flush multiple range
        Flush Count 1  Flush List fffff88003374638  (dp fffff88003374638 l1)
    From processor 4, active request of type: packet ready
        WorkerRoutine fffff800046c8e10 (nt!FsRtlpNopStackOverflowRoutine)
        Parameter[0] 0  Parameter[1] 0  Parameter[2] 0

IPI State for Processor 4

    As a sender, awaiting IPI completion from processor(s) 2, 3.

    TargetCount          2  PacketBarrier        1  IpiFrozen     2 [Frozen]


IPI State for Processor 5
    TargetCount          0  PacketBarrier        0  IpiFrozen     2 [Frozen]
 
To be honest, I haven't had a good look into the stacks and the other threads to see exact cause, I haven't got that much time at the moment.
 
Code: 
0: kd> .dumpdebug
----- 64 bit Kernel Summary Dump Analysis

DUMP_HEADER64:
MajorVersion        0000000f
MinorVersion        00001db1
KdSecondaryVersion  00000000
DirectoryTableBase  00000000`00187000
PfnDataBase         fffffa80`00000000
PsLoadedModuleList  fffff800`048a56d0
PsActiveProcessHead fffff800`048873d0
MachineImageType    00008664
NumberProcessors    00000006
BugCheckCode        00000101
BugCheckParameter1  00000000`00000021
BugCheckParameter2  00000000`00000000
BugCheckParameter3  fffff880`02f65180 //PRCB of the processor that caused the crash
BugCheckParameter4  00000000`00000002
KdDebuggerDataBlock fffff800`048510a0
SecondaryDataState  00000000
ProductType         00000001
SuiteMask           00000110

SUMMARY_DUMP64:
DumpOptions         504d4453
HeaderSize          00049000
BitmapSize          00237000
Pages               00018bf0
Bitmap.SizeOfBitMap 00237000

KiProcessorBlock at fffff800`0490fc40
  6 KiProcessorBlock entries:
  fffff800`04852e80 fffff880`009e9180 fffff880`02f65180 fffff880`02fd7180 fffff880`009b3180 fffff880`030a5180

//Processor #2 caused the crash

0: kd> ~2

2: kd> !prcb
PRCB for Processor 2 at fffff88002f65180:
Current IRQL -- 0
Threads--  Current fffff88002f70040 Next fffffa8008dfb440 Idle fffff88002f70040
Processor Index 2 Number (0, 2) GroupSetMember 4
Interrupt Count -- 0000dfa0
Times -- Dpc    0000000b Interrupt 00000005 
         Kernel 00000cff User      00000018 

2: kd> !running -it

System Processors:  (000000000000003f)
  Idle Processors:  (0000000000000022) (0000000000000000) (0000000000000000) (0000000000000000)

       Prcbs             Current         (pri) Next            (pri) Idle
  0    fffff80004852e80  fffffa8006bad040 (15)                       fffff80004860cc0  ................


Child-SP          RetAddr           Call Site
fffff880`033741d8 fffff800`0472ea4a nt!KeBugCheckEx //Expired without response, bugcheck
fffff880`033741e0 fffff800`046e16f7 nt!KeAccumulateTicks+0x4e3e //Count the ticks for the IPI
fffff880`03374270 fffff800`04623895 nt!KeUpdateSystemTime+0x377 //CLOCK_LEVEL update the system time
fffff880`03374370 fffff800`046d4113 hal!HalpHpetClockInterrupt+0x8d //High Precision Event Timer
fffff880`033743a0 fffff800`046dc9f0 nt!KiInterruptDispatchNoLock+0x163 //Send interrupt
fffff880`03374530 fffff800`046f7251 nt!KeFlushMultipleRangeTb+0x260 //Flush all TLBs
fffff880`03374600 fffff800`046f9c98 nt!MiFlushTbAsNeeded+0x1d1  //Flush TLB if needed
fffff880`03374710 fffff800`04808f86 nt!MiAllocatePagedPoolPages+0x4cc
fffff880`03374830 fffff800`046f79b0 nt!MiAllocatePoolPages+0x906
fffff880`03374970 fffff800`0480c43e nt!ExpAllocateBigPool+0xb0
fffff880`03374a60 fffff800`049f5a85 nt!ExAllocatePoolWithTag+0x82e
fffff880`03374b50 fffff800`049f563f nt!EtwpRealtimeFlushSavedBuffers+0x55
fffff880`03374b80 fffff800`049742ea nt!EtwpLogger+0x1af
fffff880`03374c00 fffff800`046c88e6 nt!PspSystemThreadStartup+0x5a
fffff880`03374c40 00000000`00000000 nt!KxStartSystemThread+0x16

  1    fffff880009e9180  fffff880009f4040 ( 0)                       fffff880009f4040  ................

Child-SP          RetAddr           Call Site
fffff880`02f1bb28 fffff880`072d772d amdppm!ReadIoMemRaw+0x30
fffff880`02f1bb30 fffff800`046e0709 amdppm!ReadGenAddr+0x21
fffff880`02f1bb60 fffff800`046cf89c nt!PoIdle+0x52a
fffff880`02f1bc40 00000000`00000000 nt!KiIdleLoop+0x2c

  2    fffff88002f65180  fffff88002f70040 ( 0) fffffa8008dfb440 (30) fffff88002f70040  ................

Child-SP          RetAddr           Call Site
00000000`00000000 00000000`00000000 0x0

  3    fffff88002fd7180  fffff88002fe2040 ( 0) fffffa80096eb060 (22) fffff88002fe2040  ................

Child-SP          RetAddr           Call Site
00000000`00000000 00000000`00000000 0x0

  4    fffff880009b3180  fffffa8006b91b50 (13)                       fffff880009be040  ................

Child-SP          RetAddr           Call Site
fffff880`031aff90 fffff800`0499434f nt!KeFlushProcessWriteBuffers+0x65
fffff880`031b0000 fffff800`049e2956 nt!ExpGetProcessInformation+0x7f
fffff880`031b0150 fffff800`049e33ad nt!ExpQuerySystemInformation+0xfb4
fffff880`031b0500 fffff800`046d6e53 nt!NtQuerySystemInformation+0x4d
fffff880`031b0540 fffff800`046d3410 nt!KiSystemServiceCopyEnd+0x13
fffff880`031b06d8 fffff880`01180e8c nt!KiServiceLinkage
fffff880`031b06e0 fffff880`011813ed cng!GatherRandomKey+0x22c
fffff880`031b0aa0 fffff800`049ce1ed cng!scavengingWorkItemRoutine+0x3d
fffff880`031b0b40 fffff800`046e1261 nt!IopProcessWorkItem+0x3d
fffff880`031b0b70 fffff800`049742ea nt!ExpWorkerThread+0x111
fffff880`031b0c00 fffff800`046c88e6 nt!PspSystemThreadStartup+0x5a
fffff880`031b0c40 00000000`00000000 nt!KxStartSystemThread+0x16

  5    fffff880030a5180  fffff880030b0040 ( 0)                       fffff880030b0040  ................

Child-SP          RetAddr           Call Site
fffff880`030cdb28 fffff880`072d772d amdppm!ReadIoMemRaw+0x30
fffff880`030cdb30 fffff800`046e0709 amdppm!ReadGenAddr+0x21
fffff880`030cdb60 fffff800`046cf89c nt!PoIdle+0x52a
fffff880`030cdc40 00000000`00000000 nt!KiIdleLoop+0x2c

2: kd> r
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=0000000000000000 rsp=0000000000000000 rbp=0000000000000000
 r8=0000000000000000  r9=0000000000000000 r10=0000000000000000
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up di pl nz na pe nc
cs=0000  ss=0000  ds=0000  es=0000  fs=0000  gs=0000             efl=00000000
00000000`00000000 ??              ???

2: kd> ~3

3: kd> r
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=0000000000000000 rsp=0000000000000000 rbp=0000000000000000
 r8=0000000000000000  r9=0000000000000000 r10=0000000000000000
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up di pl nz na pe nc
cs=0000  ss=0000  ds=0000  es=0000  fs=0000  gs=0000             efl=00000000
00000000`00000000 ??              ???

Processor #2 and #3 were both null and completely unresponsive when performing HPET functions.
HPET is used to monitor system time and run time on a system, by allowing preemptive functionality through expiring timers, controlling thread quantum etc.
Therefore, it is imperative that all processors respond to CLOCK_LEVEL interrupts.
In the event that the registers are null, with nothing on the stack because they are unresponsive, you've got a bad CPU.

I recommend you RMA the CPU if it is under warranty, which it should be given it is new.
You can try updating driver(s), as suggested by x BlueRobot, but I'm positive this is a CPU hardware error.
As well as the fact that this only occurred after a new CPU upgrade.
 
Last edited:
I can do some advanced troubleshooting with the help of good old Mr. Google but beyond that i'm pretty much lost, so it's really awesome you guys helped me out, so thnx for all the help! Much appreciated.

The driver update had no result so I will return the CPU to the seller. I assume it will be considered as DOA and that they will give me a new one, hopefully that installation will go a bit smoother.

Thnx again!
 
Yes, it'll be a faulty CPU out of a batch, it happens.
Just let them know and they should sort everything out.
 

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

Back
Top