BSOD again

zigzag3143 · Oct 10, 2010

lightice said:
Well, my LAN port somehow stopped working, I tried to "repair" and it gave me BSOD. So I'm reinstalling the driver.
Okay, this is weird, I tried reinstalling the driver and configuring the IP address, but the adaptor doesn't recognise the network. It keeps giving me 'unidentified network' and won't connect me even though I entered the correct IP/subnet values.

I can't get my network adaptor on the P5Q-pro to work now, it just gives me 'unidentified network'.
Here are the latests dmp files.
Only those dated 10/10/2010 are the recent ones,2 of them.

Ok you have quite the mix of causes.

1-memory corruption directly in two of these.
2-SPTD.sys (a virtual dvd driver that almost always causes bsod's)
3-ASACPI.sys (driver verified) (not sure if still installed--)

here is what I would do

1-remove the virtual drive software (Alcohol, daemon tools.)

Please remove any CD virtualization programs such as Daemon Tools and Alcohol 120%. They use a driver, found in your dmp, sptd.sys, that is notorious for causing BSODs. Use this SPTD uninstaller when you're done: DuplexSecure - Downloads
[/quote]
You can use MagicDisc as an alternative.

Freeware MagicISO Virtual CD/DVD-ROM(MagicDisc) Overview

2-Re-install the ASACPI.sys file with the newest possible version date

ASACPI.sys Sun Mar 27 22:30:36 2005

The 2005 version of this driver is a known BSOD cause.
Please visit this link: ASUSTeK Computer Inc.-Support- download_item_mkt
Scroll down to the Utilities category, then scroll down to the "ATK0110 driver for WindowsXP/Vista/Windows 7 32&64-bit " (it's about the 8th item down).
Download and install it.
Go to C:\Windows\System32\drivers to check and make sure that the ASACPI.sys file is date stamped from 2009 or 2010 (NOT 2005).

3-memory. Been here before. It keeps showing up. Either there is hardware causing the memory to go or memory itself.

4-Run a system file check

http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html?ltr=S

Let us know the results

Ken J

lightice · Oct 10, 2010

Hi Ken,

I have daemon tools installed.

I'll install magicdisc, thanks for the recommendation.

As for the ASACPI.sys , I do have the latest 2009 (driver date: 5/5/2009) version of the driver.

I will run a system file check in a while. Saving my documents now. Thanks.

Update 1:
Uninstalled daemon tools
Used the SPTD removal tool to uninstall
Downloaded magicdisk, not yet installed.

Update 2:
SFC complete, here is the log file.

Update 3:
I found the file from the windows DVD, it took me a while cause it wasn't in alphabetical order. *sigh*.
Running sfc again now to check if there are any more errors.
I followed the steps listed in this forum and microsoft regarding ownership taking and replacing the dll.mui file.

Update 4:
Replacing the file didn't work! ****

lightice · Oct 11, 2010

I did all the steps you listed above.

Yet today, after having my computer off for 4h and 30min. I came back and swtiched it on, used windows for 5 minutes and i got BSOD.

Earlier, I could use windows for a few hours no issues.

When I can manage to enter windows again, I'd post the dmp file.

This is the dmp file that is of the latest BSOD: 101110-18891-01.dmp

cybercore · Oct 11, 2010

101110-18891-01.dmp
DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
This is the general bug check code for fatal errors found by Driver Verifier.

BugCheck C4, {91, 0, fffffa8006bd5b60, 0}
win32k.sys ( win32k!xxxRealSleepThread+291 )

I suspect a hardware issue:

memtest86 http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

hdd scan (SMART) HDDScan

Code:

fffff880`0895ea88 fffff800`02d1624a : 00000000`000000c4 00000000`00000091 00000000`00000000 fffffa80`06bd5b60 : nt!KeBugCheckEx
fffff880`0895ea90 fffff800`02cee6b3 : fffff8a0`01bea020 fffff880`0895eb70 00000000`00000003 fffff800`02fb410a : nt! ?? ::FNODOBFM::`string'+0x4904
fffff880`0895ead0 fffff800`02cfb9ef : fffff880`0895f978 fffff880`0895f6e0 fffff880`0895fa20 00000000`00000001 : nt!RtlDispatchException+0x33
fffff880`0895f1b0 fffff800`02cc0d82 : fffff880`0895f978 00000000`000024ff fffff880`0895fa20 00000000`00000001 : nt!KiDispatchException+0x16f
fffff880`0895f840 fffff800`02cbf68a : 00000000`ffffffff fffff880`00000001 00000000`000ceb10 fffffa80`06bd5c68 : nt!KiExceptionDispatch+0xc2
fffff880`0895fa20 fffff960`0016b591 : bffff960`0016b5f1 00000000`00000000 00000000`00000000 00000000`00000001 : nt!KiGeneralProtectionFault+0x10a
fffff880`0895fbb8 bffff960`0016b5f1 : 00000000`00000000 00000000`00000000 00000000`00000001 00000000`00000000 : win32k!xxxRealSleepThread+0x291
fffff880`0895fbc0 00000000`00000000 : 00000000`00000000 00000000`00000001 00000000`00000000 00000000`00000020 : 0xbffff960`0016b5f1

Up to you to update this one, it's not gonna fix it anyway:

RTKVHD64.sys Fri May 22 21:04:20 2009
Realtek Audio (latest is Aug. 2010)

Code:

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


Loading Dump File [F:\a\Minidump\D M P\101110-18891-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 (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02c51000 PsLoadedModuleList = 0xfffff800`02e8ee50
Debug session time: Mon Oct 11 11:21:40.495 2010 (GMT-5)
System Uptime: 0 days 0:04:32.165
Loading Kernel Symbols
...............................................................
................................................................
...........................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck C4, {91, 0, fffffa8006bd5b60, 0}

Probably caused by : win32k.sys ( win32k!xxxRealSleepThread+291 )

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

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

DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
A device driver attempting to corrupt the system has been caught.  This is
because the driver was specified in the registry as being suspect (by the
administrator) and the kernel has enabled substantial checking of this driver.
If the driver attempts to corrupt the system, bugchecks 0xC4, 0xC1 and 0xA will
be among the most commonly seen crashes.
Arguments:
Arg1: 0000000000000091, A driver switched stacks using a method that is not supported by
    the operating system. The only supported way to extend a kernel
    mode stack is by using KeExpandKernelStackAndCallout.
Arg2: 0000000000000000
Arg3: fffffa8006bd5b60
Arg4: 0000000000000000

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


BUGCHECK_STR:  0xc4_91

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  firefox.exe

CURRENT_IRQL:  0

EXCEPTION_RECORD:  fffff8800895f978 -- (.exr 0xfffff8800895f978)
ExceptionAddress: fffff9600016b591 (win32k!xxxRealSleepThread+0x0000000000000291)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

TRAP_FRAME:  fffff8800895fa20 -- (.trap 0xfffff8800895fa20)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000001 rbx=0000000000000000 rcx=000000000004271f
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff9600016b591 rsp=fffff8800895fbb8 rbp=0000000000000000
 r8=fffffa8006bf17b8  r9=0000000000000000 r10=fffffffffffffffd
r11=0000000000000246 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe nc
win32k!xxxRealSleepThread+0x291:
fffff960`0016b591 c3              ret
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002d1624a to fffff80002cc1740

STACK_TEXT:  
fffff880`0895ea88 fffff800`02d1624a : 00000000`000000c4 00000000`00000091 00000000`00000000 fffffa80`06bd5b60 : nt!KeBugCheckEx
fffff880`0895ea90 fffff800`02cee6b3 : fffff8a0`01bea020 fffff880`0895eb70 00000000`00000003 fffff800`02fb410a : nt! ?? ::FNODOBFM::`string'+0x4904
fffff880`0895ead0 fffff800`02cfb9ef : fffff880`0895f978 fffff880`0895f6e0 fffff880`0895fa20 00000000`00000001 : nt!RtlDispatchException+0x33
fffff880`0895f1b0 fffff800`02cc0d82 : fffff880`0895f978 00000000`000024ff fffff880`0895fa20 00000000`00000001 : nt!KiDispatchException+0x16f
fffff880`0895f840 fffff800`02cbf68a : 00000000`ffffffff fffff880`00000001 00000000`000ceb10 fffffa80`06bd5c68 : nt!KiExceptionDispatch+0xc2
fffff880`0895fa20 fffff960`0016b591 : bffff960`0016b5f1 00000000`00000000 00000000`00000000 00000000`00000001 : nt!KiGeneralProtectionFault+0x10a
fffff880`0895fbb8 bffff960`0016b5f1 : 00000000`00000000 00000000`00000000 00000000`00000001 00000000`00000000 : win32k!xxxRealSleepThread+0x291
fffff880`0895fbc0 00000000`00000000 : 00000000`00000000 00000000`00000001 00000000`00000000 00000000`00000020 : 0xbffff960`0016b5f1


STACK_COMMAND:  kb

FOLLOWUP_IP: 
win32k!xxxRealSleepThread+291
fffff960`0016b591 c3              ret

SYMBOL_STACK_INDEX:  6

SYMBOL_NAME:  win32k!xxxRealSleepThread+291

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: win32k

IMAGE_NAME:  win32k.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4c1c483f

FAILURE_BUCKET_ID:  X64_0xc4_91_win32k!xxxRealSleepThread+291

BUCKET_ID:  X64_0xc4_91_win32k!xxxRealSleepThread+291

Followup: MachineOwner

bffff880`03ea5000 bffff880`03ec6000   raspptp  raspptp.sys  unavailable (00000000)
bffff880`03f7d000 bffff880`03f7f000   USBD     USBD.SYS     unavailable (00000000)
bffff880`05d82000 bffff880`05df3000   spsys    spsys.sys    unavailable (00000000)
fffff800`00bb7000 fffff800`00bc1000   kdcom    kdcom.dll    Tue Jul 14 04:31:07 2009 (4A5BDFDB)
fffff800`02c08000 fffff800`02c51000   hal      hal.dll      Tue Jul 14 04:27:36 2009 (4A5BDF08)
fffff800`02c51000 fffff800`0322d000   nt       ntkrnlmp.exe Sat Jun 19 07:16:41 2010 (4C1C44A9)
fffff880`00c14000 fffff880`00c58000   mcupdate_GenuineIntel mcupdate_GenuineIntel.dll Tue Jul 14 04:29:10 2009 (4A5BDF66)
fffff880`00c58000 fffff880`00c6c000   PSHED    PSHED.dll    Tue Jul 14 04:32:23 2009 (4A5BE027)
fffff880`00c6c000 fffff880`00cca000   CLFS     CLFS.SYS     Tue Jul 14 02:19:57 2009 (4A5BC11D)
fffff880`00cca000 fffff880`00d8a000   CI       CI.dll       Tue Jul 14 04:32:13 2009 (4A5BE01D)
fffff880`00d8a000 fffff880`00da4000   mountmgr mountmgr.sys Tue Jul 14 02:19:54 2009 (4A5BC11A)
fffff880`00da4000 fffff880`00dad000   atapi    atapi.sys    Tue Jul 14 02:19:47 2009 (4A5BC113)
fffff880`00dad000 fffff880`00dd7000   ataport  ataport.SYS  Tue Jul 14 02:19:52 2009 (4A5BC118)
fffff880`00dd7000 fffff880`00de2000   msahci   msahci.sys   Tue Jul 14 03:01:01 2009 (4A5BCABD)
fffff880`00de2000 fffff880`00ded000   amdxata  amdxata.sys  Tue May 19 20:56:59 2009 (4A12F2EB)
fffff880`00e00000 fffff880`00e15000   partmgr  partmgr.sys  Tue Jul 14 02:19:58 2009 (4A5BC11E)
fffff880`00e15000 fffff880`00e2a000   volmgr   volmgr.sys   Tue Jul 14 02:19:57 2009 (4A5BC11D)
fffff880`00e2a000 fffff880`00e86000   volmgrx  volmgrx.sys  Tue Jul 14 02:20:33 2009 (4A5BC141)
fffff880`00e86000 fffff880`00e8d000   pciide   pciide.sys   Tue Jul 14 02:19:49 2009 (4A5BC115)
fffff880`00e8d000 fffff880`00e9d000   PCIIDEX  PCIIDEX.SYS  Tue Jul 14 02:19:48 2009 (4A5BC114)
fffff880`00ea1000 fffff880`00f45000   Wdf01000 Wdf01000.sys Tue Jul 14 02:22:07 2009 (4A5BC19F)
fffff880`00f45000 fffff880`00f54000   WDFLDR   WDFLDR.SYS   Tue Jul 14 02:19:54 2009 (4A5BC11A)
fffff880`00f54000 fffff880`00fab000   ACPI     ACPI.sys     Tue Jul 14 02:19:34 2009 (4A5BC106)
fffff880`00fab000 fffff880`00fb4000   WMILIB   WMILIB.SYS   Tue Jul 14 02:19:51 2009 (4A5BC117)
fffff880`00fb4000 fffff880`00fbe000   msisadrv msisadrv.sys Tue Jul 14 02:19:26 2009 (4A5BC0FE)
fffff880`00fbe000 fffff880`00fcb000   vdrvroot vdrvroot.sys Tue Jul 14 03:01:31 2009 (4A5BCADB)
fffff880`00fcb000 fffff880`00ffe000   pci      pci.sys      Tue Jul 14 02:19:51 2009 (4A5BC117)
fffff880`01000000 fffff880`01073000   cng      cng.sys      Tue Jul 14 02:49:40 2009 (4A5BC814)
fffff880`01073000 fffff880`010bf000   volsnap  volsnap.sys  Tue Jul 14 02:20:08 2009 (4A5BC128)
fffff880`010bf000 fffff880`010e3000   rasl2tp  rasl2tp.sys  Tue Jul 14 03:10:11 2009 (4A5BCCE3)
fffff880`010e5000 fffff880`01131000   fltmgr   fltmgr.sys   Tue Jul 14 02:19:59 2009 (4A5BC11F)
fffff880`01131000 fffff880`01145000   fileinfo fileinfo.sys Tue Jul 14 02:34:25 2009 (4A5BC481)
fffff880`01145000 fffff880`011a3000   msrpc    msrpc.sys    Tue Jul 14 02:21:32 2009 (4A5BC17C)
fffff880`011a3000 fffff880`011dd000   rdyboost rdyboost.sys Tue Jul 14 02:34:34 2009 (4A5BC48A)
fffff880`0120a000 fffff880`013ad000   Ntfs     Ntfs.sys     Tue Jul 14 02:20:47 2009 (4A5BC14F)
fffff880`013ad000 fffff880`013c7000   ksecdd   ksecdd.sys   Tue Jul 14 02:20:54 2009 (4A5BC156)
fffff880`013c7000 fffff880`013d8000   pcw      pcw.sys      Tue Jul 14 02:19:27 2009 (4A5BC0FF)
fffff880`013d8000 fffff880`013e2000   Fs_Rec   Fs_Rec.sys   Tue Jul 14 02:19:45 2009 (4A5BC111)
fffff880`013e2000 fffff880`013f8000   AgileVpn AgileVpn.sys Tue Jul 14 03:10:24 2009 (4A5BCCF0)
fffff880`01400000 fffff880`0144a000   fwpkclnt fwpkclnt.sys Tue Jul 14 02:21:08 2009 (4A5BC164)
fffff880`0144a000 fffff880`0145a000   vmstorfl vmstorfl.sys Tue Jul 14 02:42:54 2009 (4A5BC67E)
fffff880`0145a000 fffff880`01462000   spldr    spldr.sys    Mon May 11 19:56:27 2009 (4A0858BB)
fffff880`01462000 fffff880`01474000   mup      mup.sys      Tue Jul 14 02:23:45 2009 (4A5BC201)
fffff880`01476000 fffff880`01568000   ndis     ndis.sys     Tue Jul 14 02:21:40 2009 (4A5BC184)
fffff880`01568000 fffff880`015c8000   NETIO    NETIO.SYS    Tue Jul 14 02:21:46 2009 (4A5BC18A)
fffff880`015c8000 fffff880`015f3000   ksecpkg  ksecpkg.sys  Fri Dec 11 08:03:32 2009 (4B21E0B4)
fffff880`015f3000 fffff880`015fc000   hwpolicy hwpolicy.sys Tue Jul 14 02:19:22 2009 (4A5BC0FA)
fffff880`01600000 fffff880`017fd000   tcpip    tcpip.sys    Mon Jun 14 06:39:04 2010 (4C15A458)
fffff880`01800000 fffff880`01809000   RDPCDD   RDPCDD.sys   Tue Jul 14 03:16:34 2009 (4A5BCE62)
fffff880`01809000 fffff880`01812000   rdpencdd rdpencdd.sys Tue Jul 14 03:16:34 2009 (4A5BCE62)
fffff880`01812000 fffff880`0181b000   rdprefmp rdprefmp.sys Tue Jul 14 03:16:35 2009 (4A5BCE63)
fffff880`0181b000 fffff880`01826000   Msfs     Msfs.SYS     Tue Jul 14 02:19:47 2009 (4A5BC113)
fffff880`01826000 fffff880`01837000   Npfs     Npfs.SYS     Tue Jul 14 02:19:48 2009 (4A5BC114)
fffff880`01837000 fffff880`01855000   tdx      tdx.sys      Tue Jul 14 02:21:15 2009 (4A5BC16B)
fffff880`01855000 fffff880`01862000   TDI      TDI.SYS      Tue Jul 14 02:21:18 2009 (4A5BC16E)
fffff880`01862000 fffff880`018a7000   netbt    netbt.sys    Tue Jul 14 02:21:28 2009 (4A5BC178)
fffff880`018a7000 fffff880`018b7000   CompositeBus CompositeBus.sys Tue Jul 14 03:00:33 2009 (4A5BCAA1)
fffff880`018b7000 fffff880`018c3000   ndistapi ndistapi.sys Tue Jul 14 03:10:00 2009 (4A5BCCD8)
fffff880`018cb000 fffff880`01905000   fvevol   fvevol.sys   Tue Jul 14 02:22:15 2009 (4A5BC1A7)
fffff880`01905000 fffff880`0191b000   disk     disk.sys     Tue Jul 14 02:19:57 2009 (4A5BC11D)
fffff880`0191b000 fffff880`0194b000   CLASSPNP CLASSPNP.SYS Tue Jul 14 02:19:58 2009 (4A5BC11E)
fffff880`01981000 fffff880`019ab000   cdrom    cdrom.sys    Tue Jul 14 02:19:54 2009 (4A5BC11A)
fffff880`019ab000 fffff880`019b4000   Null     Null.SYS     Tue Jul 14 02:19:37 2009 (4A5BC109)
fffff880`019b4000 fffff880`019bb000   Beep     Beep.SYS     Tue Jul 14 03:00:13 2009 (4A5BCA8D)
fffff880`019bb000 fffff880`019c9000   vga      vga.sys      Tue Jul 14 02:38:47 2009 (4A5BC587)
fffff880`019c9000 fffff880`019ee000   VIDEOPRT VIDEOPRT.SYS Tue Jul 14 02:38:51 2009 (4A5BC58B)
fffff880`019ee000 fffff880`019fe000   watchdog watchdog.sys Tue Jul 14 02:37:35 2009 (4A5BC53F)
fffff880`02c00000 fffff880`02c0b000   mssmbios mssmbios.sys Tue Jul 14 02:31:10 2009 (4A5BC3BE)
fffff880`02c0b000 fffff880`02c1a000   discache discache.sys Tue Jul 14 02:37:18 2009 (4A5BC52E)
fffff880`02c1d000 fffff880`02ca7000   afd      afd.sys      Tue Jul 14 02:21:40 2009 (4A5BC184)
fffff880`02ca7000 fffff880`02cb0000   wfplwf   wfplwf.sys   Tue Jul 14 03:09:26 2009 (4A5BCCB6)
fffff880`02cb0000 fffff880`02cd6000   pacer    pacer.sys    Tue Jul 14 03:09:41 2009 (4A5BCCC5)
fffff880`02cd6000 fffff880`02cea000   vpcnfltr vpcnfltr.sys Thu Jul 23 01:20:17 2009 (4A6790A1)
fffff880`02cea000 fffff880`02cf9000   netbios  netbios.sys  Tue Jul 14 03:09:26 2009 (4A5BCCB6)
fffff880`02cf9000 fffff880`02d16000   serial   serial.sys   Tue Jul 14 03:00:40 2009 (4A5BCAA8)
fffff880`02d16000 fffff880`02d31000   wanarp   wanarp.sys   Tue Jul 14 03:10:21 2009 (4A5BCCED)
fffff880`02d31000 fffff880`02d86c00   vpcvmm   vpcvmm.sys   Thu Jul 23 01:20:22 2009 (4A6790A6)
fffff880`02d87000 fffff880`02d9b000   termdd   termdd.sys   Tue Jul 14 03:16:36 2009 (4A5BCE64)
fffff880`02d9b000 fffff880`02dec000   rdbss    rdbss.sys    Tue Jul 14 02:24:09 2009 (4A5BC219)
fffff880`02dec000 fffff880`02df8000   nsiproxy nsiproxy.sys Tue Jul 14 02:21:02 2009 (4A5BC15E)
fffff880`03a00000 fffff880`03a56000   USBPORT  USBPORT.SYS  Tue Jul 14 03:06:31 2009 (4A5BCC07)
fffff880`03a56000 fffff880`03a7a000   HDAudBus HDAudBus.sys Tue Jul 14 03:06:13 2009 (4A5BCBF5)
fffff880`03a7a000 fffff880`03a8c000   L1E62x64 L1E62x64.sys Mon Mar 29 05:08:44 2010 (4BB00BAC)
fffff880`03a8c000 fffff880`03aca000   1394ohci 1394ohci.sys Tue Jul 14 03:07:12 2009 (4A5BCC30)
fffff880`03aca000 fffff880`03ad7000   fdc      fdc.sys      Tue Jul 14 03:00:54 2009 (4A5BCAB6)
fffff880`03ad7000 fffff880`03af5000   i8042prt i8042prt.sys Tue Jul 14 02:19:57 2009 (4A5BC11D)
fffff880`03afd000 fffff880`03b80000   csc      csc.sys      Tue Jul 14 02:24:26 2009 (4A5BC22A)
fffff880`03b80000 fffff880`03b9e000   dfsc     dfsc.sys     Tue Jul 14 02:23:44 2009 (4A5BC200)
fffff880`03b9e000 fffff880`03baf000   blbdrive blbdrive.sys Tue Jul 14 02:35:59 2009 (4A5BC4DF)
fffff880`03baf000 fffff880`03bd5000   tunnel   tunnel.sys   Tue Jul 14 03:09:37 2009 (4A5BCCC1)
fffff880`03bd5000 fffff880`03beb000   intelppm intelppm.sys Tue Jul 14 02:19:25 2009 (4A5BC0FD)
fffff880`03beb000 fffff880`03bfa000   kbdclass kbdclass.sys Tue Jul 14 02:19:50 2009 (4A5BC116)
fffff880`03e00000 fffff880`03e5a000   usbhub   usbhub.sys   Tue Jul 14 03:07:09 2009 (4A5BCC2D)
fffff880`03e5b000 fffff880`03e8a000   ndiswan  ndiswan.sys  Tue Jul 14 03:10:11 2009 (4A5BCCE3)
fffff880`03e8a000 fffff880`03ea5000   raspppoe raspppoe.sys Tue Jul 14 03:10:17 2009 (4A5BCCE9)
fffff880`03ec6000 fffff880`03ee0000   rassstp  rassstp.sys  Tue Jul 14 03:10:25 2009 (4A5BCCF1)
fffff880`03ee0000 fffff880`03eeb000   rdpbus   rdpbus.sys   Tue Jul 14 03:17:46 2009 (4A5BCEAA)
fffff880`03eeb000 fffff880`03efa000   mouclass mouclass.sys Tue Jul 14 02:19:50 2009 (4A5BC116)
fffff880`03efa000 fffff880`03efb480   swenum   swenum.sys   Tue Jul 14 03:00:18 2009 (4A5BCA92)
fffff880`03efc000 fffff880`03f3f000   ks       ks.sys       Tue Jul 14 03:00:31 2009 (4A5BCA9F)
fffff880`03f3f000 fffff880`03f51000   umbus    umbus.sys    Tue Jul 14 03:06:56 2009 (4A5BCC20)
fffff880`03f51000 fffff880`03f6e000   vpcusb   vpcusb.sys   Thu Jul 23 01:20:23 2009 (4A6790A7)
fffff880`03f6e000 fffff880`03f7d000   usbrpm   usbrpm.sys   Tue Jul 14 03:35:14 2009 (4A5BD2C2)
fffff880`03f7f000 fffff880`03fbb000   vpchbus  vpchbus.sys  Thu Jul 23 01:20:23 2009 (4A6790A7)
fffff880`03fbb000 fffff880`03fc6000   flpydisk flpydisk.sys Tue Jul 14 03:00:54 2009 (4A5BCAB6)
fffff880`03fc6000 fffff880`03fdb000   NDProxy  NDProxy.SYS  Tue Jul 14 03:10:05 2009 (4A5BCCDD)
fffff880`05028000 fffff880`051d4900   RTKVHD64 RTKVHD64.sys Fri May 22 21:04:20 2009 (4A16E924)
fffff880`05200000 fffff880`05215000   LHidFilt LHidFilt.Sys Thu Mar 18 10:51:17 2010 (4BA1E985)
fffff880`05215000 fffff880`05222000   mouhid   mouhid.sys   Tue Jul 14 03:00:20 2009 (4A5BCA94)
fffff880`05222000 fffff880`05236000   LMouFilt LMouFilt.Sys Thu Mar 18 10:51:24 2010 (4BA1E98C)
fffff880`05236000 fffff880`05259000   luafv    luafv.sys    Tue Jul 14 02:26:13 2009 (4A5BC295)
fffff880`05259000 fffff880`0527a000   WudfPf   WudfPf.sys   Tue Jul 14 03:05:37 2009 (4A5BCBD1)
fffff880`0527a000 fffff880`0528f000   lltdio   lltdio.sys   Tue Jul 14 03:08:50 2009 (4A5BCC92)
fffff880`0528f000 fffff880`052a7000   rspndr   rspndr.sys   Tue Jul 14 03:08:50 2009 (4A5BCC92)
fffff880`052db000 fffff880`05318000   portcls  portcls.sys  Tue Jul 14 03:06:27 2009 (4A5BCC03)
fffff880`05318000 fffff880`0533a000   drmk     drmk.sys     Tue Jul 14 04:01:25 2009 (4A5BD8E5)
fffff880`0533a000 fffff880`0533f200   ksthunk  ksthunk.sys  Tue Jul 14 03:00:19 2009 (4A5BCA93)
fffff880`05340000 fffff880`0534c000   Dxapi    Dxapi.sys    Tue Jul 14 02:38:28 2009 (4A5BC574)
fffff880`0534c000 fffff880`0535a000   crashdmp crashdmp.sys Tue Jul 14 03:01:01 2009 (4A5BCABD)
fffff880`0535a000 fffff880`05366000   dump_dumpata dump_dumpata.sys Tue Jul 14 02:19:47 2009 (4A5BC113)
fffff880`05366000 fffff880`0536f000   dump_atapi dump_atapi.sys Tue Jul 14 02:19:47 2009 (4A5BC113)
fffff880`0536f000 fffff880`05382000   dump_dumpfve dump_dumpfve.sys Tue Jul 14 02:21:51 2009 (4A5BC18F)
fffff880`05382000 fffff880`05390000   monitor  monitor.sys  Tue Jul 14 02:38:52 2009 (4A5BC58C)
fffff880`05390000 fffff880`053ab000   USBSTOR  USBSTOR.SYS  Tue Jul 14 03:06:34 2009 (4A5BCC0A)
fffff880`053ab000 fffff880`053c8000   usbccgp  usbccgp.sys  Tue Jul 14 03:06:45 2009 (4A5BCC15)
fffff880`053c8000 fffff880`053d6000   hidusb   hidusb.sys   Tue Jul 14 03:06:22 2009 (4A5BCBFE)
fffff880`053d6000 fffff880`053ef000   HIDCLASS HIDCLASS.SYS Tue Jul 14 03:06:21 2009 (4A5BCBFD)
fffff880`053ef000 fffff880`053f7080   HIDPARSE HIDPARSE.SYS Tue Jul 14 03:06:17 2009 (4A5BCBF9)
fffff880`0585e000 fffff880`05926000   HTTP     HTTP.sys     Tue Jul 14 02:22:16 2009 (4A5BC1A8)
fffff880`05926000 fffff880`05944000   bowser   bowser.sys   Tue Jul 14 02:23:50 2009 (4A5BC206)
fffff880`05944000 fffff880`0595c000   mpsdrv   mpsdrv.sys   Tue Jul 14 03:08:25 2009 (4A5BCC79)
fffff880`0595c000 fffff880`05989000   mrxsmb   mrxsmb.sys   Sat Feb 27 09:52:19 2010 (4B88CF33)
fffff880`05989000 fffff880`059d7000   mrxsmb10 mrxsmb10.sys Sat Feb 27 09:52:28 2010 (4B88CF3C)
fffff880`059d7000 fffff880`059fa000   mrxsmb20 mrxsmb20.sys Sat Feb 27 09:52:26 2010 (4B88CF3A)
fffff880`05c00000 fffff880`05c68000   srv2     srv2.sys     Tue Jun 22 06:20:47 2010 (4C202C0F)
fffff880`05c92000 fffff880`05d38000   peauth   peauth.sys   Tue Jul 14 04:01:19 2009 (4A5BD8DF)
fffff880`05d38000 fffff880`05d43000   secdrv   secdrv.SYS   Wed Sep 13 16:18:38 2006 (4508052E)
fffff880`05d43000 fffff880`05d70000   srvnet   srvnet.sys   Tue Jun 22 06:20:32 2010 (4C202C00)
fffff880`05d70000 fffff880`05d82000   tcpipreg tcpipreg.sys Tue Jul 14 03:09:49 2009 (4A5BCCCD)
fffff880`060a0000 fffff880`06136000   srv      srv.sys      Tue Jun 22 06:21:11 2010 (4C202C27)
fffff880`06136000 fffff880`06140000   dgderdrv dgderdrv.sys Wed Jul 21 04:56:51 2010 (4C4653E3)
fffff880`06140000 fffff880`06171000   WUDFRd   WUDFRd.sys   Tue Jul 14 03:06:06 2009 (4A5BCBEE)
fffff880`06171000 fffff880`061a7000   fastfat  fastfat.SYS  Tue Jul 14 02:23:28 2009 (4A5BC1F0)
fffff880`0fe00000 fffff880`0fe46000   dxgmms1  dxgmms1.sys  Tue Jul 14 02:38:32 2009 (4A5BC578)
fffff880`0fe46000 fffff880`0fe52000   serenum  serenum.sys  Tue Jul 14 03:00:33 2009 (4A5BCAA1)
fffff880`0fe52000 fffff880`10ae3e00   nvlddmkm nvlddmkm.sys Sat Jul 10 00:15:58 2010 (4C37918E)
fffff880`10ae4000 fffff880`10ae5180   nvBridge nvBridge.kmd Sat Jul 10 00:07:54 2010 (4C378FAA)
fffff880`10ae6000 fffff880`10bda000   dxgkrnl  dxgkrnl.sys  Fri Oct 02 04:00:14 2009 (4AC5509E)
fffff880`10bda000 fffff880`10be7000   usbuhci  usbuhci.sys  Tue Jul 14 03:06:27 2009 (4A5BCC03)
fffff880`10be7000 fffff880`10bf8000   usbehci  usbehci.sys  Tue Jul 14 03:06:30 2009 (4A5BCC06)
fffff880`10bf8000 fffff880`10c00000   ASACPI   ASACPI.sys   Thu May 14 04:25:17 2009 (4A0B72FD)
fffff960`000a0000 fffff960`003af000   win32k   win32k.sys   Sat Jun 19 07:31:59 2010 (4C1C483F)
fffff960`005a0000 fffff960`005aa000   TSDDD    TSDDD.dll    unavailable (00000000)
fffff960`006f0000 fffff960`00717000   cdd      cdd.dll      Wed May 19 22:48:26 2010 (4BF4408A)
fffff960`00810000 fffff960`00871000   ATMFD    ATMFD.DLL    Thu May 27 07:11:31 2010 (4BFDF0F3)

Unloaded modules:
fffff880`0194b000 fffff880`01959000   crashdmp.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
fffff880`01959000 fffff880`01965000   dump_ataport
    Timestamp: unavailable (00000000)
    Checksum:  00000000
fffff880`01965000 fffff880`0196e000   dump_atapi.s
    Timestamp: unavailable (00000000)
    Checksum:  00000000
fffff880`0196e000 fffff880`01981000   dump_dumpfve
    Timestamp: unavailable (00000000)
    Checksum:  00000000

lightice · Oct 11, 2010

Now that it started, it's been working since it crashed earlier.

I'll update the sound driver and run the HDDscan.
Will i need to post any report on the HDD scan?
Running the test now using
READ on my c:/ HDD.

I'll run memtest tonight through the night again, is there any specific test # that you want me to do?

I'm not sure if this information is useful:
I always get the BSOD when I do a first boot after having the computer unplugged from the power socket for several hours.
After I manage to boot back into windows, it seems to work fine and can run for the day.

cybercore · Oct 11, 2010

Run SMART with HDD scan and when it's done see if it gives you any yellow/red warnings - save them.

lightice · Oct 11, 2010

So I select the drives and just click the S.M.A.R.T button right?
Sort of instant report generation.

I did this on all my internal and my 1 external HDD.

All green indicators. No yellow/red at all.

cybercore · Oct 11, 2010

If you already did, skip it and proceed with the memtest.

lightice · Oct 11, 2010

Ok, I'll load memtest now and let it run. Thanks

Update: 2 passes no errors, I'd let it run for 12h at least today.

Btw, assuming memtest doesn't detect any errors, What course of action do we look to do next?

Update 1: Going for 5h + its 0 errors, Will let it continue.

lightice · Oct 11, 2010

Okay, I'm not sure if this is useful information.

But my RAM package says that the ram is supposed to be
4-4-4-12 , 2.2v

But memtest86 is showing 5-5-5-16

It is running at 400mhz (DDR800).

I stopped the memtest86 at 7 full passes to change the ram settings in BIOS.

I changed the ram to 4-4-4-12 and the voltage to 2.2, which is what the RAM is rated for.

I also increased the FSB termination voltage to 1.3, NB voltage to 1.3 as well. (These were in auto earlier, I read in the patriot forums that increasing these voltages with 4 DIMMS will help stabilise the system)
But now in memtest, it shows my FSB frequency to be 334mhz, it was 333mhz before.

I'll let memtest go thru the rest of the night or 12h. Should be done by lunch tomorrow.

lightice · Oct 11, 2010

Okay, BSOD again.

This time I was doing a search through a PDF file and I got BSOD.
Here is the dmp file and perfmon report.

The latest dmp file is dated 12 oct.

lightice · Oct 11, 2010

Well, I memtest while sleeping and came up with 6 errors.

I'll try replacing the ram later and run tests using the new ram chip.

1 error was in the 47mb area, the other 5 were in the 4000 mb area, same spot.

CarlTR6 · Oct 11, 2010

You might want to test each RAM stick separately, one at a time to isolate the bad one. YOU should also test each RAM slot with a known good stick.

lightice · Oct 12, 2010

I'm actually thinking of changing it to a 2x2gb config from a 4x1gb that I am currently using now though.

I'll try and check the individual slots/chips to see which is the one giving me errors.

lightice · Oct 18, 2010

Okay, I did extensive testing today.
Running 4 chips, I get tons of errors.

But running 1 chip at a time, I get 0 errors even with different slots.

What now?

How am I going to diagnose this problem?

Pirl · Oct 18, 2010

Sounds like I was right.

Same thing on my system with 4x2GB (two different kits of 2x2GB, each of which is fine on its own in either pair of coloured slots)

I haven't yet tried getting my system stable with 4 sticks, but what I'd try is the higher NB voltage with the 'stock' CL5 timings and default RAM voltage. (My logic says the looser timings should be easier on the NB)

lightice · Oct 18, 2010

Hi Pirl,

Thanks for staying with me on this issue. And with the others as well.

I did try higher NB voltage -> it was @ 1.4v when the thing just died on me and memtest gave me tons of errors.
But after that, I was on looser CL5 timing, the stock is CL4, but I left the NB @ 1.4.

Then I did further tests using CL5 , nb @ 1.4v and did the single chip/single slot , double chip + double slot test. And went through them fine.

5-5-5-16, does this sound about right?
I had the DRAM volts at 2.2, which is what the ram is made for, should I decrease/increase this?
Now it's set to AUTO in bios.

I reverted all voltages back to AUTO and i managed to boot up into windows with 4 chips.

Pirl · Oct 18, 2010

5-5-5-18 1.8v is what mine is currently running at (set to auto with a kit rated at 4-4-4-12 2.1v)
However, I've only got two sticks at the moment (I need the stability for now, will tinker with four sticks in a couple of weeks - what I'm saying now is what I plan to try myself when I can)

Set the RAM to auto and bump the NB voltage +1.0, +1.5, +2.0 volts (as long as that's still under 1.6v)
If it's still crashing, 1.9v at CL5 with +1.0 NB, +1.5, +2.0.
If still then, do a bit more research.

I was able to boot and run windows for between 10 minutes and almost two days before it'd blue screen, so it's unfortunately not always quick to see if the changes make any real difference.

lightice · Oct 18, 2010

You mean +0.1v NB right?
Because auto = 1.1v , if I add in +1 then it's above 1.6.

I'll try the suggestion out Pril, but for now I need to get some work done. :s

CarlTR6 · Oct 18, 2010

lightice said:
Okay, I did extensive testing today.
Running 4 chips, I get tons of errors.

But running 1 chip at a time, I get 0 errors even with different slots.

What now? How am I going to diagnose this problem?

I am not a RAM expert by any means. The good news is, you have found your problem. It looks like your RAM slots are OK. Now to solve it. For that, I am going to call in the RAM experts. Be patient and you will get some really good help with this.

BSOD again

New member

My Computer

New member

My Computer

New member

My Computer

cybercore

My Computer

New member

My Computer

cybercore

My Computer

New member

My Computer

cybercore

My Computer

New member

My Computer

New member

My Computer

New member

My Computer

New member

My Computer

Antique Senior Member

My Computer

New member

My Computer

New member

My Computer

New member

My Computer

New member

My Computer

New member

My Computer

New member

My Computer

Antique Senior Member

My Computer

Similar threads