Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.

Windows 7: It bsod'ed again after serveral weeks of woring fine

21 Oct 2010   #11

Windows Home Premium 64bit


Below you can find the report on my second BSOD last night, of which I spoke earlier.

This BSOD didn't happen on start up but when the computer was idling.
Verifier was enabled at the time.

Maybe it helps to diagnose the problem.
I m pretty sure its not the PSU giving me BSOD.

Thanks in advance

My System SpecsSystem Spec
21 Oct 2010   #12

Windows 7 Ultimate 32 bit

You can turn off Driver Verifier. It is not pointing to drivers; but the two BSOD's it has generated are pointing to system drivers and hardware. We will see how your system does with Driver Verifier turned off. The latest dump is inconclusive.
Error code 109, CRITICAL_STRUCTURE_CORRUPTION. Usual causes: Device driver, Breakpoint set with no debugger attached, Hardware (Memory in particular)

There are generally three different causes for this bug check:
  • A driver has inadvertently, or deliberately, modified critical kernel code or data. Microsoft Windows Server 2003 with Service Pack 1 (SP1) and later versions of Windows for x64-based computers do not allow the kernel to be patched except through authorized Microsoft-originated hot patches. For more information, see Patching Policy for x64-based Systems.
  • A developer attempted to set a normal kernel breakpoint using a kernel debugger that was not attached when the system was started. Normal breakpoints (bp) can only be set if the debugger is attached at start time. Processor breakpoints (ba) can be set at any time.
  • A hardware corruption occurred. For example, the kernel code or data could have been stored in memory that failed.

Windows 7 Kernel Version 7600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.20738.amd64fre.win7_ldr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02c0c000 PsLoadedModuleList = 0xfffff800`02e40eb0
Debug session time: Wed Oct 20 14:01:52.881 2010 (GMT-4)
System Uptime: 0 days 0:24:08.051
Loading Kernel Symbols
Loading User Symbols
Loading unloaded module list
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *

Use !analyze -v to get detailed debugging information.

BugCheck 109, {a3a039d898b675c5, 0, 38df6ea820c39d95, 101}

Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )

Followup: MachineOwner

4: kd> !analyze -v
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *

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 Patching Policy for x64-Based Systems: Information for Driver Developers
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.
Arg1: a3a039d898b675c5, Reserved
Arg2: 0000000000000000, Reserved
Arg3: 38df6ea820c39d95, Failure type dependent information
Arg4: 0000000000000101, Type of corrupted region, can be
    0 : A generic data region
    1 : Modification of a function or .pdata
    2 : A processor IDT
    3 : A processor GDT
    4 : Type 1 process list corruption
    5 : Type 2 process list corruption
    6 : Debug routine modification
    7 : Critical MSR modification

Debugging Details:






LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff80002c72580

fffff880`033625d8 00000000`00000000 : 00000000`00000109 a3a039d8`98b675c5 00000000`00000000 38df6ea8`20c39d95 : nt!KeBugCheckEx



FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: Unknown_Module

IMAGE_NAME:  Unknown_Image



Followup: MachineOwner

Obviously, the dump points to hardware. I suggest you test your CPU and RAM with Prime. Read and follow the instructions in this tutorial:

Run 3 separate tests, one on each of the setting (Blend, Small FFTs, Large FFTs). Post back with the results.
My System SpecsSystem Spec

 It bsod'ed again after serveral weeks of woring fine

Thread Tools

Similar help and support threads
Thread Forum
BSOD playing serveral games, error 0x0000124
I have a Custom builded PC, I builded it myself and actually had this problem before. I am getting this BSOD 0x0000124 and caused by ntoskrnl.exe. My build should be able to see at my profile and I have tried alot of stuff but I would be very happy and very thankful if you could help me fix this,...
BSOD Help and Support
0x80072ee2 for weeks on some PCs while others on same network are fine
Hi, I am having problems with Windows Update on some, but not all, of the computers on my home network. All are running Windows 7 (combination of Home Premium and Ultimate). Two of the PC's have not been able connect to Windows Update since the start of July. Both are connected to the...
Windows Updates & Activation
BSOD serveral times a day, error 0x0000001e
reinstalled windows7 didn't work here's the dump file thx!
BSOD Help and Support
Two BSOD's in 2 weeks
Hi , I wasn't doing anything in particular during the crash. My first crash was on Jan 4 and earlier today (i.e-Jan 10) was the second time. The only new installation I can think of was an upgrade to Firefox 9.0.1 and Skype facebook Beta. Systems info Current: Windows 7 Pro x64 full retail...
BSOD Help and Support
installs fine, runs fine, reboots..not fine
hey guys so i finally decided to install win7 x86 - everything went well - put all the standard stuff on there etc - i rebooted many times because of installations and updates on my last reboot it just got stock in the bios screen (verifying dmi pool data..success! etc) so i rebooted, same...
Installation & Setup

Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 17:12.
Twitter Facebook Google+ Seven Forums iOS App Seven Forums Android App