BSOD unexpected shutdown error

Status
This thread has been Locked and is not open to further replies. Please start a New Thread if you're having a similar issue. View our Welcome Guide to learn how to use this site.

L22

Thread Starter
Joined
Jan 14, 2015
Messages
64
Hi

For a few weeks now I have been getting recurring BSODs. I ran a memory and disk check and the BSODs stopped for a few days. Then today I got another BSOD.

I'm also a bit confused as to how to read a minidump file. I used the program WhoCrashed and it came up with this:

[FONT=Segoe UI, Arial]6 crash dumps have been found and analyzed. A third party driver has been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:

[FONT=Segoe UI, Arial]pwipf6.sys (pwipf6, Privacyware/PWI, Inc.)[/FONT]


[FONT=Segoe UI, Arial]Not too sure how to update this particular driver.[/FONT]
[/FONT]

Thanks

Tech Support Guy System Info Utility version 1.0.0.2
OS Version: Microsoft Windows 7 Home Premium, Service Pack 1, 32 bit
Processor: Intel(R) Core(TM) i3 CPU 530 @ 2.93GHz, x64 Family 6 Model 37 Stepping 2
Processor Count: 4
RAM: 3548 Mb
Graphics Card: Intel(R) HD Graphics, 1550 Mb
Hard Drives: C: Total - 953766 MB, Free - 823059 MB;
Motherboard: ASUSTeK Computer INC., P7H55-M
Antivirus: avast! Antivirus, Updated and Enabled
 

blues_harp28

Trusted Advisor
Spam Fighter
Joined
Jan 9, 2005
Messages
18,924
Hi, pwipf6.sys
Relates to either Webroot firewall or Private firewall.
Do you have one of the above installed?
If yes, uninstall and then re-install.
 

L22

Thread Starter
Joined
Jan 14, 2015
Messages
64
Got a new BSOD today.

WhoCrashed says:

[FONT=Segoe UI, Arial]7 crash dumps have been found and analyzed. 2 third party drivers have been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:

[/FONT]aswmonflt.sys (avast! File System Minifilter for Windows 2003/Vista, AVAST Software)


I'm not sure whether I should reinstall avast or what.
 

L22

Thread Starter
Joined
Jan 14, 2015
Messages
64
OK. I did as you said. Will wait and see if another one occurs :)
 

L22

Thread Starter
Joined
Jan 14, 2015
Messages
64
Not so lucky, unfortunately. :(

I got another one today. Windows seems to think I might have a memory problem so I ran a memory diagnostic scan and it came up with nothing.

Whocrashed also says it's a memory problem as well. It says:

This was probably caused by the following module: [FONT=Segoe UI, Arial]dxgmms1.sys[/FONT] (dxgmms1+0x1FF9B)
Bugcheck code: 0x50 (0xFFFFFFFF920058CC, 0x0, 0xFFFFFFFF95E1FF9B, 0x0)
Error: [FONT=Segoe UI, Arial]PAGE_FAULT_IN_NONPAGED_AREA[/FONT]
file path: C:\Windows\system32\drivers\dxgmms1.sys
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: DirectX Graphics MMS
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.

 

blues_harp28

Trusted Advisor
Spam Fighter
Joined
Jan 9, 2005
Messages
18,924
Post the Minidump files so we can check them with the Windows debugging program.

Create a new folder on the desktop and call it dumpfiles [or something similar]

Look in c:\windows\minidump
Copy the last 5 minidump files to that folder.
Close the folder and right click on it and select Send To Compressed [zipped] Folder.
Windows will compress the file and then save the new zipped file in the same location.

Use the 'manage attachments' in the 'Go Advanced' reply window to upload that zip file here as an attachment.
======
Some reasons for blue screens
New hardware - software installed.
Device driver - Video driver - corrupted - faulty.
Faulty Ram - Overheating - Dying hard drive etc.
As you have had 3 different blue screens in as many days - you may need to run an external memory test from a DVD.
But we will come back to that.
 

blues_harp28

Trusted Advisor
Spam Fighter
Joined
Jan 9, 2005
Messages
18,924
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except,
it must be protected by a Probe. Typically the address is just plain bad or it
is pointing at freed memory.

Debugging Details:
------------------
Could not read faulting driver name

READ_ADDRESS: GetPointerFromAddress: unable to read from 82db884c
Unable to read MiSystemVaType memory at 82d97f00
920058cc

FAULTING_IP:
dxgmms1!VIDMM_DEVICE::RemoveCommitment+1b
95e1ff9b 8b710c mov esi,dword ptr [ecx+0Ch]

MM_INTERNAL_CODE: 0

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0x50

PROCESS_NAME: System

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from 82c8faa8 to 82cdca1d

STACK_COMMAND: kb

FOLLOWUP_IP:
dxgmms1!VIDMM_DEVICE::RemoveCommitment+1b
95e1ff9b 8b710c mov esi,dword ptr [ecx+0Ch]

SYMBOL_STACK_INDEX: 2

SYMBOL_NAME: dxgmms1!VIDMM_DEVICE::RemoveCommitment+1b

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: dxgmms1

IMAGE_NAME: dxgmms1.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 539e3d5f

FAILURE_BUCKET_ID: 0x50_dxgmms1!VIDMM_DEVICE::RemoveCommitment+1b

BUCKET_ID: 0x50_dxgmms1!VIDMM_DEVICE::RemoveCommitment+1b

Followup: MachineOwner
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

BAD_POOL_CALLER (c2)
The current thread is making a bad pool request. Typically this is at a bad IRQL level or double freeing the same allocation, etc.
Arguments:
Arg1: 00000007, Attempt to free pool which was already freed
Arg2: 0000109b, (reserved)
Arg3: 0a830883, Memory contents of the pool block
Arg4: c29547d8, Address of the block of pool being deallocated

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

*** WARNING: Unable to verify timestamp for aswMonFlt.sys
*** ERROR: Module load completed but symbols could not be loaded for aswMonFlt.sys
GetPointerFromAddress: unable to read from 82d8584c
Unable to read MiSystemVaType memory at 82d64f00
======
The server was busy but got enough information.
The 2 minidumps from today - 30th Jan 2015

aswMonFlt.sys
Avast again - it does not like your pc!
http://www.systemlookup.com/Drivers/635-aswMonFlt_sys.html

I would uninstall Avast and try one of the following anti-virus programs.
Microsoft Security Essentials.
http://windows.microsoft.com/en-GB/windows/security-essentials-download

Avg.
http://free.avg.com/gb-en/homepage
======
BAD_POOL_CALLER - can relate to faulty Ram - but let us know if changing the anti-virus program solves the problem.
======
======
Edit
I would still run a Mem Test.
http://www.memtest.org/
Scroll down to 'Download (Pre-built & ISOs)'
'Download - Pre-Compiled Bootable ISO (.zip)'

Download the ISO file then burn the ISO to a Cd.
Start the Pc using the Cd and run the memory test overnight or for at least 8 passes.

It is best to run a full scan on individual Ram sticks if you can.
Or run the test but if any errors are shown - then remove all sticks of Ram and test each Ram stick one at a time.

Guide to using Memtest86+
http://www.bleepingcomputer.com/forums/topic207910.html
======
======
The problem could be faulty Ram and it finds the so called weak spot in the system and that may be Avast in this case.
So if you want to stay with Avast - run the MemTest first.
 

L22

Thread Starter
Joined
Jan 14, 2015
Messages
64
Ok. I might need to get some help checking the ram sticks from someone. (Don't even know where they are lol) But I should be ok. I'll report back once that's all done. Thanks again!
 

blues_harp28

Trusted Advisor
Spam Fighter
Joined
Jan 9, 2005
Messages
18,924
Just ran your first blue screen [pwipf6.sys] in the Debugging Tool and it mentioned 'Memory Management'
Run the MemTest with all the Ram sticks in place - if it finds any errors, you may need to test each stick.
 

L22

Thread Starter
Joined
Jan 14, 2015
Messages
64
I got 3 errors detected on memtest. Also I uninstalled avast and installed AVG.
 
Status
This thread has been Locked and is not open to further replies. Please start a New Thread if you're having a similar issue. View our Welcome Guide to learn how to use this site.

Users Who Are Viewing This Thread (Users: 0, Guests: 1)

As Seen On
As Seen On...

Welcome to Tech Support Guy!

Are you looking for the solution to your computer problem? Join our site today to ask your question. This site is completely free -- paid for by advertisers and donations.

If you're not already familiar with forums, watch our Welcome Guide to get started.

Join over 807,865 other people just like you!

Latest posts

Members online

Top