BSOD 0x00000014 after waking up from sleep mode

dranet · 26 Nov 2013

This BSOD occurs when I get to my office in the morning. The computer has gone to sleep overnight and it starts back up okay. I log in, and soon after the blue screen pops up. The computer is on a Windows based network, but I'm not sure this is an issue. Recently I left it logged into an account on just the local computer and when I started it up the next morning it did the same thing.

This is a brand new MSI computer (two weeks old) that I upgraded from Windows 7 Home to Windows 7 Pro 64 bit. I used drivers from the MSI website, which isn't nearly as easy to use as HP's driver site so I might have gotten something wrong. I did NOT use the Live Update tool.

Any help would be appreciated.
Tracy

Arc · 27 Nov 2013

Hi dranet.

Does it BSOD even the HP officejet is disconnected?

Take the Hitachi Drive Fitness test: 7 Free Hard Drive Testing Software Tools

Test your RAM modules for possible errors.
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 passes, preferably overnight.
If it start showing errors/red lines, stop testing. A single error is enough to determine that something is going bad there.

If all the tests are free from errors, 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

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.

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.

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

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

Code:

BugCheck 24, {1904fb, fffff88003354478, fffff88003353cd0, fffff80002bb9a9b}

Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+1df )

Followup: Pool_corruption
--------------------------------------------------------------------------
BugCheck 19, {20, fffff8a00d03f330, fffff8a00d03f4d0, 51a0302}

GetPointerFromAddress: unable to read from fffff80002cfe100
GetUlongFromAddress: unable to read from fffff80002cfe1c0
Probably caused by : fltmgr.sys ( fltmgr!FltpPerformPreCallbacks+8f0 )

Followup: MachineOwner
-------------------------------------------------------------------------------
BugCheck 50, {fffff68383546040, 0, fffff80002bde167, 5}


Could not read faulting driver name
Probably caused by : memory_corruption ( nt!MiCaptureAndResetWorkingSetAccessBits+97 )

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