Solved BSOD after upgrade system

OldEvil1 · Dec 24, 2010

Hi,
I'm new here. I already read a lot of posts to see if I could fix my BSOD problem but without luck untill now. However I saw that you guys were able to help a lot of guys and therefor I hope you'll also be able to help me with my problem.

Last week I did an upgrade of my PC. Basically I kept my 2 HD's, my PSU (recently renewed it because my old one got defective) and my case.

I bought these Items to upgrade my PC:
2X Corsair XMS CMX4GX3M2A1600C9 (so 8GB in total)
AMD Phenom II X6 1055T 2.8Ghz Boxed | HDT55TFBGRBOX
Asrock 870 Extreme3 | 870 EXTREME3
Samsung EcoGreen F4EG. 2TB | HD204UI (add on to my other 2HD's I already have)
Sapphire HD 6850 1GB GDDR5 PCIE | 11180-00-20R

I did a clean install (windows vista 64bit home basic) and installed everything on the new Samsung drive.
However from day one I'm getting sporadic BSOD's. Strange thing is that I have the impression it's more when I'm just downloading or streaming a video. Never happened during gaming (yet), I did happen during a 10-tabling poker session :/
I did se a few other times that my poker-tables were getting messed up (picture included) but I didn't get a BSOD in these cases.

I tried a lot of things but don't have the feeling that I'm close to solving it:

*I turned off (or disabled) all the items in the BIOS that state that it can cause instability?
*Checked the BIOS version of the mainboard but V1.60 is the latest.
*Performed driver sweeper (even after clean install) did find some NVIDIA drivers and removed them. (did this everytime I switched/updated drivers)
*Performed a memtest86: After 5 passes no errors were detected
*Did a benchmark Heaven V2.1 test: score ~700 (results added)
*Did a short (10min) OCCT CPU test (due to the noise I had to stop it - my wife was getting mad

) I'll repeat this once when we're out of the house.
*Did a OCCT GPU test: no probems detected
*Uninstalled my mcaffee virusscanner
*Checked the minidumps (with my limited knowledge - just learned how to open them reading these forumst)
*Removed the asrock software (as I found in 1 minidump a reference to asrocdrv.sys) (asrock tuner, asrock instant boot and a 3th power saving tool).
*Upgraded the Samsung Ecogreen Bios to be able to enable SMART monitoring
*Enabled SMART monitoring in the BIOS
*Did a HDTune test. Redid the test to be able to add the results in the ZIP file.
*Performed a 14 minute Prime95 test: no problems but same as with the OCCT CPU test: this is something I need to do when my wife is out of the house

*upgraded the drivers to catalyst 10.12.
*After BSOD upgraded the drivers to catalyst 10.12 hotfix when I found a mentioning of atikmdag.sys in the minidump.
*After BSOD downgraded the drivers to catalyst 10.10 latest hotfix.
*Replaced my new graphics card by my old nvidia 8800GT 512MB card.
*Got a BSOD during a reboot (while upgrading software or maybe driver sweeper (don't know anymore)).
*Performed a Heaven benchmark with my old graphics card and got a score of 879 (only ~700 with my new card). ??? this seems strange (or not)?

To summerize... HELP

I hope you guys have enough info to find something that's not as it should or that I should be testing/upgrading.
It would make my X-mas a lot better

tnx in advance.

OldEvil1 · Dec 24, 2010

Added the zipped mini-dump folder.
The last mini-dump is with my old graphics card
(But could be that the error was caused removing the last ATI drivers...)

OldEvil1 · Dec 25, 2010

First of all:
Merry X-mas to all!

A quick update.

Yesterday I got a BSOD with my old graphics card installed (still have it installed atm). This morning I tried to update driver sweeper (I saw I had an old version and although I clicked 'clean' my ATI-drivers stayed in the list) and I got a new BSOD.

I was doing nothing but downloading the file.

I added the mini-dump + a picture of the blue screen to this post.

This time there's a reference to rtlh64.sys (first time)

It appears it's linked to the ethernet drivers on my mainboard.
This would make sence as I already stated that I had the impression that the BSOD's were not comming when I was stressing my PC but when I was doing normal stuff (downloading a file, streaming a movie, ...).

I now upgraded my Realtek RTL8111E driver from 6.235 to 6.244 .

Will keep you posted.

OldEvil1 · Dec 25, 2010

Another episode in my nightmare.

Just minutes after posting I got a new BSOD while saving an html page.
Didn't reboot yet after the driver update so I don't know if this is a 'new' BSOD or if this BSOD could still be linked to the RTL8111E issue.

picture + mini-dump in attachment

OldEvil1 · Dec 25, 2010

and another one...
win32k.sys is now mentioned.

:cry:

:sa::sa:

EDIT: BSOD came while downloaden a new audio driver + surfing...

OldEvil1 · Dec 25, 2010

continuing my monologue:

got a BSOD while starting to watch a video online...

I think it's clear the HD6850 graphics card has nothing to do with it.
So i'm going to put this one back in (and install the latest 10.12 catalyst drivers)

Also planning on taking out 4GB of RAM.

richc46 · Dec 25, 2010

You have given be about 20 dumps, I have spot checked about 1/3. They give various codes and causes
4E, A, 1E, 7E, D1, 1A
A large number give memory as a cause and some others give drivers. Since a bad driver can cause memory problems we will start there.

Code:

Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
 
Loading Dump File [C:\Users\richc46\AppData\Local\Temp\Temp1_Pictures-mini-dump-4[1].zip\Mini122510-04.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows Server 2008/Windows Vista Kernel Version 6002 (Service Pack 2) MP (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 6002.18267.amd64fre.vistasp2_gdr.100608-0458
Machine Name:
Kernel base = 0xfffff800`02059000 PsLoadedModuleList = 0xfffff800`0221ddd0
Debug session time: Sat Dec 25 06:48:21.279 2010 (GMT-5)
System Uptime: 0 days 0:11:32.110
Loading Kernel Symbols
...............................................................
................................................................
................
Loading User Symbols
Loading unloaded module list
.........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1A, {8884, fffffa800104a900, fffffa8004d6b530, 501}
Probably caused by : memory_corruption ( nt!MiRelinkStandbyPage+a2 )
Followup: MachineOwner
---------
2: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000008884, The subtype of the bugcheck.
Arg2: fffffa800104a900
Arg3: fffffa8004d6b530
Arg4: 0000000000000501
Debugging Details:
------------------
 
BUGCHECK_STR:  0x1a_8884
CUSTOMER_CRASH_COUNT:  4
DEFAULT_BUCKET_ID:  COMMON_SYSTEM_FAULT
PROCESS_NAME:  svchost.exe
CURRENT_IRQL:  2
LAST_CONTROL_TRANSFER:  from fffff80002121172 to fffff800020b34d0
STACK_TEXT:  
fffffa60`0def98c8 fffff800`02121172 : 00000000`0000001a 00000000`00008884 fffffa80`0104a900 fffffa80`04d6b530 : nt!KeBugCheckEx
fffffa60`0def98d0 fffff800`02177bcd : fffffa80`0bfc4bb0 fffffa80`08930ee0 fffffa80`0bfc4bb0 fffffa80`08930ee0 : nt!MiRelinkStandbyPage+0xa2
fffffa60`0def9910 fffff800`02446994 : 00000000`00000000 fffffa60`00000000 00000000`00000000 fffffa80`08930000 : nt!MmSetPfnListPriorities+0x28d
fffffa60`0def9980 fffff800`02486d62 : 00000002`03481e00 00000000`00000000 fffffa80`0892e000 00000000`00000001 : nt!PfpPfnPrioRequest+0x84
fffffa60`0def99d0 fffff800`02499778 : 00000000`00000000 00000000`00000004 00000002`4ec4e659 fffffa80`07dcb501 : nt!PfSetSuperfetchInformation+0x191
fffffa60`0def9ab0 fffff800`020b2f73 : fffffa80`0bfc4bb0 00000000`044af420 00000000`08bedc50 00000000`00000000 : nt!NtSetSystemInformation+0x8fb
fffffa60`0def9c20 00000000`774c838a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`022bee08 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x774c838a
 
STACK_COMMAND:  kb
FOLLOWUP_IP: 
nt!MiRelinkStandbyPage+a2
fffff800`02121172 cc              int     3
SYMBOL_STACK_INDEX:  1
SYMBOL_NAME:  nt!MiRelinkStandbyPage+a2
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: nt
DEBUG_FLR_IMAGE_TIMESTAMP:  4c0e5ae3
IMAGE_NAME:  memory_corruption
FAILURE_BUCKET_ID:  X64_0x1a_8884_nt!MiRelinkStandbyPage+a2
BUCKET_ID:  X64_0x1a_8884_nt!MiRelinkStandbyPage+a2
Followup: MachineOwner
---------
2: kd> lmtsmn
start             end                 module name
fffffa60`0755a000 fffffa60`07569f00   1394BUS  1394BUS.SYS  Sat Jan 19 01:34:04 2008 (479199DC)
fffffa60`008f5000 fffffa60`0094b000   acpi     acpi.sys     Sat Apr 11 01:03:26 2009 (49E0249E)
fffffa60`08c03000 fffffa60`08c6e000   afd      afd.sys      Sat Apr 11 01:44:21 2009 (49E02E35)
fffffa60`0daa3000 fffffa60`0daae000   asyncmac asyncmac.sys Sat Jan 19 01:37:27 2008 (47919AA7)
fffffa60`009e1000 fffffa60`009e9000   atapi    atapi.sys    Sat Apr 11 01:34:19 2009 (49E02BDB)
fffffa60`00794000 fffffa60`007b8000   ataport  ataport.SYS  Sat Apr 11 01:34:25 2009 (49E02BE1)
fffffa60`00fd8000 fffffa60`00fe0000   AtiPcie  AtiPcie.sys  Tue May 05 11:00:22 2009 (4A005486)
fffffa60`0d7aa000 fffffa60`0d7c8000   bowser   bowser.sys   Sat Jan 19 00:54:51 2008 (479190AB)
fffffa60`08e01000 fffffa60`08ee8a00   CamDrL64 CamDrL64.sys Sat Feb 03 13:17:27 2007 (45C4D1B7)
fffff960`006b0000 fffff960`006c1000   cdd      cdd.dll      unavailable (00000000)
fffffa60`0738e000 fffffa60`073aa000   cdrom    cdrom.sys    Sat Apr 11 01:34:39 2009 (49E02BEF)
fffffa60`0067c000 fffffa60`0072e000   CI       CI.dll       Sat Apr 11 03:08:09 2009 (49E041D9)
fffffa60`00dc6000 fffffa60`00df2000   CLASSPNP CLASSPNP.SYS Sat Apr 11 01:34:15 2009 (49E02BD7)
fffffa60`0061f000 fffffa60`0067c000   CLFS     CLFS.SYS     Sat Apr 11 00:54:21 2009 (49E0227D)
fffffa60`08fc3000 fffffa60`08fd1000   crashdmp crashdmp.sys Sat Apr 11 01:34:31 2009 (49E02BE7)
fffffa60`00fe0000 fffffa60`00fea000   crcdisk  crcdisk.sys  Thu Nov 02 05:39:40 2006 (4549BCDC)
fffffa60`08d0f000 fffffa60`08d2c000   dfsc     dfsc.sys     Sat Apr 11 00:54:44 2009 (49E02294)
fffffa60`011e5000 fffffa60`011f9000   disk     disk.sys     Sat Apr 11 01:34:38 2009 (49E02BEE)
fffffa60`08f12000 fffffa60`08f3a000   Dot4     Dot4.sys     Sat Jan 19 01:28:01 2008 (47919871)
fffffa60`08f55000 fffffa60`08f5f000   Dot4Prt  Dot4Prt.sys  Sat Jan 19 01:27:58 2008 (4791986E)
fffffa60`08f02000 fffffa60`08f12000   dot4usb  dot4usb.sys  Sat Jan 19 01:28:00 2008 (47919870)
fffffa60`075d1000 fffffa60`075f4000   drmk     drmk.sys     Sat Jan 19 02:20:04 2008 (4791A4A4)
fffffa60`08fdd000 fffffa60`08fe5000   dump_atapi dump_atapi.sys Sat Apr 11 01:34:19 2009 (49E02BDB)
fffffa60`08fd1000 fffffa60`08fdd000   dump_dumpata dump_dumpata.sys Sat Apr 11 01:34:22 2009 (49E02BDE)
fffffa60`08fe5000 fffffa60`08ff1000   Dxapi    Dxapi.sys    Sat Jan 19 01:08:00 2008 (479193C0)
fffffa60`07209000 fffffa60`072ec000   dxgkrnl  dxgkrnl.sys  Thu Sep 24 21:27:15 2009 (4ABC1C73)
fffffa60`00fac000 fffffa60`00fd8000   ecache   ecache.sys   Sat Apr 11 01:36:18 2009 (49E02C52)
fffffa60`009e9000 fffffa60`009fd000   fileinfo fileinfo.sys Sat Jan 19 01:05:23 2008 (47919323)
fffffa60`007b8000 fffffa60`007ff000   fltmgr   fltmgr.sys   Sat Apr 11 00:54:38 2009 (49E0228E)
fffffa60`086a8000 fffffa60`086b2000   Fs_Rec   Fs_Rec.SYS   Sat Jan 19 00:53:41 2008 (47919065)
fffffa60`00f80000 fffffa60`00fac000   fwpkclnt fwpkclnt.sys Sat Apr 11 01:42:44 2009 (49E02DD4)
fffff800`02013000 fffff800`02059000   hal      hal.dll      Sat Apr 11 03:04:56 2009 (49E04118)
fffffa60`0740e000 fffffa60`074fb000   HDAudBus HDAudBus.sys Sat Apr 11 01:39:38 2009 (49E02D1A)
fffffa60`08f43000 fffffa60`08f55000   HIDCLASS HIDCLASS.SYS Sat Apr 11 01:39:32 2009 (49E02D14)
fffffa60`086c6000 fffffa60`086cdb80   HIDPARSE HIDPARSE.SYS Sat Jan 19 01:33:51 2008 (479199CF)
fffffa60`08f3a000 fffffa60`08f43000   hidusb   hidusb.sys   Sat Apr 11 01:39:32 2009 (49E02D14)
fffffa60`0d6de000 fffffa60`0d781000   HTTP     HTTP.sys     Tue Nov 03 15:07:14 2009 (4AF08D72)
fffffa60`086ce000 fffffa60`086e4000   i8042prt i8042prt.sys Sat Jan 19 01:28:08 2008 (47919878)
fffffa60`07511000 fffffa60`0751f000   kbdclass kbdclass.sys Sat Jan 19 01:28:05 2008 (47919875)
fffffa60`08f6a000 fffffa60`08f75000   kbdhid   kbdhid.sys   Sat Apr 11 01:33:40 2009 (49E02BB4)
fffffa60`00601000 fffffa60`0060b000   kdcom    kdcom.dll    Sat Apr 11 03:07:57 2009 (49E041CD)
fffffa60`07604000 fffffa60`07638000   ks       ks.sys       Sat Apr 11 01:33:51 2009 (49E02BBF)
fffffa60`00a07000 fffffa60`00a8e000   ksecdd   ksecdd.sys   Mon Jun 15 09:15:18 2009 (4A364966)
fffffa60`07638000 fffffa60`0763d180   ksthunk  ksthunk.sys  Sat Jan 19 01:28:14 2008 (4791987E)
fffffa60`0771d000 fffffa60`07720d80   LGBusEnum LGBusEnum.sys Mon Nov 23 20:36:48 2009 (4B0B38B0)
fffffa60`0db7f000 fffffa60`0db81480   LGVirHid LGVirHid.sys Mon Nov 23 20:36:48 2009 (4B0B38B0)
fffffa60`0d6a6000 fffffa60`0d6ba000   lltdio   lltdio.sys   Sat Jan 19 01:35:48 2008 (47919A44)
fffffa60`08d68000 fffffa60`08d8a000   luafv    luafv.sys    Sat Jan 19 00:59:06 2008 (479191AA)
fffffa60`08d48000 fffffa60`08d54980   LVUSBS64 LVUSBS64.sys Sat Feb 03 13:05:16 2007 (45C4CEDC)
fffffa60`08d55000 fffffa60`08d68000   monitor  monitor.sys  Sat Jan 19 01:32:34 2008 (47919982)
fffffa60`0770f000 fffffa60`0771b000   mouclass mouclass.sys Sat Jan 19 01:28:05 2008 (47919875)
fffffa60`08f5f000 fffffa60`08f6a000   mouhid   mouhid.sys   Sat Jan 19 01:28:10 2008 (4791987A)
fffffa60`009ce000 fffffa60`009e1000   mountmgr mountmgr.sys Sat Jan 19 01:28:01 2008 (47919871)
fffffa60`0d7c8000 fffffa60`0d7e2000   mpsdrv   mpsdrv.sys   Sat Jan 19 01:35:28 2008 (47919A30)
fffffa60`08d8a000 fffffa60`08db1000   mrxdav   mrxdav.sys   Sat Apr 11 00:55:42 2009 (49E022CE)
fffffa60`08db1000 fffffa60`08dda000   mrxsmb   mrxsmb.sys   Tue Feb 23 06:32:22 2010 (4B83BCC6)
fffffa60`077a9000 fffffa60`077f2000   mrxsmb10 mrxsmb10.sys Tue Feb 23 06:32:21 2010 (4B83BCC5)
fffffa60`08dda000 fffffa60`08df9000   mrxsmb20 mrxsmb20.sys Tue Feb 23 06:32:20 2010 (4B83BCC4)
fffffa60`08729000 fffffa60`08734000   Msfs     Msfs.SYS     Sat Jan 19 00:53:55 2008 (47919073)
fffffa60`00954000 fffffa60`0095e000   msisadrv msisadrv.sys Sat Jan 19 01:02:50 2008 (4791928A)
fffffa60`07573000 fffffa60`075ac000   msiscsi  msiscsi.sys  Sat Apr 11 01:36:09 2009 (49E02C49)
fffffa60`00a8e000 fffffa60`00ade000   msrpc    msrpc.sys    Sat Apr 11 01:32:13 2009 (49E02B5D)
fffffa60`07721000 fffffa60`0772c000   mssmbios mssmbios.sys Sat Jan 19 01:02:54 2008 (4791928E)
fffffa60`011d3000 fffffa60`011e5000   mup      mup.sys      Sat Apr 11 00:54:47 2009 (49E02297)
fffffa60`00c03000 fffffa60`00dc6000   ndis     ndis.sys     Sat Apr 11 01:43:15 2009 (49E02DF3)
fffffa60`07679000 fffffa60`07685000   ndistapi ndistapi.sys Sat Jan 19 01:37:22 2008 (47919AA2)
fffffa60`07685000 fffffa60`076b6000   ndiswan  ndiswan.sys  Sat Apr 11 01:43:39 2009 (49E02E0B)
fffffa60`08694000 fffffa60`086a8000   NDProxy  NDProxy.SYS  Sat Jan 19 01:37:26 2008 (47919AA6)
fffffa60`08c8c000 fffffa60`08c9b000   netbios  netbios.sys  Sat Jan 19 01:36:35 2008 (47919A73)
fffffa60`08786000 fffffa60`087ca000   netbt    netbt.sys    Sat Apr 11 01:42:31 2009 (49E02DC7)
fffffa60`00ade000 fffffa60`00b37000   NETIO    NETIO.SYS    Sat Apr 11 01:43:34 2009 (49E02E06)
fffffa60`08734000 fffffa60`08745000   Npfs     Npfs.SYS     Sat Apr 11 00:54:22 2009 (49E0227E)
fffffa60`08d03000 fffffa60`08d0f000   nsiproxy nsiproxy.sys Sat Jan 19 01:36:45 2008 (47919A7D)
fffff800`02059000 fffff800`02570000   nt       ntkrnlmp.exe Tue Jun 08 10:59:47 2010 (4C0E5AE3)
fffffa60`01007000 fffffa60`01187000   Ntfs     Ntfs.sys     Sat Apr 11 00:55:38 2009 (49E022CA)
fffffa60`086b2000 fffffa60`086bb000   Null     Null.SYS     Thu Nov 02 05:37:15 2006 (4549BC4B)
fffffa60`0773c000 fffffa60`07754000   nusb3hub nusb3hub.sys Thu Jan 21 22:22:18 2010 (4B5919EA)
fffffa60`072fc000 fffffa60`0732c000   nusb3xhc nusb3xhc.sys Thu Jan 21 22:22:21 2010 (4B5919ED)
fffffa60`071da000 fffffa60`071db180   nvBridge nvBridge.kmd Sat Oct 16 13:06:16 2010 (4CB9DB88)
fffffa60`06600000 fffffa60`071d9a80   nvlddmkm nvlddmkm.sys Sat Oct 16 13:12:46 2010 (4CB9DD0E)
fffffa60`07548000 fffffa60`07559b00   ohci1394 ohci1394.sys Sat Apr 11 01:39:49 2009 (49E02D25)
fffffa60`08c6e000 fffffa60`08c8c000   pacer    pacer.sys    Sat Apr 11 01:42:56 2009 (49E02DE0)
fffffa60`0098e000 fffffa60`009a3000   partmgr  partmgr.sys  Sat Apr 11 01:34:51 2009 (49E02BFB)
fffffa60`0095e000 fffffa60`0098e000   pci      pci.sys      Sat Apr 11 01:03:33 2009 (49E024A5)
fffffa60`009b7000 fffffa60`009be000   pciide   pciide.sys   Sat Apr 11 01:34:28 2009 (49E02BE4)
fffffa60`009be000 fffffa60`009ce000   PCIIDEX  PCIIDEX.SYS  Sat Apr 11 01:34:22 2009 (49E02BDE)
fffffa60`0daae000 fffffa60`0db64000   peauth   peauth.sys   Mon Oct 23 07:57:00 2006 (453CAE0C)
fffffa60`00bb4000 fffffa60`00bef000   portcls  portcls.sys  Sat Apr 11 01:39:36 2009 (49E02D18)
fffffa60`00b44000 fffffa60`00b57000   processr processr.sys Sat Jan 19 00:52:45 2008 (4791902D)
fffffa60`0060b000 fffffa60`0061f000   PSHED    PSHED.dll    Sat Apr 11 03:08:17 2009 (49E041E1)
fffffa60`08745000 fffffa60`0874e000   rasacd   rasacd.sys   Sat Jan 19 01:37:30 2008 (47919AAA)
fffffa60`07656000 fffffa60`07679000   rasl2tp  rasl2tp.sys  Sat Apr 11 01:43:37 2009 (49E02E09)
fffffa60`076b6000 fffffa60`076c6000   raspppoe raspppoe.sys Sat Apr 11 01:43:33 2009 (49E02E05)
fffffa60`076c6000 fffffa60`076e4000   raspptp  raspptp.sys  Sat Apr 11 01:43:38 2009 (49E02E0A)
fffffa60`076e4000 fffffa60`076fc000   rassstp  rassstp.sys  Sat Apr 11 01:43:46 2009 (49E02E12)
fffffa60`08cb6000 fffffa60`08d03000   rdbss    rdbss.sys    Sat Apr 11 00:55:21 2009 (49E022B9)
fffffa60`08717000 fffffa60`08720000   RDPCDD   RDPCDD.sys   Sat Jan 19 01:42:04 2008 (47919BBC)
fffffa60`08720000 fffffa60`08729000   rdpencdd rdpencdd.sys Sat Jan 19 01:42:03 2008 (47919BBB)
fffffa60`0d6ba000 fffffa60`0d6d2000   rspndr   rspndr.sys   Sat Jan 19 01:35:48 2008 (47919A44)
fffffa60`0840f000 fffffa60`08693b80   RTKVHD64 RTKVHD64.sys Tue Nov 30 04:03:19 2010 (4CF4BDD7)
fffffa60`0732e000 fffffa60`0738e000   Rtlh64   Rtlh64.sys   Thu Nov 11 01:54:23 2010 (4CDB931F)
fffffa60`0d6d2000 fffffa60`0d6de000   RtNdPt60 RtNdPt60.sys Sun Jul 19 22:27:32 2009 (4A63D614)
fffffa60`0db64000 fffffa60`0db6f000   secdrv   secdrv.SYS   Wed Sep 13 09:18:38 2006 (4508052E)
fffffa60`0753c000 fffffa60`07548000   serenum  serenum.sys  Sat Jan 19 01:28:36 2008 (47919894)
fffffa60`0751f000 fffffa60`0753c000   serial   serial.sys   Sat Jan 19 01:28:41 2008 (47919899)
fffffa60`0876b000 fffffa60`08786000   smb      smb.sys      Sat Apr 11 01:42:19 2009 (49E02DBB)
fffffa60`011cb000 fffffa60`011d3000   spldr    spldr.sys    Mon Jan 12 16:51:29 2009 (496BBB61)
fffffa60`0d60c000 fffffa60`0d6a6000   spsys    spsys.sys    Tue Mar 10 13:16:43 2009 (49B6A07B)
fffffa60`0da0f000 fffffa60`0daa3000   srv      srv.sys      Mon Sep 06 11:34:12 2010 (4C8509F4)
fffffa60`087ca000 fffffa60`087fc000   srv2     srv2.sys     Mon Sep 06 11:33:50 2010 (4C8509DE)
fffffa60`0d781000 fffffa60`0d7aa000   srvnet   srvnet.sys   Mon Sep 06 11:33:48 2010 (4C8509DC)
fffffa60`00b57000 fffffa60`00bb4000   storport storport.sys Sat Apr 11 01:34:45 2009 (49E02BF5)
fffffa60`0771b000 fffffa60`0771c480   swenum   swenum.sys   Thu Nov 02 05:37:33 2006 (4549BC5D)
fffffa60`00e0a000 fffffa60`00f80000   tcpip    tcpip.sys    Wed Jun 16 10:51:56 2010 (4C18E50C)
fffffa60`0db6f000 fffffa60`0db7f000   tcpipreg tcpipreg.sys Tue Dec 08 12:55:32 2009 (4B1E9314)
fffffa60`075ac000 fffffa60`075b9000   TDI      TDI.SYS      Sat Apr 11 01:44:14 2009 (49E02E2E)
fffffa60`0874e000 fffffa60`0876b000   tdx      tdx.sys      Sat Apr 11 01:43:00 2009 (49E02DE4)
fffffa60`076fc000 fffffa60`0770f000   termdd   termdd.sys   Sat Apr 11 01:48:13 2009 (49E02F1D)
fffff960`004b0000 fffff960`004ba000   TSDDD    TSDDD.dll    Sat Jan 19 01:42:04 2008 (47919BBC)
fffffa60`00e00000 fffffa60`00e09000   tunmp    tunmp.sys    Sat Jan 19 01:36:30 2008 (47919A6E)
fffffa60`00b37000 fffffa60`00b44000   tunnel   tunnel.sys   Thu Feb 18 06:59:46 2010 (4B7D2BB2)
fffffa60`08f75000 fffffa60`08fc3000   udfs     udfs.sys     Sat Apr 11 00:54:21 2009 (49E0227D)
fffffa60`0772c000 fffffa60`0773c000   umbus    umbus.sys    Sat Jan 19 01:34:16 2008 (479199E8)
fffffa60`08ee9000 fffffa60`08f01280   usbaudio usbaudio.sys Sat Apr 11 01:39:34 2009 (49E02D16)
fffffa60`08d2c000 fffffa60`08d48000   usbccgp  usbccgp.sys  Sat Jan 19 01:34:04 2008 (479199DC)
fffffa60`0732c000 fffffa60`0732de00   USBD     USBD.SYS     Sat Jan 19 01:33:53 2008 (479199D1)
fffffa60`071dc000 fffffa60`071ed000   usbehci  usbehci.sys  Sat Apr 11 01:39:36 2009 (49E02D18)
fffffa60`07754000 fffffa60`0779c000   usbhub   usbhub.sys   Sat Apr 11 01:39:52 2009 (49E02D28)
fffffa60`073aa000 fffffa60`073b5000   usbohci  usbohci.sys  Sat Apr 11 01:39:36 2009 (49E02D18)
fffffa60`073b5000 fffffa60`073fb000   USBPORT  USBPORT.SYS  Sat Apr 11 01:39:39 2009 (49E02D1B)
fffffa60`086e4000 fffffa60`086f2000   vga      vga.sys      Sat Jan 19 01:32:21 2008 (47919975)
fffffa60`086f2000 fffffa60`08717000   VIDEOPRT VIDEOPRT.SYS Sat Jan 19 01:32:25 2008 (47919979)
fffffa60`009a3000 fffffa60`009b7000   volmgr   volmgr.sys   Sat Apr 11 01:34:49 2009 (49E02BF9)
fffffa60`0072e000 fffffa60`00794000   volmgrx  volmgrx.sys  Sat Apr 11 01:35:14 2009 (49E02C12)
fffffa60`01187000 fffffa60`011cb000   volsnap  volsnap.sys  Sat Apr 11 01:35:33 2009 (49E02C25)
fffffa60`08c9b000 fffffa60`08cb6000   wanarp   wanarp.sys   Sat Apr 11 01:43:38 2009 (49E02E0A)
fffffa60`072ec000 fffffa60`072fc000   watchdog watchdog.sys Sat Apr 11 01:09:16 2009 (49E025FC)
fffffa60`0080d000 fffffa60`008e7000   Wdf01000 Wdf01000.sys Sat Jan 19 01:33:27 2008 (479199B7)
fffffa60`008e7000 fffffa60`008f5000   WDFLDR   WDFLDR.SYS   Sat Jan 19 01:32:33 2008 (47919981)
fffff960`000e0000 fffff960`00394000   win32k   win32k.sys   Mon Oct 18 11:25:18 2010 (4CBC66DE)
fffffa60`0756a000 fffffa60`07573000   wmiacpi  wmiacpi.sys  Sat Jan 19 01:02:42 2008 (47919282)
fffffa60`0094b000 fffffa60`00954000   WMILIB   WMILIB.SYS   Sat Jan 19 01:33:45 2008 (479199C9)
fffffa60`075c6000 fffffa60`075d1000   WsAudio_DeviceS_1_ WsAudio_DeviceS(1).sys Thu Jul 23 08:04:10 2009 (4A6851BA)
fffffa60`0764b000 fffffa60`07656000   WsAudio_DeviceS_4_ WsAudio_DeviceS(4).sys Thu Jul 23 08:04:10 2009 (4A6851BA)

Outdted drivers

Code:

 peauth.sys   Mon Oct 23 07:57:00 2006 
Null.SYS     Thu Nov 02 05:37:15 2006 
swenum.sys   Thu Nov 02 05:37:33 2006 
crcdisk.sys  Thu Nov 02 05:39:40 2006 
LVUSBS64.sys Sat Feb 03 13:05:16 2007 
CamDrL64.sys Sat Feb 03 13:17:27 2007 
processr.sys Sat Jan 19 00:52:45 2008 
Fs_Rec.SYS   Sat Jan 19 00:53:41 2008 
Msfs.SYS     Sat Jan 19 00:53:55 2008

Upgrade the above drivers
The reports that you have submitted reveal clues to the cause of your problem. They do not give a definitive answer. The more reports that we receive the more clues are made available improving our chances of finding a solution to your problem. You may have to experience several more BSODs until the final answer is discovered.

Your cause is most likely memory or bad drivers.
Take the driver verifier after you take the memory test. The memory test is a lot easier. If you fail, we may not need the memory test. In addition to the above most likely causes other also have potential.
Sometimes it take multiple attempts to correc the BSOD problem

If overclocking restore normal settings

SFC /scannow
System Files - SFC Command

Download memtest86 and test RAM
www.sevenforums.com/tutorials/105647-ram-test-memtest86.html
Run for 8 passes
If passes try a good stick in each slot for 3 passes
If fails do the same for 8 passes.

Scan with your Anti Virus

Update outdated listed drivers. If I have inadvertently listed any Microsoft Drivers, they can be ignored. If the list is extensive I have included the driver verifier test so that you may determine which drivers are in need of immediate attention.
Asacpi.sys is a driver from the Austek Computer Corp. Your driver is very old and is known to cause BSOD's in current Windows versions; it must be updated
http://support.asus.com/download/download.aspx?SLanguage=en-us

How to Find Drivers
search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
- if there are difficulties in locating them, post back with questions and someone - will help you search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- - if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.
- The most common drivers are listed on this page: http://www.carrona.org/dvrref.html
- - Driver manufacturer links are on this page: http://www.carrona.org/drvrdown.html
and here
http://www.edbott.com/weblog/the-vista-master-driver-list/
To remove any left over driver remnants, especially from graphics cards, use driver sweeper
www.guru3d.com/category/driversweeper/
You can also locate information about your driver using this information
http://www.sevenforums.com/tutorials/96442-device-manager-finding-unknown-devices.html

Driver Verifier Inst
Since the driver that crashed you has not been listed you should run driver verifier
Please run Verifier with these settings:

Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.
So, I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Windows 7 Startup Repair feature).
Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
NOTE: You can use Low Resource Simulation if you'd like. From my limited experimentation it makes the BSOD's come faster.
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.
Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).
Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.
If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.
Enable the driver verifier
www.sevenforums.com/crash-lockup-debug-how/65331-using-driver-verifier-identify-issues-drivers.html

richc46 · Dec 25, 2010

Im done, Merry Christmas.

OldEvil1 · Dec 25, 2010

Hi Richc46.
Merry X-mas and thanks for the feedback.

I've done a SFC /scannow but nothing showed up.
I looked for the outdated drivers.

LVUSBS64.sys & CamDrL64.sys are linked to my webcam. I'm now downloading the latest version (but I think this V10.5.1.2023 already is the latest version available for a Quickcam Pro 4000).

For the other drivers i really don't know how to start this job.
These are all windows system drivers and I can't seem to find a more recent version or how to install them? Any idea? (I did find a ver 6.1.7600.16385 for peauth.sys - but do I just replace the file? or should I install it somehow)?

peauth.sys - Protected Environment Authentication and Authorization Export Driver - Windows Update
Null.SYS - NULL Driver - Windows Update
swenum.sys - Plug and Play Software Device Enumerator - Windows Update
crcdisk.sys - Disk Block Verification Filter Driver - Windows Update
processr.sys - Processor Device Driver - Windows Update
Fs_Rec.SYS - File System Recognizer Driver - Windows Update
Msfs.SYS - Mailslot driver - Windows Update

btw my official windows vista CD is one of the first so I had to go via the windows updater to SP1 -> SP2 ... Maybe that's the reason I have some outdated .sys files?
Should I just find a 'friendly' soul with Vista 64 who copies his files and sends them to me?

I also removed 3 RAM sticks and I'm going to run the memtest86 overnight.
(no BSOD since I removed the RAM (yet) but still to early to tell)

richc46 · Dec 25, 2010

OldEvil1 said:
Hi Richc46.
Merry X-mas and thanks for the feedback.

I've done a SFC /scannow but nothing showed up.
I looked for the outdated drivers.

LVUSBS64.sys & CamDrL64.sys are linked to my webcam. I'm now downloading the latest version (but I think this V10.5.1.2023 already is the latest version available for a Quickcam Pro 4000).

For the other drivers i really don't know how to start this job.
These are all windows system drivers and I can't seem to find a more recent version or how to install them? Any idea? (I did find a ver 6.1.7600.16385 for peauth.sys - but do I just replace the file? or should I install it somehow)?

peauth.sys - Protected Environment Authentication and Authorization Export Driver - Windows Update
Null.SYS - NULL Driver - Windows Update
swenum.sys - Plug and Play Software Device Enumerator - Windows Update
crcdisk.sys - Disk Block Verification Filter Driver - Windows Update
processr.sys - Processor Device Driver - Windows Update
Fs_Rec.SYS - File System Recognizer Driver - Windows Update
Msfs.SYS - Mailslot driver - Windows Update

btw my official windows vista CD is one of the first so I had to go via the windows updater to SP1 -> SP2 ... Maybe that's the reason I have some outdated .sys files?
Should I just find a 'friendly' soul with Vista 64 who copies his files and sends them to me?

I also removed 3 RAM sticks and I'm going to run the memtest86 overnight.
(no BSOD since I removed the RAM (yet) but still to early to tell)

If I miss a qestion let me know
I mentioned in my lengthy post that any Microsoft drives need not be updated.
That was easy.

I think that my one easy answer takes care of all your questiions. If not let me know

OldEvil1 · Dec 26, 2010

Update:
Memtest 86:
First stick: position A1: 14 passes -> no errors
Second stick: position B1: 10 passes -> no errors
Third stick: position A2: 15 passes -> no errors

OldEvil1 · Dec 27, 2010

and 4th stick tested: 15 passes OK

More than 24h without a BSOD.

I placed all 4 of them back in and 5 hours later (when I was just watching TV - PC was just idling) the BSOD came back.

files added!

I don't really know what else to test but I'm going to take out stick 3 and 4 and see what happens...

Edit: just removed stick 3 & 4. But I did notice that one side of stick 4 wasn't 'locked'. (which is very strange as I was 100% sure I locked it properly).
Hopefully this was the cause of the BSOD. I'm going to work till the next BSOD on 2 sticks of 2GB.

Will keep you updated

richc46 · Dec 27, 2010

We have to use all the clues that are given.
Your last report indicates drivers or memory
You said with the memory sticks out you ran ok
Looks like memory
Test all sticks for 8 passes
If it fails, take a good stick and test each slot for 8 passes
If it passes test a good stick in each slot for 6 passes.

OldEvil1 · Dec 27, 2010

I already tested each stick for more than 8 passes without errors:
First stick: position A1: 14 passes -> no errors
Second stick: position B1: 10 passes -> no errors
Third stick: position A2: 15 passes -> no errors
Fourth stick: position B2: 15 passes -> no errors

As I said, I hope the last error was caused because one memory stick was not 'locked' decently when I placed all four back in.

I'm now working with 2 sticks in - will keep you posted

richc46 · Dec 27, 2010

Did you buy additional ram and mix and match?

Fiery · Dec 27, 2010

Do you have a fan over your CPU?, I know when I first updated from win2k to vista, I kept getting random BSOD, turned out my CPU was overheating, a small molex fan on it solved the problem

OldEvil1 · Dec 30, 2010

Update: Currently more then 24 hours without a BSOD. I have a stick in A1 and B1.
If it remains like this I am going to insert stick A2 and B2 after the weekend.
I'll keep you posted.

richc46 · Dec 30, 2010

Yes keep me posted and ask any questions if needed. My hunch is that memory will come up with something.

OldEvil1 · Jan 1, 2011

I worked 3 days without problems.
Today I placed the 3th and 4th memory stick back in the computer.
And just a minute ago I got a BSOD.

So I think there are 2 possibilities:
1. One of the memory sticks is broken (but they all got more then 10 passes using memtest86)
2. There's something wrong with the motherboard (when using 2A and 2B).

Things I plan to test:
Remove stick 3 and 4 and test for 5 days if I get a BSOD.
If no BSOD: place stick 3 and 4 in position of 1 and 2
If no BSOD: place Stick 1 and 2 in position 3 and 4 ...

?

PS: Happy newyear

richc46 · Jan 1, 2011

Finish the tests. Take a good stick and test each slot for 8 passes.

Solved BSOD after upgrade system

My Computer

Attachments

My Computer

Attachments

My Computer

Attachments

My Computer

Attachments

My Computer

Attachments

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

Attachments

My Computer

My Computer