Solved BSOD Memory_Management

[pswils]

Hi,

I'm experiencing a BSOD intermittently/occasionally on my ASUS ux32a. Sometimes it happens every other day, othertimes 2-3 times a day. Recent changes to my computer have been SSD fit and RAM increase. All drivers are up to date. I have carried out a RAM test (memtest86+) and this comes up clear. To my recollections this issue occurred before these two changes anyway. Initially the BSOD's were indicated as a number of different reasons, Fault in non paged area (I think) etc. I carried out a system reinstall and now the failure is indicated solely as memory_management. I apologise if my train of thought on the problem is sketchy as I have been chasing this for some time and had given up on finding a solution as I use the computer infrequently. I have been unable to create a minidump file, despite following your instructions. My antivirus was MSE but recently I've gone back to AVG and I run malwarebytes frequently. I have attached the DM log file.

Thanks in advance.

 

[Arc]

Hi pswils.

The zip you uploaded does not contain any crash dump.

Follow it: http://www.sevenforums.com/tutorials/174459-dump-files-configure-windows-create-bsod.html
Go to Option Two, Point 2. Download the .reg file and merge it in registry by double clicking it.

Now wait for another BSOD. When it occurred, search the .dmp files manually in the default path: C:\Windows\Minidump or %SystemRoot%\Minidump. See if the crash dump is recorded or not (hopefully it will be recorded).Post it following the Blue Screen of Death (BSOD) Posting Instructions.

Dont run any disc cleanup program before you upload another zip.

BTW, how many passes you ran the memtest86+?

 

[pswils]

Arc,

thanks for the advice. I applied the registry change but there was still no minidump file after tonights BSOD. I'll go through the advice threads on the site again to see if I've missed something.

 

[Arc]

Can you take a camera snap of the next BSOD screen? Let us expect that the on-screen codes will give us some hints.

 

[pswils]

Memory Management BSOD

Hi, finally managed to produced a minidump file after a full reinstall. between my last post and this one the problem became gradually worse. Not sure if it is related but the BSOD's stopped and the computer random restarts without BSOD started, and increaded in number to 3/4 per day (hence the reinstall). I have read that a lot of these types of laptops suffer from battery/motherboard issues however I'll let you analyse the issue. Please see attached file

 

[Arc]

fffff880`06f1ba68  fffff880`03a6ef7dUnable to load image \SystemRoot\system32\DRIVERS\igdkmd64.sys, Win32 error 0n2
[COLOR=Red]*** WARNING: Unable to verify timestamp for igdkmd64.sys
*** ERROR: Module load completed but symbols could not be loaded for igdkmd64.sys[/COLOR]
 igdkmd64+0x2df7d

Search for any possible update to the Intel(R) HD Graphics 4000 from https://downloadcenter.intel.com/

See how it goes. Let us know.

 

[pswils]

Service Corruption

Hi Arc,

I updated the intel driver as you instructed. My computer BSOD'd again this morning with a different message. Sorry but it occurs so briefly that it's difficult to get much info from it other than it was some sort of service corruption (different primary fail code I noticed). File attached.

 

[Arc]

This BSOD dump does not point to anything preciously but gives an idea that something network related issues are there. And you have two network items running in the background always.

Before going for an intense troubleshooting for SYSTEM_SERVICE_EXCEPTION, let us see how the computer behaves after taking this observation into consideration.

Free up the startup. Windows does not need any other program to auto start with it, but the auto start programs often conflicts and causes various problems including BSODs.

1. Click on the Start button
2. Type “msconfig (without quotes), click the resulting link. It will open the System Configuration window.
3. Select the “Startup” tab.
4. Deselect all items other than the antivirus.
5. Apply > OK
6. Accept then restart.

Do two more things. Go to https://downloadcenter.intel.com/ and search for any possible update for your Intel(R) Centrino(R) Advanced-N 6235. Also disable bluetooth, if that is not very essential for you. Enable it only when you use it, then disable it back.

See how it goes. Let us know.

 

[pswils]

Bad_Pool_Header

Hi Arc,
I updated my display driver and disabled most of the startup items. For some reason CCleaner keeps re-adding itself. My system BSOD'd again tonight, after 2 days of no failures, which is an improvement. However the failure message was Bad_Pool_Header this time. I've not seen this one before. Yet again the blue screen was too quick to take a shot of. I File attached. Thanks in advance.

 

[pswils]

Arc,

just realised that I didn't disable bluetooth after updating the driver. I've done this now and I'll see how it goes.

 

[Arc]

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

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: 0000000000000020, a pool block header size is corrupt.
Arg2: fffff8800c98d5b8, The pool entry we were looking for within the page.
Arg3: fffff8800c98da78, The next pool entry.
Arg4: 000000000d4c49b0, (reserved)

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

So you need to enable Driver Verifier to monitor the drivers at this stage.

Driver Verifier - Enable and Disable
​

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

   Information

Why Driver Verifier:
It puts a stress on the drivers, ans so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.

How Can we know that DV is enabled:
It will make the system bit of slow, laggy.

   Warning

Before enabling DV, make it sure that you have earlier System restore points made in your computer. You can check it easily by using CCleaner looking at Tools > System Restore.

If there is no points, 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 too, do a System Restore to a point you made earlier.

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

 

[pswils]

Special Pool Detected Memory Corruption

Arc,

I haven't used the computer much in the last couple of days but after setting up the verifier it ran for about 30 mins before BSOD with Special Pool Detected Memory Corruption. File attached. I think both the previous and new minidump files were included in the file. Regards.

 

[Arc]

Driver verifier detects memory corruption.

BugCheck C1, {fffff980102f2fe0, fffff980102f2274, 910018, 32}

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

Followup: MachineOwner
---------

SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION (c1)
Special pool has detected memory corruption.  [COLOR=Red]Typically the current thread's
stack backtrace will reveal the guilty party.[/COLOR]
Arguments:
Arg1: fffff980102f2fe0, address trying to free
Arg2: fffff980102f2274, address where one bit is corrupted
Arg3: 0000000000910018, (reserved)
Arg4: 0000000000000032, caller is freeing an address where nearby bytes within the same page have a single bit error

No guilty party is revealed, nothing in the raw stacks, too.

So it may not be a driver caused BSOD. Let us look at the RAM now. Test your RAM modules for possible errors.

How to Test and Diagnose RAM Issues with Memtest86+
​

Run memtest86+ for at least 8 consecutive passes.

If it start showing errors/red lines, stop testing. A single error is enough to determine that something is going bad there.

Let us know how it goes. It would be the best reporting if you can take a camera snap of the memtest86+ screen before closing it and upload the picture here.

 

[pswils]

Arc,

I've just managed to get the opportunity to carry out a series of memory tests. No faults were reported. Picture attached.

 

[Arc]

It is a memory error, as the dumps are reporting.

Driver verifier is not finding any driver causing it.

Memtest is not causing any memory failure.

So, another possibility is .... mismatch RAM.

Your 10 GB RAM consists of two sticks; one 8 GB and one 2 GB.

  Physical Memory Array Handle  000bh
  Memory Error Info Handle      [Not Provided]
  Total Width                   64 bits
  Data Width                    64 bits
  Size                          8192MB
  Form Factor                   0dh - SODIMM
  Device Set                    [None]
  Device Locator                ChannelA-DIMM0
  Bank Locator                  BANK 0
  Memory Type                   18h - Specification Reserved
  Type Detail                   0080h - Synchronous
  Speed                         1600MHz
[COLOR=Red]  Manufacturer                  8502[/COLOR]

  Physical Memory Array Handle  000bh
  Memory Error Info Handle      [Not Provided]
  Total Width                   64 bits
  Data Width                    64 bits
  Size                          2048MB
  Form Factor                   0dh - SODIMM
  Device Set                    [None]
  Device Locator                ChannelB-DIMM0
  Bank Locator                  BANK 2
  Memory Type                   18h - Specification Reserved
  Type Detail                   0080h - Synchronous
  Speed                         1600MHz
[COLOR=Red]  Manufacturer                  Hynix/Hyundai[/COLOR]

As those sticks are from different manufacturer, there remains a chance that they may not work properly with each other. RAM should be bought in a KIT, a couple or more sticks tested to work together.

Remove either one, see how the computer is running with the remaining one.

 

[pswils]

Sorted!

Arc,

thanks for all the assistance. I removed the suspect RAM and ran it in another laptop which transferred the intermittent BSOD. This laptop has been good ever since. I'd say case closed.

Thanks again,

Paul

 

[Arc]

You are welcome, Paul. Let us know for any further issue.