Thursday, August 25, 2016

Fast Solution to Error: BSOD Bug Check Code 0x00000109 Issue

BSOD Bug Check Code 0x00000109 Issue

I recently bought a completely new PC which I put together myself.
 This BSOD issue has been happening since I put this build together, at intervals of about 3-4 hours.

My hardware components are:

i5 2500k 3.3ghz
8gb Corsair DDR3 1333mhz
Nvidia GTX460
Gigabyte GA-Z68A-D3-B3
2 x 1tb Samsung Spinpoint F3s (not in RAID)

I've exhausted all the usual steps I find myself taking in these situations.
 So far i've run memtest to 800% on all my memory (no errors), re-downloaded and re-installed all my drivers, completely dis-assembled my build and methodically checked connections
for dust / anything else.
 When this final step didn't solve it, I re-installed windows on my second hard-drive and the issue occurred again just a few minutes ago after restarting.

I tested my hardware in my mates PC and it all works fine.
 Each time we left his machine running for 12 hours (most of my BSODs occurred whilst idling) and nothing happened.
 Also after reading a few of the other posts on here related to a Daemon Tools
issue being the (possible) cause of these BSODs i've not installed that or any similar program onto the new windows install.
 It was installed on my previous windows but that drive has been formatted (this is also why I won't be able to provide a log of bluescreens
that long).

Here's a screenshot of the bugcheck report:

Please let me know if you need anything else!  This issue has really put me at my wits end.... 

Thanks :)

Keys to the Problem BSOD Bug Check Code 0x00000109 Issue

Download SmartPCFixer for Free Now


If you re-installed Windows and still are getting BlueScreens the odds are it is hardware
or something that loads at a low level such as BIOS, low level chipset drivers, and some
other drivers (video is one).
Results verified by WinDBG, DumpCHK, and BlueScreenView.

The Bug_Check were 1E, 0A, and 3B.

1E CAUSE hardware.
Also implicated was Rt64win7.sys Realtek 8136/8168/8169 NDIS
6.20 64-bit Driver which is the RealTek Network driver.
This driver may or may not be
related to the hardware cause.

BugCheck 1E, 0, 0, 0, 0 <-- note all the parameters are " 0 " which makes it difficult
to gather a real definitive cause.
Probably caused by : hardware ( nt!KiKernelCalloutExceptionHandler+e )
IMAGE_NAME:  hardware
MODULE_NAME: hardware

Rt64win7.sys dated  6/23/2010  Realtek 8136/8168/8169 NDIS 6.20 64-bit Driver

BiosVersion = 0904  
BiosReleaseDate = 11/12/2009 <- check for updates to BIOS, low level chipset drivers,

and the other on-board and separate major device drivers.
BaseBoardManufacturer = ASUSTeK Computer INC.
BaseBoardProduct = P6T
BaseBoardVersion = Rev 1.xx
The hardware is unknown though it may be the netword card however that is just a guess.
Check with ASUStek Support, their on-line documentation, drivers, diagnostics, and ask in
their forums about known issues.
Update the BIOS, low level chipset drivers, and the
board major device drivers.
Also update the separate major device drivers - run DriverView
in the troubleshooter previously posted above - set VIEW to Hide Microsoft drivers - update those

without Dump in their name.

ASUStek Support

ASUStek Forums

ASUStek Drivers
Check with ASUStek and then RealTek for updates to the Rt64win7.sys driver.

Rt64win7.sys dated  6/23/2010  Realtek 8136/8168/8169 NDIS 6.20 64-bit Driver

RealTek - after checking ASUStek (and run DriverView) Search for updates to your
network device.
4. Use the methods in the troubleshooters previously posted and those below.

0A CAUSE ntkrnlmp.exe which is a Windows component which means something else drove
it into Fault.

BugCheck A, 24, 2, 0, fffff80002ede6cb
Probably caused by : ntkrnlmp.exe ( nt!KiTimerWaitTest+22b )
IMAGE_NAME:  ntkrnlmp.exe
Use the methods in the troubleshooters previously posted and those below.


3B CAUSE nvlddmkm.sys which is the Nvidia video driver.
Check with ASUStek (if on-board)
and then Nvidia for driver updates.
If no newer re-install the same ones.
It may be necessary
to revert back to an older version.
Check with ASUStek and Nvidia Support, their on-line

documentation, drivers, and ask in their forums for known issues.

BugCheck 3B, c0000005, fffff8800f2ce68e, fffff88007e85550, 0
Probably caused by : nvlddmkm.sys ( nvlddmkm+23168e )
If there is a separate video card remove ALL power and reseat the card - actually remove
and replace - do not just snug.
Do the same for all cards, memory, and cables (on both ends
when possible).
Check with ASUStek (if on-board) and then Nvidia for driver updates.
If no newer re-install the
same ones.
It may be necessary to revert back to an older version.
Check with ASUStek and

Nvidia Support, their on-line documentation, drivers, and ask in their forums for known issues.

nvlddmkm.sys dated 9/22/2011 Nvidia video drivers.

Nvidia - Drivers - Use OPTION 1 to manually enter your driver info to get most current drivers.

Nvidia Support - check with Support as it could be a known issue

Nvidia Forums - also check for forums as it could be a known issue and/or others likely to have it
Retest the memory thoroughly if you think there is any need.
Use the methods in the troubleshooters previously posted and those below.

The general BSOD troubleshooting methods have been previously posted above.
BCCode: 1E   0x0000001E 
Remove ALL power and reseat all the cards, memory, and cables (both ends when
possible) - actually remove and replace - do not just snug.
Those are for a PC and about all
that can be done for a laptop is reseat the memory and clear the vents.
Make sure the BIOS,
low level chipset drivers, and major device drivers are all up to date by check manually at the
makers' sites.
Many Bluescreens are caused by BIOS, low level chipset drivers, and other major device drivers
which are not the most current even though the computer is new.
Check manually for updates
using the methods for updates as indicated in the troubleshooter linked above and/or the methods
below (which are the same).

BCCode: 1E   0x0000001E

This is a very common bug check.
To interpret it, you must identify which exception was generated.
Common exception codes include:
An unaligned data reference was encountered.
A breakpoint or ASSERT was encountered when no kernel debugger was attached to the system.
A memory access violation occurred.
(Parameter 4 of the bug check is the address that the driver attempted to access.)
For a complete list of exception codes, see the ntstatus.h file located in theinc directory of the Windows Driver Kit.
If you are not equipped to debug this problem, you should use some basic troubleshooting techniques.
If a driver is identified in the bug check message, disable the driver or check with the manufacturer for driver updates.
Try changing video adapters.
Check with your hardware vendor for any BIOS updates.
Disable BIOS memory options such as caching or shadowing.
If you plan to debug this problem, you may find it difficult to obtain a stack trace.
Parameter 2 (the exception address) should pinpoint the driver or function that caused this problem.
If exception code 0x80000003 occurs, this indicates that a hard-coded breakpoint or assertion was hit, but the system was started with the/NODEBUG switch.
This problem should rarely occur.
If it occurs repeatedly, make sure a kernel debugger
is connected and the system is started with the/DEBUG switch.
If exception code 0x80000002 occurs, the trap frame will supply additional information.
If the specific cause of the exception is unknown, the following should be considered:
Hardware incompatibility.
First, make sure that any new hardware installed is listed in the Microsoft Windows Marketplace Tested Products List.
Faulty device driver or system service.
In addition, a faulty device driver or system service might be responsible for this error.
Hardware issues, such as BIOS incompatibilities, memory conflicts, and IRQ conflicts can also generate this error.
If a driver is listed by name within the bug check message, disable or remove that driver.
Disable or remove any drivers or services that were recently added.
If the error occurs during the startup sequence and the system partition is formatted with NTFS
file system, you might be able to use Safe Mode to rename or delete the faulty driver.
If the driver is used as part of the system startup process in Safe Mode, you need to start the computer by using the Recovery Console to access the file.
If the problem is associated with Win32k.sys, the source of the error might be a third-party remote control program.
If such software is installed, the service can be removed by starting the system using the Recovery Console and deleting the offending
system service file.
Check the System Log in Event Viewer for additional error messages that might help pinpoint the device or driver that is causing bug check 0x1E.
Disabling memory caching of the BIOS might also resolve the error.
You should also run hardware
diagnostics, especially the memory scanner, supplied by the system manufacturer.
For details on these procedures, see the owner's manual for your computer.
The error that generates this message can occur after the first restart during Windows Setup, or after Setup is finished.
A possible cause of the error is a system BIOS incompatibility.
BIOS problems can be resolved by upgrading the system BIOS version.
BCCode: 1E   0x0000001E  <-- read this link*1045.html

BCCode: 0A     0x0000000A

Check these KB's

Error message on a blue screen on a computer that is running Windows 7 or Windows Server
2008 R2: "STOP: 0x0000000A"
Stop error message on a computer that is running Windows 7 or Windows Server 2008 R2 and
that has iSCSI storage: "0x0000000A"

Those and 5 other KB Articles are available

BCCode: 0A     0x0000000A

Drivers could be at fault however disk issues or antivirus/antispyware/security products are
just as likely to be the root cause as they can force a driver to corrupt or go out of bounds.
The video driver or something affecting it would be very suspect.

Be sure the drivers, BIOS, and low level chipset drivers are all updated by manually checking
at the System maker and device makers's sites.

Below I will post a generic bluescreen troubleshooter and in the next message how to update
drivers and BIOS as well as do memory checks.

BCCode: 0A     0x0000000A
This bug check is issued if paged memory (or invalid memory) is accessed when the IRQL is too high.
The error that generates this bug check usually occurs after the installation of a faulty device driver, system service, or BIOS.
If you encounter bug check 0xA while upgrading to a later version of Windows, this error might be caused by a device driver, a system service, a virus scanner, or a backup tool that is incompatible with the new version.
Resolving the Problem
If a kernel debugger is available, obtain a stack trace.
To resolve an error caused by a faulty device driver, system service, or BIOS
Restart your computer.
Press F8 at the character-based menu that displays the operating system choices.
Select the Last Known Good Configuration option from the Windows Advanced Options menu.
This option is most effective when only one driver or service is added at a time.
To resolve an error caused by an incompatible device driver, system service, virus scanner, or backup tool
Check the System Log in Event Viewer for error messages that might identify the device or driver that caused the error.
Try disabling memory caching of the BIOS.
Run the hardware diagnostics supplied by the system manufacturer, especially the memory scanner.
For details on these procedures, see the owner's manual for your computer.
Make sure the latest Service Pack is installed.
If your system has small computer system interface (SCSI) adapters, contact the adapter manufacturer to obtain updated Windows drivers.
Try disabling sync negotiation in the SCSI BIOS, checking the cabling and the SCSI IDs of each device, and confirming
proper termination.
For integrated device electronics (IDE) devices, define the onboard IDE port as Primary only.
Also, check each IDE device for the proper master/subordinate/stand-alone setting.
Try removing all IDE devices except for hard disks.
 If the message appears during an installation of Windows, make sure that the computer and all installed peripherals are listed in the Microsoft Windows Marketplace Tested Products List.
Before upgrading to a new version of Windows, remove all third-party device drivers and system services, and disable any virus scanners.
Contact the software manufacturers to obtain updates of these third-party tools.
BCCode: 0A     0x0000000A  <-- read this link*1025.html
BCCode: 3b    0x0000003b

Try removing and reseating all cards, memory, and cables (both ends when possible) - actually
remove and replace - do not just snug (on a PC) and clean out the dust bunnies and vents.
a laptop about all that can be done is reseat the memory and clean the vents.
(Of course remove
ALL power prior to opening the case.)
3b is usually a graphic's driver (display adapter/video driver), other possibilities include
but are not limited to antivirus/antispyware/security programs and even memory (mapping).

BCCode: 3b    0x0000003b

This error has been linked to excessive paged pool usage and may occur due to user-mode graphics drivers crossing over and passing bad data to the kernel code.

BCCode: 3b    0x0000003b  <-- read this link*1074.html

Vista and Windows 7 love updated drivers so here is how to update the major ones.
References to Vista also apply to Windows 7.
This is my generic how to for proper driver updates : (update video/display driver and BIOS)

This utility makes it easy to see which versions are loaded :

DriverView - Free - utility displays the list of all device drivers currently loaded on your system.
For each driver in the list, additional useful information is displayed: load address of the driver,
description, version, product name, company that created the driver, and more.

For Drivers check System Maker as fallbacks and Device Maker's which are the most current.
Control Panel - Device Manager - Display Adapter - write down the make and complete model
of your video adapter - double click - Driver's tab - write down the version info.
Now click UPdate
Driver (this may not do anything as MS is far behind certifying drivers) - then Right Click -
Uninstall - REBOOT this will refresh the driver stack.

Repeat that for Network - Network Card (NIC), Wifi, Sound, Mouse and Keyboard if 3rd party
with their own software and drivers and any other major device drivers you have.

Now go to System Maker's site (Dell, HP, Toshiba as examples) (as rollback) and then Device
Maker's site (Realtek, Intel, Nvidia, ATI as examples) and get their latest versions.
(Look for
BIOS, Chipset and software updates at System Maker's site while there.)

Download - SAVE - go to where you put them - Right Click - RUN AD ADMIN - REBOOT after
each installation.

Always check in Device Manager - Drivers tab to be sure the version you are installing actually
shows up.
This is because some drivers rollback before the latest is installed (sound drivers
particularly do this) so install a driver - reboot - check to be sure it is installed and repeat as

Repeat at Device Makers - BTW at Device Makers DO NOT RUN THEIR SCANNER - check
manually by model.

Manually look at manufacturer's sites for drivers - and Device Maker's sites.
Installing and updating drivers in Windows 7 (updating drivers manually using the methods above
is preferred to ensure the latest drivers from System maker and Device makers are found)

If you update drivers manually then it is a good idea to disable Driver Installations in Windows
Updates, this leaves Windows Updates ON however it will not install drivers which will usually be
older and cause issues.
If Updates suggests a new driver then HIDE it (Right Click on it) and then
go look for new ones manually if you wish.

Stop Windows 7 from Automatically Installing Device Drivers

How To Disable Automatic Driver Installation In Windows 7 / Vista

Disable Windows Update Device Driver Search Prompt In Windows 7 / Vista (for Professional,
Ultimate, and Enterprise)


Memory tests do not catch all errors such as mismatched memory (possible even for sticks
that appear to be identical) and when faster memory is placed in system behind slower memory.
So it is best to also swap sticks in and out to check for those even if all memory tests fail to show
a problem.

To test RAM check here - let it run 4+ hours or so.  <-- best method

For the Windows Memory Diagnostic Tool.

Start - type in Search box ->  Memory - find Memory Diagnostics tool at top of list - Right Click -
RUN AS ADMIN follow the instructions

Windows Vista: How to Scan / Test your RAM or Memory with Windows Vista Memory Diagnostic
How to Run the Memory Diagnostics Tool in Windows 7

Test Your Computer’s Memory Using Windows Vista Memory Diagnostic Tool
Hope this helps.

Rob Brown -
Microsoft MVP <- profile - Windows Expert - Consumer : Bicycle - Mark Twain said it right.

Running System Update Readiness Command

On running the System Update readiness Command, it will Detect & Replace Incorrect Registry data with the Correct one. Which may ultimately Solve BSOD Bug Check Code 0x00000109 Issue in Windows.

  1. Open CMD as Administrator by Simply Right Clicking on Start button > Command Prompt (Admin).
  2. Now Type or Copy paste "DISM.exe /Online /Cleanup-image /Scanhealth" and hit Enter,
  3. Now again Type or Copy paste this "DISM.exe /Online /Cleanup-image /Restorehealth" and hit Enter.
  4. Close the Command Prompt Window because we are done.

Try and see if you still get the same error BSOD Bug Check Code 0x00000109 Issue in your Windows.

Note: You may be prompted to enter your administrator's password when you try to execute certain system tasks!

Another Safe way to Repair the Problem: BSOD Bug Check Code 0x00000109 Issue:

How to Fix BSOD Bug Check Code 0x00000109 Issue with SmartPCFixer?

1. You can Download Error Fixer here. Install it on your system. When you open SmartPCFixer, it will perform a scan.

2. After the scan is finished, you can see the errors and problems need to be repaired. Click Fix All.

3. When the Fixing part is finished, your computer has been speeded up and the errors have been removed

Related: How to Download Toshiba Portege R500 HDD/SSD Alert Utility v. driver,Way to Update & Download Toshiba Satellite A355-S69403 Motorola Modem Region Select Utility v. driver,Where to Download Toshiba Satellite L305-S5926 HW Setup Utility v.2.00.11 driver,[Solved] Download Toshiba Satellite L675-S7115 Laptop Checkup v. driver,Method to Download Toshiba Satellite M645-S4080 Media Controller v. driver,Best Way to Download NVidia GeForce 6100 VGA Driver v.304.51 Certified,How Can You Update & Download NVidia GeForce 9300/nForce 730i VGA Driver v.310.19 Certified,Method to Download NVidia GeForce GT 330M Driver v.340.65,How Can I Update & Download NVidia GeForce GTX 590 Driver v.280.26 WHQL,Method to Download NVidia Tesla C2050 Driver v.319.17
Read More: Troubleshooting:BSOD with Bad_Pool_Error with message,Calculating hours between dates Tech Support,Solution to Error: BSOD DRIVER_POWER_STATE_FAILURE (9f),Troubleshooting:Calculate the difference in two dates. Error,Troubleshooting:BSOD Ocurring randomly or sometimes when exiting a game Error,All diagnostic tools give 0x800700C1, troubleshooting wizard can't continue,all files try to open with adobe,all icons on desktop have changed to Adobe icon and won't open,All functions of my outlook are working except it will not let me "REPLY" or start a "NEW" email,all f1-f12 shortcuts not work

No comments:

Post a Comment