Windows 7 BSOD NO Dump File

[Joe S]

I've had trouble with BSODS and screen freezes on and of for a couple of weeks. Sometimes there is no dumpfile and sometimes there is nothing in event viewer. I uninstalled Avast free and the problem was gone for 4 days. I've tried almost everything. Cleaning out dust updating drivers sfc scannow/ diskcheck. I also reinstalled an image from before the problems started I had another this morning but no log I attacked what I've found relating to it. This is a Windows 7 64 bit with 8 gig ram and a NVIDIA GT 9800 video card. It's a HP dt500.
Joe

 

[Trouble]

Hey Joe:
Good to hear from you again, it's been awhile. Wish it could be under better circumstances. Would you please;
First make sure your machine is configured properly to facilitate the collection of .dmp files.

Go to Start and type in sysdm.cpl 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 (256 kB) in the dropdown box
Ensure that the Small Dump Directory is listed as %systemroot%\Minidump << where your .dmp files can be
found later.
Click OK twice to exit the dialogs, then reboot for the changes to take effect.

Then:
Please read the first post in this sticky thread here Link Removed
Do your best to accumulate the data required.
Run the SF Diagnostic tool (download and right click the executable and choose run as administrator)
Download and run CPUz. Use the Windows snipping tool to gather images from all tabs including all slots populated with memory under the SPD tab.
Likewise RAMMon. Export the html report, put everything into a desktop folder that you've created for this purpose, zip it up and attach it to your next post (right click it and choose send to, compressed (zipped) folder.
If you can do this we'll have a look and see if we can help find the culprit.
Regards
Randy

 

[Joe S]

Randy
Thanks It is enabled and sometimes it creates a mini dump and other times not. I did just find the memory dump file from then. I'll check and see what I can find. Most of these have seemed to come 15-20 min after an anitvirus update while I am using firefox. I thought getting rid of Avast took care of the problem until this morning.
Joe

 

[Trouble]

What did you replace Avast with?
Generally in the interest of BSOD peace of mind, we recommend MSE from here Link Removed due to 404 Error seems to be BSOD friendly, a decent product, small footprint overall and free for personal use for up to 10 computers.

 

[Joe S]

I went with AVG I used it before. It's frustrating the way they keep updating security software and try and make a complete package and ruin good products in the process. If the problem continues I may try the MS program. I wasn't that impressed with it in Windows 8. I like it to auto update and give a notification. I'm getting ready to go through the steps in your earlier post. The only hardware I've added was an internal drive late last year. I did replace the video card 2 years ago. I bad driver messed up the old one. Over the winter I pulled the heat sink and redid the thermal paste. I just put it away as a spare. I just noticed the memory dump setting got changed to kernal dump so I changed it back to small minidump.
Joe

 

[Trouble]

Sorry for the late reply. Jury duty today and just got back.
Agreed, some AV products can be a bit over zealous and actually cause some aggravation as well as in some rare instances BSODs. We've seen that a bit with Norton, McAfee as well as AVG. I suspect that is generally an issue with remnants left over from old products and or corrupted installations of newer products but it does happen.
I suspect that is at least one of the reasons why the top tier AV manufacturers all have their own vendor specific proprietary removal tools.
Link Removed
Link Removed
Link Removed
and there are lists like this one Link Removed that provide some help with locating uninstallers.
When you get around to collecting the data referenced in my earlier post. Zip it up and attach it here and we'll have a look.
Regards
Randy

 

[Joe S]

Randy
I got more BSODs today and rebooted and got another before I could find anything. I got one this afternoon and rebooted and ran checkdisk with repair checked and it appeared OK. That first one today I was in Firefox. Now I'm beginning to get them when I boot into safe mode I can't even get much of a peek at dump file with Who Crashed. One BSOD mentioned NTOSKRNL.EXE The last one had IRQL not less or equal. Do you think it's a hardware error? Would a repair install work? I hate to go thru reinstall or reimage if it's a hardware issue. What's frustrating is after I took off Avast and added the AVG it worked for 4 days. I've got an image from just after the July MS updates when everything was OK. I have a few earlier on more than one drive. I was wondering about ram or the video card
Thanks for your help.
Joe

 

[Trouble]

Actually it sounds suspiciously like a possible infection. So..... try running an offline scanner, this one will help you make a bootable CD What is Windows Defender Offline? (get the right version for your architecture) boot from the CD and run a full scan. Program defaults to quick scan so change it to full and run the scan.
You can also check your memory offline and independent of your OS

Download Memtest86+ from this location here. Burn the ISO to a CD and boot the computer from the CD from a cold boot after leaving it off for an hour or more.
Ideally let it run for at least 7 passes / 6-8 hours. If errors appear before that you can stop that particular test. Any time Memtest86+ reports errors, it can be either bad RAM or a bad Mobo slot. Perform the test RAM sticks individually as well as all possible combinations. When you find a good one then test it in all slots. Post back with the results.
See this Guide to using Memtest 86+

I'd really like to see the contents of C:\Windows\minidump
you could possibly boot to a Live CD a Linux Distro and copy it off that way, if you can't even boot into safemode, then a inplace repair might be an option Link Removed and if you have Sp1 installed you will likely need to get the install media you need from here Link Removed
But you'll likely have problems as it requires you to be booted into Windows in order to start such a repair.
Just throwing ideas out there. Without the dump files it's difficult to say with any degree of accuracy and even with the dump files, if it's crashing early on in the boot process there may not be a lot to see.

 

[Joe S]

Randy
I had A UBCD 4 Windows and retrieved 3 dumps I'll attach them. It only showed 4 gigs or ram in specs then I realized it was probably a 32 bit setup. I ran the MS Stand Alone sweeper and it didn't turn up anything. I ran startup repair 3 times it didn't find anything. The MS memory test is going now. I'll do the Mem Test as soon as I can.
Thanks alot
JoeLink Removed

 

[RingAnimated]

Im not a pro at dmp debugging, but you're bsod's are all over the place. By what i know this can mean a virus or a faulty MOBO.

csrss.exe was mentioned in one, this is a vital runtime process. A virus could be disturbing windows processes. Try using McAfee &ndash; Computer Anti-Virus Software and Internet Security For Your PC (this is a link to Stinger) as it is very good for picking up nasty infections.

 

[Trouble]

Randy
I had A UBCD 4 Windows and retrieved 3 dumps I'll attach them. It only showed 4 gigs or ram in specs then I realized it was probably a 32 bit setup. I ran the MS Stand Alone sweeper and it didn't turn up anything. I ran startup repair 3 times it didn't find anything. The MS memory test is going now. I'll do the Mem Test as soon as I can.
Thanks alot
Joe

Don't forget, if you haven't already, run a HDD Diagnostic, usually the top tier vendors have something that you can use offline. Like SeaTools for DOS, not sure what western Digital has now.
Interestingly your most recent dump file is upset about
tdrpm273.sys 8/10/2010 I believe that is part of the Acronis True Image "Try and Decide" applet

fffff880`04012968  fffff880`01cb0700 [U][B]Unable to load image tdrpm273.sys[/B][/U], Win32 error 0n2
*** WARNING: [U][B]Unable to verify timestamp for tdrpm273.sys[/B][/U]
*** ERROR: Module load completed but symbols could not be loaded for [U][B]tdrpm273.sys[/B][/U]
[U][B] tdrpm273[/B][/U]+0x43700

Not sure that, that particular piece of information is definitive as it doesn't look all that old, but could I suppose have become corrupt. Easy enough to uninstall True Image, confirm that, that driver is no longer in C:\Windows\System32\Drivers, reboot and see if that helps the problem.
DUMP 082012-25240-01.dmp:

BugCheck 18, {0, fffffa8009155dd0, 4, ffffffffffffffff}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+19da3 )
REFERENCE_BY_POINTER (18)
Arguments:
Arg1: 0000000000000000, Object type of the object whose reference count is being lowered
Arg2: fffffa8009155dd0, Object whose reference count is being lowered
Arg3: 0000000000000004, Reserved
Arg4: ffffffffffffffff, Reserved
    The reference count of an object is illegal for the current state of the object.
    Each time a driver uses a pointer to an object the driver calls a kernel routine
    to increment the reference count of the object. When the driver is done with the
    pointer the driver calls another kernel routine to decrement the reference count.
    Drivers must match calls to the increment and decrement routines. This bugcheck
    can occur because an object's reference count goes to zero while there are still
    open handles to the object, in which case the fourth parameter indicates the number
    of opened handles. It may also occur when the object’s reference count drops below zero
    whether or not there are open handles to the object, and in that case the fourth parameter
    contains the actual value of the pointer references count.
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x18
PROCESS_NAME:  services.exe
CURRENT_IRQL:  0
LAST_CONTROL_TRANSFER:  from fffff8000393efb5 to fffff800038e21c0
STACK_TEXT:  
fffff880`04012908 fffff800`0393efb5 : 00000000`00000018 00000000`00000000 fffffa80`09155dd0 00000000`00000004 : nt!KeBugCheckEx
fffff880`04012910 fffff800`03910d43 : fffffa80`0626b380 00000000`00000000 00000000`00000000 fffff880`01cb0700 : nt! ?? ::FNODOBFM::`string'+0x19da3
fffff880`04012950 fffff800`03908fff : fffffa80`0873a620 fffff880`04012a80 fffffa80`0911bec8 00000000`0000002b : nt!MiWaitForInPageComplete+0x507
fffff880`04012a30 fffff800`038ef85a : 00000000`00000000 00000000`00000000 ffffffff`ffffffff fffff800`00000000 : nt!MiIssueHardFault+0x28b
fffff880`04012ac0 fffff800`038e02ee : 00000000`00000000 000007fe`fc7d700c 00000000`77302501 000007fe`fc7a0000 : nt!MmAccessFault+0x146a
fffff880`04012c20 00000000`771fdd9c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e
00000000`0012e9d0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x771fdd9c
nt! ?? ::FNODOBFM::`string'+19da3
fffff800`0393efb5 cc              int     3
SYMBOL_STACK_INDEX:  1
SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+19da3
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: nt
IMAGE_NAME:  ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP:  4fa390f3
FAILURE_BUCKET_ID:  X64_0x18_nt!_??_::FNODOBFM::_string_+19da3
BUCKET_ID:  X64_0x18_nt!_??_::FNODOBFM::_string_+19da3

DRIVERS PRESENT:

fffff880`01072000 fffff880`010b0000   1394ohci 1394ohci.sys Sat Nov 20 04:44:56 2010 (4CE7A6A8)
fffff880`00f7a000 fffff880`00fd1000   ACPI     ACPI.sys     Sat Nov 20 03:19:16 2010 (4CE79294)
fffff880`0132a000 fffff880`01335000   amdxata  amdxata.sys  Fri Mar 19 11:18:18 2010 (4BA3A3CA)
[U][B]fffff880`01df2000 fffff880`01dfc000   avgidsha avgidsha.sys Wed Apr 18 21:19:15 2012 (4F8F7623)
fffff880`01c61000 fffff880`01c6d000   avgrkx64 avgrkx64.sys Mon Jan 30 21:11:41 2012 (4F275BED)[/B][/U]
fffff880`02db9000 fffff880`02dc0000   beep     beep.sys     Mon Jul 13 19:00:13 2009 (4A5BCA8D)
fffff880`013e3000 fffff880`013f4000   blbdrive blbdrive.sys Mon Jul 13 18:35:59 2009 (4A5BC4DF)
fffff880`010b0000 fffff880`010da000   cdrom    cdrom.sys    Sat Nov 20 03:19:20 2010 (4CE79298)
fffff880`00d05000 fffff880`00dc5000   CI       CI.dll       Sat Nov 20 07:12:36 2010 (4CE7C944)
fffff880`00c00000 fffff880`00c30000   CLASSPNP CLASSPNP.SYS Sat Nov 20 03:19:23 2010 (4CE7929B)
fffff880`00ca7000 fffff880`00d05000   CLFS     CLFS.SYS     Mon Jul 13 18:19:57 2009 (4A5BC11D)
fffff880`01000000 fffff880`01072000   cng      cng.sys      Fri Jun 01 22:25:51 2012 (4FC987BF)
fffff880`010da000 fffff880`010ea000   CompositeBus CompositeBus.sys Sat Nov 20 04:33:17 2010 (4CE7A3ED)
fffff880`0340e000 fffff880`0341c000   crashdmp crashdmp.sys Mon Jul 13 19:01:01 2009 (4A5BCABD)
fffff880`01800000 fffff880`01816000   disk     disk.sys     Mon Jul 13 18:19:57 2009 (4A5BC11D)
fffff880`0341c000 fffff880`0342f000   dump_dumpfve dump_dumpfve.sys Mon Jul 13 18:21:51 2009 (4A5BC18F)
fffff880`02c7d000 fffff880`02d9b000   dump_iaStorV dump_iaStorV.sys Thu Jun 10 19:46:19 2010 (4C11875B)
fffff880`0342f000 fffff880`0343b000   Dxapi    Dxapi.sys    Mon Jul 13 18:38:28 2009 (4A5BC574)
fffff960`004b0000 fffff960`004ce000   dxg      dxg.sys      Mon Jul 13 18:38:28 2009 (4A5BC574)
fffff880`013c3000 fffff880`013d7000   fileinfo fileinfo.sys Mon Jul 13 18:34:25 2009 (4A5BC481)
fffff880`01145000 fffff880`01191000   fltmgr   fltmgr.sys   Sat Nov 20 03:19:24 2010 (4CE7929C)
fffff960`00800000 fffff960`00809000   framebuf framebuf.dll Mon Jul 13 18:38:47 2009 (4A5BC587)
fffff880`015d8000 fffff880`015e2000   Fs_Rec   Fs_Rec.sys   Wed Feb 29 21:41:06 2012 (4F4EEFD2)
fffff880`01bb5000 fffff880`01bef000   fvevol   fvevol.sys   Sat Nov 20 03:24:06 2010 (4CE793B6)
fffff880`01a26000 fffff880`01a70000   fwpkclnt fwpkclnt.sys Sat Nov 20 03:21:37 2010 (4CE79321)
fffff800`0381a000 fffff800`03863000   hal      hal.dll      Sat Nov 20 07:00:25 2010 (4CE7C669)
fffff880`02c4a000 fffff880`02c6e000   HDAudBus HDAudBus.sys Sat Nov 20 04:43:42 2010 (4CE7A65E)
fffff880`035de000 fffff880`035f7000   HIDCLASS HIDCLASS.SYS Sat Nov 20 04:43:49 2010 (4CE7A665)
fffff880`035f7000 fffff880`035ff080   HIDPARSE HIDPARSE.SYS Mon Jul 13 19:06:17 2009 (4A5BCBF9)
fffff880`035d0000 fffff880`035de000   hidusb   hidusb.sys   Sat Nov 20 04:43:49 2010 (4CE7A665)
fffff880`01c55000 fffff880`01c61000   hotcore3 hotcore3.sys Wed Jun 23 17:54:01 2010 (4C229089)
fffff880`01c4c000 fffff880`01c55000   hwpolicy hwpolicy.sys Sat Nov 20 03:18:54 2010 (4CE7927E)
fffff880`01680000 fffff880`0169e000   i8042prt i8042prt.sys Mon Jul 13 18:19:57 2009 (4A5BC11D)
fffff880`0120c000 fffff880`0132a000   iaStorV  iaStorV.sys  Thu Jun 10 19:46:19 2010 (4C11875B)
fffff880`02c6e000 fffff880`02c7d000   kbdclass kbdclass.sys Mon Jul 13 18:19:50 2009 (4A5BC116)
fffff880`03400000 fffff880`0340e000   kbdhid   kbdhid.sys   Sat Nov 20 04:33:25 2010 (4CE7A3F5)
fffff800`00ba1000 fffff800`00bab000   kdcom    kdcom.dll    Sat Feb 05 10:52:49 2011 (4D4D8061)
fffff880`034e7000 fffff880`0352a000   ks       ks.sys       Sat Nov 20 04:33:23 2010 (4CE7A3F3)
fffff880`015ac000 fffff880`015c7000   ksecdd   ksecdd.sys   Fri Jun 01 21:50:23 2012 (4FC97F6F)
fffff880`01600000 fffff880`0162a000   ksecpkg  ksecpkg.sys  Fri Jun 01 22:27:11 2012 (4FC9880F)
fffff880`00c44000 fffff880`00c93000   mcupdate mcupdate.dll Sat Nov 20 07:03:51 2010 (4CE7C737)
fffff880`015e2000 fffff880`015f1000   mouclass mouclass.sys Mon Jul 13 18:19:50 2009 (4A5BC116)
fffff880`00fe4000 fffff880`00ffe000   mountmgr mountmgr.sys Sat Nov 20 03:19:21 2010 (4CE79299)
fffff880`02c10000 fffff880`02c1b000   Msfs     Msfs.SYS     Mon Jul 13 18:19:47 2009 (4A5BC113)
fffff880`00fda000 fffff880`00fe4000   msisadrv msisadrv.sys Mon Jul 13 18:19:26 2009 (4A5BC0FE)
fffff880`01191000 fffff880`011ef000   msrpc    msrpc.sys    Sat Nov 20 03:21:56 2010 (4CE79334)
fffff880`01816000 fffff880`01821000   mssmbios mssmbios.sys Mon Jul 13 18:31:10 2009 (4A5BC3BE)
fffff880`01c3a000 fffff880`01c4c000   mup      mup.sys      Mon Jul 13 18:23:45 2009 (4A5BC201)
fffff880`016a4000 fffff880`01797000   ndis     ndis.sys     Sat Nov 20 03:23:30 2010 (4CE79392)
fffff880`01797000 fffff880`017f7000   NETIO    NETIO.SYS    Sat Nov 20 03:23:13 2010 (4CE79381)
fffff880`02c1b000 fffff880`02c2c000   Npfs     Npfs.SYS     Mon Jul 13 18:19:48 2009 (4A5BC114)
fffff800`03863000 fffff800`03e4b000   nt       ntkrnlmp.exe Fri May 04 03:18:59 2012 (4FA390F3)
fffff880`01409000 fffff880`015ac000   Ntfs     Ntfs.sys     Thu Mar 10 21:39:39 2011 (4D79997B)
fffff880`02db0000 fffff880`02db9000   Null     Null.SYS     Mon Jul 13 18:19:37 2009 (4A5BC109)
fffff880`00dc5000 fffff880`00ded000   nvraid   nvraid.sys   Fri Mar 19 15:59:20 2010 (4BA3E5A8)
fffff880`01335000 fffff880`01360000   nvstor   nvstor.sys   Fri Mar 19 15:45:11 2010 (4BA3E257)
fffff880`00e40000 fffff880`00e55000   partmgr  partmgr.sys  Sat Mar 17 00:06:09 2012 (4F641BC1)
fffff880`00e00000 fffff880`00e33000   pci      pci.sys      Sat Nov 20 03:19:11 2010 (4CE7928F)
fffff880`015c7000 fffff880`015d8000   pcw      pcw.sys      Mon Jul 13 18:19:27 2009 (4A5BC0FF)
fffff880`00c93000 fffff880`00ca7000   PSHED    PSHED.dll    Mon Jul 13 20:32:23 2009 (4A5BE027)
fffff880`013d7000 fffff880`013e2d00   PxHlpa64 PxHlpa64.sys Wed Mar 12 20:58:17 2008 (47D88A39)
fffff880`015f1000 fffff880`015fc000   rdpbus   rdpbus.sys   Mon Jul 13 19:17:46 2009 (4A5BCEAA)
fffff880`01c00000 fffff880`01c3a000   rdyboost rdyboost.sys Sat Nov 20 03:43:10 2010 (4CE7982E)
fffff880`01dac000 fffff880`01df2000   snapman  snapman.sys  Tue Aug 10 05:15:05 2010 (4C6126A9)
fffff880`01360000 fffff880`013c3000   storport storport.sys Thu Mar 10 22:30:23 2011 (4D79A55F)
fffff880`02dfe000 fffff880`02dff480   swenum   swenum.sys   Mon Jul 13 19:00:18 2009 (4A5BCA92)
fffff880`01823000 fffff880`01a26000   tcpip    tcpip.sys    Fri Mar 30 03:34:26 2012 (4F757012)
fffff880`01c6d000 fffff880`01da4000   tdrpm273 tdrpm273.sys Tue Aug 10 04:54:18 2010 (4C6121CA)
fffff880`00c30000 fffff880`00c44000   termdd   termdd.sys   Sat Nov 20 05:03:40 2010 (4CE7AB0C)
fffff880`01a70000 fffff880`01b59000   timntr   timntr.sys   Tue Sep 29 08:36:57 2009 (4AC20D79)
fffff960`00670000 fffff960`0067a000   TSDDD    TSDDD.dll    Mon Jul 13 19:16:34 2009 (4A5BCE62)
fffff880`0352a000 fffff880`0353c000   umbus    umbus.sys    Sat Nov 20 04:44:37 2010 (4CE7A695)
fffff880`035b3000 fffff880`035d0000   usbccgp  usbccgp.sys  Thu Mar 24 22:29:14 2011 (4D8C0C0A)
fffff880`035b1000 fffff880`035b2f00   USBD     USBD.SYS     Thu Mar 24 22:28:59 2011 (4D8C0BFB)
fffff880`02c39000 fffff880`02c4a000   usbehci  usbehci.sys  Thu Mar 24 22:29:04 2011 (4D8C0C00)
fffff880`0353c000 fffff880`03596000   usbhub   usbhub.sys   Thu Mar 24 22:29:25 2011 (4D8C0C15)
fffff880`0162a000 fffff880`01680000   USBPORT  USBPORT.SYS  Thu Mar 24 22:29:12 2011 (4D8C0C08)
fffff880`03596000 fffff880`035b1000   USBSTOR  USBSTOR.SYS  Thu Mar 10 22:37:16 2011 (4D79A6FC)
fffff880`02c2c000 fffff880`02c39000   usbuhci  usbuhci.sys  Thu Mar 24 22:29:03 2011 (4D8C0BFF)
fffff880`00e33000 fffff880`00e40000   vdrvroot vdrvroot.sys Mon Jul 13 19:01:31 2009 (4A5BCADB)
fffff880`02dc0000 fffff880`02dce000   vga      vga.sys      Mon Jul 13 18:38:47 2009 (4A5BC587)
fffff880`02dce000 fffff880`02df3000   VIDEOPRT VIDEOPRT.SYS Mon Jul 13 18:38:51 2009 (4A5BC58B)
fffff880`010f5000 fffff880`01131000   vmbus    vmbus.sys    Sat Nov 20 03:57:29 2010 (4CE79B89)
fffff880`02df3000 fffff880`02dfe000   VMkbd    VMkbd.sys    Sat Mar 26 00:31:22 2011 (4D8D7A2A)
fffff880`01b59000 fffff880`01b69000   vmstorfl vmstorfl.sys Sat Nov 20 03:57:30 2010 (4CE79B8A)
fffff880`00e55000 fffff880`00e6a000   volmgr   volmgr.sys   Sat Nov 20 03:19:28 2010 (4CE792A0)
fffff880`00e6a000 fffff880`00ec6000   volmgrx  volmgrx.sys  Sat Nov 20 03:20:43 2010 (4CE792EB)
fffff880`01b69000 fffff880`01bb5000   volsnap  volsnap.sys  Sat Nov 20 03:20:08 2010 (4CE792C8)
fffff880`02c00000 fffff880`02c10000   watchdog watchdog.sys Mon Jul 13 18:37:35 2009 (4A5BC53F)
fffff880`00ec7000 fffff880`00f6b000   Wdf01000 Wdf01000.sys Mon Jul 13 18:22:07 2009 (4A5BC19F)
fffff880`00f6b000 fffff880`00f7a000   WDFLDR   WDFLDR.SYS   Mon Jul 13 18:19:54 2009 (4A5BC11A)
fffff960`00000000 fffff960`00315000   win32k   win32k.sys   Wed Jul 18 13:14:37 2012 (5006FD0D)
fffff880`01131000 fffff880`01145000   winhv    winhv.sys    Sat Nov 20 03:20:02 2010 (4CE792C2)
fffff880`00fd1000 fffff880`00fda000   WMILIB   WMILIB.SYS   Mon Jul 13 18:19:51 2009 (4A5BC117)

Remnants of AVG please uninstall and follow up with this Removal Tool Link Removed (get the correct version for your architecture)
Regards
Randy

 

[Joe S]

I'll see what I can do I've got a family emergency now. I'll get back to it when I get a chance. Thanks for the help.
Joe

 

[Joe S]

Randy
So far I got rid of AVG and replaced it with MSE. I was running Windows 8 dual boot in a virtual hard disk. I deleted that and from boot choices. I uninstalled and reinstalled the Acronis TI. I put in the Windows 7 install disk and ran startup repair 3 times and the memory test in the repair choices. There is a HP diagnostics on boot screen so I ran that but nothing showed it includes memory and HD but they run pretty fast. I was wondering could low line voltage figure into the corruption for 2 reason? One the recent high heat and the common practice here of reducing voltage to give NYC city more power in heat waves. And about a week or so before all of this started we had a tornado touch down here and tear up a lot of power and phone lines. They've been working on a lot of the lines since then so there could be local fluctuations. I wonder if that could have caused some corruption problems that snowballed. I took a quick look at MemTest does that have to be tested one stick at a time? I'll see what I can find to test the HD with the OS on it it's a Hitachi 750 gig HDS721075 KLA330 in device manager.
When this started I opened the case and blew it out good but it wasn't bad. Would it be a good idea to open it up again and pull and reseat ram sticks?
The problem yesterday turned out to be nothing serious just ate up time for a trip to ER.
Thanks for the help.
Joe

 

[Trouble]

I wonder if that could have caused some corruption problems that snowballed. I took a quick look at MemTest does that have to be tested one stick at a time? I'll see what I can find to test the HD with the OS on it it's a Hitachi 750 gig HDS721075 KLA330 in device manager.
Would it be a good idea to open it up again and pull and reseat ram sticks?

With respect to re-seating your RAM sticks... That's not a bad idea although you'll likely be doing some of that during the course of running MemTest86+

Regarding MemTest86+..... It is never a bad idea to run the test using a single stick at a time as well as testing all slots with a single known good memory module.
Personally, I will generally boot from the CD and run the test through 7 or 8 passes on a cold machine (one that has been completely off and unplugged from AC power for a half hour or so) with all sticks first.
If that produces errors, that is when I begin the single stick / single slot testing and work through all possible combinations to see if I can find the culprit.

And any Brown Outs / Low Voltage conditions or power failures that result in a "Dirty Shutdown" can result in data corruption, which sometimes can be more problematic than others.
Two of your dump files that you supplied are STOP 0x0000000A (IRQL_NOT_LESS_OR_EQUAL) and the third is an STOP 0x00000018 (REFERENCE_BY_POINTER)
Link Removed

I would strongly suggest using the native Check Disk Utility

Launch an elevated command prompt (StartOrb->All Programs->Accessories->Command Prompt, right click it and choose Run As Administrator) and type
chkdsk C: /R
hit enter and answer Yes “Y” when prompted and reboot.
Let it run all five stages. When complete check the log file in Event Viewer for results (Click the StartOrb and type event viewer and hit enter, expand Windows Logs and highlight / select Application, click Action on the menu bar and select Find and type chkdsk and hit enter.

And see what it discovers. If you have difficulty doing this from within the OS you should be able to perform the same task from within the Windows 7 Recovery Environment by booting from the install media or a Windows 7 Repair Disk. If you don't have a repair disk we have both 32 and 64 bit versions available for our members in our Downloads sections here Link Removed due to 404 Error

Your Hitachi Drive

A: If you are experiencing problems with your drive or would just like to test the drive’s integrity, download and run the HGST Link Removed - Invalid URL.
If possible, we recommend that you backup any important data before running the test. Run the quick test first. If you are experiencing problems, but receive the result 0x00 try running the Advanced Test option. When you have completed the test, please Link Removed - Invalid URL with the results and our agents will be able to assist you on resolving the problem.

Link Removed due to 404 Error
AND
Link Removed due to 404 Error

 

[Joe S]

I've got to get some more CDs I think my autistic nephew used up the ones I had. In the process of sorting thru things I did update drivers for chipset, video, network cards and a couple other things. I tried installing something and got a popup about needing netframework 4.0. apparently the one included Windows 7 isn't the full version. I updated that and the MSE seems to preform better now. I also wonder if there could have been some problems from dual booting too. Sometimes it's like looking for a needle in big haystack finding the actual cause of a problem. I have run checkdisk several times but it didn't show anything. Also I did run the drive test that is apparenlty part of the HP bios and it didn't show anything either it was just a quick test. I keep all of my data backed up on more than one HD. I've got a second internal and some externals so I have 2 or 3 backup copies of everything important.
Thanks for the help
Joe

 

[Trouble]

Sometimes it's like looking for a needle in big haystack finding the actual cause of a problem.

A very accurate definition. That's almost exactly what it's like most of the time, except for the very few instances where the answer just jumps out at you and points directly to an offending driver. Otherwise it's often a process of elimination and only slightly educated guessing.
How is the machine running now. Are you still getting BSODs? If so, are they creating new dump files (.dmp) in the C:\Windows\minidump folder? I'd be happy to take a look to see if they are indicating any additional information we might be able to use.

 

[Joe S]

I hate to jinks anything but it seems fine now . The event logs look good the only noticeable item is the winnit warning where the Comodo firewall blocks internet access until it's running. I wish I'd thought of the USB4Wind disk when this started it does comes in handy. If I should get another BOD I'll use the disk to retrieve it before booting to Windows.
Thanks a lot
Joe

 

[Joe S]

I just had another BSOD I was watching a video on Youtube with Firefox. Last Night I did install No Script in Firefox. That and a new version Core Temp and firefox updated again are my only changes. I'll attach the file. Most all of these crashes have occured while in Firefox. The actual crash was about 8:09 I'd only been on about 5 min.
Joe

 

[RingAnimated]

Well it did say something about the flash player plugin. If you say most of the BSOD's happen while in FireFox, try using a different browser, like Comodo Dragon. Thats what i use and it's pretty awesome.

 

[Joe S]

It's frustrating figuring this all out I was watching videos last night no problems but tonight I only saw about 2 min of one and crash. I was just thinking that Flash just recently updated again in the past few days. For a quick memory test I booted up 3 virtual PCs and had the ram pushed to over 7.5 gig and let is set like that for a few minutes with no problems. It's frustrating that so many things update that are intertwined like browsers and flash etc. One more thing I thought of is I uninstalled Java too.
Thanks
Joe