1. TechSpot is dedicated to computer enthusiasts and power users. Ask a question and give support. Join the community here.
    TechSpot is dedicated to computer enthusiasts and power users.
    Ask a question and give support.
    Join the community here, it only takes a minute.
    Dismiss Notice

BSoD on boot after power supply failiure

By tudor
Jun 17, 2006
  1. I have been reading your forums for a while trying to find something, and I really dunno what to do in my particular problem anymore :-s
    Thing is my power supply crashed a few times one day while I was trying to boot my PC. I replaced it, and Windows now gives me a BSoD on boot about viamraid.sys with STOP 0x0A IRQL_NOT_LESS_OR_EQUAL. I ran chkdsk /f /r a few times and the 1st time I ran it, it found 4KB of bad sectors :-( on my HD, it marked them bad.
    Now whenever I want to boot it gives me the same BSoD.
    So far i've tryed replacing the viamraid.sys with the good version from the VIA CD.
    I've tryed running memtest to see if my RAM was ok, and it is, also no dust, no overheating.
    The BSoD appears on boot exactly in the same place, if I start normally it BSoDs on the loading scree, if I run safe mode it BSoDs a little after the Windows desktop is painted.
    I'm running WinXP Pro SP2 on an Athlon XP 512MB RAM, VIA MB, 200GB Maxtor SATA HD.

    edit: and btw I forgot to mention, my HD is perfectly OK except for the 4KB bad sectors, im running on WinVista from a diferent partiton at the moment.

    This would be my minidump, can anyone please help me on this? I would really apreciate it.

    Opened log file 'c:\dlog.txt'
    kd> .sympath srv*c:\symbols*http://msdl.microsoft.com/download/symbols
    Symbol search path is: srv*c:\symbols*http://msdl.microsoft.com/download/symbols
    kd> .reload;!analyze -v;r;kv;lmnt;.logclose;q
    Loading Kernel Symbols
    ..................Unable to load image viamraid.sys, Win32 error 2
    *** WARNING: Unable to verify timestamp for viamraid.sys
    *** ERROR: Module load completed but symbols could not be loaded for viamraid.sys
    Loading User Symbols
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    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 kernel debugger is available get stack backtrace.
    Arg1: 00000030, memory referenced
    Arg2: 00000011, IRQL
    Arg3: 00000000, value 0 = read operation, 1 = write operation
    Arg4: f83899a0, address which referenced memory
    Debugging Details:
    READ_ADDRESS:  00000030 
    f83899a0 807f3028         cmp     byte ptr [edi+0x30],0x28
    LAST_CONTROL_TRANSFER:  from f8389a2e to f83899a0
    WARNING: Stack unwind information not available. Following frames may be wrong.
    805500d0 f8389a2e 822b0004 822b0fe4 822b0004 viamraid+0xa9a0
    00000000 00000000 00000000 00000000 00000000 viamraid+0xaa2e
    STACK_COMMAND:  .bugcheck ; kb
    f83899a0 807f3028         cmp     byte ptr [edi+0x30],0x28
    FOLLOWUP_NAME:  MachineOwner
    SYMBOL_NAME:  viamraid+a9a0
    MODULE_NAME:  viamraid
    IMAGE_NAME:  viamraid.sys
    FAILURE_BUCKET_ID:  0xD1_viamraid+a9a0
    BUCKET_ID:  0xD1_viamraid+a9a0
    Followup: MachineOwner
    eax=f838c020 ebx=00000000 ecx=822b0004 edx=00000000 esi=f838bca0 edi=00000000
    eip=f83899a0 esp=805500c4 ebp=805500d0 iopl=0         nv up ei ng nz na po nc
    cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010286
    f83899a0 807f3028         cmp    byte ptr [edi+0x30],0x28 ds:0023:00000030=??
    ChildEBP RetAddr  Args to Child              
    WARNING: Stack unwind information not available. Following frames may be wrong.
    805500d0 f8389a2e 822b0004 822b0fe4 822b0004 viamraid+0xa9a0
    00000000 00000000 00000000 00000000 00000000 viamraid+0xaa2e
    start    end        module name
    804d7000 806eb100   nt       ntoskrnl.exe Wed Mar 02 02:59:37 2005 (42250FF9)
    806ec000 806ffd80   hal      halacpi.dll  Wed Aug 04 08:59:04 2004 (41107B28)
    bf000000 bf011580   dxg      dxg.sys      Wed Aug 04 09:00:51 2004 (41107B93)
    bf800000 bf9c1180   win32k   win32k.sys   Thu Oct 06 03:05:44 2005 (43446A58)
    bff50000 bff52480   framebuf framebuf.dll Wed Aug 04 10:56:31 2004 (411096AF)
    f80cd000 f80def80   dump_viamraid dump_viamraid.sys Fri Mar 26 10:00:04 2004 (4063E304)
    f80df000 f80ef280   Udfs     Udfs.SYS     Wed Aug 04 09:00:27 2004 (41107B7B)
    f8110000 f8123780   VIDEOPRT VIDEOPRT.SYS Wed Aug 04 09:07:04 2004 (41107D08)
    f8144000 f8146900   Dxapi    Dxapi.sys    Fri Aug 17 23:53:19 2001 (3B7D843F)
    f814c000 f817f200   update   update.sys   Wed Aug 04 08:58:32 2004 (41107B08)
    f8180000 f81b0100   rdpdr    rdpdr.sys    Wed Aug 04 09:01:10 2004 (41107BA6)
    f81b1000 f81d3e80   USBPORT  USBPORT.SYS  Wed Aug 04 09:08:34 2004 (41107D62)
    f81d4000 f81f6680   ks       ks.sys       Wed Aug 04 09:15:20 2004 (41107EF8)
    f81fb000 f81fe780   dump_scsiport dump_scsiport.sys Wed Aug 04 08:59:51 2004 (41107B57)
    f8207000 f8209f80   mouhid   mouhid.sys   Fri Aug 17 23:47:57 2001 (3B7D82FD)
    f823f000 f8259580   Mup      Mup.sys      Wed Aug 04 09:15:20 2004 (41107EF8)
    f825a000 f8277000   Teefer   Teefer.sys   Thu Jul 01 00:49:55 2004 (40E33583)
    f8277000 f82a3a80   NDIS     NDIS.sys     Wed Aug 04 09:14:27 2004 (41107EC3)
    f82a4000 f8330480   Ntfs     Ntfs.sys     Wed Aug 04 09:15:06 2004 (41107EEA)
    f8331000 f8347780   KSecDD   KSecDD.sys   Wed Aug 04 08:59:45 2004 (41107B51)
    f8348000 f8366780   fltMgr   fltMgr.sys   Wed Aug 04 09:01:17 2004 (41107BAD)
    f8367000 f837e800   SCSIPORT SCSIPORT.SYS Wed Aug 04 08:59:39 2004 (41107B4B)
    f837f000 f8390f80   viamraid viamraid.sys Fri Mar 26 10:00:04 2004 (4063E304)
    f8391000 f83a8480   atapi    atapi.sys    Wed Aug 04 08:59:41 2004 (41107B4D)
    f83a9000 f83ce700   dmio     dmio.sys     Wed Aug 04 09:07:13 2004 (41107D11)
    f83cf000 f83ed880   ftdisk   ftdisk.sys   Fri Aug 17 23:52:41 2001 (3B7D8419)
    f83ee000 f83fea80   pci      pci.sys      Wed Aug 04 09:07:45 2004 (41107D31)
    f83ff000 f842cd80   ACPI     ACPI.sys     Wed Aug 04 09:07:35 2004 (41107D27)
    f842d000 f8444800   SPTD3453 SPTD3453.SYS Wed Aug 04 08:59:39 2004 (41107B4B)
    f8536000 f853ec00   isapnp   isapnp.sys   Fri Aug 17 23:58:01 2001 (3B7D8559)
    f8546000 f8550500   MountMgr MountMgr.sys Wed Aug 04 08:58:29 2004 (41107B05)
    f8556000 f8562c80   VolSnap  VolSnap.sys  Wed Aug 04 09:00:14 2004 (41107B6E)
    f8566000 f856ee00   disk     disk.sys     Wed Aug 04 08:59:53 2004 (41107B59)
    f8576000 f8582200   CLASSPNP CLASSPNP.SYS Wed Aug 04 09:14:26 2004 (41107EC2)
    f8586000 f8590e80   uagp35   uagp35.sys   Wed Aug 04 09:07:43 2004 (41107D2F)
    f85b6000 f85c2180   cdrom    cdrom.sys    Wed Aug 04 08:59:52 2004 (41107B58)
    f85c6000 f85d4080   redbook  redbook.sys  Wed Aug 04 08:59:34 2004 (41107B46)
    f85d6000 f85e0380   imapi    imapi.sys    Wed Aug 04 09:00:12 2004 (41107B6C)
    f85e6000 f85f2e00   i8042prt i8042prt.sys Wed Aug 04 09:14:36 2004 (41107ECC)
    f85f6000 f85fff00   termdd   termdd.sys   Wed Aug 04 08:58:52 2004 (41107B1C)
    f8616000 f8624100   usbhub   usbhub.sys   Wed Aug 04 09:08:40 2004 (41107D68)
    f8656000 f865e300   LHidUsb  LHidUsb.Sys  Fri Dec 12 02:25:39 2003 (3FD90B03)
    f8666000 f866ed80   HIDCLASS HIDCLASS.SYS Wed Aug 04 09:08:18 2004 (41107D52)
    f8676000 f86857c0   LMouFlt2 LMouFlt2.Sys Fri Dec 12 02:25:14 2003 (3FD90AEA)
    f8686000 f8695900   Cdfs     Cdfs.SYS     Wed Aug 04 09:14:09 2004 (41107EB1)
    f87b6000 f87bc200   PCIIDEX  PCIIDEX.SYS  Wed Aug 04 08:59:40 2004 (41107B4C)
    f87be000 f87c2900   PartMgr  PartMgr.sys  Sat Aug 18 04:32:23 2001 (3B7DC5A7)
    f87c6000 f87cabc0   PxHelp20 PxHelp20.sys Tue Oct 28 20:25:49 2003 (3F9EB4AD)
    f87e6000 f87e7000   fdc      fdc.sys      unavailable (00000000)
    f882e000 f8833a00   mouclass mouclass.sys Wed Aug 04 08:58:32 2004 (41107B08)
    f8846000 f884c180   HIDPARSE HIDPARSE.SYS Wed Aug 04 09:08:15 2004 (41107D4F)
    f884e000 f8852500   watchdog watchdog.sys Wed Aug 04 09:07:32 2004 (41107D24)
    f886e000 f8873000   flpydisk flpydisk.sys Wed Aug 04 08:59:24 2004 (41107B3C)
    f889e000 f88a3200   vga      vga.sys      Wed Aug 04 09:07:06 2004 (41107D0A)
    f88ae000 f88b3f80   LHidFlt2 LHidFlt2.Sys Fri Dec 12 02:25:23 2003 (3FD90AF3)
    f88be000 f88c2a80   Msfs     Msfs.SYS     Wed Aug 04 09:00:37 2004 (41107B85)
    f88ce000 f88d5880   Npfs     Npfs.SYS     Wed Aug 04 09:00:38 2004 (41107B86)
    f88e6000 f88eb000   usbuhci  usbuhci.sys  Wed Aug 04 09:08:34 2004 (41107D62)
    f8916000 f891c800   usbehci  usbehci.sys  Wed Aug 04 09:08:34 2004 (41107D62)
    f8936000 f893c000   kbdclass kbdclass.sys Wed Aug 04 08:58:32 2004 (41107B08)
    f8946000 f8949000   BOOTVID  BOOTVID.dll  Fri Aug 17 23:49:09 2001 (3B7D8345)
    f89ea000 f89edc80   mssmbios mssmbios.sys Wed Aug 04 09:07:47 2004 (41107D33)
    f8a36000 f8a37b80   kdcom    kdcom.dll    Fri Aug 17 23:49:10 2001 (3B7D8346)
    f8a38000 f8a39100   WMILIB   WMILIB.SYS   Sat Aug 18 00:07:23 2001 (3B7D878B)
    f8a3a000 f8a3b500   viaide   viaide.sys   Wed Aug 04 08:59:42 2004 (41107B4E)
    f8a3c000 f8a3d700   dmload   dmload.sys   Fri Aug 17 23:58:15 2001 (3B7D8567)
    f8a42000 f8a43100   swenum   swenum.sys   Wed Aug 04 08:58:41 2004 (41107B11)
    f8a46000 f8a47280   USBD     USBD.SYS     Sat Aug 18 00:02:58 2001 (3B7D8682)
    f8a4a000 f8a4bf00   Fs_Rec   Fs_Rec.SYS   Fri Aug 17 23:49:37 2001 (3B7D8361)
    f8a4e000 f8a4f080   Beep     Beep.SYS     Fri Aug 17 23:47:33 2001 (3B7D82E5)
    f8b2a000 f8b2ab80   Null     Null.SYS     Fri Aug 17 23:47:39 2001 (3B7D82EB)
    f8bf7000 f8bf7d00   dxgthk   dxgthk.sys   Fri Aug 17 23:53:12 2001 (3B7D8438)
    Closing open log file c:\dlog.txt
  2. Tedster

    Tedster Techspot old timer..... Posts: 6,000   +15

    like it says.... you probably have bad drivers.
Topic Status:
Not open for further replies.

Similar Topics

Add New Comment

You need to be a member to leave a comment. Join thousands of tech enthusiasts and participate.
TechSpot Account You may also...