UNEXPECTED_KERNEL_MODE_TRAP (7f) BugCheck 7F, {8, f8a07d70, 0, 0}

Rockster, thanks for helping us out!

Jose, I downloaded the BIOS utility and the chipset software for your motherboard via both the English and Spanish pages at Intel that I linked above. It appears the files are identical. Therefore, I expect it does not matter which language you choose for obtaining updates for your motherboard.

If you choose to update your BIOS, chipset drivers, etc., then I suggest you carefully read the documentation on those web pages and included with the downloads before proceeding. If you have any questions or concerns, please feel free to ask for assistance here.


I still suggest you check for viruses and other malware first via the links I provided earlier and then let please us know the results. (Your persistent QuickTime/iTunes issue is very puzzling to me and I wonder if malware is somehow involved.)

We're looking forward to hearing from you.


Thanks again, Rockster!

 

Kernel Stack overflow and not hardware problem

From your debug report, your stack limit is ec76d000 and register esp is also the same value. The root cause is stack overflow. There has only one entry in the stack trace and I have no idea who uses the stack. Anyway it is no harm to extend the size of the stack. It may solve the problem.

Refer the following article to extend the size of kernel stack
http://support.microsoft.com/?kbid=822789
http://service1.symantec.com/SUPPOR...10eaa5fc1148e6f888256bf40056e227?OpenDocument

 

I am not en expert in BOSD dump analysis. However, cpc2004 apparently is an expert. Therefore, I am attempting to learn from cpc2004's feedback (and help xabraxasx at the same time).

xabraxasx, if you use the DebugWiz tool available here at Windows BBS, that will also generate a module list that I am guessing will help us identify which module was using the stack. Canned instructions about this are here.

We used to have an expert here (JoeHobart, last posted here in Feb. 2006) who apparently required DebugWiz-generated dump lugs to provide the additional details necessary to help pinpoint causes of BSODs. I'm guessing those additional details would be helpful for cpc2004.

I suggest you use DebugWiz for any more dump logs you post.

==========

Since the focus of your issue has returned to your dump log, I am including your dump log below so we can more easily see what cpc2004 is referring to (without having to keep scrolling back and forth between this part of the discussion and the beginning of your thread).

Note: I hope nobody minds I selfishly bolded, underlined, and colored portions of your dump log that I think might be relevant in my very inexperienced pursuit of understanding dump logs.