BSOD's when transferring data ( I think)

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:

Code:

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

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

Code:

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
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  
  

[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

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!