Help with persistent BSODs and freezes please

hadenough · 06 Sep 2011

Diagnostics attached.

Like many, many others I am suffering BSODs and screen freezes with Win7 (Pro 64 bit – Full Retail). After around 18 months of random fails I am just so hacked off with the whole thing.

Sometimes the screen, keyboard and mouse freeze. This requires a manual reboot.
Sometimes there is a BSOD which does not auto reboot i.e. the screen freezes during the memory dump. This also requires a manual reboot. Sometimes there is a BSOD which completes and then auto reboots.

Nearly, but not all return Kernal Power 41 events.

The trouble began a few days after receiving the custom built pc together with peripherals and still persists today despite lots of attention from the custom builders.

For me at least, the desktop is high end….
Intel i7 950 @ 4.2 GHz
Rampage II Extreme
Corsair 3x2 Gb DDR3
NVidia GTX460 1Gb

I cannot ask more from the builders. From the outset they have done everything they can to remedy the issue. With no pressure from me they replaced the mobo, upgraded the graphics card, replaced all the memory and upgraded the cpu. Before returning the pc, Memtest and several other performance tests were run with very good results which were provided as proof.

But within hours of getting it back home I was experiencing issues again. I can only conclude it must be a peripheral or some software which is causing the problem. But the cause is the mystery and forums are full of similar stories.

Some fails occur when the pc has been left running but unused for a while (hibernation is off). But most occur using IE9 (32 bit) when pointing and clicking or scrolling a slider bar. This led me to believe it might be the mouse (Logitech MX518). But today, within 2 minutes of having uninstalled Logitech’s driver and using the MS default I got another BSOD.

Recently I installed Skype with a Logitech camera. This causes BSODs regularly. In the last video conversation it failed 3 times in less than an hour.

In respect of IE9, I noted when experimentally using 64 bit how much slower 32 bit was when grabbing and presenting a page. But if you want to run Adobe Flash then you are obliged to use IE 32 bit because Adobe only have a 64 bit version of Flash in beta. I think I’m right in saying there is a ‘compatibility layer’ between Adobe Flash (32 bit) and all 64 bit os. So, clutching at straws I ponder if that ‘layering’ might have any influence at all?

Several times in the past, just to see what happened, I have simultaneously, streamed 2 x F1 videos, run my own heavy number crunching VBA software in MS Excel, had multiple tabs open in other instances of IE, run a cd in the BluRay player and pointed the mouse all over the place. It didn’t fail on any occasion and all ran as expected.

Silly as it may seem, the busier the cpu the less risk of failure there seems to be.

So I am at a loss. What is going on? There has to be a reason for this and I would be very grateful of any assistance or advice regarding next steps to resolve this frustrating business.

T.I.A.

hadenough · 09 Sep 2011

Sorry to bump but I have not made much progress on my own. Attached are new data files.

Since my first post 3 days ago I have had a number of other BSODs but not all produced minidumps. (Tonight I followed advice to another poster from zigzag3143 on ensuring minidumps are enabled.)

I also noted advice to make changes one at a time so as to determine the cause.

After the initial post I noticed a number of threads highlighted the Win7 conflict caused by ATK0110 ACPI UTILITY and was astonished to see I had the older version installed by the custom builder, either initially at Xmas 2009, or earlier this year when they did a refurb. This is now updated to 2009.

BTW I updated the file using Device Manager. The new file shows correctly there and is also shown as changed in the Sys32 driver folder but I cannot see it listed in any of the NT6_BSOD txt files produced today. Is this ok?

After the change I did not have any issues and began to hope until browsing yesterday when it froze and BSODed.

I then progressed to another driver update as indicated by driveragent and chose the Marvell Yukon 88E8056 PCI-E Gigabit Ethernet Controller.

After about 4 hours I got 2 more BSODs whilst browsing but they did not produce a minidump.

Today there have been a number of BSODs. One whilst browsing but then several whilst running a weekly virus scan with GData. Not all produced a minidump. This has been giving problems over the last few weeks so last week I un-installed and re-installed it after which it scanned properly – but not tonight.

I’d appreciate someone having a look. I’m sorry about the size of the files but then I have lived with these BSODs for some time.

Jonathan_King · 10 Sep 2011

Hello,

It still looks like there is a hardware problem at fault here. Seeing some of these:

Code:

Event[160]:
  Log Name: System
  Source: Microsoft-Windows-WHEA-Logger
  Date: 2011-09-09T20:58:17.980
  Event ID: 18
  Task: N/A
  Level: Error
  Opcode: Info
  Keyword: N/A
  User: S-1-5-19
  User Name: NT AUTHORITY\LOCAL SERVICE
  Computer: Geoff-PC
  Description: 
A fatal hardware error has occurred.

Reported by component: Processor Core
Error Source: Machine Check Exception
Error Type: Internal Timer Error
Processor ID: 0

The details view of this entry contains further information.

HOWEVER: we have seen SPTD cause the 0x124 bugcheck before, so start out by removing it with it's installer/uninstaller utility: DuplexSecure - Downloads

Other things we can throw at this: a BIOS update. Flash the latest BIOS from here: ASUSTeK Computer Inc. - Motherboards- ASUS Rampage II Extreme

Code:

BIOS Version/Date    American Megatrends Inc. 1802, 28/01/2010

How is the power situation at your house? Could it be any less stable than the power at the PC shop? Might you have an overloaded circuit? Devices with lots of noise on the same circuit as your computer? It might be worth it to move the computer to a different circuit, one not heavily loaded.

Just for kicks, you might run the Prime95 tests: https://www.sevenforums.com/tutorials...t-prime95.html

...Summary of the dumps:

Code:


Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Tue Aug 16 09:06:30.304 2011 (UTC - 4:00)
System Uptime: 0 days 0:00:06.226
Probably caused by : hardware
BUGCHECK_STR:  0x124_GenuineIntel
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_MAE_PRV
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Tue Aug 16 08:19:07.133 2011 (UTC - 4:00)
System Uptime: 0 days 0:00:06.101
Probably caused by : hardware
BUGCHECK_STR:  0x124_GenuineIntel
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_MAE_PRV
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Fri Aug 12 19:01:50.148 2011 (UTC - 4:00)
System Uptime: 0 days 0:00:06.070
Probably caused by : hardware
BUGCHECK_STR:  0x124_GenuineIntel
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_MAE_PRV
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Fri Aug  5 18:08:17.757 2011 (UTC - 4:00)
System Uptime: 0 days 0:00:06.678
Probably caused by : hardware
BUGCHECK_STR:  0x124_GenuineIntel
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_MAE_PRV
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Fri Aug  5 11:44:06.414 2011 (UTC - 4:00)
System Uptime: 0 days 0:00:06.335
Probably caused by : hardware
BUGCHECK_STR:  0x124_GenuineIntel
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_MAE_PRV
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Wed Jul 27 01:47:25.070 2011 (UTC - 4:00)
System Uptime: 0 days 0:00:05.881
Probably caused by : hardware
BUGCHECK_STR:  0x124_GenuineIntel
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_MAE_PRV
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Tue Jul 26 11:25:02.008 2011 (UTC - 4:00)
System Uptime: 0 days 0:00:05.929
Probably caused by : hardware
BUGCHECK_STR:  0x124_GenuineIntel
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_MAE_PRV
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Thu Jul 21 03:06:06.961 2011 (UTC - 4:00)
System Uptime: 0 days 0:00:05.882
Probably caused by : hardware
BUGCHECK_STR:  0x124_GenuineIntel
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_MAE_PRV
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Thu Jul 14 03:24:36.992 2011 (UTC - 4:00)
System Uptime: 0 days 0:00:05.914
Probably caused by : hardware
BUGCHECK_STR:  0x124_GenuineIntel
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_MAE_PRV
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Tue Jul 12 11:53:56.055 2011 (UTC - 4:00)
System Uptime: 0 days 0:00:05.976
Probably caused by : hardware
BUGCHECK_STR:  0x124_GenuineIntel
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_MAE_PRV
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Thu Jul  7 10:01:56.086 2011 (UTC - 4:00)
System Uptime: 0 days 0:00:06.007
Probably caused by : hardware
BUGCHECK_STR:  0x124_GenuineIntel
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_MAE_PRV
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Tue Jun 28 18:12:36.086 2011 (UTC - 4:00)
System Uptime: 0 days 0:00:06.007
Probably caused by : hardware
BUGCHECK_STR:  0x124_GenuineIntel
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_MAE_PRV
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Sat Jun 25 14:11:41.148 2011 (UTC - 4:00)
System Uptime: 0 days 0:00:06.070
Probably caused by : hardware
BUGCHECK_STR:  0x124_GenuineIntel
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_MAE_PRV
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Fri Jun 17 13:28:07.351 2011 (UTC - 4:00)
System Uptime: 0 days 0:00:06.272
Probably caused by : hardware
BUGCHECK_STR:  0x124_GenuineIntel
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_MAE_PRV
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Fri Jun 17 04:03:08.008 2011 (UTC - 4:00)
System Uptime: 0 days 0:00:05.929
Probably caused by : hardware
BUGCHECK_STR:  0x124_GenuineIntel
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_MAE_PRV
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Fri Sep  9 14:59:41.350 2011 (UTC - 4:00)
System Uptime: 0 days 0:00:07.271
Probably caused by : hardware
BUGCHECK_STR:  0x124_GenuineIntel
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_MAE_PRV
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Fri Sep  9 14:07:57.741 2011 (UTC - 4:00)
System Uptime: 0 days 0:00:06.662
Probably caused by : hardware
BUGCHECK_STR:  0x124_GenuineIntel
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_MAE_PRV
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Fri Sep  9 15:58:09.336 2011 (UTC - 4:00)
System Uptime: 0 days 0:00:06.257
Probably caused by : hardware
BUGCHECK_STR:  0x124_GenuineIntel
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_MAE_PRV
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Thu Sep  8 07:15:03.164 2011 (UTC - 4:00)
System Uptime: 0 days 0:00:06.085
Probably caused by : hardware
BUGCHECK_STR:  0x124_GenuineIntel
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_MAE_PRV
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Tue Sep  6 04:13:47.086 2011 (UTC - 4:00)
System Uptime: 0 days 0:00:06.007
Probably caused by : hardware
BUGCHECK_STR:  0x124_GenuineIntel
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_MAE_PRV
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Sat Sep  3 14:59:20.648 2011 (UTC - 4:00)
System Uptime: 0 days 0:00:06.458
Probably caused by : hardware
BUGCHECK_STR:  0x124_GenuineIntel
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_MAE_PRV
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Fri Sep  2 23:25:26.320 2011 (UTC - 4:00)
System Uptime: 0 days 0:00:06.241
Probably caused by : hardware
BUGCHECK_STR:  0x124_GenuineIntel
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_MAE_PRV
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Tue Aug 30 21:07:23.992 2011 (UTC - 4:00)
System Uptime: 0 days 0:00:05.914
Probably caused by : hardware
BUGCHECK_STR:  0x124_GenuineIntel
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_MAE_PRV
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Sat Aug 27 01:37:16.008 2011 (UTC - 4:00)
System Uptime: 0 days 0:00:05.929
Probably caused by : hardware
BUGCHECK_STR:  0x124_GenuineIntel
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_MAE_PRV
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Thu Aug 25 04:41:55.180 2011 (UTC - 4:00)
System Uptime: 0 days 0:00:06.101
Probably caused by : hardware
BUGCHECK_STR:  0x124_GenuineIntel
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_MAE_PRV
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Wed Aug 24 10:04:56.070 2011 (UTC - 4:00)
System Uptime: 0 days 0:00:05.992
Probably caused by : hardware
BUGCHECK_STR:  0x124_GenuineIntel
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_MAE_PRV
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Fri Aug 19 17:48:35.616 2011 (UTC - 4:00)
System Uptime: 0 days 0:00:06.427
Probably caused by : hardware
BUGCHECK_STR:  0x124_GenuineIntel
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_MAE_PRV
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Fri Aug 19 06:53:58.961 2011 (UTC - 4:00)
System Uptime: 0 days 0:00:05.882
Probably caused by : hardware
BUGCHECK_STR:  0x124_GenuineIntel
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_MAE_PRV
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Fri Aug 19 06:20:44.024 2011 (UTC - 4:00)
System Uptime: 0 days 0:00:05.834
Probably caused by : hardware
BUGCHECK_STR:  0x124_GenuineIntel
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_MAE_PRV
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

hadenough · 10 Sep 2011

Hi Jonathan

I'm grateful for the response......

What is SPTD please?

Will flash the BIOS but I've never done that before. Will that change the overclock settings?

Power situation - interesting you suggest that one. I use a APC UPS. A week ago we had a blackout for 20 minutes or so and the UPS kept me going long enough to shut down properly. It does however represent a difference in my setup and the shop's. But I believed a UPS was meant to iron out spikes so had almost ruled that out as a possible cause. What has made you think it could be a problem?

Prime95 etc - when I took the pc back earlier this year I offered to take keyboard and mouse etc so they could test the whole kit supplied by them but they declined. After the replacements referred to earlier they thoroughly tested with.... Core Temp, FurMark_v1.6.5, hdtune_255, linpack64, LinX, memtest, OCCT, PRIME95, SUPER_PI.

The overclock was fine tuned and they really stressed the pc before declaring it fit for purpose. However in less than a day it had BSODed which is why I concluded it must be a peripheral or some software conflict.

Jonathan_King · 10 Sep 2011

Honestly, I doubt a peripheral would cause such problems as you are having. We do see some unusual things though, so if you have spares of anything, it certainly can't hurt.

SPTD is a driver for CD emulation programs, namely Daemon Tools and Alcohol 120%. I don't see either program installed, so I assume one was installed at an earlier time and has since been removed. SPTD remains behind, though. SPTD has a long history of causing crashes since Vista, and can fool the unsuspecting analyst into thinking there is hardware problem due to the nature of the errors. I'd still think this is a hardware problem, but as long as we don't know what the problem is...

Flashing the BIOS will reset your overclock settings. I didn't realize it was overclocked though; that could have something to do with it. Even if the stress tests pass, it's still worth resetting the default clocks.

I mentioned the power supply because it seemed to be the only hardware they didn't replace. Insufficient power to the hardware can indeed cause 0x124 BSODs, or voltage drops. You're right, the UPS should be working to stabilize the power, but what if the UPS itself is not passing along enough power to the computer? I'm not 100% firm in my knowledge there, but it may be worth running straight from the wall (better, a standard surge protector power strip, if you have one) for a couple days.

Just trying things here. The standard procedure for dealing with your kind of BSODs is running a host of hardware diagnostics, and replacing components based on that. Yet when it seems all has been tried, we must come up with other things!

hadenough · 10 Sep 2011

You are right that Daemon Tools had been installed and removed. SPTD is now also removed.

As you may gather I am not pc component experienced and after checking the Asus site, flashing the BIOS sounds scary. Thanks for confirming it will reset my overclock. As the site suggests I will need to make careful notes of all my settings before embarking on that course.

The power supply suggestion is easy to implement of course.

Because of the nature of the beast I quite understand that success is going to be more of a 'ah it hasn't BSODed since..... whatever the last action was'. So the process could take some time BUT I am mightily encouraged by your last remark "Yet when it seems all has been tried, we must come up with other things!".

Thanks for that. There is a cause lurking around somewhere. I will now get on with your suggestions.

hadenough · 11 Sep 2011

I have now put the pc on to a direct power supply i.e. non UPS.

There have been 5 BSODs today. The first happened whilst opening an avi video in WM. As soon as I clicked to open the file it BSODed with bugcheck #1. The second happened whilst I was looking at one of the jcgriff2 reports using NotePad and scrolling with the mouse - that was bugcheck #156.

Following this, I later ran Prime95 and set it to 'Small FFT'. The first and third attempts lasted beyond Test1 before a BSOD occurred - about 70 minutes I think. The second attempt failed with a BSOD immediately the program was started. All 3 bugchecks were #292.

I do not know the meaning of any of those references. Is #292 in any way related to #124 which in my innocent way I might have expected with a CPU based failure?

I'm disappointed Prime95 produced failures like this because the tests undertaken by the builder after their refurb showed the pc had performed without failure - and proof was provided. However, I begin now to appreciate the consequences of why they mentioned it was tested with a vanilla implementation of Win7. But I'm ok with that because they cannot be responsible for the software a customer chooses to run. On the other hand however, they must have also installed the old version of ATK0110 ACPI UTILITY and thus caused potential conflict. So it's not a perfect world.

As to other possible causes, I'm aware some disapprove of overclocking but there must be many, many thousands of overclocked pcs running Win7 quite happily and thus I am very reluctant to give up what I have paid for.

I've read in some expert responses that conflicts may lie hidden for some time until a user reports an unusual occurence and that is why feedback is so beneficial to all. But predominantly my pc's most common failure, #124, occurs when browsing using IE(8 now 9) 32 bit on ordinary websites and typically they occur when scrolling or moving the mouse to say change a tab.

Running Prime95 has caused failure. If #292 is hardware related do I go back to the builder and ask them to check everything again? I have explained here my reluctance to flash the BIOS as it will undo the overclock so should I update every driver I can find, chipsets, graphics, the lot? Or is there perhaps something you can spot that's different in the latest minidumps?

Jonathan_King · 12 Sep 2011

I suppose this cones down to how you look at it. You paid for an overclocked PC, yet you are having BSODs and freezes. The faster speeds may be nice, but as it is now, you lose more time than you save when the PC restarts all the time. And let me assure you, the overclocking doesn't make as much difference as you may be thinking. In CPU-intensive applications, it may help more, but in everyday browsing (surfing the web, watching videos), you won't notice a difference.

That having been said, if you're intent on having that overclock, remember, you can always set it up again yourself. If you note the overclock settings before you flash the BIOS, you can restore them afterwards. Better yet, leave it stock-clocked until after the BSODs have been shaken. Then start back up again if you wish.

You might also try diagnosing this as a hardware problem, without the further use of software diagnostics. Remove all but one stick of RAM, and if the problems persist, put in another instead. If the problem still persists, rule out a RAM problem.

hadenough · 12 Sep 2011

Ok re pointing towards a hardware issue - I'll give that a try. Should I also update chipsets etc?

I agree with your views about overclocking and use with non-intensive cpu packages. Part of the initial strategy was to provide a reasonable platform so my visiting sons could play their games. But as one has emigrated to Australia and the other has also moved away it is less and less appropraite to maintain the overhead.

Now that thought has set me wondering - I remember a long way back they did try to install a game but it wouldn't do so properly. I wonder if the resultant uninstall has somehow left a legacy even though I use CCleaner to clean the registry on a regular basis?

BTW there was another BSOD this morning - all I was doing was shutting down. It produced the same error code as the fails with Prime95 i.e. #292.

Thanks for your time so far I am determined to see and end to this isue now.

Jonathan_King · 12 Sep 2011

Personally, I wouldn't be too concerned about the chipset drivers. If you really want to you can, it won't hurt anything. I have trouble seeing this as anything but a hardware or BIOS problem though, including failed game installations. Leftover registry entries shouldn't cause any problems, but even if they did, they wouldn't show as hardware errors in the Event Viewer.