New
#31
I am unfortunately out of Ideas, but I will see if I can get others to take a look at this thread and possibly provide further help.
I am unfortunately out of Ideas, but I will see if I can get others to take a look at this thread and possibly provide further help.
Test your RAM modules for possible errors.Code:******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* CRITICAL_STRUCTURE_CORRUPTION (109) This bugcheck is generated when the kernel detects that critical kernel code or data have been corrupted. There are generally three causes for a corruption: 1) A driver has inadvertently or deliberately modified critical kernel code or data. See http://www.microsoft.com/whdc/driver/kernel/64bitPatching.mspx 2) A developer attempted to set a normal kernel breakpoint using a kernel debugger that was not attached when the system was booted. Normal breakpoints, "bp", can only be set if the debugger is attached at boot time. Hardware breakpoints, "ba", can be set at any time. 3) A hardware corruption occurred, e.g. failing RAM holding kernel code or data.
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 passes, preferably overnight.
Stress test the CPU.
Hardware - Stress Test With Prime95
The bugcheck indicates that a certain function or .pdata data structure has been corrupted or modified, the first point is the most likely since the .pdata data structure seems to be only present in CE versions of Windows. The data structure is used for exception handling.Code:BugCheck 109, {a3a039d8976ad4fc, b3b7465ee9e7a452, fffff80002d1dce0, 1} Probably caused by : ntkrnlmp.exe ( nt!CmpSyncKeyValues+0 )
Just a suggestion -this is not related to BSODs- but the OpenOffice program is a discontinued product and not receiving any more updates, instead support has been shifted to a very similar program called LibreOffice.Code:Usual causes: Device driver, Breakpoint set with no debugger attached, Hardware (Memory in particular)
Your Realtek network adapter driver seems to be outdated, I would suggest updating this driver from here - Realtek
Code:2: kd> lmvm Rt64win7 start end module name fffff880`042f7000 fffff880`0437c000 Rt64win7 (deferred) Image path: \SystemRoot\system32\DRIVERS\Rt64win7.sys Image name: Rt64win7.sys Timestamp: Fri Jun 10 07:33:15 2011 (4DF1BAAB) CheckSum: 0008B67F ImageSize: 00085000 Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
I have done memtest march 27th with 14 passes, no errors found.
Should I do it again, I had these BSOD problems already way before march 27th.
I'll do the Stress Test tonight.
So what can we do with this knowledge?
Or is it hard to pinpoint anything?
Openoffice is not BSOD related.
But the outdated realtek drivers, could they be BSOD related?
Anyway I will update the realtek drivers tonight.
hmm, So I downloaded speedfan, and already I see flames at both CPU's and at AUX.
I guess its already hot, even before the stress test, now I don't dare to do the stress test.
Or is my fear unwarrented?
Can I do the stress test?
Also speedfan in the little box with text had a warning and Bad Attributes Checksum and Bad Treshold Checksum. Is this any useful information.
Hope to hear from you, and if stress test is safe when I already see flames in speedfan, I'll do stresstest tomorrow.
As you notice that it is already hot, postpone stress testing. First Upload a snapshot Using Speccy.
- Download and install Speccy.
- File> Save snapshot.
- Save it on desktop.
- Zip it and upload it following following Screenshots and Files - Upload and Post in Seven Forums .
If we still suggest for a stress test, go for it. Otherwise dont do it.
If you think that the heat is really high (you havent given any hint .... which is not being very informative and helpful) ....dismantle the computer. Clean the inside very carefully. Clean all the air vents, clean the fan grills so that it can blow the hot air out easily.
While re-seating, apply new thermal paste to the CPU.
When done, let us see another Speccy screenshot, so that we can compare the heat difference and judge it properly accordingly.
snap shot included.
by the way, speedfan gives AUX as 92 Celsius , that cannot be normal, can it?
Your CPU seems a little warm, especially for a desktop, when did you take the screenshot? Idle or under load?