Solved Multiple BSOD Errors 0x19, 0x1A, 0x3B,

[kdgl]

Over the past couple of weeks my computer has suffered many BSOD of errors. I will be working and out of the blue I will see one. I have ran tests on my memory and my hard drives but did not find any errors. I think it could be a driver but all of mine are up to date! Any help would be greatly appreciated. Thanks and have a nice day! Here is everything that WhoCrashed has told me.... Also attached is the DM Log.

System Information (local)
--------------------------------------------------------------------------------

computer name: GRAYSON-PC
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
Hardware: MS-7850, MSI, B85-G41 PC Mate(MS-7850)
CPU: GenuineIntel Intel(R) Core(TM) i5-4690K CPU @ 3.50GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 8514437120 total




--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Thu 1/22/2015 3:48:13 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\012215-5444-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x76E80)
Bugcheck code: 0xA (0x8, 0x2, 0x1, 0xFFFFF80002A85161)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Thu 1/22/2015 3:48:13 AM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: dxgmms1.sys (dxgmms1!VidMmInterface+0x9BBF)
Bugcheck code: 0xA (0x8, 0x2, 0x1, 0xFFFFF80002A85161)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\dxgmms1.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Tue 1/20/2015 4:14:22 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\011915-6099-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x76E80)
Bugcheck code: 0x19 (0x3, 0xFFFFF880059D10B0, 0xFFFFE880059D10B0, 0xFFFFF880059D10B0)
Error: BAD_POOL_HEADER
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a pool header is corrupt.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Mon 1/19/2015 10:17:02 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\011915-5553-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x76E80)
Bugcheck code: 0x1A (0x5003, 0xFFFFF70001080000, 0x258A, 0x28FF00000B14)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Mon 1/19/2015 6:02:06 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\011915-6193-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x76E80)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002BB1123, 0xFFFFF88007B7F8E0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

 

[essenbe]

Please update your system specs in the 'My System Specs' in the bottom left of your last post. That way it will be available with every post and we don't have to hunt for it. Also, please be as detailed as possible as we many times have to look up a component and need Manufacturer and model number sometimes. Please include your PSU and CPU cooler as well. This is what I usually post. Maybe something in it will make it easy for you. Thanks.

Please fill out your System Specs​

   Information

Your System Specs will help us to help you, and doing it in this manner will make them available to all helpers in every post and keep us from hunting for them. We ask that you fill them out in as much detail as possible including Desktop or Laptop, Model number if it is an OEM computer and all components with the Manufacturer and Model number if possible.

If you will go to your last post and click the 'System Specs' in the bottom left of the post, you will find a link to update your system specs. Please fill those out in as much detail as possible, making sure to click save at the bottom of the page. If you would like to know what we would like, you can click 'My System Specs' at the bottom left of this post to see mine. If you do not know what your components are, this will help you accomplish this task. http://www.sevenforums.com/tutorials/180324-system-info-see-your-system-specs.html​

 

[essenbe]

kdgl, here are the results of your 4 dump files. Please note that each one has a different stop code and 3 of the 4 were a different cause. In my experience, that is usually caused by memory.

fffff880`03cff0a8  fffff880`0f1a0055Unable to load image \SystemRoot\system32\DRIVERS\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
 
 atikmdag
start             end                 module name
fffff880`0f024000 fffff880`102a8000   atikmdag T (no symbols)           
    Loaded symbol image file: atikmdag.sys
    Image path: \SystemRoot\system32\DRIVERS\atikmdag.sys
    Image name: atikmdag.sys
    Timestamp:        Thu Nov 20 20:30:27 2014 (546EA3C3)
    CheckSum:         0121F198
    ImageSize:        01284000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000005003, The subtype of the bugcheck.
Arg2: fffff70001080000
Arg3: 000000000000258a
Arg4: 000028ff00000b14

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff80002bb1123, Address of the instruction which caused the bugcheck
Arg3: fffff88007b7f8e0, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

BAD_POOL_HEADER (19)
The pool is already corrupt at the time of the current request.
This may or may not be due to the caller.
The internal pool links must be walked to figure out a possible cause of
the problem, and then special pool applied to the suspect tags or the driver
verifier to a suspect driver.
Arguments:
Arg1: 0000000000000003, the pool freelist is corrupt.
Arg2: fffff880059d10b0, the pool entry being checked.
Arg3: ffffe880059d10b0, the read back flink freelist value (should be the same as 2).
Arg4: fffff880059d10b0, the read back blink freelist value (should be the same as 2).

I hate to start you out on the long test, but as I say, that is usually the result of bad memory. I know you said you have already checked it, but please do it this way.

Please Run Memtest86+

   Information

Please download from this site only http://www.memtest.org/ in the middle of the page are the Download links, you can download the ISO.zip or the Auto USB Flash Drive installer.zip

Extract the Zip file. If you chose the ISO image, burn it to a CD using Windows Disk Image Burner or any Image burner you may have. If you downloaded the Auto USB installer, extract it, insert your USB 2.0 Flash Drive and take note of the drive letter. Run the installer, select the Flash Drive Letter, check the format box and press next. It will install memtest86+ to a flash drive. You can use either V4.20 or V5.01. Boot from your selected media. If you use V5.01 it will tell you to press certain buttons at the start, please press no buttons. The test will begin on it's own and continue to run until you stop it. It needs to run for 8 complete passes or until you receive an error. If you receive an error, stop the test. Even 1 error is a fail. Each pass tests a different part of the ram and each of the 10 tests in each pass tests something different. It takes a minimum of 8 passes to completely test the ram, more passes are better. It is quite a long test and will take several hours depending on how much ram you have. Due to the time length it is best to run overnight. If you have any questions, please do not hesitate to ask​

 

[kdgl]

I have already ran Memtest86+ for over 10 hours. But hey another shot can't hurt! I will run it overnight again and post my results tomorrow! Thanks so much for your response.

 

[kdgl]

The test ran over 8 passes and no errors were found. What should I try next?

 

[essenbe]

If you have any more BSODs upload the http://www.sevenforums.com/bsod-help-support/96879-blue-screen-death-bsod-posting-instructions.html here again.

Run the short and long test with Seatools for DOS http://www.sevenforums.com/tutorials/313457-seatools-dos-windows-how-use.html#Part3

 

[kdgl]

I ran both the long and short tests on both my SSD and regular hardrive and both passed. What should I try next?

 

[essenbe]

Send me the www.sevenforums.com/bsod-help-support/96879-blue-screen-death-bsod-posting-instructions.html#option2

 

[kdgl]

Here it is.

 

[essenbe]

You haven't had a BSOD since we started this thread? I'm pretty sure the dump files are the same

 

[essenbe]

I found one for the 22nd, which was in your last DM Log.

Please open an elevated command prompt ( click start, type cmd in the search box, right click on the cmd entry and select run as administrator) in the black box that opens, copy/paste sfc /scannow. If you decide to type it, notice the space between the sfc and the /. It is a system file checker which will scan your system files and attempt to correct any missing or corrupt files. What we want are the results to say windows found no integrity violations. If it says files were found but could not be repaired, close the box, reboot and run it again, after opening the administrative command prompt. You may have to reboot and run it three times for it to repair all system files. If it can't repair them after 3 reboots, let us know.

If it says 'No integrity violations found' the next thing is To create a restore point (the link to how is below) That is important as it may be your only way back. Sort the driver by provider and select all drivers NOT PROVIDED by Microsoft. Use your computer as normal for at least 24 hours of actual use. If there is anything you do which usually cause a BSOD, do it frequently. You computer may seem a little slow and sluggish, this is normal. We are putting stress on your drivers in an attempt to make the bad driver crash the computer and get caught by the dump file.

   Warning

Be sure to create a System Restore point before proceeding further http://www.sevenforums.com/tutorials/697-system-restore-point-create.html

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

   Information

What is Driver Verifier:
It puts stress on the drivers, and tries to make the faulty driver crash the computer. It is designed this way, to attempt to trap the offending driver.

What you will notice:
It will tend to make the computer rather slow and sluggish because the drivers are being stressed.

   Warning

Before enabling DV, make sure you have created a system restore point before enabling Driver Verifier. make a System Restore Point manually before enabling DV.

   Tip

• If you fail to get on the Desktop because of DV, Boot into Advanced Boot Options > Safe mode. Disable DV there. Now boot normally again, and try following the instruction of enabling DV again.
• If you cannot boot in Safe mode, do a System Restore to a point you made earlier.

Let us know the results, with the subsequent crash dumps, if any.

 

[kdgl]

I'm sorry I posted the wrong file. I did have another crash here is the right one.

 

[kdgl]

I did I posted the wrong file. Here is the right one.

 

[essenbe]

Please open an elevated command prompt ( click start, type cmd in the search box, right click on the cmd entry and select run as administrator) in the black box that opens, copy/paste sfc /scannow. If you decide to type it, notice the space between the sfc and the /. It is a system file checker which will scan your system files and attempt to correct any missing or corrupt files. What we want are the results to say windows found no integrity violations. If it says files were found but could not be repaired, close the box, reboot and run it again, after opening the administrative command prompt. You may have to reboot and run it three times for it to repair all system files. If it can't repair them after 3 reboots, let us know.

 

[essenbe]

You are having issues with corrupted system files. That is most likely caused by your illegal operating system.

Counterfeit installations such as yours contain heavily modified code that causes the installation to behave it unexpected ways. Analyzing BSOD's and determining their causes on these sorts of installations is very unreliable. For this reason, many analysts won't attempt it.

My recommendation is to install a genuine Windows 7. This will minimize the problems you are experiencing, and make subsequent diagnosis of BSOD's far more reliable. Once you are running a Genuine Windows 7 installation, and are still experiencing BSOD's, we will be happy to help you solve them

 

[kdgl]

I have tried the scan over 3 times and it is still says files were found but could not be repaired. Also I have activated my Windows as seen in my attached screenshot.

 

[essenbe]

Only because you have an activation exploit which alters system files as the post above says.

 

[essenbe]

You are using the Stolen Lenovo Key that was Blacklisted by Microsoft before Windows 7 was even released. There is no way possible you could have activated it without an exploit and heavy editing of protected system files. And you want to know why you have corrupted system files, that's why. If you will install a legal copy of Windows I suspect you will have a much better install and it will work right. If you do that and still have problems, we will be happy to assist you.