BSOD so now and then since I installed windows 7

[GovtMule]

24 hours non-stop without turning off the computer?
or 24 hours in total everytime I have the computer on?

 

[Dsprague]

either one works its a matter of preference really.

 

[GovtMule]

Today two times my screen froze but no BSOD. Just the whole computer frozen.
I turned off verifier.exe and now I don;t have this problem.

 

[Dsprague]

Verifier will often times cause erratic behavior like that, if you do not get another BSOD with in a week please mark the thread as solved.

 

[GovtMule]

I just got a BSOD again

 

[Dsprague]

Please post a fresh set of the files from the SF Diagnostic tool.

 

[GovtMule]

sorry for late reply,
here it is.

 

[GovtMule]

sorry for late reply,
here it is.

Are you still working on my problem.
Today I had BSOD again

 

[Dsprague]

I'm sorry not sure how I missed your last update, but looking back at all the things you have tried I only have a few more things left that I can think of to have you try so:

Please run the System file checker the check for any system file corruption:

SFC.EXE /SCANNOW
Go to Start and type in "cmd.exe" (without the quotes)
At the top of the search box, right click on the cmd.exe and select "Run as adminstrator"
In the black window that opens, type "SFC.EXE /SCANNOW" (without the quotes) and press Enter.
If the command finishes with anything other than "no integrity violations found" run the command three more times.
If after the third run there are still problems please run the command at boot: http://www.sevenforums.com/tutorials/139810-sfc-scannow-run-command-prompt-boot.html

 

[GovtMule]

sorry for late reply.

No violations found the first round, so I don;t need to do it anymore,do I?

Do you have anymore ideas?

it was quiet a while but lately I get those BSOD's again, today also one.

 

[Dsprague]

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.

 

[Arc]

*******************************************************************************
*                                                                             *
*                        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) [COLOR=Red]A driver has inadvertently or deliberately modified critical kernel code
 or data.[/COLOR] 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) [COLOR=Red]A hardware corruption occurred, e.g. failing RAM holding kernel code or data.[/COLOR]

Test your RAM modules for possible errors.
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

 

[x BlueRobot]

[COLOR="Red"]BugCheck 109[/COLOR], {a3a039d8976ad4fc, b3b7465ee9e7a452, fffff80002d1dce0, [COLOR="Blue"]1[/COLOR]}

Probably caused by : ntkrnlmp.exe ( nt!CmpSyncKeyValues+0 )

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.

Usual causes:  Device driver, Breakpoint set with no debugger attached, Hardware (Memory in particular)

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.

Your Realtek network adapter driver seems to be outdated, I would suggest updating this driver from here - Realtek

2: kd> [COLOR="SeaGreen"]lmvm Rt64win7[/COLOR]
start             end                 module name
fffff880`042f7000 fffff880`0437c000   Rt64win7   (deferred)             
    Image path: \SystemRoot\system32\DRIVERS\Rt64win7.sys
    Image name: Rt64win7.sys
    Timestamp:       [COLOR="Red"] Fri Jun 10 07:33:15 2011 [/COLOR](4DF1BAAB)
    CheckSum:         0008B67F
    ImageSize:        00085000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

 

[GovtMule]

*******************************************************************************
*                                                                             *
*                        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) [COLOR=Red]A driver has inadvertently or deliberately modified critical kernel code
 or data.[/COLOR] 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) [COLOR=Red]A hardware corruption occurred, e.g. failing RAM holding kernel code or data.[/COLOR]

Test your RAM modules for possible errors.
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

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.

[COLOR="Red"]BugCheck 109[/COLOR], {a3a039d8976ad4fc, b3b7465ee9e7a452, fffff80002d1dce0, [COLOR="Blue"]1[/COLOR]}

Probably caused by : ntkrnlmp.exe ( nt!CmpSyncKeyValues+0 )

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.

So what can we do with this knowledge?
Or is it hard to pinpoint anything?

Usual causes:  Device driver, Breakpoint set with no debugger attached, Hardware (Memory in particular)

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.

Your Realtek network adapter driver seems to be outdated, I would suggest updating this driver from here - Realtek

2: kd> [COLOR="SeaGreen"]lmvm Rt64win7[/COLOR]
start             end                 module name
fffff880`042f7000 fffff880`0437c000   Rt64win7   (deferred)             
    Image path: \SystemRoot\system32\DRIVERS\Rt64win7.sys
    Image name: Rt64win7.sys
    Timestamp:       [COLOR="Red"] Fri Jun 10 07:33:15 2011 [/COLOR](4DF1BAAB)
    CheckSum:         0008B67F
    ImageSize:        00085000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Openoffice is not BSOD related.
But the outdated realtek drivers, could they be BSOD related?

Anyway I will update the realtek drivers tonight.

 

[GovtMule]

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.

 

[Arc]

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 http://www.sevenforums.com/tutorials/9733-screenshots-files-upload-post-seven-forums.html .

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.

 

[x BlueRobot]

Openoffice is not BSOD related.
But the outdated realtek drivers, could they be BSOD related?

Anyway I will update the realtek drivers tonight.

I know it's not related to the BSODs, it was just a suggestion, since LibreOffice and OpenOffice are even developed by the same company I believe, it's just LibreOffice will have updates released to extend features and fix any bugs.

 

[Arc]

LibreOffice and OpenOffice are even developed by the same company I believe, ......

LibreOffice is a free and open source office suit, developed by The Document Foundation. It was forked from OpenOffice.org in 2010.

Source: LibreOffice.

 

[GovtMule]

snap shot included.

by the way, speedfan gives AUX as 92 Celsius , that cannot be normal, can it?

 

[x BlueRobot]

Your CPU seems a little warm, especially for a desktop, when did you take the screenshot? Idle or under load?