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: Random BSOD while using computer. error 0x00000109

21 May 2013   #1

Windows 7 Professional X64
 
 
Random BSOD while using computer. error 0x00000109

Hi everyone! First time poster so I'm hoping someone can help me figure this out.

I have an HP desktop computer. Specs are:
HP p7-1010
AMD Athlon II X4 645 Processor 3.1ghz
6144mb of RAM
Windows 7 pro 64bit
Onboard Video

The error im getting its 0X00000109 and then the computer reboots into windows.
I have updated all the drivers from the HP website so everything is up to date. I've also removed any virus's that were on the computer as well. I've checked the hardware with various testing programs (hiren's boot CD, memtest, pc doctor) and nothing has come back with any errors. I'm stumped as to what the cause could be. I've uploaded my dump file in the hopes someone can help. Thank you in advance for any suggestions or fixes

My System SpecsSystem Spec
.

21 May 2013   #2

Microsoft Community Contributor Award Recipient

Windows 7 Home Premium x86 Service Pack 1 - Linux Mint Mate 14 x64
 
 

Code:
BugCheck 109, {a3a039d8970d25b5, b3b7465ee98b6377, fffff80000b96bb0, 6}

*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Probably caused by : ntoskrnl.exe ( nt_fffff80000b95000+1bb0 )
Code:
Usual causes:  Device driver, Breakpoint set with no debugger attached, Hardware (Memory in particular)
This bugcheck suggests that a region of critical kernel code or data was corrupted, this could be due failing RAM where the kernel code was being held, or a driver has modified the kernel code for some reason.

Remove:

Code:
Start Menu\Programs\Norton 360
Norton is known to cause BSODs with Windows 7, and is a very bloated anti-virus program, please remove using the official Norton Removal Tool if the program or parts of the program are still remaining, then install and run full scans with these free and proven alternatives which work with Windows 7, due to their compatibility and lightweight nature of system resources.

Install and perform full scans with:
information   Information
Remember to install the free version of Malwarebytes not the free trail; untick the free trial box during installation. MSE is the most lightweight and compatible with the Windows 7 operating system

You can also view this thread for a complete free and lightweight security protection combination:Run Memtest86+ for least 9-10 passes, and preferably overnight as it can take a while to fully complete.

Test each RAM stick individually, if an error is found then move the same RAM stick into the next DIMM slot and test again, if errors are found for the same RAM stick in every available slot then you have a faulty RAM module. On the other hand, if no errors are found in the next slot or the other slots for the same RAM module, then you have a faulty DIMM slot.

Test each RAM stick and every motherboard DIMM slot available.

Quote   Quote: Originally Posted by Arc View Post
testSlot1Slot2
RAM1ErrorError
RAM2GoodGood
It is a RAM, a bad RAM.

But if you have got a result like that:
testSlot1Slot2
RAM1ErrorGood
RAM2ErrorGood
It is a motherboard issue. The particular slot is bad.
Run Driver Verifier to scan for any corrupted drivers which may be causing problems, this program works by running various stress tests on drivers, in order to produce a BSOD which will locate the driver; run for least 24 hours:
information   Information
My System SpecsSystem Spec
21 May 2013   #3

Windows 7 Ultimate Retail Box (64-bit installed) + Service Pack 1
 
 

Do: SFC /scannow [works from the START | run box, just tested]
Let it check your windows files.

That kernel is main OS file so you might consider booting from the 7 install DVD also, for a repair, if all else is failing to succeed.
My System SpecsSystem Spec
.


21 May 2013   #4

Windows 7 Professional X64
 
 

Thanks so much for all your help guys. I will give all of this a shot and see what the results are and post back here.
My System SpecsSystem Spec
21 May 2013   #5

Windows 7 Professional X64
 
 

Ran Sfc /scannow and everything came back clean. also did a chkdsk and everything came back ok. Gonna put in a win 7 CD and try to repair it and see if that works. Then try N360 and check ram. Thanks again guys
My System SpecsSystem Spec
21 May 2013   #6

Windows 7 Professional X64
 
 

used norton removal tool to uninstall Norton 360. BSOD is still occuring. Going to run Memtest on it now. one stick in each slot. Whats a good time to let the test run for?
My System SpecsSystem Spec
22 May 2013   #7

Microsoft Community Contributor Award Recipient

Windows 7 Home Premium x86 Service Pack 1 - Linux Mint Mate 14 x64
 
 

At night when your asleep, or in the mornings before you go to work/school, basically whenever your not going to be using the computer for a long period of time.
My System SpecsSystem Spec
23 May 2013   #8

Windows 7 Professional X64
 
 

Alright so so far i have done the following:

Performed a sfc /scan now and everything checked out.
Also did chkdsk and everything checked out.
Removed N360 with the norton removal tool and the BSOD's are still happening.


Im still running Memtest86 through hirens boot CD (which when trying to boot into says, No PXE stack commands (usually a bad config). So far no errors. I think 42 hours is long enough eh?

If the mem tests come back clean with no errors, what else can i do to solve this probleM?
My System SpecsSystem Spec
23 May 2013   #9

Windows 7 Professional X64
 
 

Enabled verifier.exe and upon booting into windows, a new BSOD appeared and restarted the computer. USBFILTER is what caused it according to the BSOD message. any thoughts on how to repair/remove?
My System SpecsSystem Spec
23 May 2013   #10

Windows 7 Professional X64
 
 

This is a new SF diagnostic folder im posting now. The 2nd to last minidump file (may 23rd) is the one where the usbfilter should be. There was the original BSOD in between trying to get this information before i could post it. Not sure exactly what to look for in terms of how im supposed to remove this.

Once again, i wanna thank everyone for there help with this
My System SpecsSystem Spec
Reply

 Random BSOD while using computer. error 0x00000109




Thread Tools



Similar help and support threads for2: Random BSOD while using computer. error 0x00000109
Thread Forum
Random BSOD, error 0x00000109 BSOD Help and Support
Random BSOD - error 0x00000109 BSOD Help and Support
BSOD while doing nothing, error 0x00000109 BSOD Help and Support
BSOD error 0x00000109 BSOD Help and Support
BSOD - Under no load - Error 0x00000109 Random times BSOD Help and Support
Random BSOD With Error 0X00000050 and 0X00000109, Windows 7 X64 BSOD Help and Support

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 11:10 PM.
Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App
  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33