BSOD's when transferring data ( I think)

[Scritty]

Hi,
Sorry for posting. I could really do with your help.
Home Built PC - 3 years old (except GFX which is 2 years old)
Windows 7 full retail

A few weeks ago my PC started to experience rare BSOD's. THese only occcured when data was being transferred in large quanities. Either from drive to drive or over a network.

During normal use, it was very stable (I play games, watch videos - I understand that they also transfer data as well, but I have not had any BSOD's while doing this)

A few days back I wanted to install a game client over the internet (Lord of the Rings online) It crashed about 3x while uploading the file (it was 9 gigabytes) then crashed everytime I tried to instal from the file.

I was getting concerned, so I started to back up all my files to a mobile HDD in readyness for a clean OS install I have. A couple of times during this process the system crashed again (again while transferring files)

If I grabbed a whole load at once it would crash. If i picked out a few 10's of meg at a time it was fine.

I did a full format of the HDD's and re-installed Windows 7 (full retail package)

I then put on Macafee, and a while later it crashed (Argghh). I carried on for a day, but it crashed a few more times - again while transferring stuff or downloading.
I ran Seagate drive analyzer on full - and it returned no issues.
I ran memtest86 for 4 hours - again no issues

So after advice elsewhere I uninstalled Macafee and installed AVG free (i used a tool to uninstall macafee)

A few minutes after the system crashed twice more

I realized it was because I still had "driver analyzer running" so I turned it off.

A couple of hours later it crashed again

I suspect it is either a major hardware failure (CPU or motherboard) or something really stupid I have overlooked.

Hoping it's the latter (i'm skint)

I really appreciate the help here everyone.

Regards

Paul Clarke

 

[Scritty]

edit - Just ran something called prime95 and I got a BSOD after a matter of a second or two.
Does this mean it's definitely the processor? Or could it still be something else (sorry - I'm really dim when it comes to blue screens)


Thanks
Sorry to bump - About to fall off page one, and (like Princess Leia said) you're my only hope.

Paul

 

[usasma]

12 memory dumps over 3 days - that's a lot!
It looks like most of these are STOP 0x124 errors. More info on that here: BSOD Index
Troubleshooting suggestions here: http://www.sevenforums.com/crash-lockup-debug-how/35349-stop-0x124-what-means-what-try.html

Have you updated your Razer Copperhead drivers? They have, in the past, had issues with Win7
Have you updated your Belkin wireless USB adapter? Here's a link for that: Belkin : Support : F5D8055 Wireless N+ USB Adapter - Driver + Utility FWIW - I don't recommend using these devices. A card that plugs into your motherboard will be more robust and reliable - and you should also notice a speed increase when using it.

More to follow once the memory dumps are finished running....

 

[usasma]

Lot's of hal.dll involvement - I'd suggest checking your hardware and software for compatibility at this link: Windows 7 Compatibility: Software Programs & Hardware Devices: Find Updates, Drivers, & Downloads

The Verifier enabled memory dumps blame your Copperhead drivers. Uninstall them to see if it stops the BSOD's. If it does, install a fresh copy of Win7 compatible drivers in order to use your Copperhead.
Here's the current driver:

copperhd.sys Tue Nov 01 22:54:42 2005 (43682A72)

That's before Win7 was a gleam in Bill Gates' eye!

Also, your MSI PCAlert program dates from 2008, please uninstall it.

IMO the Copperhead drivers are the most likely cause. But, that may not be the only problem. That's because of the large number of different error messages - but that's offset by the number of changes made to the system recently (trying to fix the problem). Only time will tell - Good Luck!

BSOD BUGCHECK SUMMARY

[FONT=lucida console]
Built by: 7600.16617.x86fre.win7_gdr.100618-1621
Debug session time: Wed Oct 13 16:23:48.960 2010 (UTC - 4:00)
System Uptime: 0 days 3:33:26.443
BUGCHECK_STR:  0x124_GenuineIntel
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
Bugcheck code 00000124
Arguments 00000000 864c6024 b2000040 00000800
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.x86fre.win7_gdr.100618-1621
Debug session time: Wed Oct 13 12:49:37.180 2010 (UTC - 4:00)
System Uptime: 0 days 5:39:01.538
BUGCHECK_STR:  0x124_GenuineIntel
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
Bugcheck code 00000124
Arguments 00000000 864f0024 b2000018 02000e0f
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.x86fre.win7_gdr.100618-1621
Debug session time: Wed Oct 13 07:05:21.446 2010 (UTC - 4:00)
System Uptime: 0 days 0:12:01.929
*** WARNING: Unable to verify timestamp for copperhd.sys
*** ERROR: Module load completed but symbols could not be loaded for copperhd.sys
BUGCHECK_STR:  0xc9_224
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME:  System
Bugcheck code 000000C9
Arguments 00000224 913fdc72 a7974e00 00000002
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.x86fre.win7_gdr.100618-1621
Debug session time: Wed Oct 13 06:52:38.227 2010 (UTC - 4:00)
System Uptime: 0 days 1:56:47.710
*** WARNING: Unable to verify timestamp for copperhd.sys
*** ERROR: Module load completed but symbols could not be loaded for copperhd.sys
BUGCHECK_STR:  0xc9_224
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME:  System
Bugcheck code 000000C9
Arguments 00000224 90827c72 b4514e00 00000002
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.x86fre.win7_gdr.100618-1621
Debug session time: Tue Oct 12 08:00:09.198 2010 (UTC - 4:00)
System Uptime: 0 days 0:45:05.681
BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_2_PROC
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
Bugcheck code 00000101
Arguments 00000061 00000000 80dc4120 00000001
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.x86fre.win7_gdr.100618-1621
Debug session time: Tue Oct 12 07:14:14.253 2010 (UTC - 4:00)
System Uptime: 0 days 0:33:40.736
BUGCHECK_STR:  0x124_GenuineIntel
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  mscorsvw.exe
Bugcheck code 00000124
Arguments 00000000 86964024 b2000040 00000800
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.x86fre.win7_gdr.100618-1621
Debug session time: Tue Oct 12 04:28:15.925 2010 (UTC - 4:00)
System Uptime: 0 days 0:16:05.408
BUGCHECK_STR:  0x124_GenuineIntel
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
Bugcheck code 00000124
Arguments 00000000 86509024 b2000040 00000800
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.x86fre.win7_gdr.100618-1621
Debug session time: Mon Oct 11 21:49:43.063 2010 (UTC - 4:00)
System Uptime: 0 days 0:01:58.438
*** WARNING: Unable to verify timestamp for mfehidk.sys
*** ERROR: Module load completed but symbols could not be loaded for mfehidk.sys
Probably caused by : mfehidk.sys ( mfehidk+3a2aa )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  mcshield.exe
Bugcheck code 0000000A
Arguments 00000000 00000002 00000001 828ba5c9
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.x86fre.win7_gdr.100618-1621
Debug session time: Mon Oct 11 21:47:03.993 2010 (UTC - 4:00)
System Uptime: 0 days 0:16:12.368
BUGCHECK_STR:  0x124_GenuineIntel
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
Bugcheck code 00000124
Arguments 00000000 864eb024 b2000040 00000800
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.x86fre.win7_gdr.100618-1621
Debug session time: Mon Oct 11 20:11:10.320 2010 (UTC - 4:00)
System Uptime: 0 days 0:41:12.679
BUGCHECK_STR:  0x124_GenuineIntel
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
Bugcheck code 00000124
Arguments 00000000 86519024 b2000018 02000e0f
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.x86fre.win7_gdr.100618-1621
Debug session time: Mon Oct 11 18:56:47.703 2010 (UTC - 4:00)
System Uptime: 0 days 0:06:48.062
BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_2_PROC
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
Bugcheck code 00000101
Arguments 00000060 00000000 80dc3120 00000001
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.x86fre.win7_gdr.100618-1621
Debug session time: Mon Oct 11 18:48:52.388 2010 (UTC - 4:00)
System Uptime: 0 days 0:23:02.748
BUGCHECK_STR:  0x124_GenuineIntel
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
Bugcheck code 00000124
Arguments 00000000 860ad024 b2000018 02000e0f
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  
  [/FONT]

 

[Scritty]

Great stuff..|Thanks for the reply.

After running prime95 (and it crashing in seconds) I decided to install a CPU temperature program.

The PC had been off for a while, so I turned it on = installed and started the app.

At first I couldn't understand it. It looked likek a thermometer temperature guage with no reading on it at all.

Then I realized (after looking at the instructions) was that there was a reading - it was just a solid block to the top of the guage (130 degrees plus)

Now I did reinstall my CPU when I updated the OS two days ago - but the thermal paste I used had been in the tube for several years (does this stuff "go off")

After writing the first post Ithe frequency of BSOD's increased to one every 5-10 minutes.

I don't know whether temperature was the original cause, but i think it certainly is playing up now. Off to PC world to get some new thermal paste and reinstall the CPU (maybe with a better fan/heatsink as well - it gets v hot in my office)

I will keep you posted.

I did update my Razer drivers straight after..

Thanks again.

Paul

 

[Scritty]

Turned out the temp test program was poor. Using RealTemp now - Temps were a little high (39 idle 65+ under load)

Bought more thermal paste, cleaned and reseated CPU and fan/heatsink.

Ran Realtemp -and Prime 95. BSOD about 80% of the way through.
Temperature was barely 63% on either core. So not sure whether the stress test caused the BSOD or not - beginning to think CPU is fried.

Uninstalled Razer altogether and put Microsoft intellimouse on (optical) see how that fares.

Checked all hardware on MS compatability site (all ok -though it was specific about Razer being "blue" and mines green - yeah I know.... it's just the colour of the bulb - I feel a Red Dwarf sketch coming on)

Still hopeful of finding a fix, but I am running out of ideas.
Could the CPU be the culprit? Is there any way of testing specifically?
Is the repeated failure under Prime 95 proof that is definitely is the CPU? or could it still be the motherboard or another peripheral?

What about stupid stuff like kinked HDD cables?

Changed the CMOS battery only about 4 months ago and that seems ok.
If I could narrow it down to one component or driver, then I would just replace it, but at the mo' it looks like it could be one of several.

Other than GFX, whole machine is well over 3 years old and gets used every single day - often for many hours. I realise that that isn't that long compared with some stuff, but I won't be massively gutted if the worse comes to the worse, though I would like to get another 18 months plus out of it (5 years would be nice) But I don't think this system owes me much. If it really is cooked, then I will buy a new barebones system and transfer the GFX and HDD's over. When I get a spare £70 I might buy a cheap gfx hdd and chip to use on the rest of the kit to run some SEO jobs I do.

Thanks chaps - your help is very much appreciated.

Paul

 

[usasma]

Patience friend - it may take a while to identify the problem.
Changing stuff around may also affect the length of time it takes to figure this out.

We found that the Copperhead drivers were most likely at fault. But that may not be the only problem - and it may not be the driver that's at fault. Try another mouse to ensure that there's not a hardware problem with the Copperhead device.

zip up and upload the new memory dump files so we can have a look at them. This serves several purposes - it'll give us info on the memory dumps and it will tell us if the drivers have actually been removed/updated (sometimes the installer program doesn't fix that).

The compatibility site is maintained by Microsoft, but it's just a listing of information that's been submitted to them. Microsoft doesn't test the claims of compatibility by the manufacturers.

STOP 0x124 errors are errors that are caught by the CPU and then are passed on to Windows. As such they don't have all the information that other BSOD's have. They are typically hardware problems, although we do see a higher incidence of compatibility issues causing them with Win7. They can also be caused by corruptions in Windows, or by corruptions in 3rd party drivers (although some analysts disagree on this last point).

So, the order of problem probability is:
1. Hardware
2. Compatibility (higher in Win7)
3. Windows corruption
4. 3rd party driver corruption.

Troubleshooting hardware is difficult and expensive. Most hardware troubleshooting involves either removing the device or substituting another, known good device. But some simple steps involve checking all the cabling and testing the output of things like your CMOS battery - even tho' it's only 4 months old it can still be losing it's charge.

Suggestions for a CPU stress test: CPU Stress test - Overclock.net - Overclocking.net

Here's an older post of mine about hardware troubleshooting by system stripdown: Hardware Troubleshooting Via System Stripdown

 

[Scritty]

Thanks Again...

Ok,

Thanks a lot for this help. It is appreciated.

Well, I've now got MS mouse installed and have uninstalled the Razor drivers.
As metioned above, I have done the prime95 stress test on my CPU - it failed within seconds (BSOD)

Today I checked the BIOS temperature and noticed it climbing steadily (started at 34 degrees and was 49 within 10 minutes- just in the BIOS)

I've cleaned up and re-installed the CPU but had one more BSOD since. Running Prime95 again. However I think at the time I had set a failsafe in the BIOS of 70 degrees. Prime95 ran for over 80% of it's basic cycle and the temperatures reported were close to 70 (there is a difference between the BIOS temp reporting and REALTEMPS's temp reporting - so I can't be 100% sure the BIOS may have been reporting more and triggered the shutdown - it's the last BSOD in the list)

Have had an afternoon playing LOTRO, writing emails and a little bit of surfing. touch wood - nothing yet. However I'm sure I haven't solved the issue- maybe lessened it a bit.

Thanks again.

New reports attached.

Paul

 

[usasma]

You cleaned up and reinstalled the CPU - and still were gettingclose to 70º C temps?
That's got to be fixed before moving on to any other troubleshooting.
Since you were using Prime95 - what does the system get to without running Prime95?

 

[Scritty]

The temperature pn;y got to the high 60's under Prime95. Since then it has not got higher than about 52 when playing LOTRO (though that isn't massively intensive)

I changed the thermal paste for ceramic in case it was a metal conductivity (shorting) issue.

It is currently 33-35 running more or less idle (just doing this reply with a couple of low overhead tasks running in the background)

Thanks again

Paul

 

[usasma]

Give it 24 to 36 hours. If still no BSOD, then we'll run Driver Verifier just to be sure that there's not an issue hiding on us.

Here's the instructions that I use for Driver Verifier:

Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

So, I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
NOTE: You can use Low Resource Simulation if you'd like. From my limited experimentation it makes the BSOD's come faster.
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.

If that doesn't work, post back and we'll have to see about fixing the registry entry off-line:

Delete these registry keys (works in XP, Vista, Win7):
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDrivers
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDriverLevel

More info on this at this link: Using Driver Verifier to identify issues with Windows drivers for advanced users

 

[Scritty]

Still bugging out

Hi Usasma,

Still bugging out. I had nearly a full days use yesterday before it went - for the first time ever it was actually while in an application.

(new reports attached)

The "whocrashed" reports don't help much, very generic.

I'm tempted to install Windows XP Pro on this system - I am on the verge of ordering a new system and will need my Win 7 license for that anyway. (both are full OS's not upgrades, so should be ok)

Seems no rhyme or reason to it, no real "pattern" of failure that I can see. So I am pretty much sure it's a hardware failure (mobo or CPU seem most likely to me).

Seems ok when doing very little - but that's not a lot of good

Any last thoughts?

Again thanks for your ongoing help.

Paul

 

[usasma]

Copperhead driver is now dated Nov 2009

This driver concerns me:
WinRing0.sys Sat Jul 26 09:25:10 2008 (488B25B6)

I'd run Driver Verifier using the instructions above. If the crash doesn't point to a 3rd party driver, then it's either hardware or Windows. A clean install of Windows (with updates and no 3rd party programs installed) would rule out a problem with Windows.

BSOD BUGCHECK SUMMARY

[font=lucida console]
Built by: 7600.16617.x86fre.win7_gdr.100618-1621
Debug session time: Sat Oct 16 06:41:10.287 2010 (UTC - 4:00)
System Uptime: 0 days 1:28:00.646
BUGCHECK_STR:  0x124_GenuineIntel
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
Bugcheck code 00000124
Arguments 00000000 864e4024 b2000000 00000115
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.x86fre.win7_gdr.100618-1621
Debug session time: Fri Oct 15 16:12:53.658 2010 (UTC - 4:00)
System Uptime: 0 days 12:59:31.017
BUGCHECK_STR:  0x124_GenuineIntel
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  lotroclient.ex
Bugcheck code 00000124
Arguments 00000000 864f1024 b2000000 00000115
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.x86fre.win7_gdr.100618-1621
Debug session time: Thu Oct 14 07:34:30.351 2010 (UTC - 4:00)
System Uptime: 0 days 0:10:23.726
BUGCHECK_STR:  0x124_GenuineIntel
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  prime95.exe
Bugcheck code 00000124
Arguments 00000000 86508024 b2000018 02000e0f
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.x86fre.win7_gdr.100618-1621
Debug session time: Wed Oct 13 19:01:20.343 2010 (UTC - 4:00)
System Uptime: 0 days 0:10:53.826
BUGCHECK_STR:  0x124_GenuineIntel
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
Bugcheck code 00000124
Arguments 00000000 865a5024 b2000018 02000e0f
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  
  [/font]

 

[Scritty]

[EDIT]

Had another "interrupt not received by second core" type error - Starting to think it definitley is the processor, perhaps linked to tasks shared - or swapped - between cores.
So I have gone into msconfig and disabled the second core for now

Do you think this is a decent test, or am I "widdling in the breeze"

[Original Message]

Brilliant spot usasma! Many thanks.

I thought the copperhead drivers were gone - but seems they live on.

I woiuld like to use this machine even when I upgrade, so getting it working - consistently (if not that hard) would be a great boon.

I will run the driver test utility and see where it gets me.
If (in the end) I need to by a cheap CPU to replace the one in it to keep the main system running for a few more years - then that's what I'll do. THere are some ones on the net that cost under 30 - so to keep a second system going that seems a worthwhile investment.

But first I will follow your advice. (getting rid of any trace of that copperhead driverthat I thought I uninstalled - I now have a MS optical - which I've always liked anyway...fashion eh)

Thanks for bearing with me on this.

I'll update when I have done more.

Paul

 

[usasma]

Go to C:\Windows\System32\drivers
Locate copperhead.sys and rename it to copperhead.BAK

Also, use Autoruns to stop it from loading (in the Drivers tab).
Just remove the check mark - don't delete the entry.

Run Prime95 with all cores to see if the problem core keeps erroring out on you.

Prime95 download site: Free Software - GIMPS
Prime95 Setup:
- extract the contents of the zip file to a location of your choice
- double click on the executable file
- select "Just stress testing"
- select the "Blend" test. If you've already run MemTest overnight you may want to run the "Small FFTs" test instead. (run all 3 if you find a problem and note how long it takes to error out with each)
- "Number of torture test threads to run" should equal the number of CPU's times 2 (if you're using hyperthreading).
The easiest way to figure this out is to go to Task Manager...Performance tab - and see the number of boxes under CPU Usage History
Then run the test for 6 to 24 hours - or until you get errors (whichever comes first).
This won't necessarily crash the system - but check the output in the test window for errors.
The Test selection box and the stress.txt file describes what components that the program stresses.

FWIW - I use an old Logitech Trackball instead of a mouse. I've been using it for years and won't switch to anything else!