TechSpot

Bsod on cold start, only after a date change?? error pointing to device driver

By igfloz
Feb 1, 2005
  1. Heya, Just joined and have a problem ( wouldn't be here otherwise would I ?? )

    I get a BSOD on a cold startup - which only seems to occur after a date has changed...
    What I mean is, say on the 23/1/05 I shut down pc at 3 pm then boot up the pc at 8 pm, it works fine.
    BUT if I shut down the pc on the 23/1/05 at 9 pm, then boot up at 10 am on the 24/1/05 I get a BSOD !!

    When I get the BSOD, it normally takes 3 re-boots to get Windows XP (SP2, Fully updated) to get going. The first crash happens while the "XP is loading" sreen, second crash happens as soon as I try to log in and my desktop is building up and the third crash happens just after I get a useable desktop, but as soon as I go to do something - CRASH!!

    The only other information I can offer is : -

    Event Type: Information
    Event Source: Save Dump
    Event Category: None
    Event ID: 1001
    Date: 30/01/2005
    Time: 15:34:47
    User: N/A

    Description:
    The computer has rebooted from a bugcheck. The bugcheck was: 0x0000000a (0xffbded18, 0x00000001, 0x00000000, 0x80505390). A dump was saved in: C:\WINDOWS\MEMORY.DMP


    The above error message seems to get me nowhere on microsoft and google, so any help or information would be really helpfull...


    Thanks a load in advance,

    igfloz :confused:
     
  2. cpc2004

    cpc2004 TS Rookie Posts: 2,044

    Your problem is quite interesting. Attach 3 to 4 minidumps here and you can find the minidumps at the folder \windows\minidump for xp \winnt\minidump for w2k.
     
  3. igfloz

    igfloz TS Rookie Topic Starter

    cheers cpc2004 - gonna search for some minidumps
    will have them up later......

    C:\>dumpchk.exe %systemroot%/memory.dmp
    Loading dump file C:\WINDOWS/memory.dmp
    ----- 32 bit Kernel Summary Dump Analysis

    DUMP_HEADER32:
    MajorVersion 0000000f
    MinorVersion 00000a28
    DirectoryTableBase 1e24b000
    PfnDataBase 81053000
    PsLoadedModuleList 8055ab20
    PsActiveProcessHead 80560bd8
    MachineImageType 0000014c
    NumberProcessors 00000001
    BugCheckCode 0000000a
    BugCheckParameter1 ffbde008
    BugCheckParameter2 00000001
    BugCheckParameter3 00000000
    BugCheckParameter4 80505390
    PaeEnabled 00000000
    KdDebuggerDataBlock 8054c760

    SUMMARY_DUMP32:
    DumpOptions 504d4453
    HeaderSize 00008000
    BitmapSize 0002fff0
    Pages 00004e86
    Bitmap.SizeOfBitMap 0002fff0

    KiProcessorBlock at 80559a20
    1 KiProcessorBlock entries:
    ffdff120


    Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
    Built by: 2600.xpsp_sp2_rtm.040803-2158
    Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055ab20
    Debug session time: Sun Jan 30 15:35:13 2005
    System Uptime: 0 days 0:01:04
    start end module name
    804d7000 806eb780 nt Checksum: 002160C9 Timestamp: Wed Aug 04 07:
    19:48 2004 (41108004)

    Unloaded modules:
    f75af000 f75b8000 processr.sys Timestamp: Sun Jan 30 15:34:32 2005 (41FCFE88)

    f78b7000 f78bc000 Cdaudio.SYS Timestamp: Sun Jan 30 15:34:32 2005 (41FCFE88)

    f6db4000 f6db7000 Sfloppy.SYS Timestamp: Sun Jan 30 15:34:32 2005 (41FCFE88)

    f7a97000 f7a99000 USBD.SYS Timestamp: Sun Jan 30 15:34:31 2005 (41FCFE87)

    f775f000 f776a000 lvusbsta.sys Timestamp: Sun Jan 30 15:34:31 2005 (41FCFE87)

    f7a91000 f7a93000 USBD.SYS Timestamp: Sun Jan 30 15:34:30 2005 (41FCFE86)

    f76ff000 f770a000 lvusbsta.sys Timestamp: Sun Jan 30 15:34:30 2005 (41FCFE86)

    f7a8d000 f7a8f000 USBD.SYS Timestamp: Sun Jan 30 15:34:30 2005 (41FCFE86)

    f76ef000 f76fa000 lvusbsta.sys Timestamp: Sun Jan 30 15:34:30 2005 (41FCFE86)

    f7a89000 f7a8b000 USBD.SYS Timestamp: Sun Jan 30 15:34:30 2005 (41FCFE86)

    f76df000 f76ea000 lvusbsta.sys Timestamp: Sun Jan 30 15:34:30 2005 (41FCFE86)

    f7a85000 f7a87000 USBD.SYS Timestamp: Sun Jan 30 15:34:30 2005 (41FCFE86)

    f76cf000 f76da000 lvusbsta.sys Timestamp: Sun Jan 30 15:34:30 2005 (41FCFE86)

    f7a81000 f7a83000 USBD.SYS Timestamp: Sun Jan 30 15:34:30 2005 (41FCFE86)

    f76bf000 f76ca000 lvusbsta.sys Timestamp: Sun Jan 30 15:34:30 2005 (41FCFE86)

    f7a7d000 f7a7f000 USBD.SYS Timestamp: Sun Jan 30 15:34:30 2005 (41FCFE86)

    f767f000 f768a000 lvusbsta.sys Timestamp: Sun Jan 30 15:34:30 2005 (41FCFE86)

    Finished dump check

    C:\>





    ^^That's my most recent memory dump.
     
  4. igfloz

    igfloz TS Rookie Topic Starter

    Some more minidumps

    Found the minidump folder - here are some minidumps for you to look at.

    Hope it will help :grinthumb
     
  5. igfloz

    igfloz TS Rookie Topic Starter

    Bsod

    DAMMIT !!!


    It would seem that my problem lies with a faulty stick of SDRAM (512 Mb)
    I recently added another 512 Mb to my pc, and my BSOD on bootup got even worse - all sorts of errors being reported :knock:

    since removing my original 512 Mb RAM, all my problems have gone...

    Thanks to anyone who has looked into this for me tho'

    cheers,

    igfloz.

    :rolleyes:



    P.S. - Still dunno why this should point to a driver error on the windows fault reprting tho' ???
     
  6. AnySupreme

    AnySupreme TS Rookie Posts: 34

    there is a program to check the memory..you can try downloading it and testing your memory with it...but usually when you're having a problem with memory...especially if it's new ( or you think it's new ) it could be a problem with your motherboard's bios version..some bios versions haven't yet fixed the problem until the board was already out on the market. so you should try looking into that...
     
Topic Status:
Not open for further replies.


Add New Comment

TechSpot Members
Login or sign up for free,
it takes about 30 seconds.
You may also...


Get complete access to the TechSpot community. Join thousands of technology enthusiasts that contribute and share knowledge in our forum. Get a private inbox, upload your own photo gallery and more.