Solved Win7 x64 Ultimate, BSODs constant in last few weeks

[Grunter]

Howdy!
I have had a few BSOD's lately, had not had one for a week and believed the problem solved with doing a clean install of the nvidia current video driver. However today upon booting the computer for the first time today I got a 0x050 PAGE_FAULT_IN_NONPAGED_AREA, I rebooted and everything was fine, shut down the machine and then after 4 hrs came back, turned on and got a BSOD on windows booting into the user 0x01e KMODE_EXCEPTION_NOT_HANDLED

I am actually getting agrivated and not sure where to go from here. I have attached the zip, hopefully someone can help me out. Thank you

 

[Arc]

Hello Grunter.

Avast is causing the BSODs here.

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {41790, fffffa8015a20d20, ffff, 0}

*** WARNING: Unable to verify timestamp for [URL="http://www.carrona.org/drivers/driver.php?id=aswSnx.SYS"]aswSnx.SYS[/URL]
*** ERROR: Module load completed but symbols could not be loaded for [URL="http://www.carrona.org/drivers/driver.php?id=aswSnx.SYS"]aswSnx.SYS[/URL]
Probably caused by : [URL="http://www.carrona.org/drivers/driver.php?id=aswSnx.SYS"]aswSnx.SYS[/URL] ( aswSnx+2eebf )

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

Description here: Driver Reference Table - aswSnx.SYS

And again .....

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff8800bdb3d53, fffff880096a5c70, 0}

Probably caused by : [URL="http://www.carrona.org/drivers/driver.php?id=aswMonFlt.sys"]aswMonFlt.sys[/URL] ( aswMonFlt+5d53 )

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

Description here: http://www.carrona.org/drivers/driver.php?id=aswMonFlt.sys

Uninstall Avast using Avast Uninstall Utility. Use Microsoft Security Essentials as your antivirus with windows inbuilt firewall, and free MBAM as the on demand scanner.
Download, install and update those, and then run full system scans with both of them, one by one.

Let us know the results.

 

[Grunter]

Removed avast and when booting after the safe mode boot for removal logged in and as everything was loading got BSOD APC_INDEX_MISMATCH 0x00000001
Ive included the files after the BSOD, I had added avast because in the past MSE let something in and I had to remove the virus, is AVG any better?
Thanks!

 

[Arc]

Your crash dumps are not showing any finite probable cause. In such a situation, it is better to 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.

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

 

[Grunter]

Howdy!
Thanks for your time, before I got to do this next part I got a BSOD again 0x01a MEMORY_MANEGMENT
I have the file for this one see if it shows anything
Thanks sooooo much for your help, I really appreciate it.

 

[Arc]

Better you take the suggestion as given earlier. Update the DV enabled crash dumps next time.

 

[Grunter]

Will do so, upon boot at the moment its crashing the application constantly

 

[Grunter]

Ok, I am there and followed the instructions but it only lists 2 drivers and both are Microsoft, it is not giving me a long list. Is there anything I am doing wrong?

Ok at this time was able to get more than 2 drivers in the list but they all show as a microsoft corp.
Also had another BSOD for ntfs.sys when trying to run this.

I am including the dump after this BSOD and the pervious one. Tried running the driver verifier again, only get windows drivers.

One question, would VMWare be causing these problems? Sorry I have not been able to driver verify, the list is just not pulling up as you requested

 

[Grunter]

Finally was able to run the verifier and get a huge list, rebooting the machine resulted in constant BSOD which would prompt into windows repair startup. Eventually got into safe mode to disable verifier and the one item that was the cause, or rather what was reported, was pdiports.sys
Im enclosing the new files after the 2 BSOD's with the Verifier running

 

[Arc]

The BSOD is caused by pdiports.sys; Portrait Displays low level device driver (c:\windows\system32\drivers\pdiports.sys)

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck C9, {21f, fffff88007df6970, fffff9800512ce10, 0}

Unable to load image \SystemRoot\system32\DRIVERS\PdiPorts.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for [URL="http://www.carrona.org/drivers/driver.php?id=PdiPorts.sys"]PdiPorts.sys[/URL]
*** ERROR: Module load completed but symbols could not be loaded for [URL="http://www.carrona.org/drivers/driver.php?id=PdiPorts.sys"]PdiPorts.sys[/URL]
Probably caused by : [URL="http://www.carrona.org/drivers/driver.php?id=PdiPorts.sys"]PdiPorts.sys[/URL] ( PdiPorts+1970 )

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

And the driver is historically old.

fffff880`07df5000 fffff880`07dfd000   PdiPorts T (no symbols)           
    Loaded symbol image file: PdiPorts.sys
    Image path: \SystemRoot\system32\DRIVERS\PdiPorts.sys
[COLOR=Red]    Image name: PdiPorts.sys
    Timestamp:        Fri Nov 17 06:01:16 2006[/COLOR] (455D02D4)
    CheckSum:         0000E8C4
    ImageSize:        00008000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Try to update it from Portrait Displays | Support | Technical Support For Branded Products . If any latest update is not available, uninstall that thing.

Let us know the results.

 

[Grunter]

Uninstalled and so far nothing, should I do another stress test without or just wait till there is another BSOD?

 

[Arc]

Just give it a due time .... observe the situation for a few days in normal condition.

If the problem is not cured by the uninstall, it will recur very shortly. A couple of days will be enough.

 

[Grunter]

And tadaa! 2 BSOD on login, 0x01a, setting up files, should I run the verifier?

 

[Arc]

Your crash dumps are not showing any finite probable cause.

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.
First run it with all the existing/installed RAM modules. If errors are reported, stop then and there. Otherwise run upto 8 passes.

If memtest comes 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.

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

 

[Grunter]

I will do so tonight, however running seatools seems the C: drive is faililng the short test, which might mean the drive is going bad?

 

[Arc]

I will do so tonight, however running seatools seems the C: drive is faililng the short test, which might mean the drive is going bad?

Chance is there, obviously. Seatool for dos: SeaTools | Seagate download

• Burn it in a blank cd. boot from the CD, click on "Accept", wait for it to finish detecting the drives, then in the upper left corner select "Basic Tests", then select "Long Test" and let it run.
• You can use Win32 DiscImager to create a bootable USB and run Seatools for DOS. Follow this post to know how to make a bootable Seatools USB.

Now, follow this post .... an option to repair the disc is there. If it is within repair, it will be done. Otherwise replace the HDD.

 

[Grunter]

Yea at the moment seatools is failing short tests every time with the following:
System.IndexOutOfRangeException: Index was outside the bounds of the array.
at SeaToolsforWindows.frmSTXMain.ProcessTestCompleted(Int32 xd)
at SeaToolsforWindows.frmSTXMain.Timer_Tick(Object sender, EventArgs e)
at System.Windows.Forms.Timer.OnTick(EventArgs e)
at System.Windows.Forms.Timer.TimerNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

According to Tom's Hardware should just go and replace the drive :/

 

[Arc]

If you want, you can. But if you take the long test and attempt the repair, nothing will be a loss

But, back your data up first, preferably externally.

 

[Grunter]

Thank you so much for your help, at this point backing up and RMing this HD