I have used the SF Diagnostic tool and attached the files, but there are not memory dump files as i have tried several times to enable them but the system never creates them. The crash happens randomly and is not associated with Game or any specific application. I am using Kaspersky Pure as antivirus and i am sure its not causing any problem as i have been using it on other systems and laptops.
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)
The last BSOD seen was at around 10:00 this morning (may have been earlier as the machine was found with a blue screen...), the problem I have at the moment is that the PC is not creating dump files - I have checked the settings (screen shot included) but it still won't create them.I have uploaded the output of the utilities as per the 'BSOD Assistance' posting?
I've tried to have a dump file generated on crash but it's not getting written. I followed the following page to set up how Windows would create my dump files:
Dump Files - Configure Windows to Create on BSOD
I had a few crashes of different types - photos attached. I also attached the zip file as per instructions from here: [URL]
For about a week I've been experiencing random BSODs, after about 4 months of stable performance. There are no recent hardware or software changes that I'm aware of. The crashes are truly random, sometimes it will go 2 days without a crash, and then the next day I will get 2 or 3 crashes in an hour. It doesn't seem to correlate with a particular program or device attached. For some reason, my System Restore had been turned off so I have no way of restoring to an earlier point prior before the crashes. I do however backup the system regularly with Acronis Backup, and if I can't solve this I'll have to restore to a prior Acronis backup.Here is my OS info (for full system specs click on My System Specs at bottom left of post):
- x64 - the original installed OS on the system? NO. - Full retail version (Ultimate) - What is the age of system (hardware)? LESS THAN 6 MONTHS. - What is the age of OS installation (have you re-installed the OS?) LESS THAN 6 MONTHS.
These BSODs dont let Windows finish to create a dump file...as you can see in the pictures, it always hangs in the "Initializing disk for crash dump..." and then reboots. Only one time it finished, and it was something related to Ready Boost (which was never used or allowed to be used in the system, so I am considering this as not related to the problem...I already looked for BSODs related to Ready Boost, and it came in no help). So, since the Windows dont make a dump file, I am afraid the dump files collected from your "tool" are not related to this problem. I also believe that the Bluethoot devices listed as problematic in the diagnostic tools are not related to the problem also, since I almost never use any bluethoot device with my PC.After the system reboots from the BSODs it looks like the BIOS is weird, it usually says that "no operational system was detected", so I have to turn off the PC and then wait some time and turn it on again, and usually this makes the BIOS "see" the Windows again (sometimes I have to unplug the power cable and wait until all the LEDs are off). Just a couple of times the messages were different, like "The CPU could not be overclocked" opening another BIOS screen from American Megatrends.
These BSODs usually started just after I opened Firefox...my Firefox is with a little problem at the first start up...it starts to consume 25% of my CPU and hangs...I have to kill the firefox process and then open it back again to use it (the second time it loads fine)...if I didnt I would have gotten an BSOD in just a few seconds. This happened in a few other programs too, but randomly, first the process hangs, then the entire system and then the BSOD cames. Almost all the BSODs had no usefull data on them as you can see in the pictures.But since Firefox is a memory hog and some times I got KERNEL_IN_PAGE_ERROR and KERNEL_IN_MEMORY_ERROR (I dont have that picture I think), I started to believe that the problem may be in the RAM timings, or some other RAM related problem...Now with these new Ram timings I let firefox consume 25% of my CPU, at the first start of firefox, for minutes, and the system doesn't crash anymore. Also the only 2 times Firefox had set an BSOD it came with a message from Windows before, saying that "Instruction 0x123456 (i dont know the number :P) could not be read" and then it crashed explorer.exe and then the computer crashed. As I said, it's more stable, but still not "stable".
So this is my second distinct BSOD in the last while. I turned on driver verifier to investigate the first BSOD problem because minidump files arent being created even after turning on small memory dumps (kernel dumps dont show up either). So this new BSOD appears immediately when the starting windows screen appears.
Ive attached the ntbtlog.txt file which was created through the enable boot logging option.
I have attached the collected dump files and perfmon report. Also included is a pic of the specific BSOD, and a screen dump of his system specs.- x86 (32-bit) or x64 ? X64- the original installed OS on the system? yes it is- an OEM or full retail version? OEM- What is the age of system (hardware)? Less than 12 months- What is the age of OS installation (have you re-installed the OS?) PreinstalledThere seemed to be some indication of ATI involvement in the crashes, so I have tried updating the ATI drivers, but the problem continues - perhaps once a week the system will freeze, mouse pointer can still be moved but nothing can be clicked onEventually it restarts with the DRIVER_POWER_STATE_FAILURE BSOD.
I often get random BSOD's when copying files to an external USB device. I haven't been able to tell what's triggering them. It can be a large group of files or sometimes even smaller files, so don't know if it's related to file size Am unfamilar with troubleshooting BSOD's.
System build 11 months ago Windows 7 Pro x64 Full Retail AMD Phenom II X6 1090T ASUS M4A88T-V EVO/USB3 (AM3) 16.0 GB Dual-Channel DDR3 @ 666MHz (9-9-9-24) AMD Radeon HD 6950 250GB M4-CT256M4SSD2 ATA Device (SATA-SSD) (OS) 1954GB SAMSUNG SAMSUNG HD204UI ATA Device (SATA) 1954GB SAMSUNG SAMSUNG HD204UI ATA Device (SATA)
I get BSOD sometimes when playing Battlefield 3, sometimes I don't get it. I also get BSOD when transferring large files from external hard drives or from my internal network.
been awhile since i been here but im back sadly and worried...So ima explain best i can what i did that maybe caused the BSOD. First off my cpu is OC but barely and no voltage changes and has been that way for 3 or so months. By default it runs at 3.8Ghz and i just OC it to 4.0Ghz and its been running that way fine for months and its made to be OC way more so i highly doubt its that. 2nd. I do have dameon tools and i see alot of ppl say that can cause it but again, its been on pc 4 ever and never had no issues with it and it rarely gets used but it still does get used here and there.3rd. I installed some codecs yesterday to try to get sony vegas to read a video and i probably installed 3 different codecs and some were named the same and it was the coded for a h264 or something like that, i already uninstalled that.
4th. No major changes have been made to pc, no recent windows updates, program installs or nothing has been done. Only thing i did most recently yesterday was upgraded a widget for reading GPU and its called GPU meter.5th. Finally and im scared this might be the issue is i noticed on sony vegas ( video editing program ) that it likes to max out all my cores and i noticed the temps reached 90-94 on my cpu which really scared me but ive only used this program twice but i was thinking maybe it was damaging my cpu but not sure.The last thing i was doing when it BSOD was i had a video uploading to facebook and firefox was open and a little dialoge box telling me how far video was done and apparently it got finished and i went to get drink and came back and BSOD was up and the pc didnt auto restart like it did before, had to force shutdown and restart.
This printer worked fine with Windows 7 beta and using the 64bit Vista driver and Windows 7 RC using the ms catalog driver, but now I have the official Windows 7 it just won't work
I either get an error 0x00000007a popup, or noting happens at all (would expect something to appear in the print spooler but nothing does).
Anyone else using this printer and seeing a similar problem?
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 just intalled nTune 5.05.54.00 and when I accept the agreement to use the performance tab in the control panel I get a BSOD every time. Is there a work around or another version that works with the RC?
My sscreen goes black every time I play a game , can't tell at how much time but happens frequently. I'm attaching the diagnosis of the ""dxdiag"" report. Check it out.
I have a few questions about disk clean up. First I run it and check off all of the options including dump and debug files which are both listed at 662 mb. When it's done deleting the files I run it again only to find that the debug and dump files are both still at 662 mb. Is there anything I can do to delete them? Is there an easy way to make those thumbnails come back or should I just not delete them?
Been having some crashes.At first they occurred on start up. Claiming the computer wasn't properly shut down. Now today, the other crashes started, with the first happening out of nowhere, the second happening upon starting a video game. I've been without crashes for a while now, only having used my browser(Opera) and copying some files to an external hard drive. As well as the SF tool.I only have 2 dump files available. SF tool file should be in attachments, unless I made a mistake somewhere
I am experiencing some problems with my WINDOWS 7 64bit system, it begun last night by FREEZING at random (e.g. surfing web, watching videos or playing games) fallowed by the all mighty windows BLUE SCREEN. I tired to view the minidump files using Win-Dbg but there is some problem with the SYMBOLS reading.......I can roll back my OS with SYSTEM RESTORE but......
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 computer gets a blue screen after an few minutes. it crashes faster if i open a programm. the message of the blue screen is: a problem has been detected and windows has been shut down to prevent damage to your computer.
My W7 64 bit PC has BSOD'd twice in the last week. I am just learning this fascinating part of computers and am still very much in the dark, however I made sure that my OS was configured to create a dump file, and it was however there is nothing in the Minidump folder, as a matter of fact it doesnt exist. So much fro configuring the OS to create a dump file on a crash.I DL'd Bluescreenview and it showed nothing.The message at the bottom of the BSOD mentioned something about creating crash dump files but it seemed that nothing happened, there was no progress indicator, just a whole bunch of nothing. I left it for some time to see if the message or anything changed and it didnt. I restarted the PC and went hunting for the Minidump report, or any report for that matter.
Microsoft Windows 7 Home Premium Edition (64-bit).Model p6350 - Memory 6 GB - AMD Athlon(tm) II X2 250 Processor.I have 7-zip to try to open someones dump file and I get this message.Can not open file (name of file)' as archive.I made exception in Firewall and Anti Virus. I need something to be able to open someones dump file but I can't figure out what's needed.I have this next part as written but I don't see why that should matter when i'm trying to read someone's dump file - .dmpIn the Control Panel - System Icon - Advanced System Settings - Startup and Recovery - Settings - Write an event to the system log - Small memory dump - %SystemRoot%Minidump
