1. You are viewing our forum as a guest. For full access please Register. WindowsBBS.com is completely free, paid for by advertisers and donations.

Different BSOD, can't get into windows

Discussion in 'Windows XP' started by mahme, 2008/03/20.

  1. 2008/03/20
    mahme

    mahme Inactive Thread Starter

    Joined:
    2008/03/18
    Messages:
    20
    Likes Received:
    0
    Hi

    I bought new pc parts and built my computer about a week ago, all went fine and it did run fine the first week without any problem. Then suddenly i got BSOD all of a sudden and they didn't go away and i reformated my computer yesterday and it all looked fine but again this morning BSOD all the time, i can't even get into windows (normal, last working settings or safe mode)

    1) DRIVER_IRQL_NOT_LESS_OR_EQUAL

    *** STOP: 0x000000D1 (0x8E78100A, 0x00000006, 0X00000001, 0xBAB28C3F)

    *** PCIIDEX.SYS - Adress BAB28C3F base at BAB28000, DateStamp 41107b4c

    2) PAGE_FAULT_IN_NONPAGED_AREA

    *** STOP: 0x00000050 ......

    3)

    *** STOP: 0x0000000A ......

    what should i do, what could be wrong?

    Hardware:
    Gigabyte GA-73PVM-S2H
    Intel Dual Core E2160 1.8GHz 800MHz S775
    Transcend 2048MB DDR2 PC2-6400 800MHz
    Seagate's Barracuda 7200.9 160GB S-ATA
    520W "No-Name" PSU
     
  2. 2008/03/20
    mailman Lifetime Subscription

    mailman Geek Member

    Joined:
    2004/01/17
    Messages:
    1,901
    Likes Received:
    11
    Hi, mahme. Welcome to Windows BBS! :)

    The following page might be a good place to start.

    Faulty PSUs are sometimes the cause of startup issues. You may want to consider replacing your PSU with a reputable brand/model that you are certain is capable of handling all the hardware for your computer. If the PSU turns out to not be the culprit, then at least you'll have a spare to use for troubleshooting the next time you run into similar issues.
    PSU quality apparently varies widely. People seem to recommend good quality PSUs that have at least 18A on the +12V rail(s).
     

  3. to hide this advert.

  4. 2008/03/20
    mahme

    mahme Inactive Thread Starter

    Joined:
    2008/03/18
    Messages:
    20
    Likes Received:
    0
    Hi thx for the reply.

    I checked my PSU and it had 25A on the +12V rail. And i used it on my previous P4 system. And since I use integrated network,graphic and sound I can't really see how the PSU wouldn't be able to run them proparly.
     
  5. 2008/03/20
    mailman Lifetime Subscription

    mailman Geek Member

    Joined:
    2004/01/17
    Messages:
    1,901
    Likes Received:
    11
  6. 2008/03/21
    mahme

    mahme Inactive Thread Starter

    Joined:
    2008/03/18
    Messages:
    20
    Likes Received:
    0
    Tried repair and did another reformat and I still can't still get into windows before it gets a bluescreen during startup. I updated BIOS successfully to the lated version and it didn't help either. Could the motherboard be broken or something? I know it's not the RAM since I did a 15hour memtest86 without any errors, and my harddrive passed chkdsk without any errors, the PSU should be powerfull enough since I use integrated network,sound & graphic. Any ideas?
     
  7. 2008/03/21
    hawk22

    hawk22 Geek Member

    Joined:
    2002/01/31
    Messages:
    1,991
    Likes Received:
    26
    sounds like hardware have you re-checked all the cables, no loose wires dangling around.
    Is the 4 pin 12 volt connected properly on the mobo
     
    Last edited: 2008/03/21
  8. 2008/03/21
    mailman Lifetime Subscription

    mailman Geek Member

    Joined:
    2004/01/17
    Messages:
    1,901
    Likes Received:
    11
    RAM testers do not detect all memory faults and opinions differ about which RAM tester is "best ".

    • Microsoft KB134503:

    Perhaps a different memory tester will detect errors.

    In case you decide to use other testers...If you discover an error with any of these RAM testers and the RAM tester does not identify which RAM module is defective, then re-run the test with only a single RAM module installed until you identify which module is defective. (I am not familiar with the exact information output of any of these RAM testers when they find errors.)

    ==========

    A More Reliable RAM Testing Method:
    1. Remove some of the memory modules from the computer (while the computer is off, of course).
      • For example, if two RAM modules are installed in your computer, remove one of the RAM modules.
    2. Start your computer and see if the problem goes away.
    3. If you continue to have unexpected reboots/BSODs, then replace that RAM module with another module, or install the module in a different memory slot.
    4. Start your computer and see if the problem goes away.
    Continue this process to see if you can pinpoint the cause of your problem to a specific RAM module or slot.
     
    Last edited: 2008/03/21
  9. 2008/03/21
    mailman Lifetime Subscription

    mailman Geek Member

    Joined:
    2004/01/17
    Messages:
    1,901
    Likes Received:
    11
    PSUs have gone bad on me more than once in the past. I am not ready to conclude your 520W "No-Name" PSU is not faulty.

    According to the Journey Systems link I provided above,
    I am still inclined to suggest you consider replacing your PSU with a reputable brand/model with plenty of power. (See the 10stripe and JohnnyGURU links I provided above to help you decide which brands/models of PSUs would be suitable.)

    If you want to check out prices and customer reviews, then here are a couple Newegg links.
     
  10. 2008/03/21
    mahme

    mahme Inactive Thread Starter

    Joined:
    2008/03/18
    Messages:
    20
    Likes Received:
    0
    hawk22
    Yes, all the cable are where they should be, i have checked and double checked.

    mailman
    Someone suggested i should run memtest86 at test5 for a hour, and guess what it reported back 2 errors. Now im running Microsoft's Windows Memory Diagnostic and im gonna let in run over night just to check if it finds anything. I dont have another PSU to try with at the moment so I can't check that..

    Since I could't get into winxp I decided to install winvista and I ran into bluescreens after 5min in vista but since i had 5min i could run a debug heres the output:

    Opened log file 'c:\debuglog.txt'

    Microsoft (R) Windows Debugger Version 6.8.0004.0 X86
    Copyright (c) Microsoft Corporation. All rights reserved.


    Loading Dump File [C:\Windows\Minidump\Mini032108-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
    Windows Vista Kernel Version 6000 MP (2 procs) Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 6000.16584.x86fre.vista_gdr.071023-1545
    Kernel base = 0x81800000 PsLoadedModuleList = 0x81911e10
    Debug session time: Fri Mar 21 10:57:07.164 2008 (GMT-7)
    System Uptime: 0 days 0:36:34.851
    Loading Kernel Symbols
    ..........................................................................................................................................
    Loading User Symbols
    Loading unloaded module list
    .....
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 1000000A, {0, 2, 0, 818bcda4}



    Probably caused by : memory_corruption ( nt!MiReplenishPageSlist+e5 )

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

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

    IRQL_NOT_LESS_OR_EQUAL (a)
    An attempt was made to access a pageable (or completely invalid) address at an
    interrupt request level (IRQL) that is too high. This is usually
    caused by drivers using improper addresses.
    If a kernel debugger is available get the stack backtrace.
    Arguments:
    Arg1: 00000000, memory referenced
    Arg2: 00000002, IRQL
    Arg3: 00000000, bitfield :
    bit 0 : value 0 = read operation, 1 = write operation
    bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
    Arg4: 818bcda4, address which referenced memory

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




    READ_ADDRESS: GetPointerFromAddress: unable to read from 819315ac
    Unable to read MiSystemVaType memory at 819117e0
    00000000

    CURRENT_IRQL: 2

    FAULTING_IP:
    nt!MiReplenishPageSlist+e5
    818bcda4 8b08 mov ecx,dword ptr [eax]

    CUSTOMER_CRASH_COUNT: 1

    DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

    BUGCHECK_STR: 0xA

    PROCESS_NAME: svchost.exe

    TRAP_FRAME: 8b1c796c -- (.trap 0xffffffff8b1c796c)
    .trap 0xffffffff8b1c796c
    ErrCode = 00000002
    eax=9dd52000 ebx=00001000 ecx=00016ffe edx=00000000 esi=8323509c edi=9dd52000
    eip=818e7728 esp=8b1c79e0 ebp=8b1c7a28 iopl=0 nv up ei ng nz na pe nc
    cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010286
    nt!ExAllocatePoolWithTag+0x71d:
    818e7728 832700 and dword ptr [edi],0 ds:0023:9dd52000=????????
    .trap
    Resetting default scope

    LAST_CONTROL_TRANSFER: from 818bcf51 to 818bcda4

    STACK_TEXT:
    8b1c77b8 818bcf51 818f39b4 00000004 860114c0 nt!MiReplenishPageSlist+0xe5
    8b1c77e0 818bd4a3 c04eea90 00000000 839f6030 nt!MiRemoveAnyPage+0xf2
    8b1c781c 8182a4f2 00000001 9dd52000 c04eea90 nt!MiResolveDemandZeroFault+0x4cd
    8b1c78d8 818aaf05 9dd52000 00000000 00000000 nt!MiDispatchFault+0xa8b
    8b1c7954 8188fbb4 00000001 9dd52000 00000000 nt!MmAccessFault+0x1119
    8b1c7954 818e7728 00000001 9dd52000 00000000 nt!KiTrap0E+0xdc
    8b1c7a28 86ed7372 00000011 00000370 6666744e nt!ExAllocatePoolWithTag+0x71d
    8b1c7a40 86f4b942 86efcd20 8b9a95e4 96fd80f8 Ntfs!ExAllocateFromPagedLookasideList+0x27
    8b1c7ac4 86f4a8d1 85d3fc30 840630d8 00000000 Ntfs!NtfsCreateFcb+0x16f
    8b1c7c04 86f64318 85d3fc30 83f08de0 96fd80f8 Ntfs!NtfsOpenFile+0x1c3
    8b1c7cec 86ed96b6 85d3fc30 83f08de0 9597293c Ntfs!NtfsCommonCreate+0xe39
    8b1c7d2c 818803e8 959728d4 00000000 ffffffff Ntfs!NtfsCommonCreateCallout+0x20
    8b1c7d2c 818804e1 959728d4 00000000 ffffffff nt!KiSwapKernelStackAndExit+0x118
    9597286c 00000000 00000000 00000000 00000000 nt!KiSwitchKernelStackAndCallout+0x31


    STACK_COMMAND: kb

    FOLLOWUP_IP:
    nt!MiReplenishPageSlist+e5
    818bcda4 8b08 mov ecx,dword ptr [eax]

    SYMBOL_STACK_INDEX: 0

    SYMBOL_NAME: nt!MiReplenishPageSlist+e5

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: nt

    DEBUG_FLR_IMAGE_TIMESTAMP: 471ea39c

    IMAGE_NAME: memory_corruption

    FAILURE_BUCKET_ID: 0xA_nt!MiReplenishPageSlist+e5

    BUCKET_ID: 0xA_nt!MiReplenishPageSlist+e5

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

    eax=00000000 ebx=818f39b4 ecx=ffffffff edx=82a92370 esi=831fc970 edi=00000006
    eip=818bcda4 esp=8b1c7798 ebp=8b1c77b8 iopl=0 nv up ei pl nz na pe nc
    cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010206
    nt!MiReplenishPageSlist+0xe5:
    818bcda4 8b08 mov ecx,dword ptr [eax] ds:0023:00000000=????????
    ChildEBP RetAddr Args to Child
    8b1c77b8 818bcf51 818f39b4 00000004 860114c0 nt!MiReplenishPageSlist+0xe5
    8b1c77e0 818bd4a3 c04eea90 00000000 839f6030 nt!MiRemoveAnyPage+0xf2
    8b1c781c 8182a4f2 00000001 9dd52000 c04eea90 nt!MiResolveDemandZeroFault+0x4cd
    8b1c78d8 818aaf05 9dd52000 00000000 00000000 nt!MiDispatchFault+0xa8b
    8b1c7954 8188fbb4 00000001 9dd52000 00000000 nt!MmAccessFault+0x1119
    8b1c7954 818e7728 00000001 9dd52000 00000000 nt!KiTrap0E+0xdc (FPO: [0,0] TrapFrame @ 8b1c796c)
    8b1c7a28 86ed7372 00000011 00000370 6666744e nt!ExAllocatePoolWithTag+0x71d
    8b1c7a40 86f4b942 86efcd20 8b9a95e4 96fd80f8 Ntfs!ExAllocateFromPagedLookasideList+0x27 (FPO: [Non-Fpo])
    8b1c7ac4 86f4a8d1 85d3fc30 840630d8 00000000 Ntfs!NtfsCreateFcb+0x16f (FPO: [Non-Fpo])
    8b1c7c04 86f64318 85d3fc30 83f08de0 96fd80f8 Ntfs!NtfsOpenFile+0x1c3 (FPO: [Non-Fpo])
    8b1c7cec 86ed96b6 85d3fc30 83f08de0 9597293c Ntfs!NtfsCommonCreate+0xe39 (FPO: [Non-Fpo])
    8b1c7d2c 818803e8 959728d4 00000000 ffffffff Ntfs!NtfsCommonCreateCallout+0x20 (FPO: [Non-Fpo])
    8b1c7d2c 818804e1 959728d4 00000000 ffffffff nt!KiSwapKernelStackAndExit+0x118 (FPO: [0,0] TrapFrame @ 8b1c7d44)
    9597286c 00000000 00000000 00000000 00000000 nt!KiSwitchKernelStackAndCallout+0x31
    start end module name
    80204000 8020d000 WMILIB WMILIB.SYS Thu Nov 02 01:54:53 2006 (4549B25D)
    8020d000 8021a000 WDFLDR WDFLDR.SYS Wed Dec 05 18:21:19 2007 (47575C9F)
    8021a000 80255000 CLFS CLFS.SYS Wed Dec 05 17:55:42 2007 (4757569E)
    80255000 8025d000 BOOTVID BOOTVID.dll Thu Nov 02 02:39:29 2006 (4549BCD1)
    8025d000 80266000 PSHED PSHED.dll Thu Nov 02 02:42:51 2006 (4549BD9B)
    80266000 802c6000 mcupdate mcupdate.dll Mon Apr 23 20:40:05 2007 (462D7C15)
    802c6000 802ce000 kdcom kdcom.dll Thu Nov 02 02:42:20 2006 (4549BD7C)
    80400000 8040e000 PCIIDEX PCIIDEX.SYS Fri Jan 18 19:01:56 2008 (47916824)
    8040e000 80415000 pciide pciide.sys Fri Jan 18 19:01:57 2008 (47916825)
    80415000 80425000 mountmgr mountmgr.sys Thu Nov 02 01:51:06 2006 (4549B17A)
    80425000 80434000 volmgr volmgr.sys Thu Nov 02 01:51:44 2006 (4549B1A0)
    80434000 80459000 pci pci.sys Thu Nov 02 01:35:13 2006 (4549ADC1)
    80459000 80461000 msisadrv msisadrv.sys Thu Nov 02 01:35:08 2006 (4549ADBC)
    80461000 804a4000 acpi acpi.sys Thu Nov 02 01:35:03 2006 (4549ADB7)
    804a4000 8051f000 Wdf01000 Wdf01000.sys Wed Dec 05 18:21:28 2007 (47575CA8)
    8051f000 80600000 CI CI.dll Thu Nov 02 02:42:45 2006 (4549BD95)
    80600000 80609000 crcdisk crcdisk.sys Thu Nov 02 01:52:27 2006 (4549B1CB)
    80609000 80618000 partmgr partmgr.sys Thu Nov 02 01:51:47 2006 (4549B1A3)
    80618000 80620000 spldr spldr.sys Wed Oct 25 15:40:44 2006 (453FE7EC)
    80620000 80621000 msrpc msrpc.sys unavailable (00000000)
    8064b000 8074f000 ndis ndis.sys Thu Nov 02 01:57:33 2006 (4549B2FD)
    8074f000 8075f000 fileinfo fileinfo.sys Thu Nov 02 01:36:47 2006 (4549AE1F)
    8075f000 80790000 fltmgr fltmgr.sys Thu Nov 02 01:30:58 2006 (4549ACC2)
    80790000 807ae000 ataport ataport.SYS Fri Jan 18 19:01:56 2008 (47916824)
    807ae000 807b6000 atapi atapi.sys Fri Jan 18 19:01:56 2008 (47916824)
    807b6000 80800000 volmgrx volmgrx.sys Thu Nov 02 01:51:54 2006 (4549B1AA)
    81800000 81ba1000 nt ntkrpamp.exe Tue Oct 23 18:45:00 2007 (471EA39C)
    81ba1000 81bd5000 hal halmacpi.dll Tue Dec 19 19:31:08 2006 (4588AE7C)
    86e10000 86e1f000 mup mup.sys Thu Nov 02 01:31:04 2006 (4549ACC8)
    86e1f000 86e55000 volsnap volsnap.sys Thu Nov 02 01:52:11 2006 (4549B1BB)
    86e55000 86ebf000 ksecdd ksecdd.sys Thu Nov 02 01:43:45 2006 (4549AFC1)
    86ebf000 86fc7000 Ntfs Ntfs.sys Thu Oct 25 18:40:39 2007 (47214597)
    86fc7000 87000000 NETIO NETIO.SYS Sun Jan 13 19:17:13 2008 (478AD439)
    87186000 871a7000 CLASSPNP CLASSPNP.SYS Thu Nov 02 01:51:34 2006 (4549B196)
    871a7000 871b8000 disk disk.sys Thu Nov 02 01:51:40 2006 (4549B19C)
    871b8000 871db000 fvevol fvevol.sys Thu Nov 02 01:30:07 2006 (4549AC8F)
    871db000 87200000 ecache ecache.sys Thu Nov 02 01:52:42 2006 (4549B1DA)
    87aa1000 87ab1000 HIDCLASS HIDCLASS.SYS Thu Nov 02 01:55:00 2006 (4549B264)
    87ad1000 87ae0280 ohci1394 ohci1394.sys Thu Nov 02 01:55:16 2006 (4549B274)
    87b11000 87b21000 NDProxy NDProxy.SYS Tue Jul 03 18:28:13 2007 (468AF7AD)
    87b51000 87b61000 lltdio lltdio.sys Thu Nov 02 01:56:48 2006 (4549B2D0)
    87be1000 87bf0000 raspppoe raspppoe.sys Thu Nov 02 01:58:12 2006 (4549B324)
    87e1e000 87e1f380 swenum swenum.sys Thu Nov 02 01:51:15 2006 (4549B183)
    87e2c000 87e2d700 USBD USBD.SYS Thu Aug 30 18:19:54 2007 (46D76CBA)
    87f79000 87f82000 tunmp tunmp.sys Wed Jun 06 19:56:53 2007 (466773F5)
    87f8b000 87f94000 wmiacpi wmiacpi.sys Thu Nov 02 01:35:03 2006 (4549ADB7)
    87faf000 87fb8000 hidusb hidusb.sys Thu Nov 02 01:55:01 2006 (4549B265)
    87fb8000 87fb9000 Fs_Rec Fs_Rec.SYS unavailable (00000000)
    87fc1000 87fca000 rasacd rasacd.sys Thu Nov 02 01:58:13 2006 (4549B325)
    89c01000 89c0c000 kbdclass kbdclass.sys Wed Dec 05 18:18:23 2007 (47575BEF)
    89c0c000 89c1f000 i8042prt i8042prt.sys Wed Dec 05 18:18:28 2007 (47575BF4)
    89c1f000 89c37000 parport parport.sys Thu Nov 02 01:51:29 2006 (4549B191)
    89c37000 89c51000 serial serial.sys Thu Nov 02 01:51:29 2006 (4549B191)
    89ca1000 89ca2000 fdc fdc.sys unavailable (00000000)
    89cac000 89cba000 intelppm intelppm.sys Thu Nov 02 01:30:18 2006 (4549AC9A)
    89cba000 89cc5000 tunnel tunnel.sys Wed Jun 06 19:57:03 2007 (466773FF)
    89cca000 89cdb000 dump_dumpfve dump_dumpfve.sys Thu Nov 02 01:30:04 2006 (4549AC8C)
    89cdb000 89ce5000 serenum serenum.sys Thu Nov 02 01:51:25 2006 (4549B18D)
    89d75000 89d80000 dump_ataport dump_ataport.sys Thu Nov 02 01:51:34 2006 (4549B196)
    89d90000 89d98000 mouhid mouhid.sys Wed Dec 05 18:18:25 2007 (47575BF1)
    89da0000 89da8000 dump_atapi dump_atapi.sys Fri Jan 18 19:01:56 2008 (47916824)
    89db0000 89db8000 RDPCDD RDPCDD.sys Thu Nov 02 02:02:01 2006 (4549B409)
    89db8000 89dc0000 rdpencdd rdpencdd.sys Thu Nov 02 02:02:01 2006 (4549B409)
    8a408000 8a413000 ndistapi ndistapi.sys Tue Jul 03 18:28:09 2007 (468AF7A9)
    8a413000 8a42a000 rasl2tp rasl2tp.sys Thu Nov 02 01:58:13 2006 (4549B325)
    8a42a000 8a435000 TDI TDI.SYS Thu Nov 02 01:58:46 2006 (4549B346)
    8a435000 8a460000 msiscsi msiscsi.sys Thu Nov 02 01:52:40 2006 (4549B1D8)
    8a460000 8a46d000 watchdog watchdog.sys Thu Nov 02 01:37:44 2006 (4549AE58)
    8a46d000 8a47a080 1394BUS 1394BUS.SYS Thu Nov 02 01:55:12 2006 (4549B270)
    8a4ba000 8a4bb000 parvdm parvdm.sys unavailable (00000000)
    8a4d6000 8a4dc380 HIDPARSE HIDPARSE.SYS Thu Nov 02 01:55:00 2006 (4549B264)
    8a4dd000 8a4de000 Null Null.SYS unavailable (00000000)
    8a4e4000 8a4eb000 Beep Beep.SYS Thu Nov 02 01:51:03 2006 (4549B177)
    8a4eb000 8a4fd000 HDAudBus HDAudBus.sys Mon Oct 16 09:29:50 2006 (4533B37E)
    8a4fd000 8a515000 cdrom cdrom.sys Thu Nov 02 01:51:44 2006 (4549B1A0)
    8a515000 8a523000 usbehci usbehci.sys Thu Aug 30 18:19:59 2007 (46D76CBF)
    8a523000 8a560000 USBPORT USBPORT.SYS Thu Aug 30 18:20:03 2007 (46D76CC3)
    8a560000 8a56a000 usbohci usbohci.sys Thu Aug 30 18:19:59 2007 (46D76CBF)
    8a56a000 8a574000 mssmbios mssmbios.sys Thu Nov 02 01:35:13 2006 (4549ADC1)
    8a574000 8a575000 flpydisk flpydisk.sys unavailable (00000000)
    8a57e000 8a588000 nsiproxy nsiproxy.sys Thu Nov 02 01:57:30 2006 (4549B2FA)
    8a5ba000 8a5c4000 Dxapi Dxapi.sys Thu Nov 02 01:38:17 2006 (4549AE79)
    8a5c4000 8a5ce000 secdrv secdrv.SYS Wed Sep 13 06:18:32 2006 (45080528)
    8a5f9000 8a604000 mouclass mouclass.sys Wed Dec 05 18:18:22 2007 (47575BEE)
    8a604000 8a627000 ndiswan ndiswan.sys Thu Nov 02 01:58:13 2006 (4549B325)
    8a627000 8a667000 storport storport.sys Thu Nov 02 01:51:45 2006 (4549B1A1)
    8a667000 8a704000 dxgkrnl dxgkrnl.sys Mon Jul 02 18:01:10 2007 (46899FD6)
    8a704000 8a7ff180 nvmfdx32 nvmfdx32.sys Mon Sep 10 19:10:00 2007 (46E5F8F8)
    8a804000 8a813000 termdd termdd.sys Thu Nov 02 02:02:00 2006 (4549B408)
    8a813000 8a820000 umbus umbus.sys Thu Nov 02 01:55:24 2006 (4549B27C)
    8a820000 8a8a7000 rdpdr rdpdr.sys Thu Nov 02 02:02:58 2006 (4549B442)
    8a8a7000 8a8ba000 raspptp raspptp.sys Thu Nov 02 01:58:14 2006 (4549B326)
    8a8ba000 8afff980 nvlddmkm nvlddmkm.sys Thu Oct 04 17:54:30 2007 (47058B46)
    8b000000 8b00e000 Npfs Npfs.SYS Thu Nov 02 01:30:57 2006 (4549ACC1)
    8b00e000 8b00f000 Msfs Msfs.SYS unavailable (00000000)
    8b019000 8b025000 vga vga.sys Thu Nov 02 01:53:56 2006 (4549B224)
    8b025000 8b030000 nvhda32v nvhda32v.sys Mon Jul 16 11:37:42 2007 (469BBAF6)
    8b030000 8b055000 drmk drmk.sys Thu Nov 02 02:20:49 2006 (4549B871)
    8b055000 8b082000 portcls portcls.sys Thu Nov 02 01:55:02 2006 (4549B266)
    8b082000 8b0b6000 usbhub usbhub.sys Thu Aug 30 18:20:18 2007 (46D76CD2)
    8b0c6000 8b0d3000 crashdmp crashdmp.sys Thu Nov 02 01:51:36 2006 (4549B198)
    8b196000 8b1c0000 ks ks.sys Thu Nov 02 01:51:18 2006 (4549B186)
    8b201000 8b222000 VIDEOPRT VIDEOPRT.SYS Thu Nov 02 01:54:07 2006 (4549B22F)
    8b222000 8b3ff280 RTKVHDA RTKVHDA.sys Wed Sep 19 02:11:33 2007 (46F0E7C5)
    8b408000 8b43a000 netbt netbt.sys Thu Nov 02 01:57:18 2006 (4549B2EE)
    8b43a000 8b481000 afd afd.sys Thu Nov 02 01:58:41 2006 (4549B341)
    8b481000 8b48d000 epfwtdir epfwtdir.sys Wed Feb 20 01:45:18 2008 (47BBF6AE)
    8b48d000 8b4a1000 smb smb.sys Thu Nov 02 01:57:10 2006 (4549B2E6)
    8b4e1000 8b4f6000 tdx tdx.sys Thu Nov 02 01:57:34 2006 (4549B2FE)
    8b4f6000 8b50f000 fwpkclnt fwpkclnt.sys Thu Nov 02 01:57:26 2006 (4549B2F6)
    8b50f000 8b5e0000 tcpip tcpip.sys Sun Jan 13 19:17:51 2008 (478AD45F)
    8b61f000 8b62a000 tcpipreg tcpipreg.sys Thu Nov 02 01:57:46 2006 (4549B30A)
    8b719000 8b730000 dfsc dfsc.sys Thu Nov 02 01:31:04 2006 (4549ACC8)
    8b730000 8b783000 csc csc.sys Mon Jun 18 17:48:27 2007 (467727DB)
    8b783000 8b78e000 easdrv easdrv.sys Wed Feb 20 01:57:12 2008 (47BBF978)
    8b78e000 8b7c9000 rdbss rdbss.sys Thu Nov 02 01:31:24 2006 (4549ACDC)
    8b7c9000 8b7dc000 wanarp wanarp.sys Tue Jul 03 18:28:16 2007 (468AF7B0)
    8b7dc000 8b7ea000 netbios netbios.sys Thu Nov 02 01:57:26 2006 (4549B2F6)
    8b7ea000 8b800000 pacer pacer.sys Tue Jul 03 18:27:33 2007 (468AF785)
    8ba11000 8ba20000 monitor monitor.sys Thu Nov 02 01:54:05 2006 (4549B22D)
    8ec00000 8edff000 win32k win32k.sys Wed Feb 14 18:57:33 2007 (45D3CC1D)
    92400000 92409000 TSDDD TSDDD.dll Thu Nov 02 02:02:02 2006 (4549B40A)
    92410000 9241e000 cdd cdd.dll Mon Jul 02 19:08:39 2007 (4689AFA7)
    92b54000 92b6f000 luafv luafv.sys Thu Nov 02 01:33:07 2006 (4549AD43)
    933aa000 933c0000 cdfs cdfs.sys Thu Nov 02 01:30:50 2006 (4549ACBA)
    94248000 9425b000 rspndr rspndr.sys Thu Nov 02 01:56:48 2006 (4549B2D0)
    942f2000 94380000 spsys spsys.sys Wed Oct 25 15:43:28 2006 (453FE890)
    94401000 9441a000 bowser bowser.sys Thu Nov 02 01:31:11 2006 (4549ACCF)
    9441a000 94480000 HTTP HTTP.sys Thu Nov 02 01:57:06 2006 (4549B2E2)
    94a58000 94aa4000 srv srv.sys Thu Nov 02 01:31:55 2006 (4549ACFB)
    94ae4000 94b08000 srv2 srv2.sys Thu Oct 25 18:40:47 2007 (4721459F)
    94b08000 94b1a000 mrxsmb20 mrxsmb20.sys Thu Oct 25 18:40:16 2007 (47214580)
    94b1a000 94b53000 mrxsmb10 mrxsmb10.sys Thu Nov 02 01:31:25 2006 (4549ACDD)
    94b53000 94b71000 mrxsmb mrxsmb.sys Thu Oct 25 18:40:17 2007 (47214581)
    94b71000 94b91000 mrxdav mrxdav.sys Fri Jan 11 17:45:54 2008 (47881BD2)
    94b91000 94ba5000 mpsdrv mpsdrv.sys Wed Jun 06 19:55:55 2007 (466773BB)
    94ba5000 94bc0000 srvnet srvnet.sys Thu Oct 25 18:40:43 2007 (4721459B)
    94f0b000 94f58000 eamon eamon.sys Wed Feb 20 01:56:12 2008 (47BBF93C)
    95322000 95400000 peauth peauth.sys Mon Oct 23 01:55:32 2006 (453C8384)

    Unloaded modules:
    8f350000 8f358000 drmkaud.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    87e31000 87e3e000 crashdmp.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    89d75000 89d80000 dump_ataport
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    89df0000 89df8000 dump_atapi.s
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    89cca000 89cdb000 dump_dumpfve
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    Closing open log file c:\debuglog.txt

    What do you guys think? I dont really know how to read these but I think its the ram because of this line: Probably caused by : memory_corruption ( nt!MiReplenishPageSlist+e5 )
     
    Last edited: 2008/03/21
  11. 2008/03/21
    mahme

    mahme Inactive Thread Starter

    Joined:
    2008/03/18
    Messages:
    20
    Likes Received:
    0
    Since i couldn't get into Win XP however i tried i decided to try and install Win Vista. The result was I could be in Vista for around 5min tops before i got the bluescreen again. But since i had 5min before it crashed and not before startup like with winxp i could debug the minidump that was created.

    Here it is:
    Opened log file 'c:\debuglog.txt'

    Microsoft (R) Windows Debugger Version 6.8.0004.0 X86
    Copyright (c) Microsoft Corporation. All rights reserved.


    Loading Dump File [C:\Windows\Minidump\Mini032108-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
    Windows Vista Kernel Version 6000 MP (2 procs) Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 6000.16584.x86fre.vista_gdr.071023-1545
    Kernel base = 0x81800000 PsLoadedModuleList = 0x81911e10
    Debug session time: Fri Mar 21 10:57:07.164 2008 (GMT-7)
    System Uptime: 0 days 0:36:34.851
    Loading Kernel Symbols
    ..........................................................................................................................................
    Loading User Symbols
    Loading unloaded module list
    .....
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 1000000A, {0, 2, 0, 818bcda4}



    Probably caused by : memory_corruption ( nt!MiReplenishPageSlist+e5 )

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

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

    IRQL_NOT_LESS_OR_EQUAL (a)
    An attempt was made to access a pageable (or completely invalid) address at an
    interrupt request level (IRQL) that is too high. This is usually
    caused by drivers using improper addresses.
    If a kernel debugger is available get the stack backtrace.
    Arguments:
    Arg1: 00000000, memory referenced
    Arg2: 00000002, IRQL
    Arg3: 00000000, bitfield :
    bit 0 : value 0 = read operation, 1 = write operation
    bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
    Arg4: 818bcda4, address which referenced memory

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




    READ_ADDRESS: GetPointerFromAddress: unable to read from 819315ac
    Unable to read MiSystemVaType memory at 819117e0
    00000000

    CURRENT_IRQL: 2

    FAULTING_IP:
    nt!MiReplenishPageSlist+e5
    818bcda4 8b08 mov ecx,dword ptr [eax]

    CUSTOMER_CRASH_COUNT: 1

    DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

    BUGCHECK_STR: 0xA

    PROCESS_NAME: svchost.exe

    TRAP_FRAME: 8b1c796c -- (.trap 0xffffffff8b1c796c)
    .trap 0xffffffff8b1c796c
    ErrCode = 00000002
    eax=9dd52000 ebx=00001000 ecx=00016ffe edx=00000000 esi=8323509c edi=9dd52000
    eip=818e7728 esp=8b1c79e0 ebp=8b1c7a28 iopl=0 nv up ei ng nz na pe nc
    cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010286
    nt!ExAllocatePoolWithTag+0x71d:
    818e7728 832700 and dword ptr [edi],0 ds:0023:9dd52000=????????
    .trap
    Resetting default scope

    LAST_CONTROL_TRANSFER: from 818bcf51 to 818bcda4

    STACK_TEXT:
    8b1c77b8 818bcf51 818f39b4 00000004 860114c0 nt!MiReplenishPageSlist+0xe5
    8b1c77e0 818bd4a3 c04eea90 00000000 839f6030 nt!MiRemoveAnyPage+0xf2
    8b1c781c 8182a4f2 00000001 9dd52000 c04eea90 nt!MiResolveDemandZeroFault+0x4cd
    8b1c78d8 818aaf05 9dd52000 00000000 00000000 nt!MiDispatchFault+0xa8b
    8b1c7954 8188fbb4 00000001 9dd52000 00000000 nt!MmAccessFault+0x1119
    8b1c7954 818e7728 00000001 9dd52000 00000000 nt!KiTrap0E+0xdc
    8b1c7a28 86ed7372 00000011 00000370 6666744e nt!ExAllocatePoolWithTag+0x71d
    8b1c7a40 86f4b942 86efcd20 8b9a95e4 96fd80f8 Ntfs!ExAllocateFromPagedLookasideList+0x27
    8b1c7ac4 86f4a8d1 85d3fc30 840630d8 00000000 Ntfs!NtfsCreateFcb+0x16f
    8b1c7c04 86f64318 85d3fc30 83f08de0 96fd80f8 Ntfs!NtfsOpenFile+0x1c3
    8b1c7cec 86ed96b6 85d3fc30 83f08de0 9597293c Ntfs!NtfsCommonCreate+0xe39
    8b1c7d2c 818803e8 959728d4 00000000 ffffffff Ntfs!NtfsCommonCreateCallout+0x20
    8b1c7d2c 818804e1 959728d4 00000000 ffffffff nt!KiSwapKernelStackAndExit+0x118
    9597286c 00000000 00000000 00000000 00000000 nt!KiSwitchKernelStackAndCallout+0x31


    STACK_COMMAND: kb

    FOLLOWUP_IP:
    nt!MiReplenishPageSlist+e5
    818bcda4 8b08 mov ecx,dword ptr [eax]

    SYMBOL_STACK_INDEX: 0

    SYMBOL_NAME: nt!MiReplenishPageSlist+e5

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: nt

    DEBUG_FLR_IMAGE_TIMESTAMP: 471ea39c

    IMAGE_NAME: memory_corruption

    FAILURE_BUCKET_ID: 0xA_nt!MiReplenishPageSlist+e5

    BUCKET_ID: 0xA_nt!MiReplenishPageSlist+e5

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

    eax=00000000 ebx=818f39b4 ecx=ffffffff edx=82a92370 esi=831fc970 edi=00000006
    eip=818bcda4 esp=8b1c7798 ebp=8b1c77b8 iopl=0 nv up ei pl nz na pe nc
    cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010206
    nt!MiReplenishPageSlist+0xe5:
    818bcda4 8b08 mov ecx,dword ptr [eax] ds:0023:00000000=????????
    ChildEBP RetAddr Args to Child
    8b1c77b8 818bcf51 818f39b4 00000004 860114c0 nt!MiReplenishPageSlist+0xe5
    8b1c77e0 818bd4a3 c04eea90 00000000 839f6030 nt!MiRemoveAnyPage+0xf2
    8b1c781c 8182a4f2 00000001 9dd52000 c04eea90 nt!MiResolveDemandZeroFault+0x4cd
    8b1c78d8 818aaf05 9dd52000 00000000 00000000 nt!MiDispatchFault+0xa8b
    8b1c7954 8188fbb4 00000001 9dd52000 00000000 nt!MmAccessFault+0x1119
    8b1c7954 818e7728 00000001 9dd52000 00000000 nt!KiTrap0E+0xdc (FPO: [0,0] TrapFrame @ 8b1c796c)
    8b1c7a28 86ed7372 00000011 00000370 6666744e nt!ExAllocatePoolWithTag+0x71d
    8b1c7a40 86f4b942 86efcd20 8b9a95e4 96fd80f8 Ntfs!ExAllocateFromPagedLookasideList+0x27 (FPO: [Non-Fpo])
    8b1c7ac4 86f4a8d1 85d3fc30 840630d8 00000000 Ntfs!NtfsCreateFcb+0x16f (FPO: [Non-Fpo])
    8b1c7c04 86f64318 85d3fc30 83f08de0 96fd80f8 Ntfs!NtfsOpenFile+0x1c3 (FPO: [Non-Fpo])
    8b1c7cec 86ed96b6 85d3fc30 83f08de0 9597293c Ntfs!NtfsCommonCreate+0xe39 (FPO: [Non-Fpo])
    8b1c7d2c 818803e8 959728d4 00000000 ffffffff Ntfs!NtfsCommonCreateCallout+0x20 (FPO: [Non-Fpo])
    8b1c7d2c 818804e1 959728d4 00000000 ffffffff nt!KiSwapKernelStackAndExit+0x118 (FPO: [0,0] TrapFrame @ 8b1c7d44)
    9597286c 00000000 00000000 00000000 00000000 nt!KiSwitchKernelStackAndCallout+0x31
    start end module name
    80204000 8020d000 WMILIB WMILIB.SYS Thu Nov 02 01:54:53 2006 (4549B25D)
    8020d000 8021a000 WDFLDR WDFLDR.SYS Wed Dec 05 18:21:19 2007 (47575C9F)
    8021a000 80255000 CLFS CLFS.SYS Wed Dec 05 17:55:42 2007 (4757569E)
    80255000 8025d000 BOOTVID BOOTVID.dll Thu Nov 02 02:39:29 2006 (4549BCD1)
    8025d000 80266000 PSHED PSHED.dll Thu Nov 02 02:42:51 2006 (4549BD9B)
    80266000 802c6000 mcupdate mcupdate.dll Mon Apr 23 20:40:05 2007 (462D7C15)
    802c6000 802ce000 kdcom kdcom.dll Thu Nov 02 02:42:20 2006 (4549BD7C)
    80400000 8040e000 PCIIDEX PCIIDEX.SYS Fri Jan 18 19:01:56 2008 (47916824)
    8040e000 80415000 pciide pciide.sys Fri Jan 18 19:01:57 2008 (47916825)
    80415000 80425000 mountmgr mountmgr.sys Thu Nov 02 01:51:06 2006 (4549B17A)
    80425000 80434000 volmgr volmgr.sys Thu Nov 02 01:51:44 2006 (4549B1A0)
    80434000 80459000 pci pci.sys Thu Nov 02 01:35:13 2006 (4549ADC1)
    80459000 80461000 msisadrv msisadrv.sys Thu Nov 02 01:35:08 2006 (4549ADBC)
    80461000 804a4000 acpi acpi.sys Thu Nov 02 01:35:03 2006 (4549ADB7)
    804a4000 8051f000 Wdf01000 Wdf01000.sys Wed Dec 05 18:21:28 2007 (47575CA8)
    8051f000 80600000 CI CI.dll Thu Nov 02 02:42:45 2006 (4549BD95)
    80600000 80609000 crcdisk crcdisk.sys Thu Nov 02 01:52:27 2006 (4549B1CB)
    80609000 80618000 partmgr partmgr.sys Thu Nov 02 01:51:47 2006 (4549B1A3)
    80618000 80620000 spldr spldr.sys Wed Oct 25 15:40:44 2006 (453FE7EC)
    80620000 80621000 msrpc msrpc.sys unavailable (00000000)
    8064b000 8074f000 ndis ndis.sys Thu Nov 02 01:57:33 2006 (4549B2FD)
    8074f000 8075f000 fileinfo fileinfo.sys Thu Nov 02 01:36:47 2006 (4549AE1F)
    8075f000 80790000 fltmgr fltmgr.sys Thu Nov 02 01:30:58 2006 (4549ACC2)
    80790000 807ae000 ataport ataport.SYS Fri Jan 18 19:01:56 2008 (47916824)
    807ae000 807b6000 atapi atapi.sys Fri Jan 18 19:01:56 2008 (47916824)
    807b6000 80800000 volmgrx volmgrx.sys Thu Nov 02 01:51:54 2006 (4549B1AA)
    81800000 81ba1000 nt ntkrpamp.exe Tue Oct 23 18:45:00 2007 (471EA39C)
    81ba1000 81bd5000 hal halmacpi.dll Tue Dec 19 19:31:08 2006 (4588AE7C)
    86e10000 86e1f000 mup mup.sys Thu Nov 02 01:31:04 2006 (4549ACC8)
    86e1f000 86e55000 volsnap volsnap.sys Thu Nov 02 01:52:11 2006 (4549B1BB)
    86e55000 86ebf000 ksecdd ksecdd.sys Thu Nov 02 01:43:45 2006 (4549AFC1)
    86ebf000 86fc7000 Ntfs Ntfs.sys Thu Oct 25 18:40:39 2007 (47214597)
    86fc7000 87000000 NETIO NETIO.SYS Sun Jan 13 19:17:13 2008 (478AD439)
    87186000 871a7000 CLASSPNP CLASSPNP.SYS Thu Nov 02 01:51:34 2006 (4549B196)
    871a7000 871b8000 disk disk.sys Thu Nov 02 01:51:40 2006 (4549B19C)
    871b8000 871db000 fvevol fvevol.sys Thu Nov 02 01:30:07 2006 (4549AC8F)
    871db000 87200000 ecache ecache.sys Thu Nov 02 01:52:42 2006 (4549B1DA)
    87aa1000 87ab1000 HIDCLASS HIDCLASS.SYS Thu Nov 02 01:55:00 2006 (4549B264)
    87ad1000 87ae0280 ohci1394 ohci1394.sys Thu Nov 02 01:55:16 2006 (4549B274)
    87b11000 87b21000 NDProxy NDProxy.SYS Tue Jul 03 18:28:13 2007 (468AF7AD)
    87b51000 87b61000 lltdio lltdio.sys Thu Nov 02 01:56:48 2006 (4549B2D0)
    87be1000 87bf0000 raspppoe raspppoe.sys Thu Nov 02 01:58:12 2006 (4549B324)
    87e1e000 87e1f380 swenum swenum.sys Thu Nov 02 01:51:15 2006 (4549B183)
    87e2c000 87e2d700 USBD USBD.SYS Thu Aug 30 18:19:54 2007 (46D76CBA)
    87f79000 87f82000 tunmp tunmp.sys Wed Jun 06 19:56:53 2007 (466773F5)
    87f8b000 87f94000 wmiacpi wmiacpi.sys Thu Nov 02 01:35:03 2006 (4549ADB7)
    87faf000 87fb8000 hidusb hidusb.sys Thu Nov 02 01:55:01 2006 (4549B265)
    87fb8000 87fb9000 Fs_Rec Fs_Rec.SYS unavailable (00000000)
    87fc1000 87fca000 rasacd rasacd.sys Thu Nov 02 01:58:13 2006 (4549B325)
    89c01000 89c0c000 kbdclass kbdclass.sys Wed Dec 05 18:18:23 2007 (47575BEF)
    89c0c000 89c1f000 i8042prt i8042prt.sys Wed Dec 05 18:18:28 2007 (47575BF4)
    89c1f000 89c37000 parport parport.sys Thu Nov 02 01:51:29 2006 (4549B191)
    89c37000 89c51000 serial serial.sys Thu Nov 02 01:51:29 2006 (4549B191)
    89ca1000 89ca2000 fdc fdc.sys unavailable (00000000)
    89cac000 89cba000 intelppm intelppm.sys Thu Nov 02 01:30:18 2006 (4549AC9A)
    89cba000 89cc5000 tunnel tunnel.sys Wed Jun 06 19:57:03 2007 (466773FF)
    89cca000 89cdb000 dump_dumpfve dump_dumpfve.sys Thu Nov 02 01:30:04 2006 (4549AC8C)
    89cdb000 89ce5000 serenum serenum.sys Thu Nov 02 01:51:25 2006 (4549B18D)
    89d75000 89d80000 dump_ataport dump_ataport.sys Thu Nov 02 01:51:34 2006 (4549B196)
    89d90000 89d98000 mouhid mouhid.sys Wed Dec 05 18:18:25 2007 (47575BF1)
    89da0000 89da8000 dump_atapi dump_atapi.sys Fri Jan 18 19:01:56 2008 (47916824)
    89db0000 89db8000 RDPCDD RDPCDD.sys Thu Nov 02 02:02:01 2006 (4549B409)
    89db8000 89dc0000 rdpencdd rdpencdd.sys Thu Nov 02 02:02:01 2006 (4549B409)
    8a408000 8a413000 ndistapi ndistapi.sys Tue Jul 03 18:28:09 2007 (468AF7A9)
    8a413000 8a42a000 rasl2tp rasl2tp.sys Thu Nov 02 01:58:13 2006 (4549B325)
    8a42a000 8a435000 TDI TDI.SYS Thu Nov 02 01:58:46 2006 (4549B346)
    8a435000 8a460000 msiscsi msiscsi.sys Thu Nov 02 01:52:40 2006 (4549B1D8)
    8a460000 8a46d000 watchdog watchdog.sys Thu Nov 02 01:37:44 2006 (4549AE58)
    8a46d000 8a47a080 1394BUS 1394BUS.SYS Thu Nov 02 01:55:12 2006 (4549B270)
    8a4ba000 8a4bb000 parvdm parvdm.sys unavailable (00000000)
    8a4d6000 8a4dc380 HIDPARSE HIDPARSE.SYS Thu Nov 02 01:55:00 2006 (4549B264)
    8a4dd000 8a4de000 Null Null.SYS unavailable (00000000)
    8a4e4000 8a4eb000 Beep Beep.SYS Thu Nov 02 01:51:03 2006 (4549B177)
    8a4eb000 8a4fd000 HDAudBus HDAudBus.sys Mon Oct 16 09:29:50 2006 (4533B37E)
    8a4fd000 8a515000 cdrom cdrom.sys Thu Nov 02 01:51:44 2006 (4549B1A0)
    8a515000 8a523000 usbehci usbehci.sys Thu Aug 30 18:19:59 2007 (46D76CBF)
    8a523000 8a560000 USBPORT USBPORT.SYS Thu Aug 30 18:20:03 2007 (46D76CC3)
    8a560000 8a56a000 usbohci usbohci.sys Thu Aug 30 18:19:59 2007 (46D76CBF)
    8a56a000 8a574000 mssmbios mssmbios.sys Thu Nov 02 01:35:13 2006 (4549ADC1)
    8a574000 8a575000 flpydisk flpydisk.sys unavailable (00000000)
    8a57e000 8a588000 nsiproxy nsiproxy.sys Thu Nov 02 01:57:30 2006 (4549B2FA)
    8a5ba000 8a5c4000 Dxapi Dxapi.sys Thu Nov 02 01:38:17 2006 (4549AE79)
    8a5c4000 8a5ce000 secdrv secdrv.SYS Wed Sep 13 06:18:32 2006 (45080528)
    8a5f9000 8a604000 mouclass mouclass.sys Wed Dec 05 18:18:22 2007 (47575BEE)
    8a604000 8a627000 ndiswan ndiswan.sys Thu Nov 02 01:58:13 2006 (4549B325)
    8a627000 8a667000 storport storport.sys Thu Nov 02 01:51:45 2006 (4549B1A1)
    8a667000 8a704000 dxgkrnl dxgkrnl.sys Mon Jul 02 18:01:10 2007 (46899FD6)
    8a704000 8a7ff180 nvmfdx32 nvmfdx32.sys Mon Sep 10 19:10:00 2007 (46E5F8F8)
    8a804000 8a813000 termdd termdd.sys Thu Nov 02 02:02:00 2006 (4549B408)
    8a813000 8a820000 umbus umbus.sys Thu Nov 02 01:55:24 2006 (4549B27C)
    8a820000 8a8a7000 rdpdr rdpdr.sys Thu Nov 02 02:02:58 2006 (4549B442)
    8a8a7000 8a8ba000 raspptp raspptp.sys Thu Nov 02 01:58:14 2006 (4549B326)
    8a8ba000 8afff980 nvlddmkm nvlddmkm.sys Thu Oct 04 17:54:30 2007 (47058B46)
    8b000000 8b00e000 Npfs Npfs.SYS Thu Nov 02 01:30:57 2006 (4549ACC1)
    8b00e000 8b00f000 Msfs Msfs.SYS unavailable (00000000)
    8b019000 8b025000 vga vga.sys Thu Nov 02 01:53:56 2006 (4549B224)
    8b025000 8b030000 nvhda32v nvhda32v.sys Mon Jul 16 11:37:42 2007 (469BBAF6)
    8b030000 8b055000 drmk drmk.sys Thu Nov 02 02:20:49 2006 (4549B871)
    8b055000 8b082000 portcls portcls.sys Thu Nov 02 01:55:02 2006 (4549B266)
    8b082000 8b0b6000 usbhub usbhub.sys Thu Aug 30 18:20:18 2007 (46D76CD2)
    8b0c6000 8b0d3000 crashdmp crashdmp.sys Thu Nov 02 01:51:36 2006 (4549B198)
    8b196000 8b1c0000 ks ks.sys Thu Nov 02 01:51:18 2006 (4549B186)
    8b201000 8b222000 VIDEOPRT VIDEOPRT.SYS Thu Nov 02 01:54:07 2006 (4549B22F)
    8b222000 8b3ff280 RTKVHDA RTKVHDA.sys Wed Sep 19 02:11:33 2007 (46F0E7C5)
    8b408000 8b43a000 netbt netbt.sys Thu Nov 02 01:57:18 2006 (4549B2EE)
    8b43a000 8b481000 afd afd.sys Thu Nov 02 01:58:41 2006 (4549B341)
    8b481000 8b48d000 epfwtdir epfwtdir.sys Wed Feb 20 01:45:18 2008 (47BBF6AE)
    8b48d000 8b4a1000 smb smb.sys Thu Nov 02 01:57:10 2006 (4549B2E6)
    8b4e1000 8b4f6000 tdx tdx.sys Thu Nov 02 01:57:34 2006 (4549B2FE)
    8b4f6000 8b50f000 fwpkclnt fwpkclnt.sys Thu Nov 02 01:57:26 2006 (4549B2F6)
    8b50f000 8b5e0000 tcpip tcpip.sys Sun Jan 13 19:17:51 2008 (478AD45F)
    8b61f000 8b62a000 tcpipreg tcpipreg.sys Thu Nov 02 01:57:46 2006 (4549B30A)
    8b719000 8b730000 dfsc dfsc.sys Thu Nov 02 01:31:04 2006 (4549ACC8)
    8b730000 8b783000 csc csc.sys Mon Jun 18 17:48:27 2007 (467727DB)
    8b783000 8b78e000 easdrv easdrv.sys Wed Feb 20 01:57:12 2008 (47BBF978)
    8b78e000 8b7c9000 rdbss rdbss.sys Thu Nov 02 01:31:24 2006 (4549ACDC)
    8b7c9000 8b7dc000 wanarp wanarp.sys Tue Jul 03 18:28:16 2007 (468AF7B0)
    8b7dc000 8b7ea000 netbios netbios.sys Thu Nov 02 01:57:26 2006 (4549B2F6)
    8b7ea000 8b800000 pacer pacer.sys Tue Jul 03 18:27:33 2007 (468AF785)
    8ba11000 8ba20000 monitor monitor.sys Thu Nov 02 01:54:05 2006 (4549B22D)
    8ec00000 8edff000 win32k win32k.sys Wed Feb 14 18:57:33 2007 (45D3CC1D)
    92400000 92409000 TSDDD TSDDD.dll Thu Nov 02 02:02:02 2006 (4549B40A)
    92410000 9241e000 cdd cdd.dll Mon Jul 02 19:08:39 2007 (4689AFA7)
    92b54000 92b6f000 luafv luafv.sys Thu Nov 02 01:33:07 2006 (4549AD43)
    933aa000 933c0000 cdfs cdfs.sys Thu Nov 02 01:30:50 2006 (4549ACBA)
    94248000 9425b000 rspndr rspndr.sys Thu Nov 02 01:56:48 2006 (4549B2D0)
    942f2000 94380000 spsys spsys.sys Wed Oct 25 15:43:28 2006 (453FE890)
    94401000 9441a000 bowser bowser.sys Thu Nov 02 01:31:11 2006 (4549ACCF)
    9441a000 94480000 HTTP HTTP.sys Thu Nov 02 01:57:06 2006 (4549B2E2)
    94a58000 94aa4000 srv srv.sys Thu Nov 02 01:31:55 2006 (4549ACFB)
    94ae4000 94b08000 srv2 srv2.sys Thu Oct 25 18:40:47 2007 (4721459F)
    94b08000 94b1a000 mrxsmb20 mrxsmb20.sys Thu Oct 25 18:40:16 2007 (47214580)
    94b1a000 94b53000 mrxsmb10 mrxsmb10.sys Thu Nov 02 01:31:25 2006 (4549ACDD)
    94b53000 94b71000 mrxsmb mrxsmb.sys Thu Oct 25 18:40:17 2007 (47214581)
    94b71000 94b91000 mrxdav mrxdav.sys Fri Jan 11 17:45:54 2008 (47881BD2)
    94b91000 94ba5000 mpsdrv mpsdrv.sys Wed Jun 06 19:55:55 2007 (466773BB)
    94ba5000 94bc0000 srvnet srvnet.sys Thu Oct 25 18:40:43 2007 (4721459B)
    94f0b000 94f58000 eamon eamon.sys Wed Feb 20 01:56:12 2008 (47BBF93C)
    95322000 95400000 peauth peauth.sys Mon Oct 23 01:55:32 2006 (453C8384)

    Unloaded modules:
    8f350000 8f358000 drmkaud.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    87e31000 87e3e000 crashdmp.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    89d75000 89d80000 dump_ataport
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    89df0000 89df8000 dump_atapi.s
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    89cca000 89cdb000 dump_dumpfve
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    Closing open log file c:\debuglog.txt


    What do you guys think? I don't really know how to read these but I think it's the ram because of the the following line:
    Probably caused by : memory_corruption ( nt!MiReplenishPageSlist+e5 )
     
  12. 2008/03/21
    Arie

    Arie Administrator Administrator Staff

    Joined:
    2001/12/27
    Messages:
    15,174
    Likes Received:
    412
    If you are sure that your RAM settings in the BIOS are correct, I would RMA the RAM. You already got 2 errors using Memtest, this means that the RAM is quite bad if software can find errors with it.
     
  13. 2008/03/21
    mahme

    mahme Inactive Thread Starter

    Joined:
    2008/03/18
    Messages:
    20
    Likes Received:
    0
    Sorry for the double post before!

    I checked at my BIOS for the ram settings and they are set to "Optimal" as default running at 800mhz 5-4-4-17. Have'nt changed or overclocked it all. I think ill take the ram back to the store tomorrow and see if I can get it switched. I'll update you guys later...thx for everything!
     
  14. 2008/03/22
    mahme

    mahme Inactive Thread Starter

    Joined:
    2008/03/18
    Messages:
    20
    Likes Received:
    0
  15. 2008/03/22
    mailman Lifetime Subscription

    mailman Geek Member

    Joined:
    2004/01/17
    Messages:
    1,901
    Likes Received:
    11
    I have a number of questions.

    1. Are you certain you're using proper settings in the BIOS for the new RAM?

    2. Did you fully test the new RAM for faults (via testing with software and the "more reliable" method I outlined above)?

    3. If you are certain your BIOS settings for the RAM are correct and fully testing the RAM did not identify any faults, then what are the brand and specifications for the new RAM you installed?

    4. What BIOS revision/date are you running?


    Perhaps there are compatibility issues between your RAM and the Gigabyte GA-73PVM-S2H motherboard you reported you have (or maybe there are other issues with the motherboard).


    Here's a Gigabyte link to find more information and downloads regarding your motherboard.

    5. What revision number is stamped on the motherboard? (There seems to be information for only rev. 1.0.)

    ==========

    If fully testing the RAM did not identify any faults and we don't find any known issues regarding your motherboard, then I'm curious about what EVEREST has to report about your system hardware. (Everest may not be accurate about some information it reports but it might be useful.)

    The hardware gurus might recognize things to investigate if you paste some of the EVEREST information here.

    ==========

    The reported specifications for the replacement PSU you linked has only 17A on one +12V rail and 15A on the other +12V rail. Might not be significant but it certainly is less than the minimum 18A suggested. ;) I don't know about the PSU brand/model reliability either.
     
    Last edited: 2008/03/22
  16. 2008/03/22
    mahme

    mahme Inactive Thread Starter

    Joined:
    2008/03/18
    Messages:
    20
    Likes Received:
    0
    1. The settings on the ram are set to optimal in bios thats defualt.

    2. Yes i have tested the RAM with memtest86 and Microsoft's Windows Memory Diagnostic without errors

    3. The new ram is the same brand and model, i got it replaced at the store since the first one got errors. Thats the memory specs --> http://www.webhallen.com/prod.php?id=82717

    4. I updated my bios from F3 to latest F6

    5. Rev 1.0

    I can't get into everest since i get bluescreen during startup, now when i try to reformat i get bluescreen when windows starts copying over files.

    The PSU is realible since my friend run it on his quadcore with 4gb ram 2900xt without problems.

    EDIT: My friend bought the exakt same motherboard,cpu,ram and his system is up running fine. We dont have the same hdd and psu only. But i know this psu should work proparly beacuse of the above mentioned reason. im gonna run test on my hdd soon with seatools to check its good. Is it possible my motherboard is broken somehow?

    EDIT2: I ran the long test on SeaTools that scans every sector on the harddrive for faults and it didn't find any. So im really beginning to think something is up with the motherboard. By the way is there a possibility somethings wrong with the CPU?
     
    Last edited: 2008/03/22
  17. 2008/03/22
    mailman Lifetime Subscription

    mailman Geek Member

    Joined:
    2004/01/17
    Messages:
    1,901
    Likes Received:
    11
    I suppose the "optimal" settings might not be correct. According to the RAM specs you linked, the voltage across the RAM should be 1.8V ± 0.1V (if I understand correctly). I am not certain what the default timings are.

    Keep in mind, software RAM testers do not detect all errors. Since you already had at least one faulty Transcend module, I would suspect your current Transcend modules, especially if they might have come from the same batch. I would proceed with the "more reliable" testing method I outlined above.

    OK Looks like you have the correct BIOS (as far as I can tell).

    OOPS! I forgot you cannot get into Windows. :eek:

    Yes, it is possible your motherboard is defective. Carefully look/feel for tilted/bulging/leaking capacitors on the motherboard. Study the information at the following site for details.
    • Badcaps.net (Home Page)
      Has clickable thumbnail images of bad capacitors. (Requires Javascript to be enabled in your web browser.)
      • How To Identify
        Describes symptoms and has more clickable thumbnail images of bad capacitors. (Requires Javascript to be enabled in your web browser.)
      • Badcaps FAQ (Frequently Asked Questions)
    You might need a good source of light and a magnifying lens to evaluate the capacitors. If you find issues with the capacitors, then I would be inclined to replace the motherboard.

    There may be other things to look for regarding the motherboard. I am not familiar with those though.
     
    Last edited: 2008/03/22
  18. 2008/03/22
    mailman Lifetime Subscription

    mailman Geek Member

    Joined:
    2004/01/17
    Messages:
    1,901
    Likes Received:
    11
    I don't think you responded directly to hawk22's questions yet. ;)
     
  19. 2008/03/23
    mahme

    mahme Inactive Thread Starter

    Joined:
    2008/03/18
    Messages:
    20
    Likes Received:
    0
    The voltage for the memory is set to 1.840v, the default timings are 5-5-5-18.

    The more realible method was tested because the first transced i tested in both slots, no luck and i did the same thing with the other. I only had one stick at the time.

    And yes the 4-pin 12v in connected proparly :)

    Im gonna check the links you suggested but if i don't find any vissible faults does that mean my motherboard is fine?

    EDIT: I checked the motherboard capacitors and couldn't find any vissible faults.

    "Here are some functionality symptoms and issues your system might display if your capacitors are failing. Please note that these symptoms can occur even if your capacitors are not showing the physical signs demonstrated above. This is a rare occurrence, but it does happen. Most of the time, there will be physical signs of failure.

    System Faults:
    Motherboard fails to POST.
    Memory Test Fails.
    System randomly and/or constantly reboots itself.
    Fails to fully boot (or even install) Operating System.
    System randomly and frequently freezes.
    Random & frequent 'Blue Screens of Death'
    BSoD or hard freeze under heavy drive activity (Either RAID, SCSI, or standard ATA)
    CPU temps abnormally higher than usual under typical or less load.
    *CPU VCORE & other system voltages are erratic or far out of tolerances.
    Resetting the system after a freeze and the system will not repost.
    (You have to completely power down then power back up.) "

    The system faults desscribed are pretty much what im experiencing at the moment especially these:
    Memory Test Fails.
    System randomly and/or constantly reboots itself.
    Fails to fully boot (or even install) Operating System.
    System randomly and frequently freezes.
    Random & frequent 'Blue Screens of Death'

    Maybe i should send my motherboard back what do you guys think, would you do any more testing to be sure, if so what? All tips and thoughts are welcome!
     
    Last edited: 2008/03/23
  20. 2008/03/23
    hawk22

    hawk22 Geek Member

    Joined:
    2002/01/31
    Messages:
    1,991
    Likes Received:
    26
    reading your last post reminded me some years back before I trusted myself to do many things inside the PC Case. I had the my PC at a repair shop to install a new 80 GIG HD WD and install Win.XP Pro. One week later my PC was still not ready and I questioned the Tech why and he told me that he spend 2 days trying to load XP and could not do so as soon as the the files where to load blue screen after 3 days he had the new HD tested and it had proofed to be faulty WD did confirm as such and replaced the HD.
    This might not be relevant to you but as a thought worth to keep in mind you did try just about everything else.
     
  21. 2008/03/23
    mahme

    mahme Inactive Thread Starter

    Joined:
    2008/03/18
    Messages:
    20
    Likes Received:
    0
    I did try to use my old 160 IDE harddrive which i know works and it also kept getting bluescreens during install...im totally clueless now. Any word if advice?
     

Share This Page

  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.