Windows 7 - several BSOD per day, all bug check code 0x00000109

diaspm · 07 Mar 2013

Hi

The BSOD started happening this week and since then it is occuring several times per day.

I ran BlueScreenView and i got the following specs:
bug check code: 0x00000109
caused by driver: ntoskrnl.exe
crash address: ntoskrnl.exe+75c40
File version: 6.1.7601.18044 (win7sp1_gdr.130104-1431)

I 'm completely lost on what is causing it. I checked ram and hdd for errors and both come clean (however I could not run extended checks since it takes a few hours and the BSOD breaks it). apparently all drivers are updated.

I dont't know what to do the BSOD. Help would be much appreciated.

**Pauly** · 07 Mar 2013

Hello diaspm, Welcome to SF

Nothing specific in those dumps im afraid to point at a particular cause
Bug check 0x109 wouold suggest a faulty driver or memory problems
I would first check all memory by running some diagnostic software
RAM - Test with Memtest86+
Disk Check
Hard Drive Diagnostic Procedure

Then if no faults found try enabling driver verifier
Using Driver Verifier to identify issues with Drivers
just remember if your pc wont boot after enabling then enter safe mode to turn it of again

Also you have many old drivers on your system you ned to update the old ones, heres a list of the ones that predate win 7

NTIDrvr.sys 25/03/2009 03:09:39
DKbFltr.sys 26/03/2009 03:15:42
usbfilter.sys 03/04/2009 11:39:51
UBHelper.sys 27/04/2009 08:48:19
AtiPcie.sys 05/05/2009 15:00:22
Rt64win7.sys 22/05/2009 14:52:30
mwlPSDFilter.sys 02/06/2009 10:07:30
mwlPSDNServ.sys 02/06/2009 10:07:39
mwlPSDVDisk.sys 02/06/2009 10:15:29
SynTP.sys 19/06/2009 02:33:58
RTKVHD64.sys 06/07/2009 09:18:54

diaspm · 07 Mar 2013

Thank you Pauly, both for the welcome as well as your fast reply. I will follow each one of your suggested steps and return back on results asap
cheers

diaspm · 07 Mar 2013

Some update:
1. the ram test with Memtest86+ ran without any reported error.
2. I am having trouble to run the disk check: I made a "chkdsk /R" command but the check is interrupted by BSOD. Then the laptop restarts and the check strats again from 0 (last time it happened the check was no more than 12% completed) ... i am worried data can be damaged because of it.
Any suggestion? Txs

**Pauly** · 07 Mar 2013

Scrap it and run the bootable hdd diagnostic software this runs outside of OS so hopefully no bsod

diaspm · 08 Mar 2013

Yes I had to give up from the chkdsk.
Then I went for the bootable HDD (it is a Western Digital) diagnostic tool and I was able to run the extended test (no BSODs this time:) No faults were found

It leaves me the last suggested step: I 'm gonna enable driver verifier and see what it gets.
I will report back on the results/logs

Txs!

diaspm · 08 Mar 2013

Hello again
Well it does not take long to get 3 BSOD and collect the dump files after enabling Driver Verifier.
May you please have a look to see if you can spot what can be triggering the BSODs? unfortunately I'm not skilled to read the files. Txs!

**Pauly** · 08 Mar 2013

Think we might need some help here, im going to request assistance from other BSOD members

diaspm · 08 Mar 2013

Txs mate!
If you see it is too much trouble I can always go to the a-bomb solution: reinstall windows from scratch
I was trying to avoid it but I don't want to give you so much work ...
cheers

**Pauly** · 08 Mar 2013

Got some help heres what he said

x BlueRobot said:

This is what I managed to find from the BSOD:

Code:

Arg4: 0000000000000007, 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

Code:

1: kd> !error c0000082
Error code: (NTSTATUS) 0xc0000082 (3221225602) - Too many GUIDs were requested from the allocation server at once.

It seems the MSR (Micrsoft Reserved Partition) was modified in some form, this partition is attached with a GUID which is basically just a software reference number, and is used for the GPT format for hard-drives.

Microsoft requires an MSR on every GPT disk

I'm guessing the OP is using the GPT format, and that MSR has got corrupted in some form.

I would follow these steps:

Scan for any malware or rootkits using:

Enter Command Prompt at boot, and then attempt to use the chkdsk /f /r command from there.