Fresh install 2 days ago, now random BSOD and freezes, have no idea w

[archieliu]

Hi, I have no idea what is going on with my computer.

I had a faulty hard drive with a bad sector on it and it finally failed on me.
I bought a brand new hard drive and did a fresh install of windows 7

for the past few years my windows had been running fine, but after reinstalling windows on this new hard drive, I am now getting random BSOD very often as well as random freezes.

I have attached the requested information including the cpu-z screenshots please help.

 

[archieliu]

please help? please look at my case

 

[Arc]

Make it sure that your Crucial M4-CT128M4SSD2 is running with the latest firmware.
http://www.crucial.com/support/firmware.aspx

Display driver is crashing irrespective of the driver versions. You may plan to observe teh situation by updating it to WHQL 320.18.

Stress test the Graphics Card using Furmark.
Video Card - Stress Test with Furmark

Is the computer hot? Report us the heat of the computer after a couple of hours of your normal usage. Upload a screenshot of the summery tab of Speccy.

Let us know the results.
___________________________________________________________________________________
BSOD ANALYSIS:

BugCheck 1E, {ffffffffc0000005, fffff880051f4623, 0, ffffffffffffffff}

*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+933623 )

Followup: MachineOwner
-----------------------------------------------------------------------------------------
BugCheck 1A, {5005, fffff70001080000, 7cd8, 7ce2}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+1fff5 )

Followup: MachineOwner
--------------------------------------------------------------------------------------------
BugCheck D1, {16d, 2, 0, fffff88003e9d65b}

Probably caused by : dxgmms1.sys ( dxgmms1!VidSchiSendToExecutionQueue+15b )

Followup: MachineOwner
--------------------------------------------------------------------------------------------
BugCheck 1E, {ffffffffc0000005, 0, 8, 0}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+487ed )

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

 

[archieliu]

Hi Arc,
Thank you for the reply, I was worried that no one will see my post.

I don't have a SSD installed in my computer

and I am running WHQL 320.18 i believe

lastly my computer is not hot at all.

 

[Arc]

Now I see. The zip is got overridden by another zip of the same name. Your issue is totally different than what I have posted earlier. :sarc: It is a stop 0x124, which is supposed to be a hardware error.

Test your RAM modules for possible errors.
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 passes, preferably overnight.

Stress test the Graphics Card using Furmark.
Video Card - Stress Test with Furmark

Stress test the CPU.
Hardware - Stress Test With Prime95

Scan the system for possible virus infection with the following programs.

• Anti-rootkit utility TDSSKiller
• Windows Defender Offline

Scan both the HDDs using WD data lifeguard.
_______________________________________________________________________________
BSOD ANALYSIS:

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

Use !analyze -v to get detailed debugging information.

BugCheck 124, {4, fffffa800c3268d8, 0, 0}

*** WARNING: Unable to verify timestamp for intelppm.sys
*** ERROR: Module load completed but symbols could not be loaded for intelppm.sys
Probably caused by : GenuineIntel

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

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

WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 0000000000000004, PCI Express Error
Arg2: fffffa800c3268d8, Address of the WHEA_ERROR_RECORD structure.
Arg3: 0000000000000000
Arg4: 0000000000000000

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


BUGCHECK_STR:  0x124_GenuineIntel

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  b

STACK_TEXT:  
fffff880`02ffd988 fffff800`02e13a3b : 00000000`00000124 00000000`00000004 fffffa80`0c3268d8 00000000`00000000 : nt!KeBugCheckEx
fffff880`02ffd990 fffff800`02fd6443 : 00000000`00000001 fffffa80`0c2ffb10 00000000`00000000 fffffa80`0c2ff1b0 : hal!HalBugCheckSystem+0x1e3
fffff880`02ffd9d0 fffff880`00e73bcf : fffffa80`00000750 fffffa80`0c2ffb10 00000000`00000000 fffffa80`0c3257f0 : nt!WheaReportHwError+0x263
fffff880`02ffda30 fffff880`00e735f6 : 00000000`00000000 fffff880`02ffdb80 fffffa80`0c410a80 fffff880`02ffdb00 : pci!ExpressRootPortAerInterruptRoutine+0x27f
fffff880`02ffda90 fffff800`02ebba5c : 00000000`00000000 fffff880`02ffdb80 fffffa80`0c410a80 00000000`00000001 : pci!ExpressRootPortInterruptRoutine+0x36
fffff880`02ffdb00 fffff880`0488b9c2 : fffff800`02ec86f9 00000000`003a4a24 fffffa80`0d4bf508 00000000`00000000 : nt!KiInterruptDispatch+0x16c
fffff880`02ffdc98 fffff800`02ec86f9 : 00000000`003a4a24 fffffa80`0d4bf508 00000000`00000000 ffffd319`2f207e22 : intelppm+0x39c2
fffff880`02ffdca0 fffff800`02eb78dc : fffff880`02fd5180 fffff880`00000000 00000000`00000000 fffff880`0110af5c : nt!PoIdle+0x52a
fffff880`02ffdd80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x2c


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: GenuineIntel

IMAGE_NAME:  GenuineIntel

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PCIEXPRESS

BUCKET_ID:  X64_0x124_GenuineIntel_PCIEXPRESS

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