win 7 bsod stop 1000007e

[korson]

First of all i am sorry for may bad english.

here is some description of my problem

Bsod occured when i running games or video.
my system configuration is:
CPU Core 2 duo e8400 3ghz
asus GeForce 8800GT
2gb ram
motherboard MSI ms7519

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.256.4
Locale ID: 1049

Additional information about the problem:
BCCode: 1000007e
BCP1: FFFFFFFFC0000005
BCP2: FFFFF80002CD2EA6
BCP3: FFFFF88002FD5988
BCP4: FFFFF88002FD51E0
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1

And i atached some dump files. Hope you can say wich part of my system cause the problem.

Thnak you.

 

[usasma]

9 memory dumps, 5 different errors, 7 different causes
Sounds like a hardware issue to me, please do the following:

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: Malware (read the details at the link)

Post back with the results and we'll move on from there:

Summary of the BSOD's:

[font=lucida console]  
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sat Mar 20 06:56:13.138 2010 (GMT-4)
System Uptime: 0 days 1:46:48.652
BugCheck 1000007E, {ffffffffc0000005, fffff80002cd2ea6, fffff88002fd5988, fffff88002fd51e0}
Probably caused by : NETIO.SYS ( NETIO! ?? ::FNODOBFM::`string'+6d5 )
PROCESS_NAME:  System
BUGCHECK_STR:  0x7E
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Fri Mar 19 12:58:05.488 2010 (GMT-4)
System Uptime: 0 days 2:07:13.987
BugCheck A, {fffffd80002b7b88, 2, 1, fffff80002c9db74}
Probably caused by : win32k.sys ( win32k!memset+80 )
BUGCHECK_STR:  0xA
PROCESS_NAME:  firefox.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Mon Mar 15 11:07:55.372 2010 (GMT-4)
System Uptime: 0 days 2:59:19.870
BugCheck 3B, {c0000005, fffff80002f7267c, fffff880081d4d50, 0}
Probably caused by : ntkrnlmp.exe ( nt!ObDereferenceSecurityDescriptor+20 )
BUGCHECK_STR:  0x3B
PROCESS_NAME:  war3.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Fri Mar 12 17:01:12.179 2010 (GMT-4)
System Uptime: 0 days 11:36:21.678
BugCheck D1, {10000000000a, 2, 0, fffff8800169abd4}
*** WARNING: Unable to verify timestamp for vpcnfltr.sys
*** ERROR: Module load completed but symbols could not be loaded for vpcnfltr.sys
Probably caused by : vpcnfltr.sys ( vpcnfltr+30f4 )
BUGCHECK_STR:  0xD1
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Thu Mar 11 20:27:31.475 2010 (GMT-4)
System Uptime: 0 days 10:59:02.989
BugCheck A, {380006c9610, 2, 1, fffff80002cabcab}
Probably caused by : cdfs.sys ( cdfs!CdPurgeVolume+111 )
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sat Feb 27 16:11:36.364 2010 (GMT-4)
System Uptime: 0 days 11:26:10.878
BugCheck 10E, {24, fffff8a003743300, 2000000000, 0}
*** WARNING: Unable to verify timestamp for dxgkrnl.sys
*** ERROR: Module load completed but symbols could not be loaded for dxgkrnl.sys
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::DestroyOneAllocation+28c )
BUGCHECK_STR:  0x10e_24
PROCESS_NAME:  AOgame.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Mon Feb 15 18:31:10.799 2010 (GMT-4)
System Uptime: 0 days 7:12:58.313
BugCheck A, {f8001383d3a, 2, 0, fffff80002ad73d7}
Probably caused by : memory_corruption ( nt!MiPfnShareCountIsZero+77 )
BUGCHECK_STR:  0xA
PROCESS_NAME:  KMPlayer.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Thu Feb 11 21:28:42.546 2010 (GMT-4)
System Uptime: 0 days 21:09:13.044
BugCheck A, {8000df8d9a, 2, 0, fffff80002ad93d7}
Probably caused by : memory_corruption ( nt!MiPfnShareCountIsZero+77 )
BUGCHECK_STR:  0xA
PROCESS_NAME:  KMPlayer.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Wed Jan 13 17:47:28.147 2010 (GMT-4)
System Uptime: 1 days 5:32:38.661
BugCheck A, {800132e02a, 2, 0, fffff80002abc6fb}
Probably caused by : memory_corruption ( nt!MiMapPageInHyperSpaceWorker+1b )
BUGCHECK_STR:  0xA
PROCESS_NAME:  FlylinkDC.exe
[/font]

 

[korson]

Thanks for help.

I tried Hard Drive Diagnostic. My HD passed every single test in sea diagnostic program.
I tried to change all my memory modules with new modules in different slots.
And i scanned system for viruses with two different antiviruses.
I updated my drivers for video adapter and directX.

But there is still BSOD. But this time it is different. Now there is some name of system libraries, like ndis.sys and dxgmms1.sys.

I atached new dumps. May be you can say what is my problem?

 

[usasma]

There is mention of stuff from the video sub-system and stuff from the networking sub-system.
I'd suspect that there are networking issues - but they may be complicated by your Virtual PC machines.

Please turn off all Virtual PC stuff and see if that stops the BSOD's. Leave Virtual PC off until we figure out if it's involved or not.

The latest dump files show the same pattern - 6 memory dumps, 3 different errors, 5 different causes
Still points to a hardware issue.

If the BSOD's still occur after turning off Virtual PC, then try these things:

Try this free video stress test: FurMark: Graphics Card Stability and Stress 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).
- Click "Quit" to exit

Try this free stress test: http://www.mersenne.org/freesoft/

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.
- "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).
The Test selection box and the stress.txt file describes what components that the program stresses.

Then try another networking card
Then try another video card

Summary of the BSOD's:

Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Tue Mar 23 12:54:14.560 2010 (GMT-4)
System Uptime: 0 days 2:37:34.074
BugCheck D1, {10000000000a, 2, 0, fffff8800170abd4}
*** WARNING: Unable to verify timestamp for vpcnfltr.sys
*** ERROR: Module load completed but symbols could not be loaded for vpcnfltr.sys
Probably caused by : vpcnfltr.sys ( vpcnfltr+30f4 )
BUGCHECK_STR:  0xD1
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Tue Mar 23 09:35:38.787 2010 (GMT-4)
System Uptime: 0 days 0:22:35.301
BugCheck 3B, {c0000005, fffff88003f7da65, fffff8800734e890, 0}
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_APERTURE_SEGMENT::EvictResource+2d5 )
BUGCHECK_STR:  0x3B
PROCESS_NAME:  Dethkarz.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Mon Mar 22 19:14:51.415 2010 (GMT-4)
System Uptime: 0 days 2:02:57.929
BugCheck 3B, {c0000005, fffff96000086169, fffff880080da680, 0}
Probably caused by : win32k.sys ( win32k!EBRUSHOBJ::vInitBrush+1f9 )
BUGCHECK_STR:  0x3B
PROCESS_NAME:  infium.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Mon Mar 22 17:04:00.987 2010 (GMT-4)
System Uptime: 0 days 1:39:04.361
BugCheck A, {380006776ba, 2, 0, fffff80002d066fb}
Probably caused by : memory_corruption ( nt!MiMapPageInHyperSpaceWorker+1b )
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sun Mar 21 08:35:48.181 2010 (GMT-4)
System Uptime: 0 days 1:52:51.680
BugCheck A, {f80003d3aea, 2, 0, fffff80002cea3d7}
Probably caused by : memory_corruption ( nt!MiPfnShareCountIsZero+77 )
BUGCHECK_STR:  0xA
PROCESS_NAME:  sched.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sat Mar 20 21:33:23.357 2010 (GMT-4)
System Uptime: 0 days 2:52:22.708
BugCheck 3B, {c0000005, fffff80002f7d67c, fffff880037ccd50, 0}
Probably caused by : ntkrnlmp.exe ( nt!ObDereferenceSecurityDescriptor+20 )
BUGCHECK_STR:  0x3B
PROCESS_NAME:  Garena.exe

 

[korson]

How should i turn of my Virtual PC? i mean it is installed, but i not running it when i have my BSOD. Should i uninstall win XP mode and virtual PC?

And how can i disable my built-in network card? Is it enough to turn my old card off in device manager?

 

[usasma]

The Virtual PC has loaded drivers when the BSOD occurs. Please check your startups to be sure that components from the Virtual PC aren't being loaded. If it's not a big deal for you - please uninstall the Virtual PC. You can reinstall it after we finish troubleshooting.

Disable the built-in network card in the system BIOS. If the BIOS doesn't have a selection for it, then use Device Manager to "disable" it. The difference here is that disabling it in the BIOS will prevent anything from loading - disabling it in Device Manager won't prevent it from loading, but will disable it after it's been loaded.

 

[korson]

i changed my video card. It didn’t help. i worked normally for 2 days and start to think, that it is video card problem, but today, when i run warcraft3 new bsod occured.
I changed my network card and turned off my built-in network adapter in bios. It didn’t help.
I uninstalled my Virtual PC and Win XP mode. It didn’t help. Again =(

When i run Fumark, i can’t see temperature log. Dunno why.
Tonight i will try Prime95 and post results.

Can't it be problem with my sound card? There is some terrible noise when bsod occurred.

i attached new dumps. Just in case... I am totally in despair.

 

[usasma]

One of the 3 dumps points to tcpip.sys - a component of Windows networking.
Since you've switched/removed anything normally associated with this issue, then I'd have to suspect another program/process is misbehaving (and it's one that's "internet aware"). Most often this is something like an Internet security application - what are you using for security?

I'd also suggest running 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/Windows 7 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"
- 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.

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

Summary of the BSOD's:

Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Wed Mar 24 05:20:50.011 2010 (GMT-4)
System Uptime: 0 days 1:14:49.525
BugCheck 3B, {c0000005, fffff96000096169, fffff88007111750, 0}
Probably caused by : win32k.sys ( win32k!EBRUSHOBJ::vInitBrush+1f9 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  sidebar.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sat Mar 27 06:45:47.984 2010 (GMT-4)
System Uptime: 0 days 21:52:50.498
BugCheck A, {3000000000, 2, 1, fffff80002cc4c22}
Probably caused by : tcpip.sys ( tcpip!IppMfeSetTimeOut+3c )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  war3.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sat Mar 27 08:14:05.405 2010 (GMT-4)
System Uptime: 0 days 1:15:32.919
BugCheck 3B, {c0000005, fffff80002fc067c, fffff88008633080, 0}
Probably caused by : ntkrnlmp.exe ( nt!ObDereferenceSecurityDescriptor+20 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  foobar2000.exe

 

[korson]

i'm using Avira AntiVir Personal. That's all.

My programs randomly crash from time to time. Program like FlyLink DC++, FireFox, WarCraft 3. WC3 crushes with error message like "memory can't be written'. And i have problems with system startup and shut down. When windows boot, computer may restart without any reason. Or when i try to restart my system, it freezing on shut down screen.

Using Driver Verifier now. System didn't crush yet. will wait 36 hours =)
I do not see any changes... Not any new proceses or services loaded. I working not with adinistrator accaunt. Should i use Driver Verifier with right click on it and choose "run as administrator"?

 

[korson]

while i was afk, there was a bsod. hope this is because Driver Verifier.

here i atach dump.

 

[korson]

Now i have bsod not only when i runing video and games, but when i just see web pages. Or when windows starting.

 

[usasma]

Bingo!!! This was a Verifier Enabled Minidump and it points to your network drivers as the cause. This is most likely the problem - but there are other things that could be messing with it (any program that's "internet-aware").

So, please go to Start and type "cmd" (without the quotes)
Hold down Ctrl and Shift while pressing Enter (this'll start the Command Prompt in Administrator mode).
They type "systeminfo" (without the quotes) and press Enter
Down at the bottom of the screen will be the specifics of your network controllers. Please let us know what it says (probably something with "Realtek" in it).

That'll tell us what driver you'll need.

Here's the summary of the BSOD:

Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Mon Mar 29 03:52:32.042 2010 (GMT-4)
System Uptime: 0 days 11:28:31.572
BugCheck A, {80014a07fa, 2, 0, fffff80002cfa6fb}
*** WARNING: Unable to verify timestamp for Rt64win7.sys
*** ERROR: Module load completed but symbols could not be loaded for Rt64win7.sys
Probably caused by : Rt64win7.sys ( Rt64win7+12c67 )
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
BUGCHECK_STR:  0xA
PROCESS_NAME:  System

 

[korson]

ok. here it is:

Network Card(s): 1 NIC(s) Installed.
[01]: Realtek PCIe GBE Family Controller
Connection Name: Local Area Connection
DHCP Enabled: Yes
DHCP Server: 10.198.128.1
IP address(es)
[01]: 10.198.129.67

is it really can help? i tried to change my network card few days ago. and still got a bsod. may be i have two separate problems? one with network, and one with something else?

 

[usasma]

Please download this driver (Win7 32/64 Auto Installation Program (SID:1396122)) from this link: Realtek

Then uninstall the one currently on your system.
Then install the one that you've just downloaded.
Then see if that stops the BSOD's

 

[korson]

done, as you say.
new bsod, new dump.

should i use verifier again?

 

[korson]

it getting worse.

today i figured out that my CPU overheating. I fixed it, but system still unstable.

I have many bsod’s trying boot windows. Once it is freeze while dumping memory.

 

[korson]

today i can't boot my windows. i tried to install new windows on new, fresh hard drive and got bsod while coping files.

i tried to change video card, hard drive and memory modules. And now i think that this is motherboard or CPU issue. So, i will test it.

 

[korson]

usasma, your first opinion about HardWare issue was right. I changed motherboard and everything become normal. My old m\b was MSI p45-neo-F. 2 years old.


Thank you for help, and sorry for taking so much of your time.

 

[usasma]

Sorry to hear that it was the mobo - but glad that you figured it out.
Good luck!