Windows 7 Still getting BSOD at start up after so much effort

parishpete · Oct 15, 2010

Having had so much help from this forum already to kick BSOD's into touch by updating the vast majority of drivers and removing the dodgy hardware and software, my PC still refuses to behave.

The problem is still Kernel Event 41 caused by a bad shutdown or worse. They've occurred at start up on the 6th,7th,12th & 15th Oct.

I can't attach the most recent minidumps, event files and driver list as I appear to have reached my 10Mb upload limit.

any advice welcome, even that which includes the use of a large hammer!!

regards and thanks

Pete

cybercore · Oct 15, 2010

Hello Pete,

1. Check if the Power Supply Unit is sufficient and in working order.

2. Ensure that the hardware is properly connected with recommended bios settings

3. Test the hardware with bootable media:

Link Removed - Invalid URL

RAM - Test with Memtest86+ - Windows 7 Forums

4. Do a clean install

5. Try what's outlined here:

Stop 0x124 - what it means and what to try - Windows 7 Forums

6. Upgrade Bios if haven't done so yet

7. You can submit the dumps via an upload server such as rapidshare.com

cybercore · Oct 21, 2010

102110-15600-01.dmp
BugCheck 1000008E, {c0000005, 830ccf74, 91fa808c, 0}
Process: winlogon
Stack: nt! win32k! nt!
0x8E_win32k!DrvUpdateAttachFlag+58

Have you checked for updates for the nForce drivers?

nvraid.sys Wed May 20 09:43:36 2009
nvrd32.sys Wed Aug 05 03:28:19 2009
NVIDIA nForce(TM) RAID Driver

nvsmu.sys Mon Jun 29 10:36:34 2009
NVIDIA nForce(TM) PCA Driver

nvstor.sys Wed May 20 09:44:09 2009
nvstor32.sys Wed Aug 05 03:27:05 2009
NVIDIA nForce(TM) SATA Driver

BIOS upgrade is not an option, as you have it latest already. You may want to switch SATA controller mode to AHCI, see if it behaves any better. (You'll have to reinstall Windows after switching modes)

Code:

Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [G:\102110-15600-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16617.x86fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0x82e52000 PsLoadedModuleList = 0x82f9a810
Debug session time: Thu Oct 21 10:57:57.258 2010 (UTC - 5:00)
System Uptime: 0 days 0:00:23.146
Loading Kernel Symbols
...............................................................
................................................................
.....................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000008E, {c0000005, 830ccf74, 91fa808c, 0}

Probably caused by : win32k.sys ( win32k!DrvUpdateAttachFlag+58 )

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

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

KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: 830ccf74, The address that the exception occurred at
Arg3: 91fa808c, Trap Frame
Arg4: 00000000

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - <Unable to get error code text>

FAULTING_IP: 
nt!CmpGetValueListFromCache+95
830ccf74 8b3c8f          mov     edi,dword ptr [edi+ecx*4]

TRAP_FRAME:  91fa808c -- (.trap 0xffffffff91fa808c)
ErrCode = 00000000
eax=9c6dbc70 ebx=91fa8134 ecx=00000000 edx=9c6dbc74 esi=9f02b1e8 edi=000006b4
eip=830ccf74 esp=91fa8100 ebp=91fa8108 iopl=0         nv up ei pl nz na po nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010202
nt!CmpGetValueListFromCache+0x95:
830ccf74 8b3c8f          mov     edi,dword ptr [edi+ecx*4] ds:0023:000006b4=????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x8E

PROCESS_NAME:  winlogon.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from 830ae671 to 830ccf74

STACK_TEXT:  
91fa8108 830ae671 9f0266a8 91fa8148 91fa8144 nt!CmpGetValueListFromCache+0x95
91fa816c 8304f996 91fa8308 91fa81a4 91fa81a0 nt!CmpFindValueByNameFromCache+0x47
91fa81d8 83053024 9f02b1e8 91fa8308 00000004 nt!CmpCompareNewValueDataAgainstKCBCache+0x9f
91fa8290 83052933 9d4aa590 91fa8308 00000004 nt!CmSetValueKey+0x511
91fa834c 82e9544a 800007f4 91fa8404 00000000 nt!NtSetValueKey+0x32b
91fa834c 82e945bd 800007f4 91fa8404 00000000 nt!KiFastCallEntry+0x12a
91fa83dc 830229b4 800007f4 91fa8404 00000000 nt!ZwSetValueKey+0x11
91fa840c 997665f1 40000000 800007f4 99939698 nt!RtlWriteRegistryValue+0x41
91fa8430 9976c745 ffb97610 00000001 086ef4ea win32k!DrvUpdateAttachFlag+0x58
91fa84b0 9976b312 ffb97610 ffbbdafc fe46e9d0 win32k!hCreateHDEV+0x918
91fa866c 99769e32 00000000 00000000 75800002 win32k!DrvCreateMDEV+0x5fd
91fa8778 997680ba 00000000 ffb8f748 00000000 win32k!DrvInternalChangeDisplaySettings+0x44f
91fa87bc 997694f5 00000000 ffb8f748 00000000 win32k!_DrvInternalChangeDisplaySettingsWithForcedArgs+0x2b
91fa88d0 99849bf2 00000000 ffb8f748 00000000 win32k!DrvChangeDisplaySettings+0x725
91fa892c 9984a4ee 00000000 00000000 87dc7580 win32k!xxxInternalUserChangeDisplaySettings+0x247
91fa899c 99756625 00000000 00000000 00000000 win32k!xxxUserChangeDisplaySettings+0x67
91fa8d18 99755f78 00000001 00bafb84 91fa8d34 win32k!xxxUpdatePerUserSystemParameters+0x69a
91fa8d28 82e9544a 00000001 00bafbac 771164f4 win32k!NtUserUpdatePerUserSystemParameters+0x13
91fa8d28 771164f4 00000001 00bafbac 771164f4 nt!KiFastCallEntry+0x12a
WARNING: Frame IP not in any known module. Following frames may be wrong.
00bafbac 00000000 00000000 00000000 00000000 0x771164f4


STACK_COMMAND:  kb

FOLLOWUP_IP: 
win32k!DrvUpdateAttachFlag+58
997665f1 56              push    esi

SYMBOL_STACK_INDEX:  8

SYMBOL_NAME:  win32k!DrvUpdateAttachFlag+58

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: win32k

IMAGE_NAME:  win32k.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4c7dbbb5

FAILURE_BUCKET_ID:  0x8E_win32k!DrvUpdateAttachFlag+58

BUCKET_ID:  0x8E_win32k!DrvUpdateAttachFlag+58 
80baf000 80bb7000   kdcom    kdcom.dll    Tue Jul 14 04:08:58 2009 (4A5BDAAA)
82e1b000 82e52000   hal      halmacpi.dll Tue Jul 14 02:11:03 2009 (4A5BBF07)
82e52000 83262000   nt       ntkrpamp.exe Sat Jun 19 06:55:24 2010 (4C1C3FAC)
8b807000 8b812000   mcupdate_AuthenticAMD mcupdate_AuthenticAMD.dll Tue Jul 14 02:13:13 2009 (4A5BBF89)
8b812000 8b823000   PSHED    PSHED.dll    Tue Jul 14 04:09:36 2009 (4A5BDAD0)
8b823000 8b82b000   BOOTVID  BOOTVID.dll  Tue Jul 14 04:04:34 2009 (4A5BD9A2)
8b82b000 8b86d000   CLFS     CLFS.SYS     Tue Jul 14 02:11:10 2009 (4A5BBF0E)
8b86d000 8b918000   CI       CI.dll       Tue Jul 14 04:09:28 2009 (4A5BDAC8)
8b918000 8b989000   Wdf01000 Wdf01000.sys Tue Jul 14 02:11:36 2009 (4A5BBF28)
8b989000 8b997000   WDFLDR   WDFLDR.SYS   Tue Jul 14 02:11:25 2009 (4A5BBF1D)
8b997000 8b9df000   ACPI     ACPI.sys     Tue Jul 14 02:11:11 2009 (4A5BBF0F)
8b9df000 8b9e8000   WMILIB   WMILIB.SYS   Tue Jul 14 02:11:22 2009 (4A5BBF1A)
8b9e8000 8b9f0000   msisadrv msisadrv.sys Tue Jul 14 02:11:09 2009 (4A5BBF0D)
8ba01000 8ba2b000   pci      pci.sys      Tue Jul 14 02:11:16 2009 (4A5BBF14)
8ba2b000 8ba36000   vdrvroot vdrvroot.sys Tue Jul 14 02:46:19 2009 (4A5BC74B)
8ba36000 8ba47000   partmgr  partmgr.sys  Tue Jul 14 02:11:35 2009 (4A5BBF27)
8ba47000 8ba57000   volmgr   volmgr.sys   Tue Jul 14 02:11:25 2009 (4A5BBF1D)
8ba57000 8baa2000   volmgrx  volmgrx.sys  Tue Jul 14 02:11:41 2009 (4A5BBF2D)
8baa2000 8bac1000   nvraid   nvraid.sys   Wed May 20 09:43:36 2009 (4A13A698)
8bac1000 8bae6000   CLASSPNP CLASSPNP.SYS Tue Jul 14 02:11:20 2009 (4A5BBF18)
8bae6000 8baed000   pciide   pciide.sys   Tue Jul 14 02:11:19 2009 (4A5BBF17)
8baed000 8bafb000   PCIIDEX  PCIIDEX.SYS  Tue Jul 14 02:11:15 2009 (4A5BBF13)
8bafb000 8bb66000   nvrd32   nvrd32.sys   Wed Aug 05 03:28:19 2009 (4A78D223)
8bb66000 8bb7c000   mountmgr mountmgr.sys Tue Jul 14 02:11:27 2009 (4A5BBF1F)
8bb7c000 8bb85000   atapi    atapi.sys    Tue Jul 14 02:11:15 2009 (4A5BBF13)
8bb85000 8bba8000   ataport  ataport.SYS  Tue Jul 14 02:11:18 2009 (4A5BBF16)
8bba8000 8bbcd000   nvstor   nvstor.sys   Wed May 20 09:44:09 2009 (4A13A6B9)
8bbcd000 8bbf2000   ksecpkg  ksecpkg.sys  Fri Dec 11 06:04:22 2009 (4B21C4C6)
8bc1e000 8bc65000   storport storport.sys Tue Jul 14 02:45:58 2009 (4A5BC736)
8bc65000 8bc9c000   nvstor32 nvstor32.sys Wed Aug 05 03:27:05 2009 (4A78D1D9)
8bc9c000 8bca5000   amdxata  amdxata.sys  Tue May 19 20:57:35 2009 (4A12F30F)
8bca5000 8bcd9000   fltmgr   fltmgr.sys   Tue Jul 14 02:11:13 2009 (4A5BBF11)
8bcd9000 8bcea000   fileinfo fileinfo.sys Tue Jul 14 02:21:51 2009 (4A5BC18F)
8bcea000 8bda1000   ndis     ndis.sys     Tue Jul 14 02:12:24 2009 (4A5BBF58)
8bda1000 8bddf000   NETIO    NETIO.SYS    Tue Jul 14 02:12:35 2009 (4A5BBF63)
8bddf000 8bdf8000   bowser   bowser.sys   Tue Jul 14 02:14:21 2009 (4A5BBFCD)
8be0f000 8bf3e000   Ntfs     Ntfs.sys     Tue Jul 14 02:12:05 2009 (4A5BBF45)
8bf3e000 8bf69000   msrpc    msrpc.sys    Tue Jul 14 02:11:59 2009 (4A5BBF3F)
8bf69000 8bf7c000   ksecdd   ksecdd.sys   Tue Jul 14 02:11:56 2009 (4A5BBF3C)
8bf7c000 8bfd9000   cng      cng.sys      Tue Jul 14 02:32:55 2009 (4A5BC427)
8bfd9000 8bfe7000   pcw      pcw.sys      Tue Jul 14 02:11:10 2009 (4A5BBF0E)
8bfe7000 8bff0000   Fs_Rec   Fs_Rec.sys   Tue Jul 14 02:11:14 2009 (4A5BBF12)
8bff0000 8c000000   mup      mup.sys      Tue Jul 14 02:14:14 2009 (4A5BBFC6)
8c000000 8c02d000   rdyboost rdyboost.sys Tue Jul 14 02:22:02 2009 (4A5BC19A)
8c031000 8c17a000   tcpip    tcpip.sys    Mon Jun 14 06:36:59 2010 (4C15A3DB)
8c17a000 8c1ab000   fwpkclnt fwpkclnt.sys Tue Jul 14 02:12:03 2009 (4A5BBF43)
8c1ab000 8c1ea000   volsnap  volsnap.sys  Tue Jul 14 02:11:34 2009 (4A5BBF26)
8c1ea000 8c1f2000   spldr    spldr.sys    Mon May 11 19:13:47 2009 (4A084EBB)
8c1f2000 8c1fa000   hwpolicy hwpolicy.sys Tue Jul 14 02:11:01 2009 (4A5BBF05)
8c200000 8c20b000   TDI      TDI.SYS      Tue Jul 14 02:12:12 2009 (4A5BBF4C)
8c20b000 8c21e000   rspndr   rspndr.sys   Tue Jul 14 02:53:20 2009 (4A5BC8F0)
8c235000 8c267000   fvevol   fvevol.sys   Sat Sep 26 05:24:21 2009 (4ABD7B55)
8c267000 8c278000   disk     disk.sys     Tue Jul 14 02:11:28 2009 (4A5BBF20)
8c278000 8c2fd000   HTTP     HTTP.sys     Tue Jul 14 02:12:53 2009 (4A5BBF75)
8c2fd000 8c31e000   srvnet   srvnet.sys   Fri Aug 27 06:30:39 2010 (4C77315F)
8c326000 8c345000   cdrom    cdrom.sys    Tue Jul 14 02:11:24 2009 (4A5BBF1C)
8c345000 8c368000   MpFilter MpFilter.sys Sat Mar 20 06:03:26 2010 (4BA4490E)
8c368000 8c36f000   Null     Null.SYS     Tue Jul 14 02:11:12 2009 (4A5BBF10)
8c36f000 8c376000   Beep     Beep.SYS     Tue Jul 14 02:45:00 2009 (4A5BC6FC)
8c376000 8c382000   vga      vga.sys      Tue Jul 14 02:25:50 2009 (4A5BC27E)
8c382000 8c3a3000   VIDEOPRT VIDEOPRT.SYS Tue Jul 14 02:25:49 2009 (4A5BC27D)
8c3a3000 8c3b0000   watchdog watchdog.sys Tue Jul 14 02:24:10 2009 (4A5BC21A)
8c3b0000 8c3b8000   RDPCDD   RDPCDD.sys   Tue Jul 14 03:01:40 2009 (4A5BCAE4)
8c3b8000 8c3c0000   rdpencdd rdpencdd.sys Tue Jul 14 03:01:39 2009 (4A5BCAE3)
8c3c0000 8c3c8000   rdprefmp rdprefmp.sys Tue Jul 14 03:01:41 2009 (4A5BCAE5)
8c3c8000 8c3d3000   Msfs     Msfs.SYS     Tue Jul 14 02:11:26 2009 (4A5BBF1E)
8c3d3000 8c3e1000   Npfs     Npfs.SYS     Tue Jul 14 02:11:31 2009 (4A5BBF23)
8c3e1000 8c3f8000   tdx      tdx.sys      Tue Jul 14 02:12:10 2009 (4A5BBF4A)
90c00000 90c12000   mpsdrv   mpsdrv.sys   Tue Jul 14 02:52:52 2009 (4A5BC8D4)
90c12000 90c44000   netbt    netbt.sys    Tue Jul 14 02:12:18 2009 (4A5BBF52)
90c44000 90c9e000   afd      afd.sys      Tue Jul 14 02:12:34 2009 (4A5BBF62)
90c9e000 90ca5000   wfplwf   wfplwf.sys   Tue Jul 14 02:53:51 2009 (4A5BC90F)
90ca5000 90cc4000   pacer    pacer.sys    Tue Jul 14 02:53:58 2009 (4A5BC916)
90cc4000 90cd2000   netbios  netbios.sys  Tue Jul 14 02:53:54 2009 (4A5BC912)
90cd2000 90cec000   serial   serial.sys   Tue Jul 14 02:45:33 2009 (4A5BC71D)
90cec000 90cff000   wanarp   wanarp.sys   Tue Jul 14 02:55:02 2009 (4A5BC956)
90cff000 90d0f000   termdd   termdd.sys   Tue Jul 14 03:01:35 2009 (4A5BCADF)
90d0f000 90d50000   rdbss    rdbss.sys    Tue Jul 14 02:14:26 2009 (4A5BBFD2)
90d50000 90d5a000   nsiproxy nsiproxy.sys Tue Jul 14 02:12:08 2009 (4A5BBF48)
90d5a000 90d64000   mssmbios mssmbios.sys Tue Jul 14 02:19:25 2009 (4A5BC0FD)
90d64000 90d70000   discache discache.sys Tue Jul 14 02:24:04 2009 (4A5BC214)
90d70000 90d88000   dfsc     dfsc.sys     Tue Jul 14 02:14:16 2009 (4A5BBFC8)
90d88000 90d96000   blbdrive blbdrive.sys Tue Jul 14 02:23:04 2009 (4A5BC1D8)
90d96000 90d96fa0   AsIO     AsIO.sys     Mon Aug 03 10:02:32 2009 (4A768B88)
90d97000 90db8000   tunnel   tunnel.sys   Tue Jul 14 02:54:03 2009 (4A5BC91B)
90db8000 90dc9000   amdppm   amdppm.sys   Tue Jul 14 02:11:03 2009 (4A5BBF07)
90dc9000 90de1000   parport  parport.sys  Tue Jul 14 02:45:34 2009 (4A5BC71E)
90de1000 90de26c0   ASACPI   ASACPI.sys   Thu Jul 16 06:28:28 2009 (4A5E9E5C)
90de3000 90ded000   serenum  serenum.sys  Tue Jul 14 02:45:27 2009 (4A5BC717)
90ded000 90df6000   nvsmu    nvsmu.sys    Mon Jun 29 10:36:34 2009 (4A486F02)
90df6000 90e00000   usbohci  usbohci.sys  Tue Jul 14 02:51:14 2009 (4A5BC872)
91800000 91810000   lltdio   lltdio.sys   Tue Jul 14 02:53:18 2009 (4A5BC8EE)
91814000 9185f000   USBPORT  USBPORT.SYS  Tue Jul 14 02:51:13 2009 (4A5BC871)
9185f000 9186e000   usbehci  usbehci.sys  Sat Oct 24 06:58:55 2009 (4AE27B7F)
9186e000 91873280   GEARAspiWDM GEARAspiWDM.sys Mon May 18 15:16:53 2009 (4A1151B5)
91874000 91893000   HDAudBus HDAudBus.sys Tue Jul 14 02:50:55 2009 (4A5BC85F)
91893000 918d7880   nvmf6232 nvmf6232.sys Fri Jul 31 02:47:55 2009 (4A72312B)
918d8000 918ef000   raspptp  raspptp.sys  Tue Jul 14 02:54:47 2009 (4A5BC947)
918ef000 91906000   rassstp  rassstp.sys  Tue Jul 14 02:54:57 2009 (4A5BC951)
91906000 91913000   mouclass mouclass.sys Tue Jul 14 02:11:15 2009 (4A5BBF13)
91913000 91947000   ks       ks.sys       Thu Mar 04 05:57:52 2010 (4B8F2FC0)
91947000 91955000   umbus    umbus.sys    Tue Jul 14 02:51:38 2009 (4A5BC88A)
91955000 91999000   usbhub   usbhub.sys   Sat Oct 24 07:00:05 2009 (4AE27BC5)
91999000 919aa000   NDProxy  NDProxy.SYS  Tue Jul 14 02:54:27 2009 (4A5BC933)
919aa000 919b1780   LMouFilt LMouFilt.Sys Thu Mar 18 10:50:27 2010 (4BA1E953)
919b2000 919bd000   monitor  monitor.sys  Tue Jul 14 02:25:58 2009 (4A5BC286)
919bd000 919d8000   luafv    luafv.sys    Tue Jul 14 02:15:44 2009 (4A5BC020)
919d8000 919f2000   WudfPf   WudfPf.sys   Tue Jul 14 02:50:13 2009 (4A5BC835)
93000000 93022000   ndiswan  ndiswan.sys  Tue Jul 14 02:54:34 2009 (4A5BC93A)
93022000 9303a000   raspppoe raspppoe.sys Tue Jul 14 02:54:53 2009 (4A5BC94D)
9303b000 93ab8dc0   nvlddmkm nvlddmkm.sys Sat Jul 10 00:15:14 2010 (4C379162)
93ab9000 93aba040   nvBridge nvBridge.kmd Sat Jul 10 00:10:11 2010 (4C379033)
93abb000 93b72000   dxgkrnl  dxgkrnl.sys  Fri Oct 02 03:48:33 2009 (4AC54DE1)
93b72000 93bab000   dxgmms1  dxgmms1.sys  Tue Jul 14 02:25:25 2009 (4A5BC265)
93bab000 93bb8000   CompositeBus CompositeBus.sys Tue Jul 14 02:45:26 2009 (4A5BC716)
93bb8000 93bca000   AgileVpn AgileVpn.sys Tue Jul 14 02:55:00 2009 (4A5BC954)
93bca000 93be2000   rasl2tp  rasl2tp.sys  Tue Jul 14 02:54:33 2009 (4A5BC939)
93be2000 93bed000   ndistapi ndistapi.sys Tue Jul 14 02:54:24 2009 (4A5BC930)
93bed000 93bfa000   kbdclass kbdclass.sys Tue Jul 14 02:11:15 2009 (4A5BBF13)
93bfa000 93bfb380   swenum   swenum.sys   Tue Jul 14 02:45:08 2009 (4A5BC704)
99200000 99206480   HIDPARSE HIDPARSE.SYS Tue Jul 14 02:50:59 2009 (4A5BC863)
99207000 9920ed80   LHidFilt LHidFilt.Sys Thu Mar 18 10:50:19 2010 (4BA1E94B)
9920f000 9921b000   kbdhid   kbdhid.sys   Tue Jul 14 02:45:09 2009 (4A5BC705)
9921b000 99226000   mouhid   mouhid.sys   Tue Jul 14 02:45:08 2009 (4A5BC704)
99226000 994c4540   RTKVHDA  RTKVHDA.sys  Tue Aug 18 12:30:35 2009 (4A8A74BB)
994c5000 994f4000   portcls  portcls.sys  Tue Jul 14 02:51:00 2009 (4A5BC864)
994f4000 9950d000   drmk     drmk.sys     Tue Jul 14 03:36:05 2009 (4A5BD2F5)
9950d000 9951a000   crashdmp crashdmp.sys Tue Jul 14 02:45:50 2009 (4A5BC72E)
9951a000 99585000   dump_nvrd32 dump_nvrd32.sys Wed Aug 05 03:28:19 2009 (4A78D223)
99585000 995aa000   dump_CLASSPNP dump_CLASSPNP.SYS Tue Jul 14 02:11:20 2009 (4A5BBF18)
995aa000 995bb000   dump_dumpfve dump_dumpfve.sys Tue Jul 14 02:12:47 2009 (4A5BBF6F)
995bb000 995c5000   Dxapi    Dxapi.sys    Tue Jul 14 02:25:25 2009 (4A5BC265)
995c5000 995dc000   USBSTOR  USBSTOR.SYS  Tue Jul 14 02:51:19 2009 (4A5BC877)
995dc000 995dd700   USBD     USBD.SYS     Tue Jul 14 02:51:05 2009 (4A5BC869)
995de000 995e9000   hidusb   hidusb.sys   Tue Jul 14 02:51:04 2009 (4A5BC868)
995e9000 995fc000   HIDCLASS HIDCLASS.SYS Tue Jul 14 02:51:01 2009 (4A5BC865)
99740000 9998b000   win32k   win32k.sys   Wed Sep 01 05:34:29 2010 (4C7DBBB5)
999a0000 999a9000   TSDDD    TSDDD.dll    unavailable (00000000)
999d0000 999ee000   cdd      cdd.dll      Tue Jul 14 04:04:18 2009 (4A5BD992)
9ee16000 9ee39000   mrxsmb   mrxsmb.sys   Sat Feb 27 09:32:02 2010 (4B88CA72)
9ee39000 9ee74000   mrxsmb10 mrxsmb10.sys Sat Feb 27 09:32:21 2010 (4B88CA85)
9ee74000 9ee8f000   mrxsmb20 mrxsmb20.sys Sat Feb 27 09:32:11 2010 (4B88CA7B)
9ee8f000 9eede000   srv2     srv2.sys     Fri Aug 27 06:30:45 2010 (4C773165)
9eede000 9ef2f000   srv      srv.sys      Fri Aug 27 06:31:26 2010 (4C77318E)
9ef2f000 9ef37e00   MpNWMon  MpNWMon.sys  Sat Mar 20 06:03:24 2010 (4BA4490C)
9ef38000 9ef3f000   parvdm   parvdm.sys   Tue Jul 14 02:45:29 2009 (4A5BC719)
9ef3f000 9efd6000   peauth   peauth.sys   Tue Jul 14 03:35:44 2009 (4A5BD2E0)
9efd6000 9efe0000   secdrv   secdrv.SYS   Wed Sep 13 16:18:32 2006 (45080528)
9efe0000 9efed000   tcpipreg tcpipreg.sys Tue Jul 14 02:54:14 2009 (4A5BC926)

Unloaded modules:
8c278000 8c285000   crashdmp.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  0000D000
8c2f0000 8c315000   dump_CLASSPN
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  00025000
8c285000 8c2f0000   dump_nvrd32.
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  0006B000
8c315000 8c326000   dump_dumpfve
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  00011000

parishpete · Oct 21, 2010

Thanks Cybercore.

The Nvidia RAID drivers are the latest from the ASUS site. I can't get close to RAID drivers on Nvidia's site, it's most unhelpful.

The cabling is that which came in the box. It's been clamped up with cable ties though is tied shorter than I would do. I have more cables and will have a switch around.

For the sake of £50 for a new single 1TB drive I could ditch RAID entirely which may get shot of the problem. OK, I know it's a clean install and a shed load of updates, but if it cures the woes, what the hell.

Should I switch to AHCI whatever I do?

There other errors in the event files from time to time (nothing serious) which perhaps suggests that after 11 months of BSOD's the OS is feeling a bit fragile. Perhaps a clean install is for the best.

best wishes

Pete

cybercore · Oct 21, 2010

Did your PC ever crash during OS installation? If it never did then a chance it's a bad driver.

1. The Nvidia RAID drivers are the latest from the ASUS site.

Drivers - Download NVIDIA Drivers

Can you try those from NVidia site? What is your motherboard model?

2. Should I switch to AHCI whatever I do?

In this case you'll have to reinstall Windows, it won't boot when switched from RAID to AHCI. The idea was to see if your hdd controller would handle AHCI any better than RAID, but frankly I bet it's gonna be the same. So it's up to you.

I think you need a new motherboard, I don't know, like borrow it from someone - lol. Try reflashing bios as well.

parishpete · Oct 21, 2010

Two installs;first at the shop when built 13 months ago and second in May this year when I did a clean install. Quickest easiest install I've ever seen! Certainly no crashes. I did use Windows easy transfer to get all my settings back. Could I have simply brought in corrupt system data from the original install by doing that?

1. Asus M4N78 Current download at Asus is Nvidia sata raid V111033 Sept 09

2. I doubt I can find anyone with a board going spare. I have a P4 Intel xp machine that's doing nothing. The graphics card isn't compatible but the on board might get away with it.

I have a feeling that it just doesn't like being switched right off. I'm sure that on the occasions I have, it has always BSOD'd at start up. The ironic thing is that once up and running it never has crashed during use.

Best wishes

Pete

cybercore · Oct 21, 2010

1. Asus M4N78 Current download at Asus is Nvidia sata raid V111033 Sept 09

M4N78 is nForce 720D, I can't find anything for 720D but I found one for 720I - which is 2009.10.01, so yours is indeed the latest possible.
(NVIDIA DRIVERS 15.49 WHQL)

2. This motherboard model certainly predated the release of Windows 7, so I would install XP to test: if it still BSOD'd on XP with the same raid error - that would mean faulty cabling, faulty SATA, or faulty motherboard you need to reflash or replace. If it crashes on XP as well, test the system with only one SATA connected, of course you'll need to reinstall the OS once again.

parishpete · Oct 21, 2010

Thanks for your advice. Board is supposed to be compatible

I'll go for a new drive & cables first. I want to ditch raid anyway. If that fails I'll just get a new m/board.

Can't be doing with testing one OS then the other life's too short.

Many thanks for your help

cybercore · Oct 21, 2010

parishpete said:
Can't be doing with testing one OS then the other life's too short.

LoL, I wasn't really thinking of a short life span scenario. 8-x You're right it's easier to get another mobo than spend the rest of your life testing it. =P~

parishpete · Oct 23, 2010

Hi all,

Since opening the box and pushing all the drive connectors home, BSOD every morning since. I changed the SATA cables this morning using the ones out of the BSOD free XP machine.

Files attached, read and weep!

New 1TB drive arrived yesteday. will save files and settings via easy transfer unless that's a bad idea, remove the the raid drives as they are and install the single under SATA on Monday.

I only have 2 DVD writers 1 SATA, 1 IDE (could leave one unconnected for the moment). Also USB card reader & front USB port.

Only other things connected are GForce 9500 video card, Printer on LPT1 & USB printer.

System isn't overclocked or anything fancy.

My other machine - drivers and BIOS are way out of date and yet it ticks along happily on an older motherboard!

Any final thought before surgery (other than borrow a motherboard!)

regards

Pete

TorrentG · Oct 23, 2010

1) Update Realtek HD Audio driver:

RTKVHDA RTKVHDA.sys Tue Aug 18 05:30:35 2009

Link Removed

2) Update NVIDIA video driver:

nvlddmkm nvlddmkm.sys Fri Jul 09 17:15:14 2010

Link Removed - Invalid URL

3) Update your NVIDIA RAID/chipset driver package:

nvrd32 nvrd32.sys Tue Aug 04 20:28:19 2009
nvstor32 nvstor32.sys Tue Aug 04 20:27:05 2009

NVIDIA DRIVERS 15.49 WHQL

parishpete · Oct 23, 2010

Hi Torrent,

Thanks. It looks like 1 & 2 are recent versions. Will update.

I'm already running chipset 15.49 downloaded 21/10/10, I don't there is are newer drivers within it.

I'm beginning to think there is a hardware problem. It was fine until I powered down the motherboard 4 days ago to check the cables!

regards

pete

TorrentG · Oct 23, 2010

No need to check cables. Replace the RAM.

parishpete · Oct 23, 2010

Thought.

At build delivery was delayed because 1 stick of RAM was faulty. is the replacement faulty or were both originals?

I have 2 x 2Gb sticks. How about I remove one stick and see what happens. If problems continue, swap them.

What's the chance of two sticks from seperate batches being duff?

regards

Pete

parishpete · Oct 23, 2010

the two sticks, though probably identical have different codes; VData VD2800002GOU and VData VD2U800B2G5-B.

Have asked ADATA to confirm they are the same.

Having googled them, it appears that the VD2U800 is available in the UK, the VD28000 isn't

Any thoughts?

regards

Pete

cybercore · Oct 23, 2010

You did right to ask ADATA, they'll give you a more precise answer for their products. I can tell you they look and should be the same, but I'm not 100% sure. I always buy them from the same batch.

This is a good idea:

-> I have 2 x 2Gb sticks. How about I remove one stick and see what happens. If problems continue, swap them.

parishpete · Oct 23, 2010

Thanks.

I'll take out the foreigner first and see what happens

regards

Pete

cybercore · Oct 23, 2010

Lol, actually they are both foreigners to each other.

parishpete · Oct 23, 2010

Well yes!

Now here's a poser; Win 7 32 bit can only use 3Gb and I have 4Gb. Is the unused RAM spread over both DIMMS or confined to one. And if only 3Gb is used by 32 bit, is only 3Gb tested using memtest.

Regards

pete

cybercore · Oct 23, 2010

Memtests does them all, the total RAM detected. Memtest is bootable, not the OS.

RAM - Test with Memtest86+ - Windows 7 Forums

parishpete · Oct 23, 2010

So far so good!

1 stick VD28000 RAM sitting in antistatic bag, GeForce & realtek drivers updated.

1 stick VD2U800 in channel A

And even though I powered down the mother board (which it has always hated) not a BSOD in sight after 3 restarts.

I think someone will say "I told you so"!

But for getting rid of errors from:

MMSE OOBE has stopped working
ReadyBoot has stopped working
nvrd32.sys the driver detected a controller error on (it never list a drive)

My event viewer would be empty. These 3 are all day every day.

If I dare assume RAM was my problem (it's early days) Is it worth reinstalling the chipset & RAID drivers in case dodgy RAM upset them during install?

Best wishes and yet more thanks

Pete

cybercore · Oct 23, 2010

You are celebrating too early, Pete, so far it's been smooth for 57 minutes maximum. When the RAM proves good, then take care of the drivers.

Windows 7 Still getting BSOD at start up after so much effort

New Member

New Member

New Member

New Member

New Member

New Member

New Member

New Member

New Member

Attachments

Banned

New Member

Banned

New Member

New Member

New Member

New Member

New Member

New Member

New Member

New Member

New Member