Solved Random BSOD (Maybe bad Driver)

[xtultegra]

This is a gaming computer: MOBO: Biostar 790GXE 128 M, CPU: Phenom II 940, GPU: ASUS Nvidia 660 GTX, 6 GB memory (2x2gb and 2x1gb), Hard Drive: Seagate Baracuda 1000GB, OS: Widows 7.

Nothing is or has been overclocked.

I have monitored system with apps and have no overheating issues.

I have run sfc /scannow and found no errors

I have a new 700 watt power supply

I have tried running system with just the two paired 2gb memory modules.

Frequent BSOD's. I have updated all drivers (I think). I have replaced, hard drive, and video card. I have tested memory modules with memtest. When I replaced video card the BSOD's stopped for a couple of days. I get them randomly. Sometimes as soon as I Log on to Window. I have run Checkdisc many times and have never gotten an error. I have scanned for viruses several times and have not found any. I have updated BIOS.

It seems to me that i get BSOD while gaming most often, but I can get them at any time.

Here is a list of the last few BSOD's

Driver IRQL Not less than or Equal
Stop: D1 ( 18, 2, 0, FFFFF8800168C0D8)

SYSTEM_SERVICE_EXCEPTION
Stop: 3B (C0000005, FFFFF80002FC39BC, FFFFF880096FEE30, 0)

MEMORY_MANAGEMENT
Stop: 1A ( 41287, 1201300000, 0, 0)

PFN_LIST_CORRUPT
Stop: 4E (2, 121F9F, 19FFFFF, 1)

BAD_POOL_CALLER
Stop: C2 (7, 109B, 61006B, 0xFFFFF8A004347642)

 

[koolkat77]

Hi xtultegra and welcome to seven forums.

Could be caused by Avast! antivirus or RAM.

Security App

aswRvrt.sys                 Thu May  9 14:47:02 2013 (518B6286)
aswVmm.sys                  Thu May  9 14:47:06 2013 (518B628A)
aswTdi.SYS                  Thu May  9 14:47:32 2013 (518B62A4)
aswSnx.SYS                  Thu May  9 14:48:30 2013 (518B62DE)

Crashes indicate avast! being a possible cause. Remove and replace with Microsoft Security Essentials to see if it provides more stability. Uninstallers (removal tools) for common antivirus software. Microsoft Security Essentials and Malwarebytes are recommended from a strict BSOD perspective. They do not cause blue screens on the system as other AV products do.

Microsoft Security Essentials, Free antivirus for windows and Malwarebytes Anti-Malware Free

   Information

• :warn: Do not start the free trial of MalwareBytes, unselect that option when prompted.
  
  
  
  
  
• :tip: Update and make full scans with both separately.

Memtest86+

Run Memtest86+ for at least 8-10 passes. It may take up to 20 passes to find problems. Make sure to run it once after the system has been on for a few hours and is warm, and then also run it again when the system has been off for a few hours and is cold. How to Test and Diagnose RAM Issues with Memtest86+

   Note

Pay close attention to part 3 of the tutorial in order to rule the faulty RAM stick out.

   Tip

Do this test overnight.

Let us know the results.

BSOD BUGCHECK SUMMARY

Built by: 7601.18113.amd64fre.win7sp1_gdr.130318-1533
Debug session time: Mon Jun 10 11:13:10.652 2013 (UTC + 6:00)
System Uptime: 0 days 0:00:23.152
BugCheck 1A, {41287, 69f, 0, 0}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+454f5 )
BUGCHECK_STR:  0x1a_41287
PROCESS_NAME:  LogonUI.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.18113.amd64fre.win7sp1_gdr.130318-1533
Debug session time: Mon Jun 10 10:25:17.195 2013 (UTC + 6:00)
System Uptime: 0 days 0:02:51.912
BugCheck 1A, {41287, 1201300000, 0, 0}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+454f5 )
BUGCHECK_STR:  0x1a_41287
PROCESS_NAME:  AvastSvc.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

 

[xtultegra]

Thanks for the quick reply. I will uninstall Avast and see how that goes, then I will do memtest over night tomorrow.

 

[koolkat77]

Best of luck.

 

[xtultegra]

Uninstalled avast, bought 4 gigs of new memory. Still crashing.

Newest Dump: see attachment.View attachment 273321

 

[koolkat77]

Not much I can say.

Built by: 7601.18113.amd64fre.win7sp1_gdr.130318-1533
Debug session time: Wed Jun 19 13:44:08.118 2013 (UTC + 6:00)
System Uptime: 0 days 3:24:27.804
BugCheck 4E, {9a, b5100, 2, 0}
Probably caused by : CLASSPNP.SYS ( CLASSPNP!TransferPktComplete+1ce )
BUGCHECK_STR:  0x4E_9a
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

Driver Verifier

Let's run driver verifier and see if it catches any misbehaving drivers: Driver Verifier - Enable and Disable

You could go through these links as well:
Thermal Paste and How To Use It | techPowerUp
Avoid Static Damage to Your PC | PCWorld
Power Supply Information and Selection - Tech Support Forum
Basic computer troubleshooting
How To Clear CMOS
How to clean your PC of dust and dirt
How to clean a computer

 

[xtultegra]

Thanks for the quick reply. I will uninstall Avast and see how that goes, then I will do memtest over night tomorrow.

Not much I can say.

Built by: 7601.18113.amd64fre.win7sp1_gdr.130318-1533
Debug session time: Wed Jun 19 13:44:08.118 2013 (UTC + 6:00)
System Uptime: 0 days 3:24:27.804
BugCheck 4E, {9a, b5100, 2, 0}
Probably caused by : CLASSPNP.SYS ( CLASSPNP!TransferPktComplete+1ce )
BUGCHECK_STR:  0x4E_9a
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

Driver Verifier

Let's run driver verifier and see if it catches any misbehaving drivers: Driver Verifier - Enable and Disable


Thanks, Will do!

 

[xtultegra]

newest dump

 

[koolkat77]

There's none.

Configure dumps

First, we want to make sure the computer is saving your dump files. Go to Control Panel -> System -> Advanced System Settings -> Startup and Recovery [Settings] Make sure that "Write Debugging Information" is set to Small Memory Dump (256kb) if it is not already.

http://www.sevenforums.com/tutorials/174459-dump-files-configure-windows-create-bsod.html
​

Next, make sure that the folder C:\Windows\Minidump exists. If not, create it (allow permission if asked). Make sure any dumps you want to analyze, whether yours or others', are in this folder. You can ZIP/RAR the files and send them to someone else to analyze as well.

 

[xtultegra]

Hmm used the tool from this site and did grab all, but didn't work I guess so here they are pasted from Minidump file.

 

[Arc]

Scan the system for possible virus infection with the following programs.

• Anti-rootkit utility TDSSKiller
• Windows Defender Offline

Do some Disc checks.

1. Re-seat the sata and power.
   
   
2. Run chkdsk /f/r, following the option two of the tutorial Disk Check
3. 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.

Let us know the results.

 

[xtultegra]

After installing new memory. Corsair 555-12. I seemed to be having even more BSOD's so I ran memtest and found brand new memory bad. I replaced it with old OCZ (2 gig) that I knew to be good and memtest past so I will be sending back memory and starting over!

 

[Arc]

Are you suggested to change memory? I have noticed that you are suggested to do memtest, but you havent posted the result.

Similarly you havent posted the results of virus scan and disc check.

 

[xtultegra]

Update

Have replaced memory again. TDSSKiller found nothing, Defender found nothing, Seagate Scan found nothing. I am still getting frequent BSOD. I am running verifier now and will upload results in a day or two. One thing I have noticed is that I hear a slight buzzing noise before and during crash, it sounds a bit like the noise the hard drive makes while writing but louder and seems to come from the MOBO not the hard drive. The MOBO is about the only piece of hardware I have not replaced. Bios is current but I wonder if flashing it would be worth trying?

 

[Arc]

Before replacing the motherboard, let us wait for the DV enabled crash dumps.

 

[xtultegra]

DV Related Crash Dumps

Before last two crashes i reseated everything on the MOBO.

 

[Arc]

It is some ASUS bloatware which is too old by itself.

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

Use !analyze -v to get detailed debugging information.

BugCheck C9, {226, fffff88008ddf734, fffff98016fe4ee0, 0}

Unable to load image IOMap64.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for [COLOR=Red][B]IOMap64.sys[/B][/COLOR]
*** ERROR: Module load completed but symbols could not be loaded for [COLOR=Red][B]IOMap64.sys[/B][/COLOR]
Probably caused by : [COLOR=Red][B]IOMap64.sys[/B][/COLOR] ( IOMap64+1734 )

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

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DRIVER_VERIFIER_IOMANAGER_VIOLATION (c9)
The IO manager has caught a misbehaving driver.
Arguments:
Arg1: 0000000000000226, An IRP dispatch handler has returned without passing down or completing this IRP,
    or someone forgot to return STATUS_PENDING.
Arg2: fffff88008ddf734, The address in the driver's code where the error was detected.
Arg3: fffff98016fe4ee0, IRP address.
Arg4: 0000000000000000

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


BUGCHECK_STR:  0xc9_226

DRIVER_VERIFIER_IO_VIOLATION_TYPE:  226

FAULTING_IP: 
IOMap64+1734
fffff880`08ddf734 4883ec28        sub     rsp,28h

FOLLOWUP_IP: 
IOMap64+1734
fffff880`08ddf734 4883ec28        sub     rsp,28h

IRP_ADDRESS:  fffff98016fe4ee0

DEVICE_OBJECT: fffffa8007dd0da0

CUSTOMER_CRASH_COUNT:  2

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  Monitor.exe

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff800033674ec to fffff80002ed9c00

STACK_TEXT:  
fffff880`0bb30e28 fffff800`033674ec : 00000000`000000c9 00000000`00000226 fffff880`08ddf734 fffff980`16fe4ee0 : nt!KeBugCheckEx
fffff880`0bb30e30 fffff800`0337158a : fffff800`03365b00 fffff880`08ddf734 fffff980`16fe4ee0 00000000`00000000 : nt!VerifierBugCheckIfAppropriate+0x3c
fffff880`0bb30e70 fffff800`03372593 : 00000000`00000226 fffffa80`077c7818 fffff980`16fe4ee0 00000000`ffffffff : nt!ViErrorFinishReport+0xda
fffff880`0bb30ec0 fffff800`0337d8ac : 00000000`00000000 fffffa80`077c7760 fffffa80`077c7818 fffffa80`07dd0da0 : nt!VfErrorReport1+0x63
fffff880`0bb30f60 fffff800`0337dc73 : fffffa80`077c7760 00000000`00000002 fffffa80`07dd0da0 fffff800`033703b7 : nt!IovpCallDriver2+0x1bc
fffff880`0bb30fc0 fffff800`03383d3e : fffff980`16fe4ee0 fffff980`16fe4ee0 00000000`00000002 fffffa80`07dd0da0 : nt!VfAfterCallDriver+0x353
fffff880`0bb31010 fffff800`031e450f : fffff980`16fe4ee0 fffffa80`06909b30 00000000`00000000 fffffa80`077c7760 : nt!IovCallDriver+0x57e
fffff880`0bb31070 fffff800`031d2504 : 00000000`00000000 fffff8a0`02556040 fffffa80`08175e30 fffff800`02ee2e4c : nt!IopCloseFile+0x11f
fffff880`0bb31100 fffff800`031d22c1 : fffff8a0`02556040 fffff8a0`00000001 fffff8a0`02556040 00000000`00000000 : nt!ObpDecrementHandleCount+0xb4
fffff880`0bb31180 fffff800`03194040 : 00000000`00000164 fffff8a0`02556040 fffff8a0`03154590 00000000`00000164 : nt!ObpCloseHandleTableEntry+0xb1
fffff880`0bb31210 fffff800`03193f34 : 00000000`00000004 00000000`00000000 fffffa80`06909b30 fffff800`03181391 : nt!ObpCloseHandleProcedure+0x30
fffff880`0bb31250 fffff800`031945d2 : fffff8a0`0314d001 fffff880`0bb315c0 fffffa80`06909b30 00000000`00010282 : nt!ExSweepHandleTable+0x74
fffff880`0bb31290 fffff800`031afc72 : fffff8a0`0314d060 00000000`00000000 00000000`00000000 00000000`00000000 : nt!ObKillProcess+0x62
fffff880`0bb312d0 fffff800`03195dbd : 00000000`40010004 fffff900`00812001 00000000`7efdb000 fffffa80`07e3f060 : nt!PspExitThread+0x522
fffff880`0bb313d0 fffff800`02ecc71a : fffffa80`00000028 00000000`00000000 00000000`00000000 00000000`00000000 : nt!PsExitSpecialApc+0x1d
fffff880`0bb31400 fffff800`02ecca60 : 00000000`000ce300 fffff880`0bb31480 fffff800`03195d30 00000000`00000001 : nt!KiDeliverApc+0x2ca
fffff880`0bb31480 fffff800`02ed8f37 : fffffa80`06916590 00000000`7efdb000 00000000`00000020 00000000`7efdc024 : nt!KiInitiateUserApc+0x70
fffff880`0bb315c0 00000000`77901206 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExit+0x9c
00000000`000ce280 fffff800`02ed1250 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77901206
fffff880`0bb317a0 fffffa80`08366520 : fffffa80`06916698 fffff880`0bb31900 fffff880`02fd5180 00000000`00000000 : nt!KiCallUserMode
fffff880`0bb317a8 fffffa80`06916698 : fffff880`0bb31900 fffff880`02fd5180 00000000`00000000 fffff880`0bb31db0 : 0xfffffa80`08366520
fffff880`0bb317b0 fffff880`0bb31900 : fffff880`02fd5180 00000000`00000000 fffff880`0bb31db0 5ec8b3a4`0da172ad : 0xfffffa80`06916698
fffff880`0bb317b8 fffff880`02fd5180 : 00000000`00000000 fffff880`0bb31db0 5ec8b3a4`0da172ad 8494dbd0`c9186967 : 0xfffff880`0bb31900
fffff880`0bb317c0 00000000`00000000 : fffff880`0bb31db0 5ec8b3a4`0da172ad 8494dbd0`c9186967 75c712e6`3c56c10d : 0xfffff880`02fd5180


STACK_COMMAND:  .bugcheck ; kb

SYMBOL_NAME:  IOMap64+1734

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: IOMap64

IMAGE_NAME:  IOMap64.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4b6b7a96

FAILURE_BUCKET_ID:  X64_0xc9_226_IOMap64+1734

BUCKET_ID:  X64_0xc9_226_IOMap64+1734

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

0: kd> lmvm IOMap64
start             end                 module name
fffff880`08dde000 fffff880`08de7000   IOMap64  T (no symbols)           
    Loaded symbol image file: IOMap64.sys
    Image path: IOMap64.sys
[COLOR=Red]    Image name: IOMap64.sys
    Timestamp:        Fri Feb 05 07:25:34 2010[/COLOR] (4B6B7A96)
    CheckSum:         00013681
    ImageSize:        00009000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

I'd recommend you to http://www.sevenforums.com/tutorials/219576-clean-up-factory-bloatware.html, with a special reference to Point #13

13. Consider a Clean Reinstall - Factory OEM Windows 7 which is often better than getting a new computer considering how pre-installed bloatware can corrupt Windows 7 even if it's completely cleaned up.

 

[xtultegra]

Did clean reinstall. No BSOD for 3 days now! Thanks guys!

 

[koolkat77]

Good to hear. Thanks Arc for the help in this thread.
Post if you have further issues.

 

[xtultegra]

Serious crashfest going on now! Cannot do anything for more than a few minutes.