Persistent BSOD when using Adobe CS4

Piccadillypunte · 19 Feb 2011

Hi,

I have had persistent problems using Adobe CS4 (Premiere Pro/Bridge/Media Encoder/Encore) but after looking firstly at their software the forum guys suggested checking hardware/ windows/ etc. I am working through this and here is the BSOD dumps etc.

I do hope there is a solution - The machine is wonderful when it works, and the videos are fantastic (bluray) but the BSOD -

I have looked at the BSOD viewer and I will include the c:\Windows\Minidump

It is a Windows 7 64 bit Ultimate OEM version - the original installation when I purchased the machine 15 months ago. It has never been reinstalled but I have cleaned the register.
I have also run CPUID and the following results are not really indicative of heavy work - the Core temps are then up to 81C. But are those FanPWM0 etc a problem - they never show anything but 0.
If there is anyhting else please help me get it for you.

Piccadillypunter

zigzag3143 · 19 Feb 2011

Piccadillypunte said:

Hi,

I have had persistent problems using Adobe CS4 (Premiere Pro/Bridge/Media Encoder/Encore) but after looking firstly at their software the forum guys suggested checking hardware/ windows/ etc. I am working through this and here is the BSOD dumps etc.

I do hope there is a solution - The machine is wonderful when it works, and the videos are fantastic (bluray) but the BSOD -

I have looked at the BSOD viewer and I will include the c:\Windows\Minidump

It is a Windows 7 64 bit Ultimate OEM version - the original installation when I purchased the machine 15 months ago. It has never been reinstalled but I have cleaned the register.
I have also run CPUID and the following results are not really indicative of heavy work - the Core temps are then up to 81C. But are those FanPWM0 etc a problem - they never show anything but 0.
If there is anyhting else please help me get it for you.

Piccadillypunter

No minidumps included in the upload try this method.

To enable us to assist you with your computer's BSOD symptoms, upload the contents of your "\Windows\Minidump" folder.

The procedure:

* Copy the contents of \Windows\Minidump to another (temporary) location somewhere on your machine.
* Zip up the copy.
* Attach the ZIP archive to your post using the "paperclip" (file attachments) button.

To ensure minidumps are enabled:

Go to Start, in the Search Box type: sysdm.cpl, press Enter.
Under the Advanced tab, click on the Startup and Recovery Settings... button.
Ensure that Automatically restart is unchecked.
Under the Write Debugging Information header select Small memory dump (256 kB) in the dropdown box (the 256kb varies).
Ensure that the Small Dump Directory is listed as %systemroot%\Minidump.
OK your way out.
Reboot if changes have been made.

Piccadillypunte · 19 Feb 2011

I had put them in a separate folder - they load here when I look at the zip file - try againAttachment 139204

Attachment 139205

Attachment 139206

Attachment 139207

usasma · 19 Feb 2011

50 memory dumps in about 3 weeks - phew!

Lot's of video issues - so let's pursue that first (there may be other problems).
Please start with this:

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 try the steps here: STOP 0x116: VIDEO_TDR_ERROR troubleshooting And, if possible, try another video card to see if that stops the problems.

I'll post back when the memory dumps are finished running....

usasma · 19 Feb 2011

I just notice that you cite core temps of 81º C - that's awfully hot and could be causing errors!
When you assembled the system, did you ensure that the CPU had thermal compound on it?
Have you checked to make sure that the CPU fan is running?
Have you tried having a house fan blowing into the open case - to see if it decreases the temperatures/frequency of the BSOD's?

The memory dumps show primarily STOP 0x1A errors with a smattering of STOP 0x50, 0x4E, 0xA, 0xDE, and 0x3B errors
3 causes blamed (primarily ntkrnlmp.exe with a smattering of win32k.sys, and memory_corruption causes)

So, first let's install a free temp monitoring program: Download SpeedFan - Access temperature sensor in your computer
Use it to keep an eye on the system - and see if high temps are causing the BSOD's.

Next, are you using any custom settings in the BIOS (overclocking or memory/RAM tweaks)?
If so, please reset the system to the FailSafe/Default values and rerun the memory test described in the previous post.

Please uninstall the Gigabyte Easy Saver utility. If you must use it, download a fresh copy from the Gigabyte website. The current driver is dated from August of 2008 and may have issues with Win7 (gdrv.sys Fri Aug 08 14:28:54 2008 (489C9066))

Depending on what you're using to power your RAID array (I suspect you're using the Intel ATA Controller), the JMicron ATA Controller driver is from 2008 also. Please update it or remove it from your system.

Try these free stress tests to see if there's any stability issues:

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).
- 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.

Here's a list of the older drivers (with links following). Update these as you are able - but I'm more concerned about the temperature issues right now:

Code:


jraid.sys        Mon Nov 03 21:20:09 2008 (490FB159)
amdxata.sys      Tue May 19 13:56:59 2009 (4A12F2EB)
PxHlpa64.sys     Tue Jun 23 19:16:35 2009 (4A416253)
iaStorV.sys      Wed Apr 08 12:57:17 2009 (49DCD76D)
MpFilter.sys     Tue Sep 14 20:19:28 2010 (4C901110)
Rt64win7.sys     Thu Jul 30 07:58:43 2009 (4A718AF3)
RtHDMIVX.sys     Tue Nov 23 05:27:12 2010 (4CEB9700)
NuidFltr.sys     Tue Jun 29 04:54:32 2010 (4C29B4C8)
point64.sys      Tue Jun 29 04:54:31 2010 (4C29B4C7)
RTKVHD64.sys     Wed Dec 29 22:52:42 2010 (4D1C020A)
dc3d.sys         Thu Jul 01 06:07:45 2010 (4C2C68F1)
adfs.SYS         Mon Nov 03 11:48:14 2008 (490F2B4E)
MpNWMon.sys      Tue Sep 14 20:19:30 2010 (4C901112)
gdrv.sys         Fri Aug 08 14:28:54 2008 (489C9066)
NisDrvWFP.sys    Tue Sep 14 20:20:25 2010 (4C901149)
cpuz135_x64.sys  Tue Nov 09 08:33:36 2010 (4CD94DB0)
atikmpag.sys     Tue Jan 04 21:19:38 2011 (4D23D53A)
AtihdW76.sys     Wed Nov 17 07:02:04 2010 (4CE3C43C)
atikmpag.sys     Thu Nov 25 21:16:47 2010 (4CEF188F)
atikmdag.sys     Thu Nov 25 21:46:44 2010 (4CEF1F94)
MpFilter.sys     Sat Mar 20 01:58:08 2010 (4BA463F0)
MpNWMon.sys      Sat Mar 20 01:58:00 2010 (4BA463E8)

  
http://www.carrona.org/dvrref.html#jraid.sys 
http://www.carrona.org/dvrref.html#amdxata.sys 
http://www.carrona.org/dvrref.html#PxHlpa64.sys 
http://www.carrona.org/dvrref.html#iaStorV.sys 
http://www.carrona.org/dvrref.html#MpFilter.sys 
http://www.carrona.org/dvrref.html#Rt64win7.sys 
http://www.carrona.org/dvrref.html#RtHDMIVX.sys 
http://www.carrona.org/dvrref.html#NuidFltr.sys 
http://www.carrona.org/dvrref.html#point64.sys 
http://www.carrona.org/dvrref.html#RTKVHD64.sys 
http://www.carrona.org/dvrref.html#dc3d.sys 
http://www.carrona.org/dvrref.html#adfs.SYS 
http://www.carrona.org/dvrref.html#MpNWMon.sys 
http://www.carrona.org/dvrref.html#gdrv.sys 
http://www.carrona.org/dvrref.html#NisDrvWFP.sys 
http://www.carrona.org/dvrref.html#cpuz135_x64.sys 
http://www.carrona.org/dvrref.html#atikmpag.sys 
http://www.carrona.org/dvrref.html#AtihdW76.sys 
http://www.carrona.org/dvrref.html#atikmpag.sys 
http://www.carrona.org/dvrref.html#atikmdag.sys 
http://www.carrona.org/dvrref.html#MpFilter.sys 
http://www.carrona.org/dvrref.html#MpNWMon.sys

BSOD BUGCHECK SUMMARY

Code:


Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Fri Feb 18 04:11:36.593 2011 (UTC - 5:00)
System Uptime: 0 days 0:42:55.530
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+207da )
BUGCHECK_STR:  0x1a_401
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  MsMpEng.exe
FAILURE_BUCKET_ID:  X64_0x1a_401_nt!_??_::FNODOBFM::_string_+207da
Bugcheck code 0000001A
Arguments 00000000`00000401 fffff6fb`800084e0 80000001`ecf7d863 fffff6fb`80008ce0
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = EX58-UD5
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Fri Feb 18 03:24:36.478 2011 (UTC - 5:00)
System Uptime: 0 days 0:13:31.414
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+21b46 )
BUGCHECK_STR:  0x1a_5003
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  PProHeadless.e
FAILURE_BUCKET_ID:  X64_0x1a_5003_nt!_??_::FNODOBFM::_string_+21b46
Bugcheck code 0000001A
Arguments 00000000`00005003 fffff700`01080000 00000000`00027725 00010305`0004fe4a
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = EX58-UD5
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Fri Feb 18 03:07:14.196 2011 (UTC - 5:00)
System Uptime: 0 days 0:10:47.133
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+3683c )
BUGCHECK_STR:  0x1a_5003
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  Adobe Media En
FAILURE_BUCKET_ID:  X64_0x1a_5003_nt!_??_::FNODOBFM::_string_+3683c
Bugcheck code 0000001A
Arguments 00000000`00005003 fffff700`01080000 00000000`0000d65f 0001874e`0001a8be
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = EX58-UD5
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Fri Feb 18 02:51:54.764 2011 (UTC - 5:00)
System Uptime: 0 days 1:01:40.701
Probably caused by : memory_corruption ( nt!MiReplenishPageSlist+100 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  PProHeadless.e
FAILURE_BUCKET_ID:  X64_0xA_nt!MiReplenishPageSlist+100
Bugcheck code 0000000A
Arguments 00000000`00000010 00000000`00000002 00000000`00000001 fffff800`032f8b7f
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = EX58-UD5
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Fri Feb 18 01:45:53.590 2011 (UTC - 5:00)
System Uptime: 0 days 0:11:42.527
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+31ef2 )
BUGCHECK_STR:  0x1a_403
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  ImporterProces
FAILURE_BUCKET_ID:  X64_0x1a_403_nt!_??_::FNODOBFM::_string_+31ef2
Bugcheck code 0000001A
Arguments 00000000`00000403 fffff680`0045f778 8ae00000`93d49867 fffff680`0045ff78
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = EX58-UD5
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Fri Feb 18 01:30:10.817 2011 (UTC - 5:00)
System Uptime: 0 days 1:14:25.643
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+21b46 )
BUGCHECK_STR:  0x1a_5003
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  ImporterProces
FAILURE_BUCKET_ID:  X64_0x1a_5003_nt!_??_::FNODOBFM::_string_+21b46
Bugcheck code 0000001A
Arguments 00000000`00005003 fffff700`01080000 00000000`00032f36 00032f38`00065a6c
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = EX58-UD5
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Thu Feb 17 20:44:44.977 2011 (UTC - 5:00)
System Uptime: 0 days 0:03:21.914
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+21b46 )
BUGCHECK_STR:  0x1a_5003
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  ImporterProces
FAILURE_BUCKET_ID:  X64_0x1a_5003_nt!_??_::FNODOBFM::_string_+21b46
Bugcheck code 0000001A
Arguments 00000000`00005003 fffff700`01080000 00000000`0001e53d 0001ef80`0003ea7a
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = EX58-UD5
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Thu Feb 17 20:36:57.495 2011 (UTC - 5:00)
System Uptime: 0 days 5:24:48.321
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+33906 )
BUGCHECK_STR:  0x1a_41790
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  ImporterProces
FAILURE_BUCKET_ID:  X64_0x1a_41790_nt!_??_::FNODOBFM::_string_+33906
Bugcheck code 0000001A
Arguments 00000000`00041790 fffffa80`01150dd0 00000000`0000ffff 00000000`00000000
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = EX58-UD5
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Wed Feb 16 21:44:50.593 2011 (UTC - 5:00)
System Uptime: 0 days 1:33:44.530
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+21b46 )
BUGCHECK_STR:  0x1a_5003
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  ImporterProces
FAILURE_BUCKET_ID:  X64_0x1a_5003_nt!_??_::FNODOBFM::_string_+21b46
Bugcheck code 0000001A
Arguments 00000000`00005003 fffff700`01080000 00000000`00037c28 00037c29`0006e850
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = EX58-UD5
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Wed Feb 16 20:07:01.940 2011 (UTC - 5:00)
System Uptime: 0 days 4:15:36.877
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+339c8 )
BUGCHECK_STR:  0x1a_41790
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  PProHeadless.e
FAILURE_BUCKET_ID:  X64_0x1a_41790_nt!_??_::FNODOBFM::_string_+339c8
Bugcheck code 0000001A
Arguments 00000000`00041790 fffffa80`00b2d0d0 00000000`0000ffff 00000000`00000000
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = EX58-UD5
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Wed Feb 16 15:33:26.380 2011 (UTC - 5:00)
System Uptime: 0 days 0:22:13.317
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+42ba5 )
BUGCHECK_STR:  0x1a_41287
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  MaxBackService
FAILURE_BUCKET_ID:  X64_0x1a_41287_nt!_??_::FNODOBFM::_string_+42ba5
Bugcheck code 0000001A
Arguments 00000000`00041287 00000000`00000080 00000000`00000000 00000000`00000000
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = EX58-UD5
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Wed Feb 16 05:16:58.611 2011 (UTC - 5:00)
System Uptime: 0 days 0:21:17.547
Probably caused by : memory_corruption ( nt!MiRelinkStandbyPage+c6 )
BUGCHECK_STR:  0x1a_8884
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  svchost.exe
FAILURE_BUCKET_ID:  X64_0x1a_8884_nt!MiRelinkStandbyPage+c6
Bugcheck code 0000001A
Arguments 00000000`00008884 fffffa80`0600e280 fffffa80`06056580 00000000`00000604
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = EX58-UD5
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Tue Feb 15 22:59:26.971 2011 (UTC - 5:00)
System Uptime: 0 days 0:15:54.907
Probably caused by : win32k.sys ( win32k!SURFACE::bDeleteSurface+3c8 )
BUGCHECK_STR:  0x1a_403
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  dwm.exe
FAILURE_BUCKET_ID:  X64_0x1a_403_win32k!SURFACE::bDeleteSurface+3c8
Bugcheck code 0000001A
Arguments 00000000`00000403 fffff680`00014e80 84000000`4c515867 fffff680`00014680
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = EX58-UD5
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Tue Feb 15 22:40:08.276 2011 (UTC - 5:00)
System Uptime: 0 days 0:06:18.213
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+29731 )
BUGCHECK_STR:  0x1a_5003
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  ImporterProces
FAILURE_BUCKET_ID:  X64_0x1a_5003_nt!_??_::FNODOBFM::_string_+29731
Bugcheck code 0000001A
Arguments 00000000`00005003 fffff700`01080000 00000000`000068d0 00051a21`0000d5a0
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = EX58-UD5
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Tue Feb 15 22:30:00.166 2011 (UTC - 5:00)
System Uptime: 0 days 16:31:38.102
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+21b46 )
BUGCHECK_STR:  0x1a_5003
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  ImporterProces
FAILURE_BUCKET_ID:  X64_0x1a_5003_nt!_??_::FNODOBFM::_string_+21b46
Bugcheck code 0000001A
Arguments 00000000`00005003 fffff700`01080000 00000000`00039197 0003d65d`00072a2e
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = EX58-UD5
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Tue Feb 15 00:25:54.764 2011 (UTC - 5:00)
System Uptime: 0 days 2:29:15.590
Probably caused by : ntkrnlmp.exe ( nt!ExpInterlockedPopEntrySListFault16+0 )
BUGCHECK_STR:  0x1E_c0000005
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  PProHeadless.e
FAILURE_BUCKET_ID:  X64_0x1E_c0000005_nt!ExpInterlockedPopEntrySListFault16+0
Bugcheck code 0000001E
Arguments ffffffff`c0000005 fffff800`032d7905 00000000`00000000 ffffffff`ffffffff
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = EX58-UD5
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Mon Feb 14 19:37:18.149 2011 (UTC - 5:00)
System Uptime: 0 days 2:20:42.085
Probably caused by : memory_corruption ( nt!MiCompleteProtoPteFault+7f )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x50
PROCESS_NAME:  ImporterProces
FAILURE_BUCKET_ID:  X64_0x50_nt!MiCompleteProtoPteFault+7f
Bugcheck code 00000050
Arguments fffffc80`0000b970 00000000`00000000 fffff800`032e6faf 00000000`00000007
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = EX58-UD5
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Mon Feb 14 17:12:49.920 2011 (UTC - 5:00)
System Uptime: 0 days 0:44:38.856
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+4a83 )
BUGCHECK_STR:  0x1a_41284
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  ImporterProces
FAILURE_BUCKET_ID:  X64_0x1a_41284_nt!_??_::FNODOBFM::_string_+4a83
Bugcheck code 0000001A
Arguments 00000000`00041284 00000000`41028001 00000000`0004fc3f fffff700`01080000
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = EX58-UD5
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Mon Feb 14 02:55:34.693 2011 (UTC - 5:00)
System Uptime: 0 days 0:18:27.629
Probably caused by : memory_corruption ( nt!MiBadRefCount+4f )
BUGCHECK_STR:  0x4E_9a
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x4E_9a_nt!MiBadRefCount+4f
Bugcheck code 0000004E
Arguments 00000000`0000009a 00000000`00009775 00000000`00000002 00000000`00000000
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = EX58-UD5
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Sun Feb 13 18:48:28.237 2011 (UTC - 5:00)
System Uptime: 0 days 8:22:55.175
Probably caused by : memory_corruption ( nt!MiFindNodeOrParent+0 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  svchost.exe
FAILURE_BUCKET_ID:  X64_0xA_nt!MiFindNodeOrParent+0
Bugcheck code 0000000A
Arguments 00000000`00000028 00000000`00000002 00000000`00000000 fffff800`032fc518
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = EX58-UD5
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Sun Feb 13 02:58:40.335 2011 (UTC - 5:00)
System Uptime: 0 days 1:00:10.272
Probably caused by : memory_corruption ( nt!MiBadShareCount+4c )
BUGCHECK_STR:  0x4E_99
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  PProHeadless.e
FAILURE_BUCKET_ID:  X64_0x4E_99_nt!MiBadShareCount+4c
Bugcheck code 0000004E
Arguments 00000000`00000099 00000000`000a3a95 00000000`00000003 00000000`001dcaa3
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = EX58-UD5
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Sun Feb 13 01:42:44.401 2011 (UTC - 5:00)
System Uptime: 0 days 0:11:37.339
Probably caused by : memory_corruption ( nt!MiReplenishPageSlist+100 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  ImporterProces
FAILURE_BUCKET_ID:  X64_0xA_nt!MiReplenishPageSlist+100
Bugcheck code 0000000A
Arguments 00000000`00000010 00000000`00000002 00000000`00000001 fffff800`032f8b7f
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = EX58-UD5
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Sun Feb 13 01:27:45.886 2011 (UTC - 5:00)
System Uptime: 0 days 0:13:05.823
Probably caused by : ntkrnlmp.exe ( nt!KiKernelCalloutExceptionHandler+e )
BUGCHECK_STR:  0x1E_0
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x1E_0_nt!KiKernelCalloutExceptionHandler+e
Bugcheck code 0000001E
Arguments 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = EX58-UD5
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Sun Feb 13 01:11:04.732 2011 (UTC - 5:00)
System Uptime: 0 days 0:14:59.669
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+29731 )
BUGCHECK_STR:  0x1a_5003
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  ImporterProces
FAILURE_BUCKET_ID:  X64_0x1a_5003_nt!_??_::FNODOBFM::_string_+29731
Bugcheck code 0000001A
Arguments 00000000`00005003 fffff700`01080000 00000000`0002b9eb 0001903b`0005fad6
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = EX58-UD5
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Tue Feb  8 16:47:51.796 2011 (UTC - 5:00)
System Uptime: 0 days 1:37:43.733
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+33906 )
BUGCHECK_STR:  0x1a_41790
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  ImporterProces
FAILURE_BUCKET_ID:  X64_0x1a_41790_nt!_??_::FNODOBFM::_string_+33906
Bugcheck code 0000001A
Arguments 00000000`00041790 fffffa80`04338750 00000000`0000ffff 00000000`00000000
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = EX58-UD5
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Mon Feb  7 18:26:10.283 2011 (UTC - 5:00)
System Uptime: 0 days 2:18:49.109
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+4a83 )
BUGCHECK_STR:  0x1a_41284
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  ImporterProces
FAILURE_BUCKET_ID:  X64_0x1a_41284_nt!_??_::FNODOBFM::_string_+4a83
Bugcheck code 0000001A
Arguments 00000000`00041284 00000000`18797001 00000000`0000d387 fffff700`01080000
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = EX58-UD5
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Mon Feb  7 16:03:45.538 2011 (UTC - 5:00)
System Uptime: 0 days 0:17:10.474
Probably caused by : memory_corruption ( nt!MiUnlinkPageFromLockedList+298 )
BUGCHECK_STR:  0x1a_8886
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  Adobe Encore.e
FAILURE_BUCKET_ID:  X64_0x1a_8886_nt!MiUnlinkPageFromLockedList+298
Bugcheck code 0000001A
Arguments 00000000`00008886 fffffa80`0217f440 fffffa80`021f8c70 00000000`00000500
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = EX58-UD5
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Mon Feb  7 15:42:31.552 2011 (UTC - 5:00)
System Uptime: 0 days 0:06:34.489
Probably caused by : memory_corruption ( nt!MiUnlinkPageFromLockedList+298 )
BUGCHECK_STR:  0x1a_8886
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  Adobe Encore.e
FAILURE_BUCKET_ID:  X64_0x1a_8886_nt!MiUnlinkPageFromLockedList+298
Bugcheck code 0000001A
Arguments 00000000`00008886 fffffa80`004ce480 fffffa80`004fb4b0 00000000`00000500
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = EX58-UD5
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Mon Feb  7 15:32:35.419 2011 (UTC - 5:00)
System Uptime: 0 days 0:18:43.356
BugCheck DE, {2, fffff8a015940250, fffff8a015940a51, 168d0d8c0}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+2d260 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xDE
PROCESS_NAME:  Adobe Encore.e
FAILURE_BUCKET_ID:  X64_0xDE_nt!_??_::FNODOBFM::_string_+2d260
Bugcheck code 000000DE
Arguments 00000000`00000002 fffff8a0`15940250 fffff8a0`15940a51 00000001`68d0d8c0
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = EX58-UD5
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Mon Feb  7 02:22:20.985 2011 (UTC - 5:00)
System Uptime: 0 days 0:53:25.922
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+21b46 )
BUGCHECK_STR:  0x1a_5003
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  PProHeadless.e
FAILURE_BUCKET_ID:  X64_0x1a_5003_nt!_??_::FNODOBFM::_string_+21b46
Bugcheck code 0000001A
Arguments 00000000`00005003 fffff700`01080000 00000000`00015013 00030fdd`0002a426
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = EX58-UD5
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Mon Feb  7 01:24:54.594 2011 (UTC - 5:00)
System Uptime: 0 days 3:06:06.531
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+31ef2 )
BUGCHECK_STR:  0x1a_403
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  Adobe Media En
FAILURE_BUCKET_ID:  X64_0x1a_403_nt!_??_::FNODOBFM::_string_+31ef2
Bugcheck code 0000001A
Arguments 00000000`00000403 fffff680`001bcfa8 e7b00000`405ae805 fffff680`00709c78
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = EX58-UD5
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sun Feb  6 22:15:03.275 2011 (UTC - 5:00)
System Uptime: 0 days 2:39:13.212
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+33906 )
BUGCHECK_STR:  0x1a_41790
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  svchost.exe
FAILURE_BUCKET_ID:  X64_0x1a_41790_nt!_??_::FNODOBFM::_string_+33906
Bugcheck code 0000001A
Arguments 00000000`00041790 fffffa80`033d2bd0 00000000`0000ffff 00000000`00000000
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = EX58-UD5
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sun Feb  6 16:46:50.545 2011 (UTC - 5:00)
System Uptime: 0 days 1:35:09.482
Probably caused by : memory_corruption ( nt!MiReplenishPageSlist+100 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  ImporterProces
FAILURE_BUCKET_ID:  X64_0xA_nt!MiReplenishPageSlist+100
Bugcheck code 0000000A
Arguments 00000000`00000010 00000000`00000002 00000000`00000001 fffff800`02e96b7f
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = EX58-UD5
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sun Feb  6 11:46:41.060 2011 (UTC - 5:00)
System Uptime: 0 days 18:03:31.998
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+21b46 )
BUGCHECK_STR:  0x1a_5003
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  ImporterProces
FAILURE_BUCKET_ID:  X64_0x1a_5003_nt!_??_::FNODOBFM::_string_+21b46
Bugcheck code 0000001A
Arguments 00000000`00005003 fffff700`01080000 00000000`0006eec2 000333dd`000dcd84
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = EX58-UD5
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sat Feb  5 04:40:34.032 2011 (UTC - 5:00)
System Uptime: 0 days 1:17:25.969
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+21b46 )
BUGCHECK_STR:  0x1a_5003
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  PProHeadless.e
FAILURE_BUCKET_ID:  X64_0x1a_5003_nt!_??_::FNODOBFM::_string_+21b46
Bugcheck code 0000001A
Arguments 00000000`00005003 fffff700`01080000 00000000`0001a09f 0001a0f8`0003403e
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = EX58-UD5
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sat Feb  5 03:20:12.408 2011 (UTC - 5:00)
System Uptime: 0 days 0:03:47.345
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+13bb2 )
BUGCHECK_STR:  0x1a_41201
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  svchost.exe
FAILURE_BUCKET_ID:  X64_0x1a_41201_nt!_??_::FNODOBFM::_string_+13bb2
Bugcheck code 0000001A
Arguments 00000000`00041201 fffff680`00036f48 8b700001`8e425867 fffffa80`0940d6b0
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = EX58-UD5
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sat Feb  5 02:00:13.291 2011 (UTC - 5:00)
System Uptime: 0 days 1:32:44.228
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+4a83 )
BUGCHECK_STR:  0x1a_41284
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  PProHeadless.e
FAILURE_BUCKET_ID:  X64_0x1a_41284_nt!_??_::FNODOBFM::_string_+4a83
Bugcheck code 0000001A
Arguments 00000000`00041284 00000000`fd5fb001 00000000`0001de37 fffff700`01080000
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = EX58-UD5
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Fri Feb  4 10:50:51.626 2011 (UTC - 5:00)
System Uptime: 0 days 5:47:23.452
Probably caused by : memory_corruption ( nt!MiBadRefCount+4f )
BUGCHECK_STR:  0x4E_9a
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x4E_9a_nt!MiBadRefCount+4f
Bugcheck code 0000004E
Arguments 00000000`0000009a 00000000`00018fc5 00000000`00000001 00000000`00000000
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = EX58-UD5
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Wed Feb  2 23:07:30.929 2011 (UTC - 5:00)
System Uptime: 0 days 0:36:54.865
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+339c8 )
BUGCHECK_STR:  0x1a_41790
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  ImporterProces
FAILURE_BUCKET_ID:  X64_0x1a_41790_nt!_??_::FNODOBFM::_string_+339c8
Bugcheck code 0000001A
Arguments 00000000`00041790 fffffa80`012e8aa0 00000000`0000ffff 00000000`00000000
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = EX58-UD5
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Wed Feb  2 22:26:24.181 2011 (UTC - 5:00)
System Uptime: 0 days 6:00:19.118
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+4a83 )
BUGCHECK_STR:  0x1a_41284
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  ImporterProces
FAILURE_BUCKET_ID:  X64_0x1a_41284_nt!_??_::FNODOBFM::_string_+4a83
Bugcheck code 0000001A
Arguments 00000000`00041284 00000000`692f2001 00000000`0004b85f fffff700`01080000
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = EX58-UD5
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Wed Feb  2 16:15:36.424 2011 (UTC - 5:00)
System Uptime: 0 days 0:28:17.361
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+21b46 )
BUGCHECK_STR:  0x1a_5003
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  ImporterProces
FAILURE_BUCKET_ID:  X64_0x1a_5003_nt!_??_::FNODOBFM::_string_+21b46
Bugcheck code 0000001A
Arguments 00000000`00005003 fffff700`01080000 00000000`00066ddc 00022baa`000ccbb8
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = EX58-UD5
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Wed Feb  2 03:32:14.616 2011 (UTC - 5:00)
System Uptime: 0 days 8:20:10.553
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+4a83 )
BUGCHECK_STR:  0x1a_41284
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  ImporterProces
FAILURE_BUCKET_ID:  X64_0x1a_41284_nt!_??_::FNODOBFM::_string_+4a83
Bugcheck code 0000001A
Arguments 00000000`00041284 00000000`33508001 00000000`0002c2a7 fffff700`01080000
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = EX58-UD5
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Tue Feb  1 19:08:23.676 2011 (UTC - 5:00)
System Uptime: 0 days 0:40:23.613
Probably caused by : ntkrnlmp.exe ( nt!KeZeroSinglePage+10 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  svchost.exe
FAILURE_BUCKET_ID:  X64_0xA_nt!KeZeroSinglePage+10
Bugcheck code 0000000A
Arguments fffff880`02a48000 00000000`00000000 00000000`00000001 fffff800`02f144d0
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = EX58-UD5
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Tue Feb  1 18:24:18.436 2011 (UTC - 5:00)
System Uptime: 0 days 0:50:22.372
Probably caused by : memory_corruption ( nt!MiUnlinkPageFromLockedList+298 )
BUGCHECK_STR:  0x1a_8886
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  MsMpEng.exe
FAILURE_BUCKET_ID:  X64_0x1a_8886_nt!MiUnlinkPageFromLockedList+298
Bugcheck code 0000001A
Arguments 00000000`00008886 fffffa80`014b2090 fffffa80`014ee0c0 00000000`00000500
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = EX58-UD5
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Tue Feb  1 17:30:13.425 2011 (UTC - 5:00)
System Uptime: 0 days 0:55:55.362
BugCheck DE, {2, fffff8a00e0e33e8, fffff8a00e0eb7e9, 1475018c0}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+2d260 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xDE
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xDE_nt!_??_::FNODOBFM::_string_+2d260
Bugcheck code 000000DE
Arguments 00000000`00000002 fffff8a0`0e0e33e8 fffff8a0`0e0eb7e9 00000001`475018c0
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = EX58-UD5
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Fri Jan 28 20:59:49.903 2011 (UTC - 5:00)
System Uptime: 0 days 5:01:35.840
Probably caused by : memory_corruption ( nt!MiUnlinkPageFromLockedList+8e )
BUGCHECK_STR:  0x4E_2
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  svchost.exe
FAILURE_BUCKET_ID:  X64_0x4E_2_nt!MiUnlinkPageFromLockedList+8e
Bugcheck code 0000004E
Arguments 00000000`00000002 00000000`0003b53a 00000000`0022ffff 00000000`00000001
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = EX58-UD5
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Mon Jan 24 23:04:18.956 2011 (UTC - 5:00)
System Uptime: 0 days 3:50:33.893
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+21b46 )
BUGCHECK_STR:  0x1a_5003
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  PProHeadless.e
FAILURE_BUCKET_ID:  X64_0x1a_5003_nt!_??_::FNODOBFM::_string_+21b46
Bugcheck code 0000001A
Arguments 00000000`00005003 fffff700`01080000 00000000`0002c4b7 0000fc47`00058d6e
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = EX58-UD5
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Mon Jan 24 19:09:58.773 2011 (UTC - 5:00)
System Uptime: 0 days 0:51:24.710
Probably caused by : memory_corruption ( nt!MiRelinkStandbyPage+115 )
BUGCHECK_STR:  0x1a_8885
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  svchost.exe
FAILURE_BUCKET_ID:  X64_0x1a_8885_nt!MiRelinkStandbyPage+115
Bugcheck code 0000001A
Arguments 00000000`00008885 fffffa80`011ad3b0 fffffa80`0014e380 00000000`00000502
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = EX58-UD5
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Mon Jan 24 18:14:33.739 2011 (UTC - 5:00)
System Uptime: 0 days 2:59:16.676
Probably caused by : ntkrnlmp.exe ( nt!AlpcpCancelMessagesByRequestor+84 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  taskhost.exe
FAILURE_BUCKET_ID:  X64_0x3B_nt!AlpcpCancelMessagesByRequestor+84
Bugcheck code 0000003B
Arguments 00000000`c0000005 fffff800`03168540 fffff880`029f5e30 00000000`00000000
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = EX58-UD5
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Mon Jan 24 01:01:31.408 2011 (UTC - 5:00)
System Uptime: 0 days 0:52:57.234
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+4a83 )
BUGCHECK_STR:  0x1a_41284
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  ImporterProces
FAILURE_BUCKET_ID:  X64_0x1a_41284_nt!_??_::FNODOBFM::_string_+4a83
Bugcheck code 0000001A
Arguments 00000000`00041284 00000000`7987f001 00000000`0004d10f fffff700`01080000
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = EX58-UD5
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

Piccadillypunte · 20 Feb 2011

Thank you so much for all the work done so far. I have tried to begin but it has been a most frustrating day.

I finally managed to get a version of Memtest running on the machine concerned, and it ran until it had done 10% of the test - 21% of the first pass and then hung. I let it go for some time, but it was obvious it was doing nothing at all.

I tried again with exactly the same result.

I went back and check out all the various versions etc (I already had a CD version 3.5 but I see it has some problems and my recollection is it did not run previously on this machine). I tried loading from USB but that never works, no matter what I do. I tried a DVD version (which is what I had running but hung) but I downloaded it again to make certain I had the latest version and I had done everything correctly, but now it begins loading it and hangs before it actually starts.

I tried the USB stick version on my laptop and it works just fine, but that is running XP and is 32bit and has only 4gb of memory.

The machine still works just fine, but I cannot get past your first request - a memory test.

I have looked at the fans and all are running (6 of them). I did not assemble this machine myself, but ti was done by a major outlet here and I would have expected the paste to have been applied and correctly. I have tried another application I have, which has huge Excel macros - these run for hours non stop - and I have deliberately set up a long running one but the temperature remains stable at about 48 to 51C max.

I'll go back to it tomorrow, but if you have any suggestions I would appreciate them.

Thanks once again

Piccadillypunter

Piccadillypunte · 20 Feb 2011

I have made some progress but I am concerned - not sure what to do.

1. Memtest does not work with 4gb and higher. I have managed to get memtest 3.5a to load but multiprocessors and 4gb and higher is "experimental" and does not work. Other users report the same problems. I loaded the microsoft memory checker but it only checks the first 4gb and it is fine. Unless someone can show me where to get an 8gb multiprocess version of memtest I think I'll have to move on.

2. The HDD seagate seatools test of both raid arrays was fine.

3. Furmark worked fine on the video card and ran for at least three hours pushing the max temp up to 74c on the graphics card.

4. I am up to the Prime test and it is the temperature that worries me. After about 20 mins running the core temps were all up to 92C. As soon as I stopped the test it dropped immediately to 63c and then drifted back to 44c. How hot is too hot? And what can I do about it. Should I just sail on?

Piccadillypunte · 21 Feb 2011

"Depending on what you're using to power your RAID array (I suspect you're using the Intel ATA Controller), the JMicron ATA Controller driver is from 2008 also. Please update it or remove it from your system."

Okay, I have a Gigabyte motherboard and a Gigabyte GBB36X controller driver is installed AND an Intel CH8R/ICH9R/ICH10R/DO SATA RAID Controller

My RAID 5 is controlled from BIOS and I expect it is using the Intel controller. But if I remove the Gigabyte controller will I loose all my data? How can I tell?

I am running Driver Mender and it wants to update the Intel raid driver, but says to only do so when re-intalling the system - it never mentions the JMicron Raid controller and I did not realise it was even there.

I have seen other references to people who have removed the Gigabyte controller and end up in a knot

usasma · 21 Feb 2011

Please use MemTest86+ - not MemTest. MemTest86+ is precompiled to test more than 4gB of RAM.
Here's the link: Memtest86+ - Advanced Memory Diagnostic Tool

I've used the v4.10 at work since it was first released, and have just recently started trying the v4.20. The only issue that I have with it is on a few Asus systems - and they won't run the regular MemTest either.

92ºC is way too hot, and 63ºC is still too hot. So you have to start looking at cooling solutions for your CPU - it just shouldn't get that hot. If the fan is working and the cooler appears to be properly seated on the CPU - then it's time to take that apart and see if there is thermal paste installed.

Don't mess with the RAID!!! I've done it, and have had some very heart-wrenching moments. Luckily I was able to restore the array - but it's not something that you want to do!!! We'll deal with the drivers for the Intel and Gigabyte/JMicron controllers later.

Did you uninstall the Gigabyte Easy Saver utility? That's important to do because it's known to have issues with Win7.

Have you had any other BSOD's? If so, please zip up and upload the memory dumps (from C:\Windows\Minidump) with your next post.

Piccadillypunte · 23 Feb 2011

Hi usasma

I tried memtest86+ again using the link you gave me. Same result - it goes through the startup stuff and then says Loading ................................

and that is all folks. It just stops there without showing aything else. The later version puts up a menu and then does much the same thing when you take option 2 (multiple processors)

I know it is not much help but that is what happens.

I am catching up on a bit of absolutely necessary work before tackling the heat issues - I'll have to take the system right down for a few hours at least while I check for paste etc.

I'll be back!!!!