BSOD - nothing at MS knowledge base

Dell Dimension 8250 - WinXP Pro SP2 repair install - AGP video - RDRAM

Windows installed OK right up until the desktop is supposed to show up. It goes to the blue Welcome screen, then the screen right after that, then it goes to a BSOD "A driver has overrun a stack-based buffer. This overrun could potentially allow a malicious user to gain control of this machine." The error code is 0x000000F7. And then it counts down a dump of physical memory. There's nothing at the knowledge base for that error code, and only 3 hits for the 'overrun' error message: one for Win2003, Win2000, and OS2(???). I've swapped video cards but I'm unable to swap RAM because it's the very rare and even more costly RDRAM (aka RIMM or RAMBUS). I did run 5 passes of a memory diagnostic and it passed 100%. I'm running a hard drive test right now, so far so good.
Any help, ideas, links, or suggestions will be greatly appreciated.

Thanks :major

BTW- I didn't know if this should go in the hardware forum, the driver forum, or here in the software forum. I figured I'd get the most exposure here

 

found the cause was that Windows was installed on a slave drive....

0x000000F5:
0x000000F6: PCI_VERIFIER_DETECTED_VIOLATION
0x000000F7: DRIVER_OVERRAN_STACK_BUFFER <------ your error...
0x000000F8: RAMDISK_BOOT_INITIALIZATION_FAILED
0x000000F9: DRIVER_RETURNED_STATUS_REPARSE_FOR_VOLUME_OPEN
0x000000FA:
0x000000FB:

 

:confused How'd you figure that out??? And the BIOS shows the drive as being IDE0 Master. But I will check the jumpers on the drive and replace the cable after the drive diagnostic finishes.

 

Drive diagnostic passed 100%. Jumper was set to cable select; I changed it to Master. Removed the old cable; installed a brand new 80-strand IDE cable. It made no difference.

 

I'm no finding anything helpful. Amazingly most F7 errors apply to ovens!

 

You might wanna take a look at this http://forums.majorgeeks.com/showthread.php?t=35246

Might help ya out, good luck!

 

Thanks. That was my next step....

If anyone else has anything (and I mean ANYTHING) that might be helpful, please post!

 

Debug it..pray it throws ya a bone.

Not all stop errors are well documented by MS, unfortunately. I had a nifty one caused by Panda Antivirus, and the stop error code was a bunch of random numbers. Only debugging found the culprit.

 

I don't mean to hijack this thread, but is this path in the document still correct:
SRV*c:\symbols*http://msdl.microsoft.com/download/symbols

If you just try to open the link you get:
"The data you requested cannot be retrieved."

I'm assuming you have to go get the symbol package for your OS from here:
http://www.microsoft.com/whdc/devtools/debugging/symbolpkg.mspx

Then after you install the symbols you use the path to where they were installed. o

 

That is the correct path still, yes. Its not meant to be browseable via browser. The debugger is intelligent enough to determine what symbols you need, according to the OS being used, and what OS the memory dump is from.


Microsoft® Symbol Server

Welcome to the Microsoft Symbol Server. This site is provided by Microsoft to enhance debugging by automatically retrieving symbols for various Microsoft products during a debugging session.

The data at this site is not browseable. Instead, it is accessed by the debuggers that ship with Debugging Tools for Windows .
For more information about how to use the Microsoft Symbol Server click here .