Multiple BSOD on new computer

[Halnz]

Gigabyte MA790XT-UD4P AM3
MS Window Vista Home Premium 64bit
Galazy GF 8400GS PCIe 512MB
AMD Phenom 11 x4 810
WD 640GB 7200RPM
Corsair TR3X6G133C9 6GB DDR3


I keep getting BSOD's and the details on the blue screen keep changing. I am never doing any real RAM hogging stuff when it crashes, often just surfing. I ran large complex filters in Photoshop CS2 with no problem at all.

This computer is only a few days old, and it ran fine for about 24 hours at the place it was built. I am running a Wacom pen tablet CTE-640 (installed the latest drivers).

We have Comodo firewall, and had Avast but replaced it with AVG in case Avast was causing the problems.

I am a graphic artist and while this new computer is fabulous as far as speed and effiency goes, and I adore the Vista look, the BSOD's are driving me crazy.

They did mention that they had troubles initially installing the RAM and had to change them around the slots or something...

I appreciate any help I can get. I have uploaded the minidump files. I even had a BSOD while trying to post this. *sigh*

 

[Halnz]

It bluescreened before I added our scanner/printer/CS2 and most other things. I "think" I installed Comodo and Avast before the first BSOD but I am not sure.

 

[Halnz]

One more thing, I am using an unsupported Microsoft Intellitype Pro 2.2 Keyboard, that still works apart from my beloved scroll. I wonder if this could be the cause?

 

[Halnz]

I was hoping to have an answer when I woke up, can someone please look at what I uploaded and help me out? My work is suffering and the stress is making me sick.

 

[usasma]

Crud! I erased the entire post that I was composing! :0(

Anywho, here's a summary list of the bugchecks:

Built by: 6001.18000.amd64fre.longhorn_rtm.080118-1840
Debug session time: Mon Jun  8 21:59:37.488 2009 (GMT-4)
System Uptime: 0 days 0:00:07.503
BugCheck D1, {fffff6fc00245218, 2, 0, fffffa6000fb560b}
Probably caused by : ecache.sys ( ecache!EcBlockFind+b7 )
PROCESS_NAME:  System
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 6002.18005.amd64fre.lh_sp2rtm.090410-1830
Debug session time: Tue Jun  9 22:49:26.111 2009 (GMT-4)
System Uptime: 0 days 0:07:20.513
BugCheck 50, {ffffe480262574b0, 0, fffffa60086e0e48, 7}
Probably caused by : nsiproxy.sys ( nsiproxy!NsippCancelChangeNotificationRoutine+ec )
PROCESS_NAME:  svchost.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 6002.18005.amd64fre.lh_sp2rtm.090410-1830
Debug session time: Wed Jun 10 23:56:04.248 2009 (GMT-4)
System Uptime: 0 days 0:31:01.984
BugCheck 1E, {ffffffffc0000005, fffffa6000b6c338, 0, ffffffffffffffff}
Probably caused by : NETIO.SYS ( NETIO!RtlGetNextExpiredTimerWheelEntry+98 )
PROCESS_NAME:  System
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 6002.18005.amd64fre.lh_sp2rtm.090410-1830
Debug session time: Thu Jun 11 00:11:11.947 2009 (GMT-4)
System Uptime: 0 days 0:14:13.604
BugCheck 1A, {3452, 172000, fffff700010807d0, 0}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+1c506 )
PROCESS_NAME:  svchost.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 6002.18005.amd64fre.lh_sp2rtm.090410-1830
Debug session time: Thu Jun 11 07:35:20.315 2009 (GMT-4)
System Uptime: 0 days 0:04:06.956
BugCheck 4E, {2, 158d15, 1affff, 1}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+8804 )
PROCESS_NAME:  SearchProtocolH
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 6002.18005.amd64fre.lh_sp2rtm.090410-1830
Debug session time: Thu Jun 11 13:56:13.833 2009 (GMT-4)
System Uptime: 0 days 0:01:47.863
BugCheck 50, {fffffa8096009900, 1, fffff800028c5429, 5}
Probably caused by : memory_corruption ( nt!MmCreateKernelStack+c9 )
PROCESS_NAME:  svchost.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 6002.18005.amd64fre.lh_sp2rtm.090410-1830
Debug session time: Thu Jun 11 18:45:06.044 2009 (GMT-4)
System Uptime: 0 days 4:47:53.200
BugCheck D1, {ffffe4802eb30548, 2, 1, fffffa600701fc10}
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : dxgkrnl.sys ( dxgkrnl!VIDMM_GLOBAL::UnreferenceDisplayingAllocation+4 )
PROCESS_NAME:  System
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 6002.18005.amd64fre.lh_sp2rtm.090410-1830
Debug session time: Thu Jun 11 23:44:35.055 2009 (GMT-4)
System Uptime: 0 days 3:57:46.471
BugCheck 3D, {0, 0, 0, fffffa6007024333}
Probably caused by : hardware ( dxgkrnl!VidSchiCheckPendingDeviceCommand+a8 )
PROCESS_NAME:  firefox.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 6002.18005.amd64fre.lh_sp2rtm.090410-1830
Debug session time: Fri Jun 12 02:24:52.791 2009 (GMT-4)
System Uptime: 0 days 2:39:32.003
BugCheck F4, {3, fffffa8008e8bc10, fffffa8008e8be48, fffff80002af28d0}
Probably caused by : csrss.exe
PROCESS_NAME:  csrss.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 6002.18005.amd64fre.lh_sp2rtm.090410-1830
Debug session time: Fri Jun 12 05:16:18.970 2009 (GMT-4)
System Uptime: 0 days 0:42:38.063
BugCheck D1, {139797, 2, 0, fffffa6000b3b338}
Probably caused by : NETIO.SYS ( NETIO!RtlGetNextExpiredTimerWheelEntry+98 )
PROCESS_NAME:  System
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 6002.18005.amd64fre.lh_sp2rtm.090410-1830
Debug session time: Fri Jun 12 06:41:50.945 2009 (GMT-4)
System Uptime: 0 days 1:24:47.985
BugCheck 3B, {c000001d, fffff9600011dfc4, fffffa600e9a11f0, 0}
Probably caused by : hardware ( win32k!bGetNtoW_Win31+3a4 )
PROCESS_NAME:  iexplore.exe

From looking at them, they mainly seem to be errors involving memory (could be CPU cache, RAM, or even the pagefile). A large portion of them could also point to an improperly functioning driver. Some pagefile type errors can also be caused by a malfunctioning hard drive - but I don't expect that that's the case here (but it is possible).

This comment seems to be significant to this situation:

They did mention that they had troubles initially installing the RAM and had to change them around the slots or something...

So, the first step would be to perform a bootable memory diagnostic. I'd suggest this free test: Memtest86 - Memory Diagnostic Page
Let the test run for a minimum of 3 passes (overnight is better). If it starts spitting errors out you can stop the test and post back here for some more instructions (to determine if it's the memory sticks or something else). More instructions here: Bootable Memory Test Diagnostics

Just in case it's a hard drive issue, you can run a bootable hard drive diagnostic from the manufacturer of your hard drive. More information on this is available here: Bootable Hard Drive Diagnostics

The next step would be to delete and recreate your pagefile in case it's corrupted. To do this, follow the instructions here: Delete/Recreate the pagefile

If that doesn't fix the issues, then we'll have to see about replacing your drivers. The most outdated drivers on your system are for the WACOM tablet - they're dated from February of 2007. This predates both SP1 and SP2 for Vista - so there's a good chance that it may not be working properly with Vista (or it could have become corrupted)

I believe that these are the appropriate drivers (Windows Cons. Driver 5.1.0-4 for Vista (32 or 64 bit) and XP (32 or 64 bit) updated: 2008-12-16) for your WACOM tablet, but double check me to be sure: wacom

Ensure that you follow the directions completely when installing them, particularly this part:

For best results, uninstall any Wacom tablet drivers older than v.5.05, restart and temporarily disable your antivirus software and Windows Defender. Then install this new driver. After installation has been successfully completed, re-enable your antivirus software and Windows Defender. (To disable or enable Windows Defender, go to Start – All Programs – Windows Defender. Then select Tools – Options. Under Administrator options (at the very bottom), select or clear the Use Windows Defender check box, and then click Save. If you are prompted for an administrator password or confirmation, type the password or provide confirmation.)

Good luck!

 

[Halnz]

Thank you so much for your help. I was in tears this morning with frustration. I will run through the diagnostic tests and see what happens.

I appreciate the time you took to answer. Will report back when the tests are done.

 

[Halnz]

Okay, have had the guys that built my machine around here and we did loads of memtests and while all the RAM passed, it failed if it was in certain slots. So we are thinking it may be the motherboard rather than the ram, and they did mutter something about the dual channnel but I don't understand it.

They did something in the bios and I am now sitting on 4G ram at least until Monday. We will probably end up taking the motherboard back. It will be interesting to see if I still get blue screens.....

 

[usasma]

If you've isolated bad slots in the motherboard, then it should be replaced (since it's a new system). There's no telling what caused the slots to go bad (so it could get worse) and you paid for a functioning motherboard - which this one isn't.

Good luck!

 

[Halnz]

Thanks!

I just read on another thread that my Phenom may not support triple channel. Does this mean we can't have 3 2GB sticks in the slots and we should get one more to even things up?

 

[usasma]

You'll have to check the AMD site for the specifics on the Phenom, and the Gigabyte site for the specifics for your motherboard. I concentrate on the BSOD's, so let's wait for someone with more hardware knowledge to post.

 

[Halnz]

Okay thanks, think I should start a new thread?

 

[usasma]

I'm still fairly new here, so I'm not aware of all the different forums that are available.
I'd start a new thread with the title something like: Phenom and triple channel memory issues and then provide a link back to this post.