BSOD‘s daily for many times

Abuobeida Makawi asked on

Dear everybody read this:

I will be thankful if someone help me to use my useless new asus laptop ( k56cm- core i5- 8G RAM - 750 HDD- Intel  HD4000- Nvidia gforce 2G graphics card - QUALCOMM Bluetooth - realtek sound -15.6 LED screen) which I bought it with windows 8 single language pre installed and then upgraded through win-store to windows8.1 single language.

My problem is that I cant use my laptop for an hour without  a suddenly restart caused by BSOD every time with its reason including ( bad pool header--- service exception--- NTFS.sys ---- memory management --- low or equal something --- kernel security check failure --- critical process died and OTHER reasons I do not remember ) also I checked the drivers with asus update all of it are up to date . I don't have any antivirus I use win- defender . Also don't have any freak or cracked apps just the normal (office- Ccleaner- hot spot shield- Win SDDK for win-phone- some games (AC 3 - PES2013- AGE OF EMPIRES FORGOTTEN -PRINCE OF PERSIA -CRYSIS) and some apps on metro screen. also some times I use to make my laptop as a WIFI hotspot by connectify  to connecting my phone and IPad.

please help if someone can and sorry for my bad English.

2 people had this question

Abuse history

The answered status icon Answer
Patrick Barker replied on


We have three bug checks:


This indicates that a critical system process died.

2: kd> !process ffffe0000465a3c0 3
GetPointerFromAddress: unable to read from fffff802dcfbc000
PROCESS ffffe0000465a3c0
    SessionId: none  Cid: 02f8    Peb: 7ff6c6a4c000  ParentCid: 0244
    DirBase: 1091ac000  ObjectTable: ffffc00001dcb4c0  HandleCount: <Data Not Accessible>
    Image: wininit.exe

^^ Service Control Manager (SCM) is a special system process under the Windows NT family of operating systems, which starts, stops and interacts with Windows service processes.


This bug check indicates that the kernel has detected the corruption of a critical data structure.

BugCheck 139, {3, ffffd000375b3010, ffffd000375b2f68, 0}

The 1st parameter of the bugcheck is 3 which indicates that a LIST_ENTRY was corrupted. Code 3, LIST_ENTRY corruption. This type of bug check can be difficult to track down and indicates that an inconsistency has been introduced into a doubly-linked list (detected when an individual list entry element is added to or removed from the list).

-- FAILURE_BUCKET_ID:  X64_0x139_dxgmms1!VIDMM_LINEAR_POOL::Free+16cdf

^^ Direct X MMS.


This indicates that a severe memory management error occurred.

BugCheck 1A, {31, ffffe00005d28d20, ffffd00038399000, ffffc0000bcd0002}

The 1st parameter of the bug check is 31 which indicates the image relocation fix-up table or code stream has been corrupted. This is probably a hardware error.


1. You have various Asus bloatware drivers listed and loaded (AiCharger.sys, etc). Please uninstall any/all installed Asus software.

2. Uninstall Connectify.

3. Uninstall PowerISO.

4. If you're still crashing after all of the above, run Memtest for NO LESS than ~8 passes (several hours):


Download Memtest86+ here:

Which should I download?

You can either download the pre-compiled ISO that you would burn to a CD and then boot from the CD, or you can download the auto-installer for the USB key. What this will do is format your USB drive, make it a bootable device, and then install the necessary files. Both do the same job, it's just up to you which you choose, or which you have available (whether it's CD or USB).

Do note that some older generation motherboards do not support USB-based booting, therefore your only option is CD (or Floppy if you really wanted to).

How Memtest works:

Memtest86 writes a series of test patterns to most memory addresses, reads back the data written, and compares it for errors.

The default pass does 9 different tests, varying in access patterns and test data. A tenth test, bit fade, is selectable from the menu. It writes all memory with zeroes, then sleeps for 90 minutes before checking to see if bits have changed (perhaps because of refresh problems). This is repeated with all ones for a total time of 3 hours per pass.

Many chipsets can report RAM speeds and timings via SPD (Serial Presence Detect) or EPP (Enhanced Performance Profiles), and some even support changing the expected memory speed. If the expected memory speed is overclocked, Memtest86 can test that memory performance is error-free with these faster settings.

Some hardware is able to report the "PAT status" (PAT: enabled or PAT: disabled). This is a reference to Intel Performance acceleration technology; there may be BIOS settings which affect this aspect of memory timing.

This information, if available to the program, can be displayed via a menu option.

Any other questions, they can most likely be answered by reading this great guide here:



Debugger/Reverse Engineer.
1 person found this helpful

Abuse history