Jump to content


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.

Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.


Any help on a BSOD on Windows 2008 DC

  • Please log in to reply
3 replies to this topic

#1 cpixley


  • Members
  • 2 posts
  • Local time:01:30 PM

Posted 19 June 2013 - 10:47 AM

Log Name:      System

Source:        Microsoft-Windows-WER-SystemErrorReporting

Date:          6/18/2013 10:09:51 PM

Event ID:      1001

Task Category: None

Level:         Error

Keywords:      Classic

User:          N/A

Computer:      GSADC01


The computer has rebooted from a bugcheck.  The bugcheck was: 0x000000c5 (0xfffffa7a060d0600, 0x0000000000000002, 0x0000000000000000, 0xfffff80001bb2f8c). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 061813-28501-01.

Event Xml:

<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">


    <Provider Name="Microsoft-Windows-WER-SystemErrorReporting" Guid="{ABCE23E7-DE45-4366-8631-84FA6C525952}" EventSourceName="BugCheck" />

    <EventID Qualifiers="16384">1001</EventID>






    <TimeCreated SystemTime="2013-06-19T03:09:51.000000000Z" />


    <Correlation />

    <Execution ProcessID="0" ThreadID="0" />



    <Security />



    <Data Name="param1">0x000000c5 (0xfffffa7a060d0600, 0x0000000000000002, 0x0000000000000000, 0xfffff80001bb2f8c)</Data>

    <Data Name="param2">C:\Windows\MEMORY.DMP</Data>

    <Data Name="param3">061813-28501-01</Data>





BC AdBot (Login to Remove)


#2 x64


  • Members
  • 352 posts
  • Gender:Male
  • Location:London UK
  • Local time:07:30 PM

Posted 20 June 2013 - 01:28 PM

Stop 0x000000c5 is DRIVER_CORRUPTED_EXPOOL, so think about any recent driver updates.


One exmple of such an error is http://support.microsoft.com/kb/969550 but the issue could be any driver on the system


Running your memory.dmp file through http://www.nirsoft.net/utils/blue_screen_view.html may help isolate the errant driver, but failing that either reversing any recent driver update, or performing a full update of drivers and server firmware (for example if it is an HP system, installing the latest Proliant support pack and using the firmware update CD, or using the HP SUM) would be a good idea.



#3 cpixley

  • Topic Starter

  • Members
  • 2 posts
  • Local time:01:30 PM

Posted 21 June 2013 - 09:05 AM

Nirsoft shows the fault in the NT Kernel & System  ntoskrnl.exe

#4 Anshad Edavana

Anshad Edavana

  • Members
  • 2,805 posts
  • Gender:Male
  • Location:India
  • Local time:01:00 AM

Posted 21 June 2013 - 11:54 AM



Here is the Microsoft MSDN description about the stop code you are recieving.




Usual causes - Faulty driver or in some cases a faulty memory module. 


Please follow the below steps. 


1 ) Run Memtest86+ to verify the health status of your RAM.




You should run at least 7 passe with Memtest to properly test the RAM. It may take several hours depending on the amount of RAM the system have. More passes is more better.


2 ) Change system setting to write small memory dumps.


  -Go to Start and type in "sysdm.cpl" (without the quotes) and press Enter

  -Click on the Advanced tab
  -Click on the Startup and Recovery Settings button
  -Ensure that "Automatically restart" is unchecked
  -Under the Write Debugging Information header select "Small memory dump " in the dropdown box
  -Ensure that the Small Dump Directory is listed as "%systemroot%\Minidump" (without the quotes)
  -Click OK twice to exit the dialogs, then reboot for the changes to take effect.



3 ) If the RAM is OK, enable driver verifier to force crash the driver which corrupts the pool. Follow the instructions from the below link.




You will experience a sluggishness after enabling verifier as it stress test all third party drivers. When it detects a violation, system will show a blue screen which hopefully contains the necessary info to troubleshoot.


Upload the minidumps (C:\Windows\mindump) to a free file hosting site  and post the link to it . You can zip the minidump folder to reduce the size.





0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users