Windows 7 Unexpected BSOD results in crash dump (new custom built computer)

[Vaher]

Hello,

I am requesting assistance with a an occasional hung computer and BSOD. I am unable to obtain "run as administrator" when right click on W7F Diagnostic Tool. W7F Diagnostic Tool error message: "Unhandled exception has occured in your application." Error message details are included in the attachment.

Link Removed

 

[usasma]

Please try running this app: Blue Screen of Death (BSOD) Posting Instructions - Windows 8, 7 & Vista

If you're overclocking, please stop the overclock while we're troubleshooting. Feel free to resume the overclock once the system has been stabilized.

Please un-install ZoneAlarm, it may be conflicting with your Kaspersky.

If all of this doesn't stop the BSOD's, please run these free hardware diagnostics: Link Removed. Let us know the results and we can move on from there.



Analysis:
The following is for informational purposes only.

[FONT=lucida console]**************************Mon Feb 25 13:27:00.708 2013 (UTC - 5:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\022513-5834-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Built by: [B]7601[/B].18044.amd64fre.win7sp1_gdr.130104-1431
System Uptime:[B]0 days 0:33:55.707[/B]
*** WARNING: Unable to verify timestamp for intelppm.sys
*** ERROR: Module load completed but symbols could not be loaded for intelppm.sys
Probably caused by :[B]GenuineIntel[/B]
BugCheck [B]124, {0, fffffa80071a8028, be000000, 800400}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments: 
Arg1: 0000000000000000, Machine Check Exception
Arg2: fffffa80071a8028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000be000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000800400, Low order 32-bits of the MCi_STATUS value.
BUGCHECK_STR:  0x124_GenuineIntel
PROCESS_NAME:  System
FAILURE_BUCKET_ID: [B]X64_0x124_GenuineIntel_PROCESSOR_MAE[/B]
CPUID:        "Intel(R) Core(TM) i7-3770 CPU @ 3.40GHz"
MaxSpeed:     3400
CurrentSpeed: [B]3502[/B]
 
Processor may be overclocked!
Expected Frequency:   3400
Actual Frequency:     3502
Overclock Ratio:      [COLOR=red]1.03[/COLOR]
 
  BIOS Version                  3402
  BIOS Release Date             05/07/2012
  Manufacturer                  System manufacturer
  Product Name                  System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Mon Feb 25 11:48:52.907 2013 (UTC - 5:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\022513-5943-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Built by: [B]7601[/B].18044.amd64fre.win7sp1_gdr.130104-1431
System Uptime:[B]0 days 0:32:36.907[/B]
*** WARNING: Unable to verify timestamp for intelppm.sys
*** ERROR: Module load completed but symbols could not be loaded for intelppm.sys
Probably caused by :[B]GenuineIntel[/B]
BugCheck [B]124, {0, fffffa80071a5028, be000000, 800400}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments: 
Arg1: 0000000000000000, Machine Check Exception
Arg2: fffffa80071a5028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000be000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000800400, Low order 32-bits of the MCi_STATUS value.
BUGCHECK_STR:  0x124_GenuineIntel
PROCESS_NAME:  System
FAILURE_BUCKET_ID: [B]X64_0x124_GenuineIntel_PROCESSOR_MAE[/B]
CPUID:        "Intel(R) Core(TM) i7-3770 CPU @ 3.40GHz"
MaxSpeed:     3400
CurrentSpeed: [B]3502[/B]
 
Processor may be overclocked!
Expected Frequency:   3400
Actual Frequency:     3502
Overclock Ratio:      [COLOR=red]1.03[/COLOR]
 
  BIOS Version                  3402
  BIOS Release Date             05/07/2012
  Manufacturer                  System manufacturer
  Product Name                  System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
[/FONT]

3rd Party Drivers:
The following is for information purposes only.
Any drivers in red should be updated or removed from your system. And should have been discussed in the body of my post.

[FONT=lucida console]**************************Mon Feb 25 13:27:00.708 2013 (UTC - 5:00)**************************
intelppm.sys                Mon Jul 13 19:19:25 2009 (4A5BC0FD)
IOMap64.sys                 Thu Feb  4 20:55:34 2010 (4B6B7A96)
amdxata.sys                 Fri Mar 19 12:18:18 2010 (4BA3A3CA)
btath_rcp.sys               Thu Jun 24 02:17:21 2010 (4C22F871)
btath_flt.sys               Thu Jun 24 02:17:38 2010 (4C22F882)
btath_bus.sys               Thu Jun 24 02:17:43 2010 (4C22F887)
btath_hcrp.sys              Tue Jun 29 05:30:43 2010 (4C29BD43)
jraid.sys                   Tue Aug 10 05:28:44 2010 (4C611BCC)
btath_lwflt.sys             Mon Sep 13 04:26:54 2010 (4C8DE04E)
e1c62x64.sys                Tue Sep 21 17:34:15 2010 (4C9924D7)
HECIx64.sys                 Tue Oct 19 19:33:43 2010 (4CBE2AD7)
ElRawDsk.sys                Tue Oct 26 05:34:13 2010 (4CC6A095)
RTKVHD64.sys                Tue Nov 23 05:14:08 2010 (4CEB93F0)
btath_a2dp.sys              Mon Feb 14 20:47:47 2011 (4D59DB43)
btfilter.sys                Tue Mar  8 01:15:22 2011 (4D75C97A)
iaStor.sys                  Fri May 20 12:52:24 2011 (4DD69C48)
asmtxhci.sys                Wed Sep 14 03:36:09 2011 (4E705969)
asmthub3.sys                Wed Sep 14 03:36:19 2011 (4E705973)
PDFsFilter.sys              Thu May 10 12:29:02 2012 (4FABECCE)
nvhda64v.sys                Tue Jul  3 11:25:04 2012 (4FF30ED0)
klflt.sys                   Fri Aug  3 12:10:13 2012 (501BF7E5)
klif.sys                    Fri Aug 17 11:01:07 2012 (502E5CB3)
nvlddmkm.sys                Thu Aug 30 11:50:16 2012 (503F8BB8)
vsdatant.sys                Mon Oct 29 19:02:35 2012 (508F0B0B)
ISWKL.sys                   Fri Nov  2 13:56:58 2012 (5094096A)
[/FONT]

Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed

 

[Vaher]

usasma,

Thank you for your assistance. It appears that un-installing ZoneAlarm was the solution. Yesterday the computer ran for more then 12 hours, until manual restart. Previously the BSOD would occur within 20 minutes. Bitdefender Internet Security was installed to replace ZoneAlarm.

Should I continue to submit the reports for app: Blue Screen of Death (BSOD) Posting Instructions - Windows 8, 7 & Vista?

 

[usasma]

"Nothing succeeds like success!"
We don't need any further reports unless the BSOD's recur.
I generally suggest waiting a week to see if they'll come back - at that point I think that the BSOD's may be fixed
After 2 weeks without a BSOD - I'm pretty sure that it's been fixed for good.

Good luck to you!

 

[Vaher]

It is good that I did not have to wait two weeks. BSOD returned.

StartRep.exe Application Error
The instructions at 0xfae2297f reference memory at 0xffffffff. The memory could not be read.

Windows Memory Diagnostic tool = no problems

Startup Repair cannot repair this computer automatically.
Problem Details
Problem signature:
Problem Event Name: StartupRepairOffline
Problem Signature 01: 6.1.7600.16385
Problem Signature 02: 6.1.7600.16385
Problem Signature 03: unknown
Problem Signature 04: 21199926
Problem Signature 05: AutoFailure
Problem Signature 06: 2
Problem Signature 07: 0xfc
OS Version: 6.1.7601.2.1.0.256.1
Locale ID: 1033

Restoring system to an earlier time allowed computer startup to continue.

 

[Vaher]

I am also receiving "Error: Windows Explorer has stopped working." For this error I am following the instructions at Error: Windows Explorer has stopped working. I will continuously edit this post with the results from each step that is followed. I will also return to the instructions in usasma's first reply for the BSOD Posting Instructions and the free hardware diagnostics.

1) System File Checker (CFS)
"Windows Resource Protection did not find any integrity violations"

 

[usasma]

If the problems continue, please generate a new set of reports (even though you're not reporting BSOD's).
Also, please do this:

- open Event Viewer (eventvwr.msc)
- expand the Custom Views category (left click on the > next to the words "Custom Views")
- right click on Administrative Events
- select "Save all Events in Custom View as..."
- save the file as Admin.evtx
- zip up the file (right click on it, select "Send to", select "Compressed (zipped) folder")
- upload it with your next post (if it's too big, then upload it to a free file-hosting service and post a link here).