Too Many BSOD's now

[TomiHendrix]

Hi guys

I used to get BSOD's a lot whilst media was playing (iTunes, WMP) etc, now i just get BSOD's a lot, doesn't matter what i'm doing.

Could you please help?

I've attached a zip file of the dumps and perfmon report as per your BSOD posting instructions.

It's Windows 7 x64.
It is an OEM version purchased online but i installed myself and the only OS to have been installed on this PC.
Hardware is all relatively new, purchased January 2009. In May this year i bought a new harddrive and Windows 7 Ultimate and started fresh. Old harddrive was formatted and used for storage only. The OS has not been reinstalled.

Please let me know if you need anything else, it's becoming quite frustrating now.

A million thankyou's in advance!

 

[TomiHendrix]

Hi Guys,

These are coming thick and fast now...does anyone have any ideas what i can look for? I'm really trying to avoid a re-install if i can help it. I've run memory tests and all sorts of things i've seen work for other people and haven't come up with anything.

Any suggestions would be greatly appreciated!

 

[yowanvista]

There is no file attached, try again

 

[TomiHendrix]

Have uploaded again. Guarantee you it was there the first time but hey ho

 

[yowanvista]

Enable Driver verifier to locate the faulting driver

- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out.

Then upload the new dumps file located in C:\Windows\Minidump



-Run a scan of Malwarebytes in safe mode with networking


-You have outdated drivers on your system

Upadte your Realtek drivers Realtek

Rt64win7.sys        fffff880`03596000    fffff880`035c8000    0x00032000    0x49a65b0d    26/02/2009 13:04:13

 

[TomiHendrix]

Hi Yowanvista,

I sincerely apologise for the delay in getting back to you. I know support can be a thankless job at times but it was not my intention. I ended up relocating to a different country and completely forgot about this until i got my computer setup and it started happening again.

I followed your steps before i moved and found a few programs to be causing issues. I have removed them but still get the occasional BSOD, gradually getting more frequent again.

I have attached logs from crashes with verifier running. I also ran a full scan with malwarebytes and did not find anything nasty.

I have updated the realtek driver and appear to be up to date with all other updates.

Can i be a pain and ask you to look at the attached zip file again for me? Any pointers on where i should look/ what i should try next would be greatly appreciated!

Many many many thanks in advance!

 

[yowanvista]

Memory corruption is mentioned, test your RAM
http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

CRITICAL_STRUCTURE_CORRUPTION (109)
This bugcheck is generated when the kernel detects that critical kernel code or
data have been corrupted. There are generally three causes for a corruption:
1) A driver has inadvertently or deliberately modified critical kernel code
 or data. See http://www.microsoft.com/whdc/driver/kernel/64bitPatching.mspx
2) A developer attempted to set a normal kernel breakpoint using a kernel
 debugger that was not attached when the system was booted. Normal breakpoints,
 "bp", can only be set if the debugger is attached at boot time. Hardware
 breakpoints, "ba", can be set at any time.
3) A hardware corruption occurred, e.g. failing RAM holding kernel code or data.
Arguments:
Arg1: a3a039d89a88b6fa, Reserved
Arg2: b3b7465eed0586c0, Reserved
Arg3: fffff800031690e0, Failure type dependent information
Arg4: 0000000000000001, 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

Debugging Details:
------------------


BUGCHECK_STR:  0x109

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  CODE_CORRUPTION

PROCESS_NAME:  System

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff80003086d00

STACK_TEXT:  
fffff880`02fe1598 00000000`00000000 : 00000000`00000109 a3a039d8`9a88b6fa b3b7465e`ed0586c0 fffff800`031690e0 : nt!KeBugCheckEx


STACK_COMMAND:  kb

CHKIMG_EXTENSION: !chkimg -lo 50 -d !nt
    fffff8000316916d - nt!IopCleanupNotifications+8d
    [ 48:58 ]
1 error : !nt (fffff8000316916d)

MODULE_NAME: memory_corruption

IMAGE_NAME:  memory_corruption

FOLLOWUP_NAME:  memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MEMORY_CORRUPTOR:  ONE_BIT

FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_ONE_BIT

BUCKET_ID:  X64_MEMORY_CORRUPTION_ONE_BIT

Followup: memory_corruption
---------

 

[TomiHendrix]

I ran the advised memory test overnight last night. In just under 12 hours it completed 13 passes and no errors. Is their another way to test the memory or stress it perhaps?

Incidentally i had another BSOD yesterday and all i had done is opened outlook and a browser once seeing your reply to go and view it. Nothing else was running.

 

[yowanvista]

I ran the advised memory test overnight last night. In just under 12 hours it completed 13 passes and no errors. Is their another way to test the memory or stress it perhaps?

Incidentally i had another BSOD yesterday and all i had done is opened outlook and a browser once seeing your reply to go and view it. Nothing else was running.

Upload this dump file

 

[TomiHendrix]

Please see the attached.

 

[yowanvista]

An Unknown Module(unidentifiable driver) is the cause, this happens when old software/old drivers are installed
Identifying it can be difficult, remove any old software that use drivers

 

[TomiHendrix]

Was this the same for all 50 dump files? Apologies for being a pain but i was looking for something a little stronger to go off than just randomly deleting software. It defeats the purpose of having an operating system if i can't use software with it. You found other issues previously so just wondering if there is something else i can try before this, as to be honest starting from scratch sounds less time consuming than removing an application at a time and waiting to see if that was the lucky winner or not? Is there a way to list all drivers installed and i can try to narrow this down a little?

 

[yowanvista]

Was this the same for all 50 dump files? Apologies for being a pain but i was looking for something a little stronger to go off than just randomly deleting software. It defeats the purpose of having an operating system if i can't use software with it. You found other issues previously so just wondering if there is something else i can try before this, as to be honest starting from scratch sounds less time consuming than removing an application at a time and waiting to see if that was the lucky winner or not? Is there a way to list all drivers installed and i can try to narrow this down a little?

It was mentioned in the last dumps. To view all your drivers, open an elevated command prompt and enter "driverquery", all dates will be listed along with the drivers

 

[TomiHendrix]

Would i be right in thinking that if all modules are displayed with the drivers in the output of a driverquery and none are marked 'unknown' then the culprit is not going to be there?

 

[yowanvista]

Would i be right in thinking that if all modules are displayed with the drivers in the output of a driverquery and none are marked 'unknown' then the culprit is not going to be there?

The culprit is probably an old driver