Windows 7 Persistent BSOD and CTD problem

[Splendid Belt]

Hi. I've been having a persistent BSOD and CTD problem with my desktop PC for over a year now. It's getting to the point where it's unuseable.

I upgraded frmo Vista to Windows 7 in an attempt to resolve the issue, but sadly it's still there. I then went back and upgraded again as a 'fresh install' option, electing to remove all previous data, but even this didn't work.

Although interestingly, it's stored my previous data in a folder called 'Windows.old' which it won't let me delete, even though I have the admin (and only) account on the system. When I use cccleaner and similar programmes, it claims to fine registry problems in this folder which I'm unable to do anything about. Could this be the problem?

The pC is fine for general use, but the problem happens whenever I try to use it for gaming. I've scanned for malware using various utilities (I have AVG installed), updated the Direct X drivers, checked the video card drivers are up to date, checked for RAM errors, and checked my GPU and CPU temps (60 degrees, and up to 85 degress respectively).

Here's a BSOD message I had:

STOP 0x0000008E (0xC0000005, 0x91CDa6C4, 0xA752C500, 0x00000000)

dxgkrnl.sys - Address 91CDA6C4 base at 91CD80000, DateStamp 4ce78ffe

After this I ran the latest Direct X web installer, but I'm still getting both BSODs and CTDs.

I can provide my DXDiag info if that helps. Really grateful for any help, this has been going on too long!

 

[Elmer]

When attaching dmp files, PLEASE put them in a single zipped folder​

Hi Splendid Belt and Welcome to The Forum.

STOP 0x0000008E: KERNEL_MODE_EXCEPTION_NOT_HANDLED
Usual causes: Insufficient disk space, Device driver, Video card, BIOS, Breakpoint in startup without having a debugger attached, Hardware incompatibility, Faulty system service, 3rd party remote control, Memory.

Old and incompatible drivers can and do cause issues with Windows 7, often giving false error codes.
Random stop codes can often indicate hardware issues.

As a Priority:

As you can see, there are a lot of possible causes for a stop error 8E.

We really need to see the DMP file as it contains the only record of the sequence of events leading up to the crash, what drivers were loaded, and what was responsible.

To ensure minidumps are enabled:
Go to Start, in the Search Box type: sysdm.cpl, press Enter.
Under 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 (the 256kb varies).
Ensure that the Small Dump Directory is listed as %systemroot%\Minidump.
OK your way out.
Reboot if changes have been made.

The .dmp files are located at C:\Windows\Minidump. Until a .dmp file is generated, the Minidump folder may not exist.

Go to your C:\Windows\Minidump folder. Copy the .dmp files to a new folder on your desktop. Zip up that folder and attach to a post.

Please see: Link Removed Following Method 2:
Download and run the SF Diagnostics Tool. Right click the SF Diag tool and select Run as Administrator before running. When the reports have been created, zip them up and attach to a post.

Download and run CPU-Z. Take screenshots**/snips of the CPU tab, Mainboard tab, Memory tab and all the slot #'s under the SPD tab.
Go to Post Reply, click on the Go Advanced button and attach the screenshots**/snips to your post for all the RAM experts to see by using the paper clip you will find on the top toolbar. Do not zip them up.
**If screenshots, please crop.

Also see: Link Removed

When attaching dmp files, PLEASE put them in a single zipped folder
​

 

[Splendid Belt]

Thanks for the quick reply Elmer. I'll reply again with the requested info once I've had a chance to get it. Thanks again.

SB

 

[Splendid Belt]

Here are the pics taken from CPU-z, and the zipped up dump files and files from the diagnostic tool.

Thanks in advance for the help, and let me know if there's anything else I can provide.

SB

 

[Splendid Belt]

Hi, did I provide all the info you need? Happy to dig around for more if it helps.

Thanks again,

SB

 

[Splendid Belt]

Had lots more CTDs and a couple more BSODs lately. THe last BSOD had a different error code to normal. Here are the dumps.

 

[Elmer]

STOP 0x0000008E: KERNEL_MODE_EXCEPTION_NOT_HANDLED
Usual causes: Insufficient disk space, Device driver, Video card, BIOS, Breakpoint in startup without having a debugger attached, Hardware incompatibility, Faulty system service, 3rd party remote control, Memory.

Your latest dump file lists dxgmms1.sys as the probable cause.
This is a Windows System file and for it to be the cause of your crash is highly unlikely.
Old and incompatible drivers can and do cause issues with Windows 7, often giving false error codes.
Random stop codes can often indicate hardware issues.


As a Priority:

AVG is known to be a cause of BSOD's on Windows 7 systems. Suggest that you uninstall it. Download the correct Link Removed for your system (32 or 64 bit).
If you have AVG ID protection installed, download the AVGID Protection Remover from the above link as well (it wouldn't hurt to download and run it anyway). Download BSOD friendly Link Removed due to 404 Error as AVG's replacement.
Uninstall AVG through the Control Panel. Re-boot to Safe Mode and run the AVG Removal tool(s). Re-boot to normal mode and install MSE. Make sure your Windows firewall is enabled! After your blue screens have been resolved, feel free to re-try AVG.


Drivers with Updates:

Rt86win7.sys Thu Feb 26 09:04:22 2009 Link Removed If you're unsure about manually installing drivers then choose the Win7 and WinServer 2008 R2 Auto Installation Program (SID:1477671) option to download.


Bugcheck Analysis:

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

Use !analyze -v to get detailed debugging information.

BugCheck 1000008E, {c0000005, 91dc4995, 9acc36ec, 0}

Probably caused by : dxgmms1.sys ( dxgmms1!VidMmReferenceDmaBuffer+b )

Followup: MachineOwner

Drivers:

89613000 8965b000   ACPI     ACPI.sys     Sat Nov 20 08:37:52 2010 (4CE788E0)
89b40000 89b9a000   afd      afd.sys      Mon Apr 25 03:18:00 2011 (4DB4D9D8)
91f11000 91f23000   AgileVpn AgileVpn.sys Tue Jul 14 00:55:00 2009 (4A5BC954)
897a7000 897b0000   amdxata  amdxata.sys  Fri Mar 19 16:19:01 2010 (4BA3A3F5)
99b4d000 99b56000   asyncmac asyncmac.sys Tue Jul 14 00:54:46 2009 (4A5BC946)
8977b000 89784000   atapi    atapi.sys    Tue Jul 14 00:11:15 2009 (4A5BBF13)
89784000 897a7000   ataport  ataport.SYS  Sat Nov 20 08:38:00 2010 (4CE788E8)
9141b000 91433000   AtihdW73 AtihdW73.sys Tue Oct 18 08:08:59 2011 (4E9D260B)
9143c000 91d0c000   atikmdag atikmdag.sys Thu Nov 10 02:46:11 2011 (4EBB3AF3)
9095d000 909a2000   atikmpag atikmpag.sys Thu Nov 10 02:12:20 2011 (4EBB3304)
99a71000 99a90400   AVGIDSDriver AVGIDSDriver.Sys Sun Jul 10 23:35:23 2011 (4E1A292B)
89e9e000 89ea2000   AVGIDSEH AVGIDSEH.Sys Sun Jul 10 23:35:37 2011 (4E1A2939)
99a1c000 99a20480   AVGIDSFilter AVGIDSFilter.Sys Sun Jul 10 23:35:55 2011 (4E1A294B)
9994a000 9994c700   AVGIDSShim AVGIDSShim.Sys Tue Oct 04 04:48:52 2011 (4E8A8224)
908f3000 90929a80   avgldx86 avgldx86.sys Fri Oct 07 04:54:26 2011 (4E8E77F2)
89ef3000 89f00000   avgmfx86 avgmfx86.sys Mon Aug 08 04:40:42 2011 (4E3F5ABA)
89e97000 89e9d500   avgrkx86 avgrkx86.sys Tue Sep 13 05:01:23 2011 (4E6ED593)
89f9c000 89fe2700   avgtdix  avgtdix.sys  Sun Jul 10 23:44:49 2011 (4E1A2B61)
89f07000 89f0e000   Beep     Beep.SYS     Tue Jul 14 00:45:00 2009 (4A5BC6FC)
908e5000 908f3000   blbdrive blbdrive.sys Tue Jul 14 00:23:04 2009 (4A5BC1D8)
8949f000 894a7000   BOOTVID  BOOTVID.dll  Tue Jul 14 02:04:34 2009 (4A5BD9A2)
9989f000 998b8000   bowser   bowser.sys   Wed Feb 23 04:47:32 2011 (4D649164)
942f0000 9430e000   cdd      cdd.dll      Sat Nov 20 11:56:35 2010 (4CE7B773)
89ed4000 89ef3000   cdrom    cdrom.sys    Sat Nov 20 08:38:09 2010 (4CE788F1)
894e9000 89594000   CI       CI.dll       Sat Nov 20 12:05:17 2010 (4CE7B97D)
89e72000 89e97000   CLASSPNP CLASSPNP.SYS Tue Jul 14 00:11:20 2009 (4A5BBF18)
894a7000 894e9000   CLFS     CLFS.SYS     Tue Jul 14 00:11:10 2009 (4A5BBF0E)
89980000 899dd000   cng      cng.sys      Thu Nov 17 03:36:35 2011 (4EC48143)
91f04000 91f11000   CompositeBus CompositeBus.sys Sat Nov 20 09:50:21 2010 (4CE799DD)
90af1000 90afe000   crashdmp crashdmp.sys Tue Jul 14 00:45:50 2009 (4A5BC72E)
90869000 908cd000   csc      csc.sys      Sat Nov 20 08:44:32 2010 (4CE78A70)
908cd000 908e5000   dfsc     dfsc.sys     Sat Nov 20 08:42:32 2010 (4CE789F8)
9085d000 90869000   discache discache.sys Tue Jul 14 00:24:04 2009 (4A5BC214)
89e61000 89e72000   disk     disk.sys     Tue Jul 14 00:11:28 2009 (4A5BBF20)
90a15000 90a2e000   drmk     drmk.sys     Tue Jul 14 01:36:05 2009 (4A5BD2F5)
90b09000 90b12000   dump_atapi dump_atapi.sys Tue Jul 14 00:11:15 2009 (4A5BBF13)
90afe000 90b09000   dump_dumpata dump_dumpata.sys Tue Jul 14 00:11:16 2009 (4A5BBF14)
90b12000 90b23000   dump_dumpfve dump_dumpfve.sys Tue Jul 14 00:12:47 2009 (4A5BBF6F)
90adc000 90ae6000   Dxapi    Dxapi.sys    Tue Jul 14 00:25:25 2009 (4A5BC265)
91d0c000 91dc3000   dxgkrnl  dxgkrnl.sys  Sat Nov 20 09:08:14 2010 (4CE78FFE)
91dc3000 91dfc000   dxgmms1  dxgmms1.sys  Thu Feb 03 03:45:05 2011 (4D4A24C1)
91eaf000 91eba000   fdc      fdc.sys      Tue Jul 14 00:45:45 2009 (4A5BC729)
897e4000 897f5000   fileinfo fileinfo.sys Tue Jul 14 00:21:51 2009 (4A5BC18F)
91400000 9140a000   flpydisk flpydisk.sys Tue Jul 14 00:45:45 2009 (4A5BC729)
897b0000 897e4000   fltmgr   fltmgr.sys   Tue Jul 14 00:11:13 2009 (4A5BBF11)
899eb000 899f4000   Fs_Rec   Fs_Rec.sys   Tue Jul 14 00:11:14 2009 (4A5BBF12)
89e2f000 89e61000   fvevol   fvevol.sys   Sat Nov 20 08:40:22 2010 (4CE78976)
89d69000 89d9a000   fwpkclnt fwpkclnt.sys Sat Nov 20 08:39:08 2010 (4CE7892C)
83007000 8303e000   hal      halmacpi.dll Sat Nov 20 08:37:38 2010 (4CE788D2)
91dfc000 91e1b000   HDAudBus HDAudBus.sys Sat Nov 20 09:59:28 2010 (4CE79C00)
90a2e000 90a7e000   HdAudio  HdAudio.sys  Sat Nov 20 10:00:19 2010 (4CE79C33)
90ac9000 90adc000   HIDCLASS HIDCLASS.SYS Sat Nov 20 09:59:37 2010 (4CE79C09)
91433000 91439480   HIDPARSE HIDPARSE.SYS Tue Jul 14 00:50:59 2009 (4A5BC863)
90abe000 90ac9000   hidusb   hidusb.sys   Sat Nov 20 09:59:38 2010 (4CE79C0A)
9981a000 9989f000   HTTP     HTTP.sys     Sat Nov 20 08:40:17 2010 (4CE78971)
89e27000 89e2f000   hwpolicy hwpolicy.sys Sat Nov 20 08:37:35 2010 (4CE788CF)
91ed2000 91eea000   i8042prt i8042prt.sys Tue Jul 14 00:11:23 2009 (4A5BBF1B)
8970d000 89714000   intelide intelide.sys Tue Jul 14 00:11:19 2009 (4A5BBF17)
9094b000 9095d000   intelppm intelppm.sys Tue Jul 14 00:11:03 2009 (4A5BBF07)
91eea000 91ef7000   kbdclass kbdclass.sys Tue Jul 14 00:11:15 2009 (4A5BBF13)
80bb5000 80bbd000   kdcom    kdcom.dll    Tue Jul 14 02:08:58 2009 (4A5BDAAA)
91fba000 91fee000   ks       ks.sys       Sat Nov 20 09:50:17 2010 (4CE799D9)
8996d000 89980000   ksecdd   ksecdd.sys   Thu Nov 17 03:15:56 2011 (4EC47C6C)
89ae9000 89b0e000   ksecpkg  ksecpkg.sys  Thu Nov 17 03:37:34 2011 (4EC4817E)
90b63000 90b73000   lltdio   lltdio.sys   Tue Jul 14 00:53:18 2009 (4A5BC8EE)
90b2e000 90b49000   luafv    luafv.sys    Tue Jul 14 00:15:44 2009 (4A5BC020)
89409000 8948e000   mcupdate_GenuineIntel mcupdate_GenuineIntel.dll Sat Nov 20 12:00:54 2010 (4CE7B876)
90b23000 90b2e000   monitor  monitor.sys  Tue Jul 14 00:25:58 2009 (4A5BC286)
91ef7000 91f04000   mouclass mouclass.sys Tue Jul 14 00:11:15 2009 (4A5BBF13)
90ae6000 90af1000   mouhid   mouhid.sys   Tue Jul 14 00:45:08 2009 (4A5BC704)
89729000 8973f000   mountmgr mountmgr.sys Sat Nov 20 08:38:09 2010 (4CE788F1)
998b8000 998ca000   mpsdrv   mpsdrv.sys   Tue Jul 14 00:52:52 2009 (4A5BC8D4)
998ca000 998ed000   mrxsmb   mrxsmb.sys   Wed Apr 27 03:17:20 2011 (4DB77CB0)
998ed000 99928000   mrxsmb10 mrxsmb10.sys Sat Jul 09 03:29:57 2011 (4E17BD25)
99928000 99943000   mrxsmb20 mrxsmb20.sys Wed Apr 27 03:17:26 2011 (4DB77CB6)
89f60000 89f6b000   Msfs     Msfs.SYS     Tue Jul 14 00:11:26 2009 (4A5BBF1E)
89664000 8966c000   msisadrv msisadrv.sys Tue Jul 14 00:11:09 2009 (4A5BBF0D)
89942000 8996d000   msrpc    msrpc.sys    Tue Jul 14 00:11:59 2009 (4A5BBF3F)
90853000 9085d000   mssmbios mssmbios.sys Tue Jul 14 00:19:25 2009 (4A5BC0FD)
89e17000 89e27000   mup      mup.sys      Tue Jul 14 00:14:14 2009 (4A5BBFC6)
899f4000 89aab000   ndis     ndis.sys     Sat Nov 20 08:39:19 2010 (4CE78937)
91f3b000 91f46000   ndistapi ndistapi.sys Tue Jul 14 00:54:24 2009 (4A5BC930)
91f46000 91f68000   ndiswan  ndiswan.sys  Sat Nov 20 10:07:48 2010 (4CE79DF4)
9140a000 9141b000   NDProxy  NDProxy.SYS  Sat Nov 20 10:07:39 2010 (4CE79DEB)
89fea000 89ff8000   netbios  netbios.sys  Tue Jul 14 00:53:54 2009 (4A5BC912)
89b0e000 89b40000   netbt    netbt.sys    Sat Nov 20 08:39:22 2010 (4CE7893A)
89aab000 89ae9000   NETIO    NETIO.SYS    Sat Nov 20 08:40:03 2010 (4CE78963)
89f6b000 89f79000   Npfs     Npfs.SYS     Tue Jul 14 00:11:31 2009 (4A5BBF23)
90849000 90853000   nsiproxy nsiproxy.sys Tue Jul 14 00:12:08 2009 (4A5BBF48)
82c04000 83007000   nt       ntkrnlmp.exe Wed Oct 26 03:21:15 2011 (4EA76E9B)
89813000 89942000   Ntfs     Ntfs.sys     Fri Mar 11 03:21:11 2011 (4D799527)
89f00000 89f07000   Null     Null.SYS     Tue Jul 14 00:11:12 2009 (4A5BBF10)
89c00000 89c1f000   pacer    pacer.sys    Tue Jul 14 00:53:58 2009 (4A5BC916)
91eba000 91ed2000   parport  parport.sys  Tue Jul 14 00:45:34 2009 (4A5BC71E)
896a1000 896b2000   partmgr  partmgr.sys  Sat Nov 20 08:38:14 2010 (4CE788F6)
99943000 9994a000   parvdm   parvdm.sys   Tue Jul 14 00:45:29 2009 (4A5BC719)
8966c000 89696000   pci      pci.sys      Sat Nov 20 08:37:57 2010 (4CE788E5)
89722000 89729000   pciide   pciide.sys   Tue Jul 14 00:11:19 2009 (4A5BBF17)
89714000 89722000   PCIIDEX  PCIIDEX.SYS  Tue Jul 14 00:11:15 2009 (4A5BBF13)
899dd000 899eb000   pcw      pcw.sys      Tue Jul 14 00:11:10 2009 (4A5BBF0E)
9994d000 999e4000   peauth   peauth.sys   Tue Jul 14 01:35:44 2009 (4A5BD2E0)
909e6000 90a15000   portcls  portcls.sys  Tue Jul 14 00:51:00 2009 (4A5BC864)
8948e000 8949f000   PSHED    PSHED.dll    Tue Jul 14 02:09:36 2009 (4A5BDAD0)
91f23000 91f3b000   rasl2tp  rasl2tp.sys  Tue Jul 14 00:54:33 2009 (4A5BC939)
91f68000 91f80000   raspppoe raspppoe.sys Tue Jul 14 00:54:53 2009 (4A5BC94D)
91f80000 91f97000   raspptp  raspptp.sys  Tue Jul 14 00:54:47 2009 (4A5BC947)
91f97000 91fae000   rassstp  rassstp.sys  Tue Jul 14 00:54:57 2009 (4A5BC951)
90808000 90849000   rdbss    rdbss.sys    Sat Nov 20 08:42:44 2010 (4CE78A04)
91fae000 91fb8000   rdpbus   rdpbus.sys   Tue Jul 14 01:02:40 2009 (4A5BCB20)
89f48000 89f50000   RDPCDD   RDPCDD.sys   Sat Nov 20 10:22:19 2010 (4CE7A15B)
89f50000 89f58000   rdpencdd rdpencdd.sys Tue Jul 14 01:01:39 2009 (4A5BCAE3)
89f58000 89f60000   rdprefmp rdprefmp.sys Tue Jul 14 01:01:41 2009 (4A5BCAE5)
89dea000 89e17000   rdyboost rdyboost.sys Sat Nov 20 09:00:07 2010 (4CE78E17)
90b73000 90b86000   rspndr   rspndr.sys   Tue Jul 14 00:53:20 2009 (4A5BC8F0)
91e80000 91ea5000   Rt86win7 Rt86win7.sys Thu Feb 26 09:04:22 2009 (49A65B16)
999e4000 999ee000   secdrv   secdrv.SYS   Wed Sep 13 14:18:32 2006 (45080528)
91ea5000 91eaf000   serenum  serenum.sys  Tue Jul 14 00:45:27 2009 (4A5BC717)
89b9a000 89bb4000   serial   serial.sys   Tue Jul 14 00:45:33 2009 (4A5BC71D)
89de2000 89dea000   spldr    spldr.sys    Mon May 11 17:13:47 2009 (4A084EBB)
99a91000 99ae3000   srv      srv.sys      Fri Apr 29 03:46:30 2011 (4DBA2686)
99a21000 99a71000   srv2     srv2.sys     Fri Apr 29 03:46:13 2011 (4DBA2675)
999ee000 99a0f000   srvnet   srvnet.sys   Fri Apr 29 03:46:08 2011 (4DBA2670)
91fb8000 91fb9380   swenum   swenum.sys   Tue Jul 14 00:45:08 2009 (4A5BC704)
89c1f000 89d69000   tcpip    tcpip.sys    Thu Sep 29 04:22:11 2011 (4E83E463)
99a0f000 99a1c000   tcpipreg tcpipreg.sys Sat Nov 20 10:07:13 2010 (4CE79DD1)
89f90000 89f9c000   TDI      TDI.SYS      Sat Nov 20 08:39:18 2010 (4CE78936)
89f79000 89f90000   tdx      tdx.sys      Sat Nov 20 08:39:17 2010 (4CE78935)
89bc7000 89bd8000   termdd   termdd.sys   Sat Nov 20 10:21:10 2010 (4CE7A116)
942c0000 942c9000   TSDDD    TSDDD.dll    unavailable (00000000)
9092a000 9094b000   tunnel   tunnel.sys   Sat Nov 20 10:06:40 2010 (4CE79DB0)
90a7e000 90abe000   udfs     udfs.sys     Sat Nov 20 08:42:27 2010 (4CE789F3)
91fee000 91ffc000   umbus    umbus.sys    Sat Nov 20 10:00:23 2010 (4CE79C37)
9143a000 9143b700   USBD     USBD.SYS     Fri Mar 25 02:57:53 2011 (4D8C04B1)
91e71000 91e80000   usbehci  usbehci.sys  Fri Mar 25 02:57:58 2011 (4D8C04B6)
909a2000 909e6000   usbhub   usbhub.sys   Fri Mar 25 02:58:34 2011 (4D8C04DA)
91e26000 91e71000   USBPORT  USBPORT.SYS  Fri Mar 25 02:58:05 2011 (4D8C04BD)
91e1b000 91e26000   usbuhci  usbuhci.sys  Fri Mar 25 02:57:56 2011 (4D8C04B4)
89696000 896a1000   vdrvroot vdrvroot.sys Tue Jul 14 00:46:19 2009 (4A5BC74B)
89f0e000 89f1a000   vga      vga.sys      Tue Jul 14 00:25:50 2009 (4A5BC27E)
89f1a000 89f3b000   VIDEOPRT VIDEOPRT.SYS Tue Jul 14 00:25:49 2009 (4A5BC27D)
8973f000 89768180   vmbus    vmbus.sys    Sat Nov 20 09:14:58 2010 (4CE79192)
89d9a000 89da2380   vmstorfl vmstorfl.sys Sat Nov 20 09:14:37 2010 (4CE7917D)
896b2000 896c2000   volmgr   volmgr.sys   Sat Nov 20 08:38:06 2010 (4CE788EE)
896c2000 8970d000   volmgrx  volmgrx.sys  unavailable (00000000)
89da3000 89de2000   volsnap  volsnap.sys  Sat Nov 20 08:38:13 2010 (4CE788F5)
89bb4000 89bc7000   wanarp   wanarp.sys   Sat Nov 20 10:07:45 2010 (4CE79DF1)
89f3b000 89f48000   watchdog watchdog.sys Tue Jul 14 00:24:10 2009 (4A5BC21A)
89594000 89605000   Wdf01000 Wdf01000.sys Tue Jul 14 00:11:36 2009 (4A5BBF28)
89605000 89613000   WDFLDR   WDFLDR.SYS   Tue Jul 14 00:11:25 2009 (4A5BBF1D)
89fe3000 89fea000   wfplwf   wfplwf.sys   Tue Jul 14 00:53:51 2009 (4A5BC90F)
94060000 942b0000   win32k   win32k.sys   Thu Nov 24 04:25:06 2011 (4ECDC722)
89769000 8977b000   winhv    winhv.sys    Sat Nov 20 08:38:15 2010 (4CE788F7)
8965b000 89664000   WMILIB   WMILIB.SYS   Tue Jul 14 00:11:22 2009 (4A5BBF1A)
90b49000 90b63000   WudfPf   WudfPf.sys   Sat Nov 20 09:58:55 2010 (4CE79BDF)

Unloaded modules:
99b56000 99b6d000   99152669.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  00017000
99ae3000 99b4d000   spsys.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  0006A000
89ea2000 89eaf000   crashdmp.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  0000D000
89eaf000 89eba000   dump_ataport
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  0000B000
89eba000 89ec3000   dump_atapi.s
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  00009000
89ec3000 89ed4000   dump_dumpfve
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  00011000

Let us know how it goes. If you get further problems with blue screens, attach your new dump files and details and we'll move on from there.

HTH.

 

[Splendid Belt]

Thanks for the response Elmer. I updated the driver, but had another BSOD within 10 mins unfortunately.

I can uninstall AVG, but I was getting these issues even in the two weeks when I didn't have it installed, after deleting everything and upgrading to Windows 7.

I've attached the new dump from just now, it was the driver irql less or not equal error.

Thanks in advance again.

 

[Elmer]

Would appreciate removing AVG, at least until you settle down.

Can you adjust your RAM timings in the BIOS from 5-5-5-15 to 5-5-5-18

 

[Splendid Belt]

I uninstalled AVG. By the way, I got this report from Windows, which I'm sure is very much advice for beginners, but I'm posting it here in case it's useful:

"Microsoft is unable to determine the exact cause of this error. However, this problem was most likely caused by an error in your computer’s random access memory (RAM). RAM is the main internal storage area the computer uses to run programs and store data.

During the crash analysis, we noticed the basic input/output system (BIOS) version on this computer does not match the specifications for the central processing unit (CPU), also known as a processor, that is installed on your computer. This can occur when a newer processor is installed on an older system board or older BIOS. Using a BIOS that does not support the installed processor can result in Windows system crashes."

I'll change the RAM settings now.

 

[Elmer]

Yes, the bios is old (2007). The newest version I can see is from 2008, v3.8 Link Removed due to 404 Error.

 

[Splendid Belt]

Sorry to be so dense, but I can't see how to adjust RAM timings in my BIOS - I've been through all the possible settings and I can't see it.

Would you recommend updating my BIOS to the newer version?

 

[Elmer]

Have a look at the reasons its been updated. See if you've had any of the "issues" the updates address.

 

[Splendid Belt]

I downloaded the MSI 'Live Update' programme to update the BIOS. It scanned my system, and showed me the BIOS update I needed. Downloaded it fine, but then the programme stops working each time I try to go to the next step. And when I find the BIOS update files it downloaded, the executable does nothing.

The update doesn't specifically talk about stability issues, but mentioned CPU code fixes. The fact that I've wiped this system and upgraded to a new OS and still got the same problem makes me think it could well be a BIOS, or other underlying issue.

But right now I'm stuck at the stage of apparently being unable to update my BIOS, and also being unable to change my RAM settings as you previously suggested.

 

[Elmer]

Well. I had a look at a manual for your MoBo and have to admit it's lost me!! Not the clearest (to me) of manuals to find the ram timings.

The update doesn't specifically talk about stability issues, but mentioned CPU code fixes. The fact that I've wiped this system and upgraded to a new OS and still got the same problem makes me think it could well be a BIOS, or other underlying issue.

I think that MS pretty much got it right with their response to you. Hoping someone who is more into BIOS settings than I takes a look. This is the manual I downloaded. Think I got the right board!

 

[Splendid Belt]

Thanks again for this Elmer. Would you recommend I take the PC to a specialist to get the BIOS upgraded? I'm worried about completely destroying it if I try myself...

 

[Splendid Belt]

I've had a further thought. I may be wrong, but I think the crashing problem started after I installed my current graphics card. The old one pretty much blew up whilst gaming, but I don't think the system used to crash at that point.

Not sure if that helps, but thought I'd mention it.

 

[Elmer]

Would you recommend I take the PC to a specialist to get the BIOS upgraded? I'm worried about completely destroying it if I try myself...

I can understand your 'nervousness' although updating bios is a lot easier these days than it was. For the price of taking it to a specialist you could most likely afford to upgrade your MoBo with a nice new one (well, near enough!!). Have you no-one you could ask who has updated their BIOS before who could help you?

 

[Splendid Belt]

My helpful IT guru friend moved to Denmark, unhelpfully. Seems I'm a bit stuck.

 

[Elmer]

I'm not going to say to you tht you should update your bios if you don't feel confident in doing so. And a quick look at the instructions seems to show the "old" method, as in, boot from floppy etc.. Nowadays you can just run from your system. PC re-boots. Voila!! Updated bios (that's the simplified version!!).

Has AVG been removed (still showing on last dump file)?