I have a Lenovo u410 Ultrabook with an odd problem that began 3-4 months ago that I've been unable to resolve.
Whenever the laptop resumes from sleep mode it forces a complete restart and fails to create a dump file. I have verified that windows is set to create dump files and if I force a crash in some other way I will get a dump file but when it crashes when trying to resume my minidumps folder remains empty.
As far as I can tell it enters sleep mode fine and it's not until it tries to resume that the reboot is triggered. When the problem began I was on Windows 8 and since then have upgraded to 8.1 ... The laptop was able to sleep normally for the first 2-3 months I had it.
Things I have tried so far:
-Installing all the official drivers from the Lenovo support website. - Running system file checker. -Running the Microsoft Safety Scanner. -Sleeping with no peripheral devices connected, tried both while running on AC and battery. -Removing and re-seating the memory. -Refreshing windows (I haven't tried a complete reset yet, hoping to avoid that if I can).
In event viewer I get the following error and critical event each time after it reboots:
Error: The previous system shutdown at <time> on <date> was unexpected.Critical: The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.There are no other warnings, errors, critical entries.
I am attaching the results of the "Grab All" in the SF Diagnostic Tool right after a reboot. Other than sleep mode not functioning the laptop appears to be running normally without any problems.
i have done a fresh install a couple weeks ago and have just been enduring this constant crash but it generally occurs after pc has gone to standby/sleep overnight and i see it when i return to the PC in the morning.
PC specs: Windows 8.1 x64 2x 8 gb Ballistix DDr-1600 ASrock Z87 Pro3 AMD Radeon HD 6800 Series 2x Samsung SSD 120gb 840 EVO
My computer randomly crash when i sleep the computer. normally, it should sleep and the power light should be off in 30 seconds, but when it crash, it takes 5 minutes and finally the computer shutdown instead of sleeping.
And the problem is... i can't have the screenshot of my bluescreen because it always happened when the screen is off....
if i opened memory.dmp with windbg ,it sayd "memory corruption"..... Here is my debug file generated by SF, i opened it with windbg(64 bit) and it says "Probably caused by : ntoskrnl.exe ( nt+5a440 )" it seems a system application ,how could i solve it?
I bought my Sony VAIO flip on 12 Feb this year. At the beginning of April it started frequently crashing (a few times a day when using it on my commute and in the evening). It (almost) always crashes with a BSOD, but no error code, and no crash dump generated. About a quarter of the time, upon restarting from the crash, its says "Couldn't start Windows. Internal SSD not found". I'd keep restarting it and it would fail to start with the same error. If I leave it for a while (30 mins+), it restarts fine, until the next crash.
Given the 'SSD not found' errors, I had assumed it was a hardware fault with the drive failing intermittently. This would also explain the lack of crash dumps if the drive had issues and Windows couldn't write to it. However, I've read around and found some SSDs displaying this behaviour after a crash due to unexpected power loss to the drive, so I'm now wondering if this is a symptom not a cause.
Furthermore, windows restore does show windows updated some drivers at the beginning of April when the crashes started.
I did have one crash with and error code and a dump (24th April) but this is the exception. From the event log (occurrences of id 41 "The system has rebooted without cleanly shutting down first") I can see crashes a few times a day every day I've used the computer in April:
My system(HP pav-g6) is dual booted with win7 and win 8.1 I have installed all recommended drivers from HP and done all windows updates. I crash trying to wake from sleep. In win 7 this problem does not occur. Check disk, seatools, & memtest have already been completed with all passes.
I am trying to debug some crash dumps which all point to NTOSKRNL.EXE but I am unable to debug or even analyze it because the WinDBG throws me an error :-
Code: ************* Symbol Path validation summary **************Response Time (ms) LocationOK C:symbols Symbol search path is: C:symbols Executable search path is: C:symbols Unable to load image SystemRootsystem32 toskrnl.exe, Win32 error 0n2*** WARNING: Unable to verify timestamp for ntoskrnl.exe*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Now, I am unable to understand what is the reason behind this even after much browsing. Also, the symbols are downloaded and saved in C:/Symbols. I am sure that these are working because some DUMP files which do not point to NTOSKRNL get debugged fine.
Also, one more issue I am facing that whenever I have to open another crash dump file immediately after closing one, the option for opening the Crash Dump gets greyed out -_-' . The only way to open another DUMP file is via closing and opening workspace and everything again?
I usually boot my machine in the morning, use it for a bit and then leave for work. After a time, the machine goes to sleep. About 5 or 6 hours latter, WMC wakes the machine to record a TV show. The recording never happens. When I get home, the machine is one but unresponsive with no display. The power button does not shut the machine down. I have to long hold the power button to kill the machine. In addition, if the machine sleeps for a shorter period and I wake it with the mouse, it crashes and restarts. I had to look at a log to find out that the machine restarted because, again, no display.
What I've done: Updated the BIOS sfc /scannow (revealed errors) ... /RestoreHealth (fixed errors) Drive and memory diagnostics Checked my problem against this forum which revealed other crash at wake threads but I'm not able to interpret the log file...
my hp pavilion dv6 6514nr sleeps when i close the lid and anytime i try to open it up it it crashes with the BSOD: system thread exception not handled screen i tried using blue screen view to read the dump files but it showed me it had something to do with ntoskrnl.exe
Blue screen of death after installing comme view for wifi, issue - Microsoft Community
i installed software (comm view for wifi) but after that my pc is going to blue screen of death ,after that i unistalled the app but i see its look like comme view for wifi changed my wirless adaptor name to another name and my pc again its going to blue screen of death...
yesterday i was think that comme view for wifi not was unistalled complitly and i installed comme view for wifi again and deleted with software (perfect unistaller) but after that i see this new problems in my windows... many of my app is not showing but files of app still in c:/program files....
recycle bin folder is gone
change pc option is not opening
when i install new programs not coming with apps
i decided to refresh my pc after that most problem was fixed but i got diffrent bsod
the bsod came while i downloading big files like 100 mb from internet
I recently had a crash on my system while updating my ATI Radeon HD 5450 graphics card.
This occurred yesterday while updating to Catalyst v13.1, released on Jan 17 2013. Once I start the install, at around mid installation the BSOD appears and restarts my computer. I have since then done a clean install of Windows 8 Pro and it keeps appearing every time I try to update my graphics card. I've had this card for about a year now and with no problems until now.
The crash dump file appears in c:/windows/minidump
PC SPECS: Gateway DX Windows 8 Pro 64bit AMD Athlon X2 Dual Core 2.7Ghz 6GB DDR2 ATI Radeon HD 5450 1GB 640GB HDD Dump Files View attachment 011913-13743-01.dmp View attachment 011913-29000-01.dmp
Every time i open my notebook for example when i arrive at home,my notebook welcomes me with that error. but after this i can work on notebook , browse, and anything you can do without experiencing any error.
My notebook is: Acer aspire 5742G 4GB ram DDR3 Geforce GT540M (1GB) Intel Core i5 500GB HDD
I was going through doing a disk cleanup and ran across the options to delete "Debug Dump Files" and System error memory dump files" boh of wich hold 758MB ...are these safe to delete during disk cleanup or should I leave them alone?
This pops up sometimes on the desktop after I power on
Your PC RAN into a problem: C:WindowsMinidump-40214-46000-01.dmp C:WindowsMEMORY.DMP C:UsersUserAppDataLocalTempWER-104406-0.sysdata.xml
It asked me to send details to windows and I sent. I don't know what's the problem and these are the only other problems I experienced: 1)Slower cold booting 2)It takes a longer time for the lights to off after shutting down. We can only turn the switch off after the lights off
Recent PC activities: 1) Defragmentation for OS(C) and Data(D) 2) Installed and played The Sims 3 (usage is around 9GB) with Mods 3) OS(C) Disk Cleanup deleted items: Downloaded Program files, Temporary Internet files and Temporary files (not sure if I deleted System Error Memory Dump Files & System Error Minidump Files or not)
I have recently installed fresh Windows 8 on my laptop - HP 6735b. Installation went smooth, it has installed all the drievers on his own, I just installed few more applications and within few days, problems appeared. I'm getting BSOD on startup, but sometimes it starts normaly and after few minutes/hours - BSOD appears.
I have begun experiencing BSOD frequently but the system does not leave a dump file even though it is configured for that and has the page file enabled with more than adequate memory allotted. I'm attaching the file for review and comment.
Recently I built my first gaming PC and I have started having occasional BSOD's when gaming. Here are my specs.
RAM = Crucilal Ballistix 8GB kit 1600 2 x 4GB GPU = Sapphire HD 7970 CPU = intel i5 4670k Motherboard = Asus Z87 A HDD = Western Digital Blue 1TB SSD = Samsung Evo 120GB CPU Cooler = Hyper 212 EVO Processor Cooler PSU = Corsair CX750M Optical Drive = LiteOn IHOS104 4x BD-ROM SATA Blu-Ray
The errors that appear when my PC restarts are to do with memory dumping.
I am using an ASUS K55N laptop, equipped with an AMD A8-4500M APU, 4GB single-channel RAM, and of course, Windows 8 standard x64.
Occasionally, anywhere from an hour to three days after a boot-up, the computer will hang while in sleep mode (screen will be off but indicator lights will remain on for about 5 minutes in sleep mode) and shut off. Upon restarting, I'll be greeted by a "Your PC ran into a problem and had to restart" Windows prompt. Of course, a minidump will also be produced. However, there is no BSOD anywhere to be found.
Upon looking into these dump files with WinDbg, all of them point toward my Atheros AR9485 wireless card's driver; either athw8x.sys or athrx.sys depending on the driver I was using at the time. I have tried several Atheros drivers, to no avail. I have tried using new drivers, old drivers, Windows 7 drivers, you name it. At this moment, I am using a Windows 7 driver. Yet, it has not solved the issue.
Verifier is disabled, although I believe my issue can be attributed to debugging. I have literally tried everything and it persists.
I keep getting a Mini dump Error, tried to copy n paste it, wouldn't allow, then took screenshot, and lost it - so next time it happens i`ll edit and upload it - in mean time here is my reports, hope rar is ok....
For the past few weeks I have been experiencing random, albeit infrequent, BSOD's.
1. Occurred while using Thunderbird 2. Occurred while using Firefox 3. Occurred while playing Dota 2
I had several processes open behind the programs listed.
What tends to happen is that the mouse and/or keyboard stops working before the computer crashes. Then it stalls at the Bios screen and will not boot up without a restart.
A few things: 1. The CPU is overclocked, but the overclock was working well on prior installations. The other systems used MBR as opposed to GPT which the current system uses. (Don't know if this matters). 2. I made a few changes to the system settings to try and optimize my SSD (see: The SSD Optimization Guide Redesigned | The SSD Review and SSD tweaker)
So for the past 8 days I've been getting BSOD's (Kernel Data Inpage Error) randomly about once a day, without any dumps or logs being created, despite the settings being right and WERS service running.
Two weeks ago my 2 year old SSD (Corsair Force GT) died. Bios would freeze at around 70% when trying to boot off it, other computers wouldn't recognize it, it was basically bricked (i suspect the controller, since I only had it for 2 years, and only used for OS). So I sent it back, and they ended up giving me a different model (Corsair Force GS).
I performed a fresh install of Windows 8.1 Pro x64 on the new SSD, and ever since then I've been having the BSOD's. At first I suspected a driver problem, but Windows says all drivers are up to date and there's another weird thing happening: after the BSOD, when restarts and tries to boot up again, the BIOS freezes at around 70% again (around the time when it communicates with the default boot device), and I have to manually shut it down (from the power button), and turn it back on again(this time it works fine, and writes the 'Event 41, Kernel Power' event to logs).
I suspect it's the SSD again, but I can't explain it. It's been driving me crazy for the past week, especially since I also use this laptop (Acer Aspire 5737z) for work.
I got an excellent deal on an SSD (it's hard to beat free ;D ). It's incredibly small is the only problem, however. Only 32GB's. Anyways I installed windows on it, and before I've even entered the setup, I went back into the install CD, open command prompt and robocopied the Users and Program Files (x86) to my 2TB HDD. But now I have a problem...
In windows 7 you could have easily moved the 'Program Files' and 'ProgramData' directories over to another HDD and it would have worked just fine. However, the metro protection crap on Windows 8 forbids you from doing this... Well I mean you could, but it would result in no windows updates (updates will always fail) and Metro apps will fail to start and will not install. So I HAVE to keep the existing files inside the program files/programdata located on the boot drive.
If I had a larger SSD, this wouldn't really be a problem, however because mine is so small, there no room for any new information on that drive once windows is installed. However, I still want to receive updates and use metro apps. So my question is...
how to keep existing files on a partition, but then create a link to a different Volumw that any new directories will be written to?
I've installed win 8 consumer release not long ago, and the windows keep crash from time to time with and says to search for dpc watchdog violation for more info.
Aafter the PC is restarting it says that the problem was with memory.dmp.
At the beginning it happened once in a few weeks so I didn't care but now it happens more often which in not good! before the crash itself happens the PC freeze and make some weird buzz-like sound, sometime it keeps working after but sometime it crash.
I have now tried several times to create a second user on my new build, and every time I get the BSOD about 10-15 seconds after signing in as the new user. I get the message BAD_POOL_CALLER or BAD_POOL_HEADER. I already tried uninstalling AVAST as I read it created issues for some people, but that didn't change anything. My system works perfectly as long as I am signed in under my own user account, but as soon as I try a different user, I get the BSOD. I attached the minidump files that were created during the multiple times I tried to log in as a new user.
Here is what I wanted to do: right click in File Explorer on a local disk, so I can share it, so I can access that drive from my laptop. Attached a picture, I want to share "Local Disk (E:)", underlined with red, with my mad paint skills. You can see a snippet from my task bar as well, it is important.
Here is the problem: after right clicking, the OS seems to think about 1-2 seconds, then it closes the File Explorer, then kills my task bar, every icon disappears for a few seconds, then everything loads back, tho File Explorer won't open again automatically. Back in Windows7 and XP etc. days this was typically something like an "explorer.exe" crash. Attached another picture, how my taskbar looks exactly, at the moment of restarting. Note: the taskbar flashes before reappearing - still without icons - with dark blue color for a brief moment, then it loads my icons, as I mentioned above. Dark blue is the color of my "Start screen", or however it is officialy called, not sure. The pic:
Also, you can see at the right side, the clock does not show as well.
My setup is like this: I have a 500GB hard drive: C: is the system partition, D: is the data partition. E: is a completely separate 320GB hard drive, another data partition. I have a fully legal Windows 8 Professional, with updates installed(perfectly up to date, I just did an update check, everything is installed) provided by MSDNAA (or Dreamspark nowadays, if I am right) for university students. Every hardware works good, so something went wrong with Windows 8. I am not completly sure, but I think I could right click the drives a while ago, it started just now. Also, I can right click everything else without error, just not the disks. I don't want to roll back to Windows7, since I really like 8, but if this won't get sorted out, I may have to.
Here is what I did: It was obvious that something 3rd party context menu extension (shell extension) caused the problem. I did try to disable extensions 1 by 1, to see if it solves it. Finally, disabling "NVIDIA CPL Context Menu Extension" solved my problem.
I Just installed a fresh windows 8 on my computer and it worked fine until I installed the nvidia drivers. Without nvidia drivers it works fine, but after installing it it starts to freeze and crash. After I remove the nvidia driver is it works fine again. I tried the newest and the older nvidia drivers but none of them were stable. The symtopms are different each time. Sometimes BSOD sometimes some part of graphics on the screen goes pink sometimes the screen blacks out and does not return until I hard reset it.