BSOD, screen freeze and auto-restarts

[Norsey]

I have a Windows home premium 64 bit OS, it's OEM and the original OS on the pc. I got the PC last november, and have not reinstalled the OS.

I've experienced BSOD error messages, screen freezes, auto restarts and yesterday it wouldn't initiate anything but the fans (it does now for some reason). I've done a complete system/ virus check (norton 360). I've done a memory check, and a disk check, neither gave any proper results, though the disk check freezed completely twice (had to reboot). I've attached the info dump thingy as requested here, but I have no idea how to do a system health check (pc language is norwegian, so searching for it/ attempted translations didn't work out too well..)

any help on either the errors or the system health check would be great

Forgot to add: I tried using windows update, but then the system wouldn't start and made me reset the comp to before the update

 

[Norsey]

managed to do the system health report now, any help is appreciated

 

[usasma]

Anti-Virus Removal:
Please do the following:
- download a free antivirus for testing purposes: Free AntiVirus
- uninstall the Norton from your system (you can reinstall it, if so desired, when we're done troubleshooting)
- remove any remnants of Norton using this free tool: KB Article Not Found
- IMMEDIATELY install and update the free antivirus
- check to see if this fixes the BSOD's

Please disable your NEC USB 3.0 Controller in Device Manager.
Then rename the following files from .sys to .BAK (they're in C:\Windows\System32\drivers)
- nusb3hub.sys
- nusb3xhc.sys
Then reboot (after we're done troubleshooting you can rename them back to .sys and regain the functionality)

OLDER DRIVERS PRESENT IN THE DUMP FILES
- Please update these drivers from the device manufacturer's website - or uninstall/remove them from your system. Reference links included below.
- DO NOT use Windows Update or the Update Drivers function of Device Manager.
- Windows Update exceptions may be noted below for Windows drivers:

[font=lucida console]
amdxata.sys       Tue May 19 13:56:59 2009 (4A12F2EB)
SYMDS64.SYS       Fri Oct 15 13:53:54 2010 (4CB89532)
SYMEFA64.SYS      Mon Nov 15 16:56:23 2010 (4CE1AC87)
SYMNETS.SYS       Tue Nov 30 18:24:40 2010 (4CF587B8)
IDSvia64.sys      Fri Nov 05 17:13:11 2010 (4CD47367)
SYMEVENT64x86.SYS Fri Jul 30 19:05:59 2010 (4C535AD7)
Ironx64.SYS       Fri Nov 12 18:06:50 2010 (4CDDC88A)
SRTSPX64.SYS      Fri Nov 19 19:18:10 2010 (4CE713C2)
SCDEmu.SYS        Mon Apr 12 04:52:25 2010 (4BC2DF49)
eeCtrl64.sys      Fri May 21 17:44:45 2010 (4BF6FECD)
BHDrvx64.sys      Mon Nov 15 18:11:35 2010 (4CE1BE27)
AsUpIO.sys        Sun Jul 05 22:21:38 2009 (4A515FB2)
AsIO.sys          Mon Aug 03 03:03:16 2009 (4A768BB4)
nusb3hub.sys      Thu Apr 22 21:34:35 2010 (4BD0F92B)
nusb3xhc.sys      Thu Apr 22 21:34:36 2010 (4BD0F92C)
GEARAspiWDM.sys   Mon May 18 08:17:04 2009 (4A1151C0)
ASACPI.sys        Wed Jul 15 23:31:29 2009 (4A5E9F11)
Rtlh64.sys        Wed Aug 25 03:39:39 2010 (4C74C8BB)
nvlddmkm.sys      Sat Oct 16 13:12:46 2010 (4CB9DD0E)
nvBridge.kmd      Sat Oct 16 13:06:16 2010 (4CB9DB88)
nvhda64v.sys      Tue Sep 07 16:08:40 2010 (4C869BC8)
RTKVHD64.sys      Tue Nov 02 07:25:59 2010 (4CCFF547)
SRTSP64.SYS       Fri Nov 19 19:17:58 2010 (4CE713B6)
ENG64.SYS         Mon Dec 13 20:47:30 2010 (4D06CCB2)
EX64.SYS          Mon Dec 13 20:55:48 2010 (4D06CEA4)
[/font]

http://www.carrona.org/dvrref.html#amdxata.sys
http://www.carrona.org/dvrref.html#SYMDS64.SYS
http://www.carrona.org/dvrref.html#SYMEFA64.SYS
http://www.carrona.org/dvrref.html#SYMNETS.SYS
http://www.carrona.org/dvrref.html#IDSvia64.sys
http://www.carrona.org/dvrref.html#SYMEVENT64x86.SYS
http://www.carrona.org/dvrref.html#Ironx64.SYS
http://www.carrona.org/dvrref.html#SRTSPX64.SYS
http://www.carrona.org/dvrref.html#SCDEmu.SYS
http://www.carrona.org/dvrref.html#eeCtrl64.sys
http://www.carrona.org/dvrref.html#BHDrvx64.sys
http://www.carrona.org/dvrref.html#AsUpIO.sys
http://www.carrona.org/dvrref.html#AsIO.sys
http://www.carrona.org/dvrref.html#nusb3hub.sys
http://www.carrona.org/dvrref.html#nusb3xhc.sys
http://www.carrona.org/dvrref.html#GEARAspiWDM.sys
http://www.carrona.org/dvrref.html#ASACPI.sys
http://www.carrona.org/dvrref.html#Rtlh64.sys
http://www.carrona.org/dvrref.html#nvlddmkm.sys
http://www.carrona.org/dvrref.html#nvBridge.kmd
http://www.carrona.org/dvrref.html#nvhda64v.sys
http://www.carrona.org/dvrref.html#RTKVHD64.sys
http://www.carrona.org/dvrref.html#SRTSP64.SYS
http://www.carrona.org/dvrref.html#ENG64.SYS
http://www.carrona.org/dvrref.html#EX64.SYS

BSOD BUGCHECK SUMMARY

[font=lucida console]
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Sun Feb 27 16:51:29.732 2011 (UTC - 5:00)
System Uptime: 0 days 0:00:13.183
*** WARNING: Unable to verify timestamp for Unknown_Module_00000000`00000000
*** WARNING: Unable to verify timestamp for fvevol.sys
*** ERROR: Module load completed but symbols could not be loaded for fvevol.sys
Probably caused by : ataport.SYS ( ataport!IdeLunQueueInsert+36 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  smss.exe
FAILURE_BUCKET_ID:  X64_0xA_ataport!IdeLunQueueInsert+36
Bugcheck code 0000000A
Arguments 00000000`000010af 00000000`00000002 00000000`00000001 fffff800`032c10a2
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Sat Feb 26 20:05:17.418 2011 (UTC - 5:00)
System Uptime: 0 days 2:04:42.540
Probably caused by : win32k.sys ( win32k!NtGdiDdDDIEscape+b )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x50
PROCESS_NAME:  League of Lege
FAILURE_BUCKET_ID:  X64_0x50_win32k!NtGdiDdDDIEscape+b
Bugcheck code 00000050
Arguments fffff880`096e7160 00000000`00000001 fffff960`0026cdc3 00000000`00000002
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Sat Feb 26 15:18:22.859 2011 (UTC - 5:00)
System Uptime: 0 days 0:04:59.279
Probably caused by : ntkrnlmp.exe ( nt!KeWaitForSingleObject+a )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x50
PROCESS_NAME:  lol.launcher.e
FAILURE_BUCKET_ID:  X64_0x50_nt!KeWaitForSingleObject+a
Bugcheck code 00000050
Arguments fffff500`07456490 00000000`00000001 fffff800`032d9b6a 00000000`00000007
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  
  [/font]

 

[Norsey]

Getting rid of Norton seems to have done the trick, I'll report back if the troubles don't stay away

 

[Norsey]

got some 00007f errors now, haven't been as bad as before, but as this is what it started with before I thought I'd try to strike it early this time, uploaded system health report and the minidump stuff

 

[usasma]

I'm late for work, so try this and I'll respond back when I get home:

Uninstall the Asus stuff, then check in C:\Windows\System32\drivers for these drivers:
AsUpIO.sys
AsIO.sys

If present, rename from .sys to .BAK

Disable the USB 3.0 controller in Device Manager
Then rename these drivers from .sys to .BAK
nusb3xhc.sys
nusb3hub.sys

Visit the nVidia website ( Drivers - Download NVIDIA Drivers ) and download the latest version of the nForce chipset drivers and the geForce video drivers for your system and video card.

Run this free diagnostic for your hard drive: HD Diagnostic (read the details at the link)

Then run Driver Verifier according to these directions:

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

I haven't reviewed the following stuff, so don't do anything with it:

OLDER DRIVERS PRESENT IN THE DUMP FILES
- Please update these drivers from the device manufacturer's website - or uninstall/remove them from your system. Reference links included below.
- DO NOT use Windows Update or the Update Drivers function of Device Manager.
- Windows Update exceptions may be noted below for Windows drivers:

[FONT=lucida console]
amdxata.sys     Tue May 19 13:56:59 2009 (4A12F2EB)
aswNdis.sys     Sat Jan 09 16:22:03 2010 (4B48F37B)
aswNdis2.sys    Wed Feb 23 09:56:46 2011 (4D65202E)
SCDEmu.SYS      Mon Apr 12 04:52:25 2010 (4BC2DF49)
Rtlh64.sys      Wed Aug 25 03:39:39 2010 (4C74C8BB)
AsUpIO.sys      Sun Jul 05 22:21:38 2009 (4A515FB2)
AsIO.sys        Mon Aug 03 03:03:16 2009 (4A768BB4)
nusb3xhc.sys    Thu Apr 22 21:34:36 2010 (4BD0F92C)
GEARAspiWDM.sys Mon May 18 08:17:04 2009 (4A1151C0)
ASACPI.sys      Wed Jul 15 23:31:29 2009 (4A5E9F11)
nvhda64v.sys    Tue Sep 07 16:08:40 2010 (4C869BC8)
nusb3hub.sys    Thu Apr 22 21:34:35 2010 (4BD0F92B)
nvlddmkm.sys    Sat Oct 16 13:12:46 2010 (4CB9DD0E)
nvBridge.kmd    Sat Oct 16 13:06:16 2010 (4CB9DB88)
RTKVHD64.sys    Tue Nov 02 07:25:59 2010 (4CCFF547)
[/FONT]

http://www.carrona.org/dvrref.html#amdxata.sys
http://www.carrona.org/dvrref.html#aswNdis.sys
http://www.carrona.org/dvrref.html#aswNdis2.sys
http://www.carrona.org/dvrref.html#SCDEmu.SYS
http://www.carrona.org/dvrref.html#Rtlh64.sys
http://www.carrona.org/dvrref.html#AsUpIO.sys
http://www.carrona.org/dvrref.html#AsIO.sys
http://www.carrona.org/dvrref.html#nusb3xhc.sys
http://www.carrona.org/dvrref.html#GEARAspiWDM.sys
http://www.carrona.org/dvrref.html#ASACPI.sys
http://www.carrona.org/dvrref.html#nvhda64v.sys
http://www.carrona.org/dvrref.html#nusb3hub.sys
http://www.carrona.org/dvrref.html#nvlddmkm.sys
http://www.carrona.org/dvrref.html#nvBridge.kmd
http://www.carrona.org/dvrref.html#RTKVHD64.sys

BSOD BUGCHECK SUMMARY

[FONT=lucida console]
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Tue Mar  1 18:04:26.679 2011 (UTC - 5:00)
System Uptime: 0 days 2:19:38.115
Probably caused by : ntkrnlmp.exe ( nt!KiDoubleFaultAbort+b2 )
BUGCHECK_STR:  0x7f_8
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  League of Lege
FAILURE_BUCKET_ID:  X64_0x7f_8_nt!KiDoubleFaultAbort+b2
Bugcheck code 0000007F
Arguments 00000000`00000008 00000000`80050031 00000000`000006f8 00000000`00200246
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Tue Mar  1 14:42:56.937 2011 (UTC - 5:00)
System Uptime: 0 days 0:05:40.763
Probably caused by : ntkrnlmp.exe ( nt!KiDoubleFaultAbort+b2 )
BUGCHECK_STR:  0x7f_8
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  opera.exe
FAILURE_BUCKET_ID:  X64_0x7f_8_nt!KiDoubleFaultAbort+b2
Bugcheck code 0000007F
Arguments 00000000`00000008 00000000`80050031 00000000`000006f8 fffff800`032c9ccf
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Mon Feb 28 14:09:25.022 2011 (UTC - 5:00)
System Uptime: 0 days 3:43:51.442
Probably caused by : Ntfs.sys ( Ntfs!NtfsPreRequestProcessingExtend+7a )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
BUGCHECK_STR:  0x24
FAILURE_BUCKET_ID:  X64_0x24_Ntfs!NtfsPreRequestProcessingExtend+7a
Bugcheck code 00000024
Arguments 00000000`001904fb fffff880`02f938b8 fffff880`02f93120 fffff880`010353da
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  
  [/FONT]

 

[Norsey]

uninstalled the ASUS stuff (the .sys files weren't there after uninstall), got the driver, disabled the USB 3.0 stuff and checked the harddisk (with the manufacturers search engine since the page you linked to recommended that) smart search was clean, doing a complete one while I'm out later. haven't had any problems again while doing so

edit: got an 0A (IRQ_NOT_LESS_OR_EQUAL) error now, I'll do the driver verifier thing now and let it stand overnight to see what happens

 

[Norsey]

performed the driver verifier now, the extended harddisk search didn't find anything wrong.

 

[usasma]

Crud!!! The Asus driver are hiding in C:\Windows\SysWow64\drivers\
And they're still loaded in the last memory dump.

Of the last 4 memory dumps, the last 2 are Verifier Enabled memory dumps.
One blames your video drivers, one blames the core of the OS
The non-Verifier Enabled memory dumps blame a Windows networking component and the core of the OS

So, I'd have to suspect that this is a hardware problem - although the low level that the Asus drivers function at could also be responsible.

Please also uninstall PowerISO because the drivers show up as older and we want to remove all possibilities. Feel free to reinstall it after we're done troubleshooting.

Once all of that is done, if the BSOD's continue - then it's time to start more hardware troubleshooting. I'd suggest trying a new video card if you can borrow one - DO NOT BUY ONE!!! This is only a guess on my part.

And then, you can start with these free hardware tests:

I suggest starting all troubleshooting with the following diagnostic tests. They'll save you a lot of time and heartache if there is a hardware failure, and you'll have the disks on hand in case you need them in the future:

H/W Diagnostics:
Please start by running these bootable hardware diagnostics:
Memory Diagnostics (read the details at the link)
HD Diagnostic (read the details at the link)

Also, please run one of these free, independent online malware scans to ensure that your current protection hasn't been compromised: Free Online AntiMalware Scanners (read the details at the link)

Then, if the above tests pass, I'd try these free stress tests:

FurMark download site: FurMark: VGA Stress Test, Graphics Card and GPU Stability Test, Burn-in Test, OpenGL Benchmark and GPU Temperature | oZone3D.Net
FurMark Setup:
- If you have more than one GPU, select Multi-GPU during setup
- In the Run mode box, select "Stability Test" and "Log GPU Temperature"
Click "Go" to start the test
- Run the test until the GPU temperature maxes out - or until you start having problems (whichever comes first).
NOTE: Set the alarm to go off at 90ºC. Then watch the system from that point on.
- Click "Quit" to exit

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 please 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.
More details on the use of this test: Torture test your CPU with Prime95

Two other video stress tests (may be more stressful than FurMark):
Video Memory stress Test - МИРNVIDIA / Утилиты / VMT
Artifact Locator - МИРNVIDIA / Утилиты / Artifact Locator
Sorry, but I don't read the language that this website is made in.

Another interesting test that just came to my attention: Download - OCCT Website english
USE AT YOUR OWN RISK - program doesn't have a whole bunch of safety features to protect you from yourself!

Then here's a set of tests from my DRAFT writeup on Prime95:

DRAFT Prime95 testing procedure
This is in case you are getting errors in Prime95 and want to nail down the cause

Run HDD diag and MemTest prior to Prime95

Run Blend test
Run Inplace Large FFT's test
Run Small FFT's test

Run CPU Stress Tests
- http://downloadcenter.intel.com/Detail_Desc.aspx?agr=Y&DwnldID=19182&lang=eng
- 7Byte : Hot CPU Tester Pro
- 7Byte : BurnIn64
- CPU Stress test - Overclock.net - Overclocking.net
- Fossil Free Online CPU Load or Stress Test.
- CPU Stability Test description, System Resources Tune-Up. Downloads List By All Time Popularity | PCWorld - PCWorld
- CPU Stress test - Overclock.net - Overclocking.net
- |MG| CPU Stability Test 6.0 Download
- LinX - A simple Linpack interface - XtremeSystems Forums

Run Video Stress Tests
- FurMark: VGA Stress Test, Graphics Card and GPU Stability Test, Burn-in Test, OpenGL Benchmark and GPU Temperature | oZone3D.Net
- МИРNVIDIA / Утилиты / VMT
- МИРNVIDIA / Утилиты / Artifact Locator

Swap RAM sticks around per Steps 7 through 10 of this link and run Prime95 (in Blend mode) on each stick/slot: Memory Diagnostics
This is because of issues found in this topic: http://www.sevenforums.com/crashes-debugging/124155-blue-screens-again-2.html#post1076674
************************
DISCUSSION:
Small FFT's test CPU cache and very little memory.
Large FFT's access' a lot of memory - but in-place option keeps it limited
Blend is not run in-place, so it cycles the tests through a lot of RAM

All tests stress the CPU
In-place large FFT's and Blend also test CPU/RAM interface (mobo in all but Athlon64 and Intel i-series)
- This would then be testing the memory controller onboard the CPU in the Athlon64 and i-series processors
In-place large FFT's stress CPU more than Blend
MemTest is better at testing RAM

Prime 95 tests 3 things:
- Memory
- CPU/RAM interface (mobo in all but Athlon64 and Intel i-series)
- CPU

FWIW - the distinction between RAM and different types of memory in the system is one that I've made. The documentation that I've read speaks of RAM issues and CPU cache - and doesn't mention the other aspects. BUT, this is just speculation on my part, so we'll have to see how it works for us.
Link to explanation about i-series CPU/RAM interface: Intel Core - Wikipedia, the free encyclopedia

Common features of all Nehalem based processors include an integrated DDR3 memory controller as well as QuickPath Interconnect or PCI Express and Direct Media Interface on the processor replacing the aging quad-pumped Front Side Bus used in all earlier Core processors.

 

[Norsey]

sorry for the long wait, but been sorta busy with school lately :/ got the hardware checked out now, the CPU turned out to be defective, so replaced it now and hopefully there will be no more problems