Blue screen of death problem...need to fix

It appears to be the same minidump.

Kernel dumps are located on the system root folder (directory)

So if Windows is on the C: drive, it will be under C:\memory.dmp

Matt

 

i set it to system root (windows folder) /memorydump so it creates a folder called memory dump and dumps it in there. or should i create it by myself? i didnt find anything in my I drive (which is where wind is located).

 

Do a Start -> Search for *.dmp. In the search, set it to find hidden and system files.

You should find it is not actually IN a folder, just under C:\

Matt

 

Im a little busy now so ill do in as soona s i get to my main comp (the one with that problem). thanks a lot, ill try.

 

Hi, Ed.

Matt asked me to step in with information about likely dump file locations. With my machine anyway (Windows XP Home SP2), even with my system configured to write a Kernel dump, it also has written a minidump when my system has crashed.

When using the DebugWiz tool to browse to the I:\WINDOWS\Minidump\ folder, look for dump files that are named as follows.

If you have your system configured to write a Kernel dump to %SystemRoot%\MEMORY.DMP (as shown in the image attached below), then I expect Windows will write the MEMORY.DMP file in the Windows folder. (The path appears to be I:\WINDOWS\MEMORY.DMP in your case.) If the .DMP file is not located there, then try looking in the root folder (I:\).

If you have "Overwrite any existing file" UNchecked and you already have a MEMORY.DMP file in your Windows folder, then I expect you will be prompted to modify the name for the new dump file (after a new system crash) so it does not overwrite the existing dump file.

A quick way to access the Startup and Recovery window is to hold down your Windows key and press the Pause/Break key. That will bring up the System Properties window. Click the "Advanced" tab and the Startup and Recovery section will be located near the bottom of that Window. Click its "Settings" button to open the window I have displayed in the attached image. (Click the Thumbnail to view the full-size image.)

If any of this is confusing or you have difficulty locating the appropriate dump files, then please let us know.

 

yeah i know about that. im just saying that i was expecting it to go into the windows/memorydump folder, the way i set it. currently i have a memory.dmp file in my windows folder which is the 1 gb one. im gonna switch to my other comp soon and try to get it to save it normally. thanks.

 

The summary information below translated to english means that the computer couldn't continue because it couldn't read from the file system which typically means that it couldn't read from the disk. I suspect if you look in your system event log, you will see other errors like Event ID 9's or Event ID 11's indicating disk issues. If this isn't the case then you still have some issue related to reading your hard disks.

KERNEL_DATA_INPAGE_ERROR (7a)
The requested page of kernel data could not be read in. Typically caused by
a bad block in the paging file or disk controller error. Also see

If the error status is 0xC000009A, then it means the request failed because
a filesystem failed to make forward progress.

John

 

wow thanks, you guys are great. Ill do that now and report to you by editing this post.
PS: i havent been getting blue screens last night, sorry so thats why i cant post a kernel

 

weird but ive been using my comp all day today and didnt get a single blue screen...

 

I have had BSOD issues in the past that seemed to clear themselves up over several days.

If you are using the NTFS file system for your Windows XP operating system, then I suppose it is possible Windows XP's "journaling file system" is doing its job to make it more stable.

• Wikipedia:
  • Journaling file system
  • NTFS

If you do not want to wait for a BSOD and you want to manually generate a BSOD to test your Startup and Recovery settings, then have a look at the following article.

• Microsoft: Windows feature lets you generate a memory dump file by using the keyboard
  

I think the "APPLIES TO" section of that article used to list Windows XP Professional (but not Home). Now only Windows Server 2003 versions are listed. However, when I tried it last August with my Windows XP Home SP2 computer, I was successful. No need to post the DebugWiz info for those crashes though.

 

I was working on my comp all day, even playing flatout 2 without any blue screens. Today morning i came on and i was talking to someone on msn and she added files to the sharing folder which was when it crashed. It told me some weird codes (sorry didnt record) about win32k.sys.
Then it happened again when she added stuff to sharing folders. Then i went to my other comp.
Any ideas about the win32k.sys?