hi
I am using win2k ADS. I am having a wierd problem..my system restarts automatically. thats not my question here..when i try to copy a huge file say 600 MB my machine reboots automatically before the file is saved into my HDD.. When the machine restarts my HDD(d:\ where i am trying to copy the file) is showing the extra 600 MB . But the file is not there. is there any way to restore the 600 MB lost .Only way i tried is formatting..but i cant do that everytime. i am runnning out of disk space. can any one help me on this

Regards
Mysterio

Are you using NTFS or FAT32? Is the drive's write cache turned on? Try running chkdsk c: /f changing c: to whatever drive letter you're having problems with.

Well, if you'de turn off the automatic reboot function after a crash (Properties of your computer, advanced page, startup and recovery settings) you might find out what goes wrong. The 'Blue Screen Of Death' will tell you some info on why it crashed.

With this information we can possible find you a solution . . .

another thing you can do is take a look in c:\windows\system32\minidump (may be c:\windows\minidump can't remember which), and take one of the files from there and post it here as an attachment, i'll download it and run it through ms's debugger for you and see what it says :), the files in that folder are what's contained in memory at the time it bluescreened and the debugger can usually tell you what file(s) caused the blue screen which is useful in figuring out what's wrong

Wow, that nice Sephiroth.

Yoy must tell me sometime how that works, cause I sure would love to know more about this!

Hi Sephiroth

I don't have the problem that TheMysterio has but I am familiar with C:\Windows\Minidump and have often looked in there but, I just looked for that folder and it's not there now and I don't know why.

I am running XP Pro and I reinstalled the system about two weeks ago and I don't see minidump anymore. Any ideas?

Regards

Brave01Heart

I'm not Sephiroth :) but you can change the settings by selecting the properties of your computer, go to the advanced tab, and change the "Write debug information" on the startup and recovery page. Change the setting to "Small memory dump".

I don't know if this is what you ment btw, but still, hope it helps!

The folder is created the first time the computer blue screens. Until it does, it won't be there, so hope it never appears :D

k, once i finish a few things i'll post a faq on how to do that :D :ph34r:

Cool. Thanks!

I'm sure a lot of people will benefit from that.

first thanks for your repies guys. as i was busy i didnt had time to check the forums. i am not sure of how to trun off the automatic rebooting..but will check that.. i will also post the file minidump tomorrow so that Sephiroth can help me out to fix the problem. I am using Fat 32.

Thanks
TheMysterio

Hi Sephiroth & Le Cactus

Many thanks for your help ......... you learn something knew everyday. :o)

Best regards

Brave01Heart

@ Sephiroth When you get time....which we all run out of ...it would be great help for a step by step as how to solve problems like that using the ms debugger. I know you said you would and just letting you know it will be nice and Many Thanks. Maybe we can help others

hi Sephiroth
how do i attach a file
:huh:

try emailing it to Sephiroth@betaone.net and I'll get back to ya when I get it :), sorry for the late reply, been a bit busy

hey Sephiroth
I've emailed u the Mini110302-01.dmp file. please do the needful
TheMysterio

Ok, here goes :)

I don't have the symbol package for Win2K SP3 (symbols are files to debug system files against), I'm not sure if they have even made them yet, and I can't get a detailed analysis as I'm not on 2K, but here's what i can get by comparing them to the xp symbols, which shouldn't be too much different.


UdfReadr.sys is what is causing it to crash and reboot. udfreader, I think that is probably Adaptec software. I would search for that file and see what app installed it, then either check for a newer version of the app and see if it stops, or if all else fails uninstall the app and see what happens. I'm just glad it wasn't an NT system file, else it would have been a pain in the ass to debug a 2K file on an XP box, lol. I'm pretty sure that's Adaptec software though, possibly DirectCD, good luck, let us know how it turns out :D

Ok, before I go to bed, here's a quick run through of the MS Debugger.

You can grab the debugger from

http://www.microsoft.com/ddk/debugging/default.asp

After you've downloaded the debugger, click the Symbols link and there's an explination there of how to download kernel symbols.

Start the debugger, click file, source file path, and set that to C:\Windows\System32 (assuming that path is right to your system32 folder, and if it complains about not being able to load files, try either %systemroot% or C:\Windows) and do the same for Image File Path.

You'll then set the Symbol Path from the directions on the link, changing downstream store to the place on your hdd you want to store downloaded kernel symbols.

From there, you can do a few things, debug the windows kernel, attach the debugger to and debug a running process, debug a C source file, debug an exe, or debug a minidump. I haven't played around with any of the options other than debugging a minidump.

Choose file \ open crash dump, navigate to your Minidump folder after a blue screen, open the minidump, let it save workspace information, and then you'll get two windows.

One is line by line the assembly code for what's in memory when the crash happened, all jibberish to me :D, and the other is a screen that will look like what I pasted above. Play around with your image and source paths if you get files could not be loaded errors. Once it's done, type !analyze -v to get a detailed analysis, and it will usually be able to tell you the exact file or files that caused the system to crash, using the one above as an example it would be something like this:

UdfReadr.sys was loaded in ram, conflicted with ntoskrnl.exe, and that caused the machine to crash.

If you need anymore of an explination I'll be happy, just ask :), for now, I must sleep, got classes at 8am, lol. :D

hi Sephiroth

I have a CD Writer so i use Adaptec Direct CD. you Direct CD is the culprit?. I will also download the MS Debugger and play with it..if i have any problem will ping you

Thanks for ure help

Regards
Mysterio

np :), uninstall direct cd and see what happens ;)

ok will try that and will getback to u on monday.
Happy weekend

regards
the Mysterio

this is my error

:

Use !analyze -v to get detailed debugging information.

BugCheck 1000008E, {c0000005, bf865728, f29027d4, 0}

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

Unable to load image win32k.sys
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : win32k.sys ( win32k+65728 )


What can i do ?!

Followup: MachineOwner

i upgraded the UDF READER an the problem of auto rebooting is not happening.. but no one has suggested me what to do abt the 600 mb space it has taken while improper copying. please help me on this
Thanks to Sephiroth for finding out the problem

Thanks
TheMysterio

Hmmm,

It might be that your computer was making complete memorydumps (or does some error reporting) while rebooting.

Enable the view of all files, including hidden and system files (the "View" tab of the "Folder Options..." from the "Tools" menu of your Explorer :)) and do a search for *.dmp.

You've prolly got some huge .dmp files.

Hopes this helps.

Thanks Sephiroth ;)

I have download the debugger and the symbols :lol:

This is a really big folder for symbols (734megs) but now I can try it