BSOD Error i need help

[johnyuntenohne]

Hello from Germany, I get BSOD at random intervals.

I do not know at what's wrong.

I have run Memtest and the result was: Error 0

Just look at the screenshots.

thx

 

[Arc]

Hi johnyuntenohne.

Click on the button below ....



It will download the DM log collector. Right click on the application and run as administrator. It will generate a .zip file on your desktop. Upload the .zip.
http://www.sevenforums.com/tutorials/9733-screenshots-files-upload-post-seven-forums.html

 

[johnyuntenohne]

there

 

[Arc]

[COLOR=Red]BugCheck 109[/COLOR], {a3a039d89bcc57bd, b3b7465eee4a92c7, fffff880009f6540, 3}

Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )

Followup: MachineOwner
---------

CRITICAL_STRUCTURE_CORRUPTION (109)
This bugcheck is generated when the kernel detects that critical kernel code ordata 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 Kernel patch protection for x64-based operating systems
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.

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.

If it start showing errors/red lines, stop testing. A single error is enough to determine that something is going bad there.

If there is no error, enable Driver Verifier to monitor the drivers.
Driver Verifier - Enable and Disable
Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

   Information

Why Driver Verifier:
It puts a stress on the drivers, ans so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.

How Can we know that DV is enabled:
It will make the system bit of slow, laggy.

   Warning

Before enabling DV, make it sure that you have earlier System restore points made in your computer. You can check it easily by using CCleaner looking at Tools > System Restore.

If there is no points, make a System Restore Point manually before enabling DV.

   Tip

• If you fail to get on the Desktop because of DV, Boot into Advanced Boot Options > Safe mode. Disable DV there. Now boot normally again, and try following the instruction of enabling DV again.
• If you cannot boot in Safe mode too, do a System Restore to a point you made earlier.

Let us know the results, with the subsequent crash dumps, if any.

 

[johnyuntenohne]

Memtest no errors...

I start driver verifier 24h but no bsod...

It seems that only when I Flash player or Java are started bsod happened.

Flash Player often crashes. I also, as I said, several times formatted, and after the reformat crashes Flash Player still on.

 

[Arc]

We need to data as per the BSOD posting instructions; as stated in post #2.

 

[johnyuntenohne]

I have already inserted in the Third Post

 

[johnyuntenohne]

There is the new

 

[Arc]

I have already inserted in the Third Post

Everytime you report a BSOD, it should be there.

And it is not DV enabled.

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

For a verifier enabled BSOD, the DEFAULT_BUCKET_ID read as VERIFIER_ENABLED_VISTA_MINIDUMP.

Run verifier /query in a command prompt to identify if verifier is really working in the background or not.