i'm trying to create another partition so i can run windows 7 or xp, am following a tutorial on Internet showing how to do this and everything is working great until i click finish on the new simple volume wizard. then the pop-up appears, warning that clicking yes will change the basic volume to some other volume (dynamic i believe) and that i would not be able to start other operating systems from it. i click yes anyway.now disk c is labeled crash dump when it was previously labeled as a primary partition. and the header bar by disk 0 is now green rather than blue (i think it was blue).new volume (f is the new volume i created.i tried system restore but this computer has only been running for an hour and we have not created any restore points yet.
I have a brand new Windows 7 64bit build with a clean install from an Upgrade CD and noticed in BIOS that my 1st boot device must be "Windows Boot Manager" or it asks for the CD. I only have 1 storage device (SSD) in the system and when I look under Disk Management in windows, it shows a 100MB "EFI System Partition" in addition to the primary partition (which is labeled "Boot, Crash Dump, and Primary Partition" - so it seems to have the boot files on it).
As I only have the one non-optical storage device I did not set any partition parameters at install. I Attempted to do a Startup Repair with the windows disc to maybe try and delete the EFI partition and got the "... System Recovery Options is incompatible with the version you are trying to repair" error. Not sure what that is. If Disk Management shows a healthy partition with "Boot" listed as being contained, why can I not select the SSD as boot device #1? I can boot perfectly fine with the Windows Boot Manager listed as boot device #1 and the SSD as #2, however it's not ideal.
I used to get a crash dump opening certain folders, usually was one of my car picture folders, recently it's my downloads with my minecraft etc in it.. I've run check disk but it happens over and over and over, never fails.The bug check is as follows 0x000000F4 (0x00000003,0x87558828,0x875899 4,0x8321CD60)When it runs check disk it deletes thousands of orphan files it tells me, 12kb in bad sectors, deleting corrupt file record segment 37572, deleting index entry for a ton of dll files. Also since this started my computer is convinced it isn't genuine windows when it really is..
Recently re installed windows 7 from my windows 7 disc.Hard drive was formatted.Worked fine for about 4 weeks then it crash dumped.When i re start the laptop it goes to windows error page and goes to system repair or start windows normally. Either of these starts windows then goes blank and re starts.When i go into the bios and boot from a disc it starts windows but then the windows screen shows but it has no start up and just freezes. I have tried to re install windows again and it get to the language settings page and the goes starting windows and it does not do anymore just stays on the strating windows page.
It can be any game from something like Minecraft to Battlefield 3 which causes problems for me. The first conclusion I could make was that there may be a problem with my Video card as playing high end games like BF3 can be very demanding on the average computer. I have updated drivers and tried to fix it to no end. These BSODs seem to happen at least 1-3 times a day. The crash dumps can happen both when starting up the game or while I am playing it. I don't know whether any of this information is useful or whether it is even related to what can be seen by analysing the files from sf-diagnostic. All the files needed should be attached.
I've had three BSOD's in three days now all while playing either Skyrim and Dead Island. I have the three individual crash dumps attached.The video card I am using is new to the system and has had its drivers updated to Nvidia's latest (not those from the manufacturer's homepage).My guess is that I'm either having some kind of conflict with drivers here or that my PSU is inadequate but without being able to decipher the information in the dumps I can't tell. BSOD's are not my specialty at all but I don't want to simply ignore this.
I tried searching first but I seem to have trouble finding the proper terms to narrow the search enough... So I just post this.I put together a HTPC for 24/7 usage (windows media center and iMON remote control, spotify, PowerDVD for Blu-Ray movies). Minimal amount of additional software installed. The problem is it locks up often. The whole Windows 7 goes fully unresponsive (all you can do is power off -> on). It rarely stays responsive for 48 hours. No crash dump is generated. The event log shows nothing special, mainly two error items, one related with errors on Microsoft Security Essentials and the other is Circular Kernel Context Logger session failing to start.The main question is: what is there to do, is there a program that could monitor which other program seems to halt the system? I'd hate to go through eliminating each and every software/hardware component... The second question is: just in case, does anything below ring any bells what might cause the problem?
My wife's laptop has developed a bad habit of randomly locking up to the point you have to hold the power button to shut the laptop off. I'm just wondering if it's possible to get Windows to write a crash dump off events like that, or is that at the point where it's just not going to happen even with the correct options selected?
The laptop is a HP G62 Notebook PC running Windows 7. More exact information can be provided if needed.
i have recently had a crash dump file appear in c:windowsminidump.i am uploading it here, for those who my wish to review it.however, i cannot specify what the cause of thes problem my have been.
my 2 year-old toshiba satellite l675d-s7016 has been making a loud screeching noise for the past week. it only happens when i'm watching videos (hulu, Internet, etc.) it slows the video down, distorts it, and then my computer has blue screen and shuts down. i think that it started when i downloaded a screen-sharing program called join me. i never used the program, but i can't even find it in my "programs." i'm using windows 7?
on each startup/restart/reboot I get a pair of these errors, about 15 seconds apart. System is a P4 desktop, 4GB ram, conventional hdd, windows 7 ulti x64.
I read through a few threads with similar topics but the issues were either not quite the same and/or resolved comparatively easily. I am trying to repair a 1.5 year-old HP Pavilion running Windows 7 Home Premium 64. This machine is used as the main office computer in a small doctor's office. In spite of my warnings, anti-virus software was not installed until it was too lateThere was a major issue about seven months ago that required another company to repairThe problem is explorer.exe will not run. Double-clicking a shortcut on the desktop, clicking the text name of a program from the Start menu, and even in the cmd results in the same response, a dialog box pops up stating windows explorer has stopped working.
windows is checking for a solution to the problem. followed by another box stating windows explorer is restarting. But the requested application never starts. I have run the Ultimate Boot CD 4 Win, replaced the hard drive and cloned all data, run numerous registry scans, malware scans and antivirus scans. Initially removing over 1500 virus/malware hits and over 1400 registry errors. But the main problem persists, explorer.exe won't open programs.
I've heard the term memory dump file or dump file being used? I was wondering what it means?I've gathered that it may be something to do with error messages or errors.
I install Windows 7 64 bit in a 60 gb partition of my HDD (C drive). I have about 200 GB free space in D drive. Now I want to make a 60 GB partition from the free space of D drive.
It has been a month or two that I bought a new Pc and now I suddenly get a blue screen (dump). I have also attached the .dmp file which I got in the minidump folder.
i bought a computer 1 month ago and every time i start the com or surf the net for fews hours it will start to have blue screen and say physical memory dump .i followed the instrution above and do the zip file or my scan .
Just build a new computer running windows 7 64-bit- it's fast and works great. I bought an external hard drive to back it up and every time I run a back up I get a BSOD. I have a dump file but don't know how to read it so I am posting it here.Actually it seems that I can not upload the dump file here.
My new ACER has as processor "INTEL PREMIUM P6200". Random poking around reveals that under windowssystem32driverstore there is a VERY large number of inf files for AMD64. I can delete all that crap without worrying about a thing, right? Windows 7 home premium SP1.
I have recently put a RAID 0 WD raptor 300g in place and when ever I cold boot I get a 50/50 chance that I get a screen dump and a reboot. On reboot I see one of the raptors takes 10 to 20 secons to initialise. Once second reboot happens the system works fine. Is it my drive or memory or what?
one day my computer crashed then it started chkdsk after the chkdsk, a program called "objectdock" got corrupted.So i deleted it somehow and now my computer gets BSOD everytime i reboot it?Is there any ways to save my comp. without using an complete restore?
So Ive now been getting random BSODs on my desktop for a month now, and was troubleshooting the problem all this time. Finally, to out rule any corrupt/conflicting drivers I freshly reinstalled windows (which didnt help though).
Since this reinstall, however, no more dump files are created during the BSODs. It just shows:
Collecting data for crash dump ... Initializing disk for crash dump ...
And it stays at this, no usual data dumping, even after letting the screen sit for about an hour. It recorded the dump files normally before the re-installation.
I already checked system properties, under the advanced tab, to ensure that the dump file creation was enabled. It is.
Also, does anyone know what could cause this bsod? From the dumpfiles before the reinstallation, i know that Hal.dll is the driver causing the problems. Could it be my OC? ( I doubt it as returning the CPU to factory settings resulted in the same BSODs)
