BSOD code 0x109

redsiamesecat

Member
Joined
Jun 28, 2013
Posts
20
hello i hv problem with BSOD code 0x109..
my laptop is asus n46vz , win 7 ultimate 64 bit
when i bought this laptop from my friend, it works just fine...
but after i bought it,i use ssd so i reinstall the OS on ssd , its win 7 ulti 64 bit too...
but a problem occured when i playing bluestack ( android emulator), it makes my laptop BSOD... at random times
i think its bcus i hv failed update the important file on windows update ( already posted it on windows update section)
please check it, i've attached the info..
thx b4 :)

 
Hi,

All of the attached dumps are of the CRITICAL_STRUCTURE_CORRUPTION (109) bugcheck. This bugcheck is generated when the kernel detects that critical kernel code or data have been corrupted.

Update the following driver -
Code:
ewusbmdm    fffff880`0a7b1000    fffff880`0a7cc780    Tue Jul 31 03:48:10 2007 (46aee93a)    000293c0        ewusbmdm.sys

^
Huawei DataCard USB PN driver

Welcome to login Huawei website

If you cannot find an update for this software, remove the device in question that is using this driver for temporary troubleshooting purposes.

Also, something to note from the perfmon report - 'One or more services has failed. The service did not stop gracefully, suggesting the service may have crashed or one of its components stopped in an unsupported way.'

The service in question was ATKGFNEX from Lenovo. The ATKGFNEX service controls the hot keys (FN, volume, etc). I would recommend DISABLING this service:

Start > services.msc > Find ATKGFNEX and select right click > Properties. After that, stop the service, and then next to startup type, click on the dropdown menu and select 'Disable'.. click Apply. You may need to restart.

Also~ 'The Security Center reports that Windows Update is disabled' - Why is this? Enable Windows Updates again.

If updating / removing the device loading this driver does not help, and disabling the service does not help, enable Driver Verifier to see if we can catch a device driver causing issues:

Driver Verifier:
What is Driver Verifier?
Driver Verifier is included in Windows 7, Windows Server 2008 R2, Windows Vista, Windows Server 2008, Windows 2000, Windows XP, and Windows Server 2003 to promote stability and reliability; you can use this tool to troubleshoot driver issues. Windows kernel-mode components can cause system corruption or system failures as a result of an improperly written driver, such as an earlier version of a Windows Driver Model (WDM) driver.
Essentially, if there's a 3rd party driver believed to be at issue, enabling Driver Verifier will help flush out the rogue driver by flagging it and causing your system to BSOD.
Before enabling Driver Verifier, it is recommended to create a System Restore Point:
Vista - START | type rstrui - create a restore point
Windows 7 - START | type create | select "Create a Restore Point"
How to enable Driver Verifier:
Start > type "verifier" without the quotes > Select the following options -
1. Select - "Create custom settings (for code developers)"
2. Select - "Select individual settings from a full list"
3. Check the following boxes -
- Special Pool
- Pool Tracking
- Force IRQL Checking
- Deadlock Detection
- Security Checks (Windows 7)
- Concurrentcy Stress Test (Windows 8)
- DDI compliance checking (Windows 8)
- Miscellaneous Checks
4. Select - "Select driver names from a list"
5. Click on the "Provider" tab. This will sort all of the drivers by the provider.
6. Check EVERY box that is NOT provided by Microsoft / Microsoft Corporation.
7. Click on Finish.
8. Restart.
Important information regarding Driver Verifier:
- If Driver Verifier finds a violation, the system will BSOD.
- After enabling Driver Verifier and restarting the system, depending on the culprit, if for example the driver is on start-up, you may not be able to get back into normal Windows because Driver Verifier will flag it, and as stated above, that will cause / force a BSOD.
If this happens, do not panic, do the following:
- Boot into Safe Mode by repeatedly tapping the F8 key during boot-up.
- Once in Safe Mode - Start > type "system restore" without the quotes.
- Choose the restore point you created earlier.
If you did not set up a restore point, do not worry, you can still disable Driver Verifier to get back into normal Windows:
- Start > Search > type "cmd" without the quotes.
- To turn off Driver Verifier, type in cmd "verifier /reset" without the quotes.
- Restart and boot into normal Windows.
How long should I keep Driver Verifier enabled for?
It varies, many experts and analysts have different recommendations. Personally, I recommend keeping it enabled for at least 36-48 hours. If you don't BSOD by then, disable Driver Verifier.
My system BSOD'd, where can I find the crash dumps?
They will be located in C:\Windows\Minidump
Any other questions can most likely be answered by this article:
Using Driver Verifier to identify issues with Windows drivers for advanced users


Regards,

Patrick
 
Last edited:
Hi,

All of the attached dumps are of the CRITICAL_STRUCTURE_CORRUPTION (109) bugcheck. This bugcheck is generated when the kernel detects that critical kernel code or data have been corrupted.

Update the following driver -
Code:
ewusbmdm    fffff880`0a7b1000    fffff880`0a7cc780    Tue Jul 31 03:48:10 2007 (46aee93a)    000293c0        ewusbmdm.sys

^
Huawei DataCard USB PN driver

Welcome to login Huawei website

If you cannot find an update for this software, remove the device in question that is using this driver for temporary troubleshooting purposes.

Also, something to note from the perfmon report - 'One or more services has failed. The service did not stop gracefully, suggesting the service may have crashed or one of its components stopped in an unsupported way.'

The service in question was ATKGFNEX from Lenovo. The ATKGFNEX service controls the hot keys (FN, volume, etc). I would recommend DISABLING this service:

Start > services.msc > Find ATKGFNEX and select right click > Properties. After that, stop the service, and then next to startup type, click on the dropdown menu and select 'Disable'.. click Apply. You may need to restart.

If updating / removing the device loading this driver does not help, and disabling the service does not help, enable Driver Verifier to see if we can catch a device driver causing issues:

Driver Verifier:

Regards,

Patrick

thx for the fast response..
i think its not related to my modem huawei..
bcuz when it started to bsod, i didnt use modem at all...
but now i use modem for my internet..

i think ill check using driver verifier..
thx for answer...
 
The driver is loaded though, and it's out of date (from 2007). Make sure you also disable the service.

Off to bed, will check thread when I wake up.

Regards,

Patrick
 
Also, something to note from the perfmon report - 'One or more services has failed. The service did not stop gracefully, suggesting the service may have crashed or one of its components stopped in an unsupported way.'

The service in question was ATKGFNEX from Lenovo. The ATKGFNEX service controls the hot keys (FN, volume, etc). I would recommend DISABLING this service:

Start > services.msc > Find ATKGFNEX and select right click > Properties. After that, stop the service, and then next to startup type, click on the dropdown menu and select 'Disable'.. click Apply. You may need to restart.

Also~ 'The Security Center reports that Windows Update is disabled' - Why is this? Enable Windows Updates again.



oh yes, oh why i hv lenovo service on my asus laptop ???
and about windows update, actually i hv problem too...
and i hv make a thread on windows update section too...
if u want to read it , its here
thx
 
oh did i cant edit my post? i want to update the curent situation..
oh well, ill post it here..

ok, i already enable the driver verifier...
next, i restarted then, when i want to post that i already enable the driver verifier...
but when i open google chrome i get BSOD code 0x0c4...
but im not too sure, so i restarted again, but i got the BSOD again when open google chrome...
so i disable the driver verifier, to posting ...
ive attached the minidump of the bsod..
thx
 

Attachments

Hi,

The verifier enabled dump is failing to flag a device driver, however, the process fault is ekrn.exe. Usually process faults don't mean much as it's essentially just the process that crashed at the time of the system blue screening, however, ekrn.exe is ESET'S NOD32, the anti virus. I am going to temporarily recommend uninstalling NOD32 for troubleshooting purposes and replacing it with Microsoft Security Essentials to ensure there is not an issue being cause here by it conflicting:

How do I manually uninstall my Windows ESET product? - ESET Knowledgebase

Regards,

Patrick
 
Hi -

Thanks for running the WMI app. It shows a 1 GB page file on drive N: + peak virtual memory usage at 188 MB:
Read More:

Your OS drive is c: and you have 4 GB physical RAM. If page file setting was the default "system managed", one approximately 4.3 GB would be created on OS drive c:

Your OS drive is listed as PLEXTOR PX-128M5S SSD. Check manufacturer's support site for firmware upgrade -

http://www.plextoramericas.com/index.php/ssd/px-m5s-series

One entry related to memory depletion was found in the Application Event Viewer log related to Bluetooth & .NET -
Read More:


The System Event log recorded ~275 entries citing exhaustion of virtual memory:
Code:
Event[16998]:
  Log Name: System
  Source: Microsoft-Windows-Resource-Exhaustion-Detector
  Date: 2013-05-28T12:32:47.081
  Event ID: 2004
  Task: Resource Exhaustion Diagnosis Events
  Level: Warning
  Opcode: Contains the results of the diagnosis.
  Keyword: [color=red]Events related to exhaustion of system commit limit (virtual memory)[/COLOR].

Windows successfully diagnosed a low virtual memory condition. 
The following programs consumed the most virtual memory: 
[B]DragonNest.exe[/B] (4808) consumed 1299816448 bytes, 
[B]BtTray.exe[/B] (2672) consumed 125992960 bytes, and 
[B]ekrn.exe[/B] (2140) consumed 98037760 bytes.

These are the top offenders (consumers of virtual memory) - the top 3 were listed with each event recorded:
  • HD-Frontend.exe - 277 MB
  • chrome.exe - 137 MB
  • ekrn.exe - 124 MB
  • DragonNest.exe - 1.3 GB
  • BtTray.exe - Bluetooth - 126 MB
  • ekrn.exe - ESET kernel - 98 MB
  • SO3D.exe - 789 MB
  • HD-Frontend.exe - 190 MB
  • chrome.exe - 175 MB


The Event Viewer mentioned "...exhaustion of system commit limit..". Here is an explanation by Bruce Sanderson -

Memory, Committed Bytes - this is a measure of the demand for virtual memory

This counter shows how many bytes have been allocated by processes and to which the operating system has committed a RAM page frame or a page slot in the pagefile (perhaps both). As Committed Bytes grows above the amount of available RAM, paging will increase and the amount of the pagefile in use will also increase. At some point, paging activity will start to significantly impact perceived performance.
Bruce Sanderson's general Windows information: RAM, virtual memory, pagefile, and all that stuff

Included in: http://support.microsoft.com/kb/2160852

From my Windows 8 x64 system w/ 4 GB RAM

Commit limit is 8.3 GB per 1st screenshot (SysInternals Process Explorer) with current usage = 2.6 GB; the 2nd screenshot is of RESMON (Windows Resource Monitor) and shows commit limits by process -

ProcExp_SystemInfo.PNG

Resmon_07-06-2013.PNG


It is likely that the 1,000 MB page file was too small for your system needs.

I suggest that you reset page file settings - select "automatically manage page file for all drives. . ." and see if memory exhaustion issues continue.

Regards. . .

jcgriff2


EDIT:


For info, processes - physical memory usage:
Read More:


EDIT #2 - reference thread - https://www.sysnative.com/forums/wi...er-resetting-blue-screen-death.html#post49715
 
Last edited:
thx for the answer patrick n jcgriff2

so, the cause of my BSOD is bcuz i set my virtual memory to only 1GB ...
and the fact is my laptop needs much more virtual memory than 1GB ?
i'll try ur suggestion to automatically manage the virtual memory.. hope it wont make my laptop BSOD again
thx..
 
err sorry, i want to edit my post above ^

thx for the answer patrick n jcgriff2

i've already updated my SSD firmare to the up2date firmware when i first using it...
oh yeah i forgot tell it here,that time the virtual memory low happens all the time when i didnt set my paging file ( zero virtual memory) but then i raised it to 1GB , and it seems it decreased the virtual memory low problem...
and now my memory still 1GB.and the issues of virtual memory low was long gone when i set it to 1GB (except when i multitasking greatly, like open game music browser dll, but i rarely do that, thats why i just making it to 1GB)
but i still get BSOD randomly whenever i playing bluestack (HD-Frontend.exe), and i see on ur post above that HD-Frontend.exe used 200++ MB memory...
but when i play other games like dragonnest.exe (1.3GB memory) or SO3D.exe (700+MB memory) the BSOD doesnt happen at all...
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top