Intel DX38BT/DX48BT (Bone Trail)

[GWillakers]

Originally Posted by Sandog

The program works fine at scans <= 1200dpi so the program works. I get a memory error message from the scanner program (writing to high addresses I believe). I am almost positive my memory is functioning correctly.

Getting an error from the program itself is indicative that the program remained in control after it discovered a problem.

An application program would seldom remain in control after a "machine check"
or failure of the intel chip.

Scanning at a higher resolution, would take you down different paths in the program and transfer more data. (possibly buffer overrun)

If you are running with over 3GB you might also be encountering a problem with the way you board layed out the memory. Could be conflicting with that of memory used by other hardware in your system.

It really smells like a problem with software, or a configuration issue.

[Sandog]

It does it with 2GB or 4GB of RAM. I'll add this from Wiki to what ATINUT posted earlier. "Intel errata Ax39, Ax43, Ax65, Ax79, Ax90, Ax99 are said to be particularly serious. 39, 43, 79, which can cause unpredictable behavior or system hang, have been fixed in recent steppings." I do not rule out my X6800 and also I've had this scanner for years. It worked fine before at 4800dpi.

From: Theo de Raadt
Date: 2007-06-27

"Various developers are busy implimenting workarounds for serious bugs
in Intel's Core 2 cpu.

These processors are buggy as hell, and some of these bugs don't just
cause development/debugging problems, but will *ASSUREDLY* be
exploitable from userland code.

As is typical, BIOS vendors will be very late providing workarounds /
fixes for these processors bugs. Some bugs are unfixable and cannot
be worked around. Intel only provides detailed fixes to BIOS vendors
and large operating system groups. Open Source operating systems are
largely left in the cold.

Full (current) errata from Intel:

http://download.intel.com/design/pro...t/31327922.pdf

- We bet there are many more errata not yet announced -- every month
this file gets larger.
- Intel understates the impact of these erraata very significantly.
Almost all operating systems will run into these bugs.
- Basically the MMU simply does not operate as specified/implimented
in previous generations of x86 hardware. It is not just buggy, but
Intel has gone further and defined "new ways to handle page tables"
(see page 58).
- Some of these bugs are along the lines of "buffer overflow"; where
a write-protect or non-execute bit for a page table entry is ignored.
Others are floating point instruction non-coherencies, or memory
corruptions -- outside of the range of permitted writing for the
process -- running common instruction sequences.
- All of this is just unbelievable to many of us."

An easier summary document for some people to read:
http://www.geek.com/images/geeknews/...1_21__full.gif

[traveler]

Is that saying that you can't trust a Core 2 CPU?

[Sandog]

I am not sure the date is right on the quote above. Most of the errata has been know for a while and probably won't effect even most hardcore computer users. The update MS posted was for something to do with mice or keyboards hanging up with Intel C2D I believe and didn't address the errata listed. Not trying to scare C2D users this late in the game but I started fishing for some info. about this when I couldn't find an answer to my problem. I am not worried about my X6800, I am more worried about the Q9540 and the next Intel chipset board I buy.

[Sandog]

Originally Posted by traveler

Is that saying that you can't trust a Core 2 CPU?

LOL, I wish I didn't post it now. It is kinda scary but in reality millions of users aren't having problems otherwise it would be addressed. Like I said, this is sorta old news even though the errata list keeps growing. Intel does a good job at finding these problems while users hardly ever get to see them.

[traveler]

Originally Posted by Sandog

LOL, I wish I didn't post it now. It is kinda scary but in reality millions of users aren't having problems otherwise it would be addressed. Like I said, this is sorta old news even though the errata list keeps growing. Intel does a good job at finding these problems while users hardly ever get to see them.

Oh good.

So when I calculate how far the end of the universe is and pi to the last decimal point, I can be sure it's right then.

[ATINUT]

I haven't run in to any of the bugs as of yet with my Core 2 Duo.

Most users like Sandog, said won't even run in to these bugs.

[traveler]

Originally Posted by ATINUT

I haven't run in to any of the bugs as of yet with my Core 2 Duo.

Most users like Sandog, said won't even run in to these bugs.

The big question I really have with it is the accracy of the results from Folding or SETI.

Perhaps after I get my Core 2 Quad built I'll run Prime95 for twenty-four hours plus and see what happens.

[GWillakers]

Originally Posted by traveler

The big question I really have with it is the accracy of the results from Folding or SETI.

Perhaps after I get my Core 2 Quad built I'll run Prime95 for twenty-four hours plus and see what happens.

I was just gonna post a similar comment....

Oh well with folding... I guess no big loss...

I always figured it for a goverment plot to syphon off spare cpu cycles to
sift through all our e-mail and look for hidden messages in the bit patterns of photographs.

[mastruck]

I just built a new DX38BT system withthe following config:

System assembled:
1) Processor BXS - Intel Core 2 Quad Q / 3Ghz QX9650;
2) Motherboard - BOXDX38BT- Intel S Motherboard;
3) Memory GB - (2) 1GB DDR3 1333 Qmonda;
4) Hard drives - WD 140GB Raptor SATA ;
5) video card: Gigabyte GFX 8500GT+ ;
6) case - Coolermaster Midtower w/550W Power Supply

When I powered it up for the 1st time I get the following message:

"Bios 1.1.0L62";
"Marvel 88SE61xx Adapter";
"Initializing";
"...... "(several minutes);
"Something wrong with adapter!."

Does anyone have any ideas on what might be wrong here?

[oldsarge]

I had the same error. The Marvel controller would not recognize my
Pioneer DVD reader which was IDE. I finally found that it would see
an old IDE Zip drive. I don't have any IDE hard drives to check further.
I just disabled the Marvel in the bios.

[Sandog]

Yes it sounds like a controller setting in BIOS issue. Good luck and congrats on a very nice system.

[oldsarge]

New bios up #1397

[Ford Freak]

I just ordered a dx38bt and retail q6600 from Newegg for $484. I was able to save $25 by getting them at the same time. Now I'm waiting for a particular 2x1gb set of RAM.

[fvbounty]

Originally Posted by Ford Freak

I just ordered a dx38bt and retail q6600 from Newegg for $484. I was able to save $25 by getting them at the same time. Now I'm waiting for a particular 2x1gb set of RAM.

Congratulations, that should be a really nice rig, what ram are you looking at? What video card?