1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.
  2. You are viewing our forum as a guest. For full access please Register. WindowsBBS.com is completely free, paid for by advertisers and donations.

PAGE_FAULT_IN_NONPAGED_AREA from 8GB of RAM in x64 Windows XP

Discussion in 'Windows XP' started by Iscabis, 2008/09/29.

  1. 2008/09/29
    Iscabis

    Iscabis Inactive Thread Starter

    Joined:
    2008/09/11
    Messages:
    12
    Likes Received:
    0
    Trophy Points:
    76
    Computer Experience:
    Experienced
    As you can see from my system specs, I am running XP Pro x64. 4GB of RAM ran just fine, but 3 weeks ago I tried putting 4GB more and I started getting the 0x50 PAGE_FAULT_IN_NONPAGED_AREA BSOD. Everytime, disks.sys was noted as the faulty file in the Blue Screen message. I found the DebugWiz program on here, and I analyzed all my minidumps with it. Out of the 22 debug log files from my BSOD minidumps, 19 or 20 were always caused by the same file: wmiprvse.exe. I will be sure to post the most recent log that happened last night at the end of my message. Let me explain everything I have tried first in the past 3 weeks to help anyone reading this narrow down what can be done to possibly fix my issue.
    --------------------------------------------------------------------------

    ***I have not OC'ed anything at all, so that isn't an issue***

    All the RAM is the exact same type, brand and model number, so that shouldn't be an issue. I have tried the newer 4GB of RAM by itself and that did not cause any problem. I have tested all the RAM slots on my motherboard, and they are all working. I have run memtest86+ multiple times and there were no errors. So I think it is safe to say that the RAM is not the issue.

    I have verified my video card software is not the issue, since I have tried a 7600gt as well and I got the same BSOD. I have a SATA controller card, but even with that out I still got the BSOD. I updated my motherboard BIOS and drivers to the latest version, and the BSOD still occurred. I tried disconnecting a problematic hard drive, but still got the BSOD. I also uninstalled my AV program, but that didn't help either. I have tried almost everything at this point. I have reinstalled Windows about 5 times, and nothing worked.

    I eventually was able to isolate something that triggered the BSOD, and this was my Realtek lan driver. Right after installing my motherboard drivers (the first thing after installing Windows) and restarting, I installed my lan drivers and got the BSOD. When I uninstalled it, my computer was stable with the 8GB of RAM. Knowing this, I purchased an Intel network card hoping this would solve my problem once and for all. It did, for almost 24 hours. I think after starting Steam my computer spit out the BSOD again.

    This biggest problem with this was sometimes I got the BSOD right after Windows was done logging in and starting the programs up. Other times, like the one I just mentioned, it seemed like I had fixed the problem before I got the BSOD again. I would even be able to use the internet sometimes for a long period of time before the BSOD happened. It would appear that there is something wrong with the wmiprvse.exe file in Windows and having 8GB of RAM and possibly some other driver getting angry as well. Sometimes, there is both a SYSTEM one and a NETWORK SERVICE one in task manager. I am guessing the NETWORK SERVICE one is the culprit, but I do not know enough about that stuff to know for sure.

    Sorry for being so long-winded with all this. It's just that I have already done so much troubleshooting on my own that I thought it would help anyone reading this to fix the problem easier if I told them what I did. I am completely defeated on this one for the time being. I reloaded Windows with only the 4GB of RAM until I find an answer to this issue. I don't mind running on 4GB of RAM, but it is the fact that my computer SHOULD be able to handle 8GB of RAM that worries me. Plus, I already bought it, so I would kind of like to use it and not let it collect dust in the package.

    Thanks to anyone who takes the time to read this long post. Below this is the latest debug log as I mentioned in the beginning. I have 21 others if they are needed. Just let me know.


    Iscabis
    **********************************************************

    Opened log file 'c:\debuglog.txt'

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


    Loading Dump File [D:\Main Backup\Mini092808-01.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: C:\WINDOWS;C:\WINDOWS\system32;C:\WINDOWS\system32\drivers
    *** WARNING: Unable to verify checksum for ntkrnlmp.exe
    Windows Server 2003 Kernel Version 3790 (Service Pack 1) MP (4 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 3790.srv03_sp1_rtm.050324-1447
    Kernel base = 0xfffff800`01000000 PsLoadedModuleList = 0xfffff800`011ad0c0
    Debug session time: Sun Sep 28 13:12:07.406 2008 (GMT-4)
    System Uptime: 0 days 0:18:24.531
    *** WARNING: Unable to verify checksum for ntkrnlmp.exe
    Loading Kernel Symbols
    ...........................................................................................................
    Loading User Symbols
    Loading unloaded module list
    ..............................
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 50, {fffffadfd8514850, 0, fffffadf28e2d290, 0}

    *** WARNING: Unable to verify checksum for disk.sys

    Could not read faulting driver name
    *** WARNING: Unable to verify checksum for PartMgr.sys
    *** WARNING: Unable to verify checksum for fltMgr.sys
    Probably caused by : disk.sys ( disk!memcpy+60 )

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

    0: kd> !analyze -v;r;kv;lmtn;.logclose;q
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    PAGE_FAULT_IN_NONPAGED_AREA (50)
    Invalid system memory was referenced. This cannot be protected by try-except,
    it must be protected by a Probe. Typically the address is just plain bad or it
    is pointing at freed memory.
    Arguments:
    Arg1: fffffadfd8514850, memory referenced.
    Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
    Arg3: fffffadf28e2d290, If non-zero, the instruction address which referenced the bad memory
    address.
    Arg4: 0000000000000000, (reserved)

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


    Could not read faulting driver name

    READ_ADDRESS: fffffadfd8514850

    FAULTING_IP:
    disk!memcpy+60
    fffffadf`28e2d290 488b040a mov rax,qword ptr [rdx+rcx]

    MM_INTERNAL_CODE: 0

    CUSTOMER_CRASH_COUNT: 1

    DEFAULT_BUCKET_ID: DRIVER_FAULT

    BUGCHECK_STR: 0x50

    PROCESS_NAME: wmiprvse.exe

    CURRENT_IRQL: 1

    TRAP_FRAME: fffffadf26f7d520 -- (.trap 0xfffffadf26f7d520)
    .trap 0xfffffadf26f7d520
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=fffffadf373038b0 rbx=0000000000000000 rcx=fffffadf3738eee0
    rdx=00000000a1185970 rsi=fffffa8061446353 rdi=0000000000000034
    rip=fffffadf28e2d290 rsp=fffffadf26f7d6b8 rbp=fffffadf37ec61b0
    r8=0000000000000018 r9=0000000000000003 r10=5be6ebd002150008
    r11=fffffadf3738eee0 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0 nv up ei pl nz na po nc
    disk!memcpy+0x60:
    fffffadf`28e2d290 488b040a mov rax,qword ptr [rdx+rcx] ds:0004:fffffadf`d8514850=????????????????
    .trap
    Resetting default scope

    LAST_CONTROL_TRANSFER: from fffff800010a43ab to fffff800010501d0

    STACK_TEXT:
    fffffadf`26f7d448 fffff800`010a43ab : 00000000`00000050 fffffadf`d8514850 00000000`00000000 fffffadf`26f7d520 : nt!KeBugCheckEx
    fffffadf`26f7d450 fffff800`0104ee19 : 00000000`00000003 fffffadf`28e44537 fffffadf`385d1f00 fffffadf`385d1f40 : nt!MmAccessFault+0xa22
    fffffadf`26f7d520 fffffadf`28e2d290 : fffffadf`28e2a8dd 00000000`00000000 fffffadf`375e8010 00000000`00000000 : nt!KiPageFault+0x119
    fffffadf`26f7d6b8 fffffadf`28e2a8dd : 00000000`00000000 fffffadf`375e8010 00000000`00000000 fffffadf`37ec6670 : disk!memcpy+0x60
    fffffadf`26f7d6c0 fffffadf`294562a5 : 00000000`c0100080 fffffadf`26f7d950 fffffadf`37302510 fffffadf`26f7dcf0 : disk!DiskDeviceControl+0x7ed
    fffffadf`26f7d930 fffff800`013667fe : fffffadf`37302510 fffffadf`26f7dcf0 00000000`00000000 fffffadf`37302510 : PartMgr!PmDeviceControl+0x49a
    fffffadf`26f7d9c0 fffffadf`28dd4962 : ffffffff`ffffffff fffffadf`37302510 00000000`00000000 fffffadf`372fc7f0 : nt!RawDispatch+0x15e
    fffffadf`26f7da10 fffff800`0129abc0 : 00000000`00000000 fffffadf`26f7dcf0 00000000`00000001 fffffadf`385d1f40 : fltMgr!FltpDispatch+0x1c2
    fffffadf`26f7da70 fffff800`0129ac76 : fffffadf`373c28f0 00000000`00000000 00000000`00000000 00000000`00000000 : nt!IopXxxControlFile+0xa69
    fffffadf`26f7db90 fffff800`0104fce2 : fffffadf`26f7dc18 00000000`00000000 00000000`7dbed001 fffffadf`373c28f0 : nt!NtDeviceIoControlFile+0x56
    fffffadf`26f7dc00 00000000`78ef12da : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x3
    00000000`00e1de68 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x78ef12da


    STACK_COMMAND: kb

    FOLLOWUP_IP:
    disk!memcpy+60
    fffffadf`28e2d290 488b040a mov rax,qword ptr [rdx+rcx]

    SYMBOL_STACK_INDEX: 3

    SYMBOL_NAME: disk!memcpy+60

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: disk

    IMAGE_NAME: disk.sys

    DEBUG_FLR_IMAGE_TIMESTAMP: 42435dc8

    FAILURE_BUCKET_ID: X64_0x50_disk!memcpy+60

    BUCKET_ID: X64_0x50_disk!memcpy+60

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

    rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000050
    rdx=fffffadfd8514850 rsi=fffffadfd8514850 rdi=fffffadf385cf760
    rip=fffff800010501d0 rsp=fffffadf26f7d448 rbp=fffff6fd6fec28a0
    r8=0000000000000000 r9=fffffadf26f7d520 r10=fffff6fb7dbed000
    r11=0000000000000001 r12=fffffadf37302510 r13=fffffadf26f7d520
    r14=fffff800011b42c0 r15=0000000000000000
    iopl=0 nv up ei pl zr na po nc
    cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00000246
    nt!KeBugCheckEx:
    fffff800`010501d0 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:fffffadf`26f7d450=0000000000000050
    Child-SP RetAddr : Args to Child : Call Site
    fffffadf`26f7d448 fffff800`010a43ab : 00000000`00000050 fffffadf`d8514850 00000000`00000000 fffffadf`26f7d520 : nt!KeBugCheckEx
    fffffadf`26f7d450 fffff800`0104ee19 : 00000000`00000003 fffffadf`28e44537 fffffadf`385d1f00 fffffadf`385d1f40 : nt!MmAccessFault+0xa22
    fffffadf`26f7d520 fffffadf`28e2d290 : fffffadf`28e2a8dd 00000000`00000000 fffffadf`375e8010 00000000`00000000 : nt!KiPageFault+0x119 (TrapFrame @ fffffadf`26f7d520)
    fffffadf`26f7d6b8 fffffadf`28e2a8dd : 00000000`00000000 fffffadf`375e8010 00000000`00000000 fffffadf`37ec6670 : disk!memcpy+0x60
    fffffadf`26f7d6c0 fffffadf`294562a5 : 00000000`c0100080 fffffadf`26f7d950 fffffadf`37302510 fffffadf`26f7dcf0 : disk!DiskDeviceControl+0x7ed
    fffffadf`26f7d930 fffff800`013667fe : fffffadf`37302510 fffffadf`26f7dcf0 00000000`00000000 fffffadf`37302510 : PartMgr!PmDeviceControl+0x49a
    fffffadf`26f7d9c0 fffffadf`28dd4962 : ffffffff`ffffffff fffffadf`37302510 00000000`00000000 fffffadf`372fc7f0 : nt!RawDispatch+0x15e
    fffffadf`26f7da10 fffff800`0129abc0 : 00000000`00000000 fffffadf`26f7dcf0 00000000`00000001 fffffadf`385d1f40 : fltMgr!FltpDispatch+0x1c2
    fffffadf`26f7da70 fffff800`0129ac76 : fffffadf`373c28f0 00000000`00000000 00000000`00000000 00000000`00000000 : nt!IopXxxControlFile+0xa69
    fffffadf`26f7db90 fffff800`0104fce2 : fffffadf`26f7dc18 00000000`00000000 00000000`7dbed001 fffffadf`373c28f0 : nt!NtDeviceIoControlFile+0x56
    fffffadf`26f7dc00 00000000`78ef12da : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x3 (TrapFrame @ fffffadf`26f7dc70)
    00000000`00e1de68 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x78ef12da
    start end module name
    fffff800`00800000 fffff800`0085e000 hal hal.dll Thu Mar 24 20:39:38 2005 (42435DCA)
    fffff800`01000000 fffff800`0146e000 nt ntkrnlmp.exe Thu Mar 24 20:53:55 2005 (42436123)
    fffff97f`ff000000 fffff97f`ff45c000 win32k win32k.sys Thu Mar 24 20:51:20 2005 (42436088)
    fffff97f`ff45c000 fffff97f`ff483000 dxg dxg.sys Thu Mar 24 23:54:35 2005 (42438B7B)
    fffff97f`ff483000 fffff97f`ff48d000 framebuf framebuf.dll Thu Mar 24 23:54:35 2005 (42438B7B)
    fffffadf`26990000 fffffadf`26a5a000 srv srv.sys Thu Mar 24 20:51:01 2005 (42436075)
    fffffadf`26ae6000 fffffadf`26b76000 HTTP HTTP.sys Thu Mar 24 20:52:42 2005 (424360DA)
    fffffadf`26cc0000 fffffadf`26d09000 mrxdav mrxdav.sys Thu Mar 24 20:40:14 2005 (42435DEE)
    fffffadf`272e1000 fffffadf`2730e000 dump_atapi dump_atapi.sys Thu Mar 24 20:39:30 2005 (42435DC2)
    fffffadf`2730e000 fffffadf`2732f000 Cdfs Cdfs.SYS Thu Mar 24 20:50:49 2005 (42436069)
    fffffadf`2732f000 fffffadf`27344000 HIDCLASS HIDCLASS.SYS Thu Mar 24 20:43:28 2005 (42435EB0)
    fffffadf`2738a000 fffffadf`27456000 mrxsmb mrxsmb.sys Thu Mar 24 20:52:07 2005 (424360B7)
    fffffadf`27456000 fffffadf`274a7000 rdbss rdbss.sys Thu Mar 24 20:52:51 2005 (424360E3)
    fffffadf`274a7000 fffffadf`274c7000 arp1394 arp1394.sys Thu Mar 24 20:37:57 2005 (42435D65)
    fffffadf`274c7000 fffffadf`27515000 afd afd.sys Thu Mar 24 20:52:53 2005 (424360E5)
    fffffadf`27515000 fffffadf`27578000 netbt netbt.sys Thu Mar 24 20:53:49 2005 (4243611D)
    fffffadf`27578000 fffffadf`275b0000 ipnat ipnat.sys Thu Mar 24 20:43:59 2005 (42435ECF)
    fffffadf`275b0000 fffffadf`27671000 tcpip tcpip.sys Thu Mar 24 20:51:31 2005 (42436093)
    fffffadf`27671000 fffffadf`2769c000 ipsec ipsec.sys Thu Mar 24 20:55:00 2005 (42436164)
    fffffadf`2769c000 fffffadf`276b0000 Npfs Npfs.SYS Thu Mar 24 20:40:08 2005 (42435DE8)
    fffffadf`276b0000 fffffadf`276bb000 ndisuio ndisuio.sys Thu Mar 24 20:43:19 2005 (42435EA7)
    fffffadf`27f30000 fffffadf`27f50000 usbhub usbhub.sys Thu Mar 24 20:43:35 2005 (42435EB7)
    fffffadf`28050000 fffffadf`28064000 NDProxy NDProxy.SYS Thu Mar 24 20:44:07 2005 (42435ED7)
    fffffadf`280aa000 fffffadf`280c0000 termdd termdd.sys Thu Mar 24 20:37:51 2005 (42435D5F)
    fffffadf`280c0000 fffffadf`28116000 rdpdr rdpdr.sys Thu Mar 24 20:40:26 2005 (42435DFA)
    fffffadf`28126000 fffffadf`28132000 kbdhid kbdhid.sys Thu Mar 24 20:38:12 2005 (42435D74)
    fffffadf`28136000 fffffadf`28140000 mouhid mouhid.sys Thu Mar 24 20:38:12 2005 (42435D74)
    fffffadf`28166000 fffffadf`28170000 hidusb hidusb.sys Thu Mar 24 20:43:29 2005 (42435EB1)
    fffffadf`28176000 fffffadf`28180600 usbccgp usbccgp.sys Thu Mar 24 20:43:37 2005 (42435EB9)
    fffffadf`281b6000 fffffadf`281cc000 msgpc msgpc.sys Thu Mar 24 20:43:36 2005 (42435EB8)
    fffffadf`281cc000 fffffadf`281ec000 psched psched.sys Thu Mar 24 20:43:39 2005 (42435EBB)
    fffffadf`281ec000 fffffadf`2820f000 raspptp raspptp.sys Thu Mar 24 20:54:55 2005 (4243615F)
    fffffadf`2820f000 fffffadf`28223000 raspppoe raspppoe.sys Thu Mar 24 20:44:12 2005 (42435EDC)
    fffffadf`28223000 fffffadf`2824f000 ndiswan ndiswan.sys Thu Mar 24 20:54:57 2005 (42436161)
    fffffadf`2824f000 fffffadf`28275000 rasl2tp rasl2tp.sys Thu Mar 24 20:54:11 2005 (42436133)
    fffffadf`28275000 fffffadf`282be000 ks ks.sys Thu Mar 24 20:51:08 2005 (4243607C)
    fffffadf`282be000 fffffadf`282d4000 redbook redbook.sys Thu Mar 24 20:39:21 2005 (42435DB9)
    fffffadf`282d4000 fffffadf`282ef000 cdrom cdrom.sys Thu Mar 24 20:39:39 2005 (42435DCB)
    fffffadf`282ef000 fffffadf`28306000 imapi imapi.sys Thu Mar 24 20:40:04 2005 (42435DE4)
    fffffadf`28306000 fffffadf`2832b000 parport parport.sys Thu Mar 24 20:38:46 2005 (42435D96)
    fffffadf`2832b000 fffffadf`2834e000 serial serial.sys Thu Mar 24 20:38:54 2005 (42435D9E)
    fffffadf`2834e000 fffffadf`2836a000 nic1394 nic1394.sys Thu Mar 24 20:37:57 2005 (42435D65)
    fffffadf`2836a000 fffffadf`2839ce00 e1G5132e e1G5132e.sys Wed Nov 07 14:20:09 2007 (47320FE9)
    fffffadf`2839d000 fffffadf`283d7000 USBPORT USBPORT.SYS Thu Mar 24 20:43:32 2005 (42435EB4)
    fffffadf`283d7000 fffffadf`283fa000 VIDEOPRT VIDEOPRT.SYS Thu Mar 24 20:42:27 2005 (42435E73)
    fffffadf`28bce000 fffffadf`28c04000 Mup Mup.sys Thu Mar 24 20:52:51 2005 (424360E3)
    fffffadf`28c04000 fffffadf`28c5f000 NDIS NDIS.sys Thu Mar 24 20:53:38 2005 (42436112)
    fffffadf`28c5f000 fffffadf`28d77000 Ntfs Ntfs.sys Thu Mar 24 20:51:14 2005 (42436082)
    fffffadf`28d77000 fffffadf`28daa000 KSecDD KSecDD.sys Thu Mar 24 20:40:20 2005 (42435DF4)
    fffffadf`28daa000 fffffadf`28dcd000 sr sr.sys Thu Mar 24 20:43:35 2005 (42435EB7)
    fffffadf`28dcd000 fffffadf`28e0a000 fltMgr fltMgr.sys Thu Mar 24 20:40:28 2005 (42435DFC)
    fffffadf`28e0a000 fffffadf`28e29000 CLASSPNP CLASSPNP.SYS Thu Mar 24 20:50:34 2005 (4243605A)
    fffffadf`28e29000 fffffadf`28e3e000 disk disk.sys Thu Mar 24 20:39:36 2005 (42435DC8)
    fffffadf`28e3e000 fffffadf`28e6b000 atapi atapi.sys Thu Mar 24 20:39:30 2005 (42435DC2)
    fffffadf`28e6b000 fffffadf`28eb6000 volsnap volsnap.sys Thu Mar 24 20:40:09 2005 (42435DE9)
    fffffadf`28eb6000 fffffadf`28efc000 dmio dmio.sys Thu Mar 24 20:42:32 2005 (42435E78)
    fffffadf`28efc000 fffffadf`28f3c000 ftdisk ftdisk.sys Thu Mar 24 20:39:53 2005 (42435DD9)
    fffffadf`28f3c000 fffffadf`28f52000 MountMgr MountMgr.sys Thu Mar 24 20:38:07 2005 (42435D6F)
    fffffadf`28f52000 fffffadf`28f65a00 1394BUS 1394BUS.SYS Thu Mar 24 20:43:44 2005 (42435EC0)
    fffffadf`28f66000 fffffadf`28f7cc80 ohci1394 ohci1394.sys Thu Mar 24 20:43:44 2005 (42435EC0)
    fffffadf`28f7d000 fffffadf`28f9e000 pci pci.sys Thu Mar 24 20:43:33 2005 (42435EB5)
    fffffadf`28f9e000 fffffadf`28ff2000 ACPI ACPI.sys Thu Mar 24 20:43:26 2005 (42435EAE)
    fffffadf`29106000 fffffadf`29118000 intelppm intelppm.sys Thu Mar 24 20:39:38 2005 (42435DCA)
    fffffadf`29119000 fffffadf`2912b000 wanarp wanarp.sys Thu Mar 24 20:44:05 2005 (42435ED5)
    fffffadf`2912c000 fffffadf`2913e000 netbios netbios.sys Thu Mar 24 20:43:27 2005 (42435EAF)
    fffffadf`2913f000 fffffadf`29151000 Fips Fips.SYS Thu Mar 24 20:43:13 2005 (42435EA1)
    fffffadf`29152000 fffffadf`29163000 USBSTOR USBSTOR.SYS Thu Mar 24 20:43:35 2005 (42435EB7)
    fffffadf`293fb000 fffffadf`29405000 kdcom kdcom.dll Thu Mar 24 23:54:15 2005 (42438B67)
    fffffadf`2940b000 fffffadf`29414000 BOOTVID BOOTVID.dll Thu Mar 24 23:54:04 2005 (42438B5C)
    fffffadf`2941b000 fffffadf`29424000 WMILIB WMILIB.SYS Thu Mar 24 20:43:56 2005 (42435ECC)
    fffffadf`2942b000 fffffadf`29434000 isapnp isapnp.sys Thu Mar 24 20:43:32 2005 (42435EB4)
    fffffadf`2943b000 fffffadf`2944b000 PCIIDEX PCIIDEX.SYS Thu Mar 24 20:39:25 2005 (42435DBD)
    fffffadf`2944b000 fffffadf`2945b000 PartMgr PartMgr.sys Thu Mar 24 20:50:42 2005 (42436062)
    fffffadf`2945b000 fffffadf`29466000 crcdisk crcdisk.sys Thu Mar 24 20:42:06 2005 (42435E5E)
    fffffadf`2949b000 fffffadf`294a6000 raspti raspti.sys Thu Mar 24 20:44:11 2005 (42435EDB)
    fffffadf`294bb000 fffffadf`294c5200 HIDPARSE HIDPARSE.SYS Thu Mar 24 20:43:26 2005 (42435EAE)
    fffffadf`294cb000 fffffadf`294d5000 ndistapi ndistapi.sys Thu Mar 24 20:44:06 2005 (42435ED6)
    fffffadf`294db000 fffffadf`294eb000 update update.sys Thu Mar 24 20:38:07 2005 (42435D6F)
    fffffadf`294eb000 fffffadf`294f8000 Msfs Msfs.SYS Thu Mar 24 20:40:07 2005 (42435DE7)
    fffffadf`294fb000 fffffadf`29507000 serenum serenum.sys Thu Mar 24 20:38:50 2005 (42435D9A)
    fffffadf`2950b000 fffffadf`29515000 rasacd rasacd.sys Thu Mar 24 20:44:16 2005 (42435EE0)
    fffffadf`2952b000 fffffadf`29535000 mnmdd mnmdd.SYS Thu Mar 24 20:42:22 2005 (42435E6E)
    fffffadf`2953b000 fffffadf`2954a000 TDI TDI.SYS Thu Mar 24 20:46:57 2005 (42435F81)
    fffffadf`2955b000 fffffadf`29564000 dump_WMILIB dump_WMILIB.SYS Thu Mar 24 20:43:56 2005 (42435ECC)
    fffffadf`2956b000 fffffadf`29578000 mouclass mouclass.sys Thu Mar 24 20:38:09 2005 (42435D71)
    fffffadf`2957b000 fffffadf`29589000 vga vga.sys Thu Mar 24 20:42:24 2005 (42435E70)
    fffffadf`2959b000 fffffadf`295a8000 mssmbios mssmbios.sys Thu Mar 24 20:43:35 2005 (42435EB7)
    fffffadf`295ab000 fffffadf`295b7000 flpydisk flpydisk.sys Thu Mar 24 20:39:10 2005 (42435DAE)
    fffffadf`295cb000 fffffadf`295d8000 ptilink ptilink.sys Thu Mar 24 20:38:44 2005 (42435D94)
    fffffadf`295db000 fffffadf`295e9000 kbdclass kbdclass.sys Thu Mar 24 20:38:09 2005 (42435D71)
    fffffadf`295eb000 fffffadf`295f7000 Dxapi Dxapi.sys Thu Mar 24 20:39:08 2005 (42435DAC)
    fffffadf`295fb000 fffffadf`29605000 RDPCDD RDPCDD.sys Thu Mar 24 20:38:04 2005 (42435D6C)
    fffffadf`2960b000 fffffadf`29615980 usbehci usbehci.sys Thu Mar 24 20:43:31 2005 (42435EB3)
    fffffadf`2961b000 fffffadf`29624000 watchdog watchdog.sys Thu Mar 24 20:43:05 2005 (42435E99)
    fffffadf`2964b000 fffffadf`29655000 Fs_Rec Fs_Rec.SYS Thu Mar 24 20:39:42 2005 (42435DCE)
    fffffadf`2965b000 fffffadf`29669000 fdc fdc.sys Thu Mar 24 20:39:10 2005 (42435DAE)
    fffffadf`2966b000 fffffadf`29672f00 usbuhci usbuhci.sys Thu Mar 24 20:43:34 2005 (42435EB6)
    fffffadf`29673000 fffffadf`2967b000 audstub audstub.sys Thu Mar 24 20:43:08 2005 (42435E9C)
    fffffadf`2967b000 fffffadf`29683000 Null Null.SYS Thu Mar 24 20:38:07 2005 (42435D6F)
    fffffadf`2969b000 fffffadf`296a3000 CdaC15BA CdaC15BA.sys Wed Dec 10 10:11:51 2003 (3FD737B7)
    fffffadf`296a3000 fffffadf`296ab000 CdaD10BA CdaD10BA.sys Wed Dec 10 10:11:51 2003 (3FD737B7)
    fffffadf`296ab000 fffffadf`296b3000 secdrv secdrv.sys Thu Apr 01 07:26:05 2004 (406BFC4D)
    fffffadf`297fb000 fffffadf`29802000 pciide pciide.sys Thu Mar 24 20:39:26 2005 (42435DBE)
    fffffadf`29802000 fffffadf`29809000 dmload dmload.sys Thu Mar 24 20:42:29 2005 (42435E75)
    fffffadf`29944000 fffffadf`29949e80 ksthunk ksthunk.sys Thu Mar 24 20:38:16 2005 (42435D78)
    fffffadf`299c9000 fffffadf`299d0000 Beep Beep.SYS Thu Mar 24 20:38:06 2005 (42435D6E)
    fffffadf`29bab000 fffffadf`29bac400 swenum swenum.sys Thu Mar 24 20:38:18 2005 (42435D7A)
    fffffadf`29bb5000 fffffadf`29bb6d80 USBD USBD.SYS Thu Mar 24 20:43:30 2005 (42435EB2)

    Unloaded modules:
    fffffadf`26ea1000 fffffadf`26edf000 HDAudBus.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    fffffadf`272d0000 fffffadf`2730e000 HDAudBus.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    fffffadf`272d0000 fffffadf`2730e000 HDAudBus.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    fffffadf`272d0000 fffffadf`2730e000 HDAudBus.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    fffffadf`272f1000 fffffadf`2732f000 HDAudBus.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    fffffadf`27306000 fffffadf`27344000 HDAudBus.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    fffffadf`27306000 fffffadf`27344000 HDAudBus.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    fffffadf`27306000 fffffadf`27344000 HDAudBus.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    fffffadf`27306000 fffffadf`27344000 HDAudBus.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    fffffadf`27306000 fffffadf`27344000 HDAudBus.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    fffffadf`27306000 fffffadf`27344000 HDAudBus.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    fffffadf`2958b000 fffffadf`29597000 kbdhid.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    fffffadf`27753000 fffffadf`27770000 i8042prt.SYS
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    fffffadf`295eb000 fffffadf`295f4000 Sfloppy.SYS
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    fffffadf`27732000 fffffadf`27770000 HDAudBus.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    fffffadf`27732000 fffffadf`27770000 HDAudBus.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    fffffadf`27732000 fffffadf`27770000 HDAudBus.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    fffffadf`27752000 fffffadf`27790000 HDAudBus.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    fffffadf`278c5000 fffffadf`27903000 HDAudBus.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    fffffadf`279c5000 fffffadf`27a03000 HDAudBus.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    fffffadf`27ac5000 fffffadf`27b03000 HDAudBus.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    fffffadf`27bc5000 fffffadf`27c03000 HDAudBus.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    fffffadf`27cf2000 fffffadf`27d30000 HDAudBus.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    fffffadf`27df2000 fffffadf`27e30000 HDAudBus.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    fffffadf`27ef2000 fffffadf`27f30000 HDAudBus.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    fffffadf`28012000 fffffadf`28050000 HDAudBus.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    fffffadf`28012000 fffffadf`28050000 HDAudBus.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    fffffadf`2963b000 fffffadf`29649000 vgapnp.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    fffffadf`2806c000 fffffadf`280aa000 HDAudBus.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    fffffadf`28399000 fffffadf`283d7000 HDAudBus.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    Closing open log file c:\debuglog.txt
     
  2. 2008/09/30
    Arie

    Arie Administrator Administrator Staff

    Joined:
    2001/12/27
    Messages:
    14,912
    Likes Received:
    379
    Trophy Points:
    1,093
    I suggest you start by running chkdsk /f to check your hard drive for errors.

    Also note
    I suggest running sfc /Scannow to make sure the system files are all OK.

    Lastly I wouldn't want to be running x64 Windows XP, that's only a stop-gap x64 solution.
     
    Arie,
    #2

  3. to hide this advert.

  4. 2008/09/30
    Iscabis

    Iscabis Inactive Thread Starter

    Joined:
    2008/09/11
    Messages:
    12
    Likes Received:
    0
    Trophy Points:
    76
    Computer Experience:
    Experienced
    I will run those scans after I get back from work today.

    I have been running XP Pro x64 for a long time now, and this is the first major problem I have ever had with it. Do you think it is possible that even though it should be able to support 8GB of RAM that there is inherently something wrong with it that it gives me these issues? When I have 4GB of RAM present, I get no issues. It is only when 8GB is present that anything bad happens.

    The only option that I would have for switching OS's would be to go back to x86 XP, but then I wouldn't be able to even use all of my 4GB of RAM so I won't be doing that.

    Thanks for the reply. I will get back to you after I run those scans.
     
  5. 2008/09/30
    Iscabis

    Iscabis Inactive Thread Starter

    Joined:
    2008/09/11
    Messages:
    12
    Likes Received:
    0
    Trophy Points:
    76
    Computer Experience:
    Experienced
    Alright, I got both of your recommendations done.

    I ran chkdsk /f on all of my hdd's, and I ran sfc /scannow a few times just in case. No error messages popped up, nor were any problems found with any of the tests.

    Even if x64 XP is only a stop-gap solution, it is the only option I have right now for an x64 OS. My main purpose for my computer is gaming, so Linux would not fit my needs so well. If Vista is a "better" x64 route, I don't want to purchase it now since Windows 7 could be here in 2010. Plus, I am one of those people who would like to avoid Vista if at all possible.

    Do you think it is possible that the system files themselves are behaving funny when 8GB of RAM is present? That is the only other explanation I can think of right now. If you have any more input, then great. If not, that is fine too. I am willing to admit defeat on this one if that becomes my only remaining option.

    Thanks a lot for your help so far by the way! The sfc tool is something I did not know existed, but it can definitely come in handy in the future. Also, I do have a lot more debug logs if you think those can help a bit.
     
  6. 2008/10/01
    Arie

    Arie Administrator Administrator Staff

    Joined:
    2001/12/27
    Messages:
    14,912
    Likes Received:
    379
    Trophy Points:
    1,093
    No, XP x64 should be able to handle 8GB of RAM. This could be an incompatibility between the RAM (since it seems you had 4GB originally and added another 4GB recently). Make sure that the RAM is compatible with the motherboard.
     
    Arie,
    #5
  7. 2008/10/01
    Iscabis

    Iscabis Inactive Thread Starter

    Joined:
    2008/09/11
    Messages:
    12
    Likes Received:
    0
    Trophy Points:
    76
    Computer Experience:
    Experienced
    I have verified that all the modules are the same and are definitely compatible with my motherboard. The only time my computer would crash is after I installed the software for my onboard lan. It also crashed after ditching the onboard and using a brand new Intel network card. After uninstalling the onboard lan originally, my computer would become stable again with the 8GB of RAM. Or at least it seemed stable. I installed a lot of other things after uninstalling the onboard lan and everything went fine. But, my computer did not always crash right away, so it may have been an illusion. The preceding is why I suspect something network-related. I also believe that whenever my computer didn't crash right away after start up, I was be doing something on the internet.

    Either way, I swear it is Windows and the way the "network service" version of wmiprvse.exe is behaving. Thanks again for your help. Any other suggestions? Do I need to start making angry phonecalls to Microsoft? ;)
     
  8. 2008/10/02
    Arie

    Arie Administrator Administrator Staff

    Joined:
    2001/12/27
    Messages:
    14,912
    Likes Received:
    379
    Trophy Points:
    1,093
    Check in your BIOS if you have NVIDIA's "Active Armour" firewall protection. If so, switch it off.
     
    Arie,
    #7
  9. 2008/10/02
    Iscabis

    Iscabis Inactive Thread Starter

    Joined:
    2008/09/11
    Messages:
    12
    Likes Received:
    0
    Trophy Points:
    76
    Computer Experience:
    Experienced
    I have never seen that in the settings anywhere. Plus, I have an Intel chipset, so it should not be there anyway. I don't have any firewalls active except for the hardware one built in to my router. Thank you for the suggestion though! The search continues...
     
  10. 2008/10/04
    Iscabis

    Iscabis Inactive Thread Starter

    Joined:
    2008/09/11
    Messages:
    12
    Likes Received:
    0
    Trophy Points:
    76
    Computer Experience:
    Experienced
    Does anyone have any more advice on this one? Do you think this would be a good time to use Microsoft tech support and ask about this? Thanks in advance.
     
  11. 2008/10/07
    Iscabis

    Iscabis Inactive Thread Starter

    Joined:
    2008/09/11
    Messages:
    12
    Likes Received:
    0
    Trophy Points:
    76
    Computer Experience:
    Experienced
    Anymore advice on this issue at all? If not, then no big deal. If no more help comes and I eventually figure this out, I will reply here saying so. But, I am pretty sure I can't solve this one on my own.
     
  12. 2008/10/07
    rsinfo

    rsinfo SuperGeek Alumni

    Joined:
    2005/12/25
    Messages:
    3,813
    Likes Received:
    147
    Trophy Points:
    843
    Location:
    New Delhi, India
    Computer Experience:
    Experienced but ! en
    Does your motherboard supports 8 GB without poking around in BIOS ?

    From the symptoms it seems that Windows is using some area reserved by BIOS. Look in BIOS if you have any option to switch this reservation off or on or even move the memory areas around.
     
  13. 2008/10/07
    Iscabis

    Iscabis Inactive Thread Starter

    Joined:
    2008/09/11
    Messages:
    12
    Likes Received:
    0
    Trophy Points:
    76
    Computer Experience:
    Experienced
    That is definitely something I have not considered. I will check that out and reply back here with the results. Thanks!
     
  14. 2008/10/13
    Iscabis

    Iscabis Inactive Thread Starter

    Joined:
    2008/09/11
    Messages:
    12
    Likes Received:
    0
    Trophy Points:
    76
    Computer Experience:
    Experienced
    I looked through all of the settings in my BIOS, and I never saw anything related to turning this memory reservation off or even moving it around. Is there any way to set something like this in Windows? Or, any other thoughts on this? I have little faith that using Microsoft tech support would help any unless I knew the exact problem that was happening. I could try Gigabyte tech support if no one has anymore suggestions.

    Thanks for all the help and suggestions thus far! Keep them up if you can.
     
    Last edited: 2008/10/13
  15. 2008/10/23
    Iscabis

    Iscabis Inactive Thread Starter

    Joined:
    2008/09/11
    Messages:
    12
    Likes Received:
    0
    Trophy Points:
    76
    Computer Experience:
    Experienced
    Just wanted to check one more time if anyone else had any suggestions before I see what Gigabyte and Microsoft have to say. Thanks!
     
  16. 2009/11/09
    dreamie

    dreamie Inactive

    Joined:
    2009/11/08
    Messages:
    5
    Likes Received:
    0
    Trophy Points:
    76
    Computer Experience:
    experienced
    I've just had similar issue where a gigabyte MB didnt work properly with 8gb RAM while 4GB is just fine. After googling the issue I found out the issue is that the gigabyte MB operates on 1.8v for ram while my OCZ Reaper needs at least 2.1v. So I simply changed the voltage in my MB bios and no more BSOD's. By now it's on 2.0 and everything finally works fine.

    I know this thread is a year old but since I had the same issue just now, it might assist others who encounter this issue too.
     
    Last edited: 2009/11/09
  17. 2009/11/09
    Iscabis

    Iscabis Inactive Thread Starter

    Joined:
    2008/09/11
    Messages:
    12
    Likes Received:
    0
    Trophy Points:
    76
    Computer Experience:
    Experienced
    I am finally following up that I was never able to find a solution to my problem. However, dreamie seems to have some excellent input in the previous post that could help many people in this situation.

    Nothing I tried with my configuration fixed my problem. I verified this recently before upgrading to Windows 7. With Windows 7 I have no problems with more than 4GB of RAM. I completely skipped Vista like many people did, and I have to say Windows 7 is great so far. For anyone holding out with XP, Windows 7 does seem to be the right one to switch to.

    Since I didn't change anything in my configuration, there must have been something weird with the Gigabyte drivers and XP Pro x64. Windows 7 installs motherboard drivers automatically for you too. So if you can't find drivers for your motherboard online, you should be ok.

    Sorry if I sound like a spokesperson for the new OS, but it really is a fine piece of software. Until January 2010, students with a valid university email address can get Windows 7 for only $30!

    So that is my followup on this mess I had ages ago. All of the things suggested in this thread are great methods for finding the source of your problem. If all else fails, upgrading to Windows 7 should definitely fix your problem once and for all.

    Good luck to anyone still wrestling with this problem!


    Iscabis
     
  18. 2009/11/10
    dreamie

    dreamie Inactive

    Joined:
    2009/11/08
    Messages:
    5
    Likes Received:
    0
    Trophy Points:
    76
    Computer Experience:
    experienced
    Well in my case I really tried everything and pretty much had your same symptoms and same error and trial results. I was this close installing windows 7 too but then I realized if it's a wrong voltage in the bios issue then a diff OS won't make it any better.

    In the end I guess your cause of the issue was still different since I looked at your corsair requirements (if you still use the same one) and 1.8v-1.9v should be fine, unlike my OCZ Reaper that must be using at least 2.0v
     
  19. 2009/11/10
    Iscabis

    Iscabis Inactive Thread Starter

    Joined:
    2008/09/11
    Messages:
    12
    Likes Received:
    0
    Trophy Points:
    76
    Computer Experience:
    Experienced
    Yeah, that is very true.

    I am using the same Corsair RAM, and I messed with the voltages when I had the other RAM before switching. It seemed to help for awhile, but eventually failed in the end as a solution.

    Regardless, using proper voltages is definitely very important.
     
  20. 2009/11/14
    dreamie

    dreamie Inactive

    Joined:
    2009/11/08
    Messages:
    5
    Likes Received:
    0
    Trophy Points:
    76
    Computer Experience:
    experienced
    Hah. It appears our issues were a like more then I thought. My voltage modifications also hold for a few days and then those annoying bsod's came back.. So I finally switched to win7 and now finally I'm crash free. :)
     
  21. 2009/11/14
    tashman847

    tashman847 Inactive

    Joined:
    2009/11/03
    Messages:
    112
    Likes Received:
    4
    Trophy Points:
    108
    Location:
    Bristol, UK
    Computer Experience:
    Intermediate
    Hi Iscabis have you updated your motherboards BIOS out of interest?

    Just out of interest what board are you running?

    Can you list your system specs including PSU.

    Thanks :)

    Tom
     

Share This Page