Bsod on cold start, only after a date change?? error pointing to device driver
igfloz
02-01-2005, 06:27 PM
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:
cpc2004
02-03-2005, 09:06 AM
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.
Ad
02-03-2005, 09:06 AM
igfloz
02-03-2005, 04:16 PM
cheers cpc2004 - gonna search for some minidumps
will have them up later......
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.
igfloz
02-03-2005, 05:53 PM
Found the minidump folder - here are some minidumps for you to look at.
Hope it will help :grinthumb
igfloz
02-19-2005, 04:59 PM
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' ???
AnySupreme
02-20-2005, 01:08 AM
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...