Windows 10: Tracing BugCheck 0x00000109

I brought a computer home that I had used at work for the last 4 years without any issue whatsoever. It is a custom built machine operating on a Intel Corporation DQ57TM LGA1156 motherboard with a Intel Core i5 660 @ 3.33GHz. Since using it at home with a different system drive it has begun experiencing daily BSOD crashes. I have reinstalled the Win 10 OS multiple times on the same and different hard drives, so I don't think it is a system issue. I have tried different combinations of RAM cards and they do not appear to be the source of the problem either. Each instance seems to involve the following cascade of errors as gleaned from the Event Log. I should add this ordered list is based on the time stamp from the log. I probably should not assume this means this is the actual order in which the events occurred. From first entry to the last :


1. Kernel-Power Event ID 41 "The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly."


2. Kernel-Processor-Power Event ID 34 "Idle power management features on processor 0 in group 0 are disabled due to a firmware problem. Check with the computer manufacturer for updated firmware."


3. Event Log Event ID 6008 - citing some prior timestamp of an unexpected shutdown that does NOT appear in the Event Log itself "The previous system shutdown at xx:xx:xx PM on ‎xx/xx/xxxx was unexpected."


4. WLAN-AutoConfig "WLAN Extensibility Module has failed to start."


So, should I be looking at the first two events Processor/power issues as the root cause of the issue and assuming that the WLAN error is a symptom of the processor issue or should I be targeting the Wifi device and/or its driver as the main cause of my crashes? My hunch is that the latter fails and reports due to the former. What would be the most likely sources of this novel issue, again, after so many years of using this computer without having it occur?


Thanks,


-Steve

:)

 

Critical_structure_corruption. The computer has rebooted from a bugcheck. The bugcheck was: 0x00000109.

I have recently seen crashing of my Windows 10 recently. In the event viewer. I see this error which is The computer has rebooted from a bugcheck. The bugcheck was: 0x00000109
(0xa39fffe32a28b7fd, 0xb3b70c697caa8e6f, 0xffffc08a88bfda20, 0x000000000000001c).

This error causes a reboot of my computer and a blue screen. Can anyone kindly help me on this? Thanks

 

The computer has rebooted from a bugcheck. The bugcheck was: 0x00000109

Hello I just experienced a BSOD and am not sure why this has happened .This PC is newly built at 2 months old and the only thing I was doing during the time was starting it up after it was in sleep mode for 2-3 hours and browsing twitter. There have not
been any hardware changes except the installation of a new front fan, an moving my GPU from one PCI-E slot to another. Below is the bug check message and the Skydrive link to the Memory Dump. Any help and suggestions on why this occurred would be appreciated.

SkyDrive Link: MEMORY.DMP

The computer has rebooted from a bugcheck. The bugcheck was: 0x00000109 (0xa3a004e7f2a8d629, 0xb3b7116e452713d4, 0xfffff803819000a8, 0x0000000000000001). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: c155e36a-4341-47d0-87db-15e4b2cd1f98.

 

Critical_structure_corruption. The computer has rebooted from a bugcheck. The bugcheck was: 0x00000109.

Hi,

The error code 0x00000109 can be due to data corruption on your device. To better understand your concern, we'd like to know the following:

• The last known changes made/activities performed on your device prior to your concern.
• The version and build of Windows 10 that you're using on your device. To check this, you can perform the steps posted on this
  
  link.

In addition, we'd like to request for a minidump (DMP) file for us to have a look on what causes the issue. To know about the process of finding and uploading DMP files, we'd recommend checking the

post of ZigZag3143 (MS -MVP). You can refer to the screenshot below to easily locate it on the post.





In the meantime, we'd recommend performing the steps posted on this
link to troubleshoot blue screen errors on your device.

Note: ZigZag3143 (MS -MVP)'s post also includes other tips/recommendation on how to fix blue screen errors.

We look forward to your response.