Jump to content
winetuti

BAD_POOL_CALLER - MWAC.SYS CRASH

Recommended Posts

Hi winetuti,

There doesn't appear to be a BSOD event recorded, only unexpected shut downs.

2019-09-04T09:46:17.534        The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
2019-09-04T07:17:37.754        The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
2019-09-02T21:34:51.097        The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

However, the amount of hard drive related events is concerning and could explain the lack of BSOD events.

 

Please do the following for each partition in Windows Explorer:

  1. Right click and select properties
  2. Go to Tools
  3. Click Check to start error checking.

 

After error checking is finished, please provide the reports: https://www.sysnative.com/forums/threads/find-check-disk-chkdsk-results.11937/

 

2019-09-04T10:07:44.456        Volume ?? (\Device\HarddiskVolumeShadowCopy1) requires an Online Scan.  An Online Scan will automatically run as part of the next scheduled maintenance task.  Alternatively you may run "CHKDSK /SCAN" locally via the command line, or run "REPAIR-VOLUME <drive:> -SCAN" locally or remotely via PowerShell.
2019-09-04T09:46:16.425        Volume 😄 (\Device\HarddiskVolume3) requires an Online Scan.  An Online Scan will automatically run as part of the next scheduled maintenance task.  Alternatively you may run "CHKDSK /SCAN" locally via the command line, or run "REPAIR-VOLUME <drive:> -SCAN" locally or remotely via PowerShell.
2019-09-04T07:17:36.644        Volume 😄 (\Device\HarddiskVolume3) requires an Online Scan.  An Online Scan will automatically run as part of the next scheduled maintenance task.  Alternatively you may run "CHKDSK /SCAN" locally via the command line, or run "REPAIR-VOLUME <drive:> -SCAN" locally or remotely via PowerShell.
2019-09-02T21:58:15.393        Volume 😄 (\Device\HarddiskVolume3) requires an Online Scan.  An Online Scan will automatically run as part of the next scheduled maintenance task.  Alternatively you may run "CHKDSK /SCAN" locally via the command line, or run "REPAIR-VOLUME <drive:> -SCAN" locally or remotely via PowerShell.
2019-09-02T21:34:50.050        Volume 😄 (\Device\HarddiskVolume3) requires an Online Scan.  An Online Scan will automatically run as part of the next scheduled maintenance task.  Alternatively you may run "CHKDSK /SCAN" locally via the command line, or run "REPAIR-VOLUME <drive:> -SCAN" locally or remotely via PowerShell.
2019-09-02T21:31:11.424        Volume 😄 (\Device\HarddiskVolume3) requires an Online Scan.  An Online Scan will automatically run as part of the next scheduled maintenance task.  Alternatively you may run "CHKDSK /SCAN" locally via the command line, or run "REPAIR-VOLUME <drive:> -SCAN" locally or remotely via PowerShell.
2019-08-30T17:53:23.721        Volume ?? (\Device\HarddiskVolumeShadowCopy1) requires an Online Scan.  An Online Scan will automatically run as part of the next scheduled maintenance task.  Alternatively you may run "CHKDSK /SCAN" locally via the command line, or run "REPAIR-VOLUME <drive:> -SCAN" locally or remotely via PowerShell.
2019-08-21T22:03:37.566        Volume 😄 (\Device\HarddiskVolume3) requires an Online Scan.  An Online Scan will automatically run as part of the next scheduled maintenance task.  Alternatively you may run "CHKDSK /SCAN" locally via the command line, or run "REPAIR-VOLUME <drive:> -SCAN" locally or remotely via PowerShell.
2019-08-17T15:58:04.393        Volume 😄 (\Device\HarddiskVolume3) requires an Online Scan.  An Online Scan will automatically run as part of the next scheduled maintenance task.  Alternatively you may run "CHKDSK /SCAN" locally via the command line, or run "REPAIR-VOLUME <drive:> -SCAN" locally or remotely via PowerShell.
2019-08-12T18:13:54.566        Volume 😄 (\Device\HarddiskVolume3) requires an Online Scan.  An Online Scan will automatically run as part of the next scheduled maintenance task.  Alternatively you may run "CHKDSK /SCAN" locally via the command line, or run "REPAIR-VOLUME <drive:> -SCAN" locally or remotely via PowerShell.
2019-08-12T18:11:52.115        Volume ?? (\Device\HarddiskVolumeShadowCopy1) requires an Online Scan.  An Online Scan will automatically run as part of the next scheduled maintenance task.  Alternatively you may run "CHKDSK /SCAN" locally via the command line, or run "REPAIR-VOLUME <drive:> -SCAN" locally or remotely via PowerShell.
2019-07-31T20:17:55.550        Volume 😄 (\Device\HarddiskVolume3) requires an Online Scan.  An Online Scan will automatically run as part of the next scheduled maintenance task.  Alternatively you may run "CHKDSK /SCAN" locally via the command line, or run "REPAIR-VOLUME <drive:> -SCAN" locally or remotely via PowerShell.
2019-07-21T22:02:56.582        Volume 😄 (\Device\HarddiskVolume3) requires an Online Scan.  An Online Scan will automatically run as part of the next scheduled maintenance task.  Alternatively you may run "CHKDSK /SCAN" locally via the command line, or run "REPAIR-VOLUME <drive:> -SCAN" locally or remotely via PowerShell.
2019-07-13T16:50:34.408        Volume 😄 (\Device\HarddiskVolume3) requires an Online Scan.  An Online Scan will automatically run as part of the next scheduled maintenance task.  Alternatively you may run "CHKDSK /SCAN" locally via the command line, or run "REPAIR-VOLUME <drive:> -SCAN" locally or remotely via PowerShell.
2019-07-13T16:45:36.060        Volume ?? (\Device\HarddiskVolumeShadowCopy1) requires an Online Scan.  An Online Scan will automatically run as part of the next scheduled maintenance task.  Alternatively you may run "CHKDSK /SCAN" locally via the command line, or run "REPAIR-VOLUME <drive:> -SCAN" locally or remotely via PowerShell.
2019-07-06T18:19:09.534        Volume 😄 (\Device\HarddiskVolume3) requires an Online Scan.  An Online Scan will automatically run as part of the next scheduled maintenance task.  Alternatively you may run "CHKDSK /SCAN" locally via the command line, or run "REPAIR-VOLUME <drive:> -SCAN" locally or remotely via PowerShell.
2019-06-30T20:59:55.408        Volume 😄 (\Device\HarddiskVolume3) requires an Online Scan.  An Online Scan will automatically run as part of the next scheduled maintenance task.  Alternatively you may run "CHKDSK /SCAN" locally via the command line, or run "REPAIR-VOLUME <drive:> -SCAN" locally or remotely via PowerShell.

Share this post


Link to post
Share on other sites

Could you provide the results please, the logs the error checking creates.

Share this post


Link to post
Share on other sites

Log Name:      Application
Source:        Chkdsk
Date:          04/09/19 22:19:02
Event ID:      26226
Task Category: None
Level:         Information
Keywords:      Classic
User:          N/A
Computer:      MiniPC
Description:
Chkdsk was executed in scan mode on a volume snapshot.  

Checking file system on 😧

Stage 1: Examining basic file system structure ...
                                                                                          2136064 file records processed.                                                        
File verification completed.
                                                                                          1000 large file records processed.                                  
                                                                                          0 bad file records processed.                                    

Stage 2: Examining file name linkage ...
                                                                                          2148098 index entries processed.                                                      
Index verification completed.
                                                                                       
                                                                                       

Stage 3: Examining security descriptors ...
Security descriptor verification completed.
                                                                                          6018 data files processed.                                          
CHKDSK is verifying Usn Journal...
                                                                                          33863296 USN bytes processed.                                                          
Usn Journal verification completed.

Windows has scanned the file system and found no problems.
No further action is required.

1953512447 KB total disk space.
 840053792 KB in 2128977 files.
    718612 KB in 6019 indexes.
   2295315 KB in use by the system.
     65536 KB occupied by the log file.
1110444728 KB available on disk.

      4096 bytes in each allocation unit.
 488378111 total allocation units on disk.
 277611182 allocation units available on disk.

----------------------------------------------------------------------


Stage 1: Examining basic file system structure ...

Stage 2: Examining file name linkage ...

Stage 3: Examining security descriptors ...

Windows has scanned the file system and found no problems.
No further action is required.

Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Chkdsk" />
    <EventID Qualifiers="0">26226</EventID>
    <Level>4</Level>
    <Task>0</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2019-09-04T19:19:02.000000000Z" />
    <EventRecordID>314315</EventRecordID>
    <Channel>Application</Channel>
    <Computer>MiniPC</Computer>
    <Security />
  </System>
  <EventData>
    <Data>

Checking file system on 😧

Stage 1: Examining basic file system structure ...
                                                                                          2136064 file records processed.                                                        
File verification completed.
                                                                                          1000 large file records processed.                                  
                                                                                          0 bad file records processed.                                    

Stage 2: Examining file name linkage ...
                                                                                          2148098 index entries processed.                                                      
Index verification completed.
                                                                                       
                                                                                       

Stage 3: Examining security descriptors ...
Security descriptor verification completed.
                                                                                          6018 data files processed.                                          
CHKDSK is verifying Usn Journal...
                                                                                          33863296 USN bytes processed.                                                          
Usn Journal verification completed.

Windows has scanned the file system and found no problems.
No further action is required.

1953512447 KB total disk space.
 840053792 KB in 2128977 files.
    718612 KB in 6019 indexes.
   2295315 KB in use by the system.
     65536 KB occupied by the log file.
1110444728 KB available on disk.

      4096 bytes in each allocation unit.
 488378111 total allocation units on disk.
 277611182 allocation units available on disk.

----------------------------------------------------------------------


Stage 1: Examining basic file system structure ...

Stage 2: Examining file name linkage ...

Stage 3: Examining security descriptors ...

Windows has scanned the file system and found no problems.
No further action is required.
</Data>
    <Binary>00982000AC932000A8932000000000007D1F0000000000000000000000000000</Binary>
  </EventData>
</Event>

Share this post


Link to post
Share on other sites

Do you have a custom size configured for the pagefile? If so, please let Windows manage the pagefile.

Now it's waiting for a BSOD to occur.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.

×
×
  • Create New...

Important Information

This site uses cookies - We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.