Solved BSOD error Win7/8/8.1

[mrroccat]

Hello I had same issue before 2 months and it fixed alone but now I reinstalled windows 8.1 still same now i tried windows 7 and a little bit better but again it appears the same issue.RAM changed and DVD drive removed but it still does it.

"This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)"

p.s.

Also sometimes on screen appears some red I can say lines and browsers crash again and again..(this happened before on 8.1 but fixed alone)

System specs and all other details included @zip

 

[Thedoctor44]

1: kd> [COLOR="Green"]!pool fffff8a00df1e4e0[/COLOR]
GetPointerFromAddress: unable to read from fffff80003309100
Pool page fffff8a00df1e4e0 region is Unknown
 fffff8a00df1e000 size:  4d0 previous size:    0  (Allocated)  Ntff
*fffff8a00df1e4d0 size:  350 previous size:  4d0  (Free)      *....
		[COLOR="Red"]Owning component : Unknown[/COLOR] (update pooltag.txt)
 fffff8a00df1e820 size:   c0 previous size:  350  (Free )  FIcs
 fffff8a00df1e8e0 size:   90 previous size:   c0  (Allocated)  FSim
 fffff8a00df1e970 size:   30 previous size:   90  (Allocated)  CMIn (Protected)
 fffff8a00df1e9a0 size:   40 previous size:   30  (Allocated)  CMNb (Protected)
 fffff8a00df1e9e0 size:   90 previous size:   40  (Allocated)  FSim
 fffff8a00df1ea70 size:   30 previous size:   90  (Allocated)  Ntf0
 fffff8a00df1eaa0 size:   b0 previous size:   30  (Allocated)  Ntfo
 fffff8a00df1eb50 size:   90 previous size:   b0  (Allocated)  Ntfc
 fffff8a00df1ebe0 size:   30 previous size:   90  (Allocated)  PfFK
 fffff8a00df1ec10 size:  3f0 previous size:   30  (Free)       CcPh

I'm struggling to find anything in these dump files apart from a few windows functions that involve BLOBS.

1: kd> [COLOR="Green"]k[/COLOR]
Child-SP          RetAddr           Call Site
fffff880`0a215788 fffff800`0320470f nt!KeBugCheckEx
fffff880`0a215790 fffff800`032054f1 nt!ExDeferredFreePool+0xcbb
fffff880`0a215820 fffff800`033998ee nt!ExFreePoolWithTag+0x411
fffff880`0a2158d0 fffff800`030dae54 nt!SepTokenDeleteMethod+0x7e
fffff880`0a215900 fffff800`0337440a nt!ObfDereferenceObject+0xd4
fffff880`0a215960 fffff800`030dae54 nt!AlpcpDeletePort+0x17a
fffff880`0a215990 fffff800`033dfca7 nt!ObfDereferenceObject+0xd4
fffff880`0a2159f0 fffff800`033e0738 nt!AlpcpMessageDestroyProcedure+0x67
fffff880`0a215a30 fffff800`033df402 nt!AlpcpDestroyBlob+0x28
fffff880`0a215a60 fffff800`033e0d56 nt!AlpcpReceiveMessage+0x65f
fffff880`0a215b00 fffff800`030d0e53 nt!NtAlpcSendWaitReceivePort+0x1e6
fffff880`0a215bb0 00000000`76ff1b0a nt!KiSystemServiceCopyEnd+0x13
00000000`0200f558 00000000`00000000 0x76ff1b0a

Memtest86 will test your RAM

   Information

Run Memtest86 for at least 8 passes so we get enough information to confirm that your RAM isn't failing

If memtest86 comes back clean then try Driver Verifier.

Enable driver verifier but only enable the options: Standard settings and IRP logging step 3.
Don't enable Force Pending I/O Requests

Enable Driver Verifier to monitor the drivers.
Driver Verifier -Enable and Disable
Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

   Information

We use Driver Verifier as it puts a stress on the drivers, and so it makes the unstable drivers crash. This should flag the driver responsible in the dump file.
It

Driver Verifier will make the system laggy, this is normal so don't worry.

Before enabling DV, make sure that you have earlier System restore points made in your computer.

If there are no points, make a System Restore Point Manually

Post back the results.

 

[mrroccat]

Hello thanks for help, new results attached.

It says atikmdag.sys , but I dont believe that.


p.s.

Before 2/3 days I have Installed older version of ati drivers but nahh

 

[Thedoctor44]

The latest versions of display drivers at the moment seem to be causing quite a lot of issues.
Roll back using the device manager and see if the issue persists.

Your AMD driver is in fact causing issues.

BugCheck [COLOR="red"]D5[/COLOR], {fffff9802552c2a8, 0, fffff880130e47de, 0}

Unable to load image atikmdag.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for atikmdag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys

Could not read faulting driver name
Probably caused by : [COLOR="Red"]atikmdag.sys[/COLOR] ( atikmdag+bf7de )

This bugcheck indicates that a pool header in memory was referenced after is was freed, in other words after a pool is wiped clean or "freed" it removes all information regarding the previous driver, if the driver still uses the same pointer to the old address it can cause issues which is why the system bugchecks.

 

[mrroccat]

Hello, It has been crashe 2 more times but now its stable nothing happening.PC is On like 48hours and everything looks fine.Removed Catalyst manager and now it looks fine.

Two crashes after unistalling catalyst manager :

This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)


Thanks for your help.Great forum again and again.

 

[Thedoctor44]

Upload the new dump files.
You are clearly still having issues.

 

[mrroccat]

Okay, attached.

This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)

 

[Thedoctor44]

There are no new dump files.

Is Driver Verifier enabled as requested?

 

[mrroccat]

No its disabled after 36hrs, also was enabled 6hrs after Catalyst manager was unistalled.

 

[Thedoctor44]

Did you run memtest86?

Try re enabling it.
I have my doubts.

 

[mrroccat]

Yes no RAM issues. Here are the new results.

 

[Thedoctor44]

I'm not getting anything from this dump...

Driver Verifier has detected memory corruption but it cannot find the driver responsible.

Can you let it run again.

BugCheck C1, {fffff9806816cee0, fffff9806816c281, 890118, 23}

Probably caused by : [COLOR="Red"]memory_corruption[/COLOR] ( nt!MiCheckSpecialPoolSlop+9a )

Thee are quite a few I/O requests which is the only lead I'm having.

 

[mrroccat]

Here are some screenshoots. Maybe its a bad pair of ram cuz its not 16GB kit. Waiting to finish

 

[Thedoctor44]

Don't bother finishing, in fact it doesn't finish you have to manually stop it.

One error is enough to determine bad RAM.

Because you've had errors then you'll need to swap your RAM sticks around to determine whether or not it's the RAM sticks or motherboard DIMM slots.

If the output is like this then you have bad RAM so the stick(s) need replacing.

Test|Slot 1|Slot 2
RAM 1| Error | Error
RAM 2|Good|Good

If the output is like this then you should replace the motherboard, however you can leave that DIMM slot empty although it's not advised to use a system with a faulty motherboard.

Test|Slot 1|Slot 2
RAM 1| Error |Good
RAM 2| Error |Good

 

[mrroccat]

I changed the slots and all instruction you posted.And its a defective pair of RAM. i testet first pair in all slots and no problem no error no nothing, when I put the 2nd pair a lot of errors in all slots.So i take it out and I have 60 months guarantee. Pc now runs smoothly.No BSOD error no nothing. Look at screenshots, now I mean its solved cuz its not motherboard issue but RAM issue.thanks again for your help I appreciate.

 

[Thedoctor44]

That's your issue then.

Glad you got it solved
Any more issues let me know.
Make sure you mark the thread as solved.