BSOD at Shutdown and Restart - Alienware m14x R2

[mwr1113]

I have been dealing with this issue for nearly a year. I have done multiple re-installations of Windows 7, I have spoken to Alienware support who sent me a new hard drive thinking that was the issue... That was about 6 months or so ago and I'm now getting corruption messages for files on the new HD.

The bsod occurs when I try to shut down or restart the computer. It is a power state failure. I have run a bluescreen viewer program and was shown it's being caused by ntoskrnl.exe. I've attached all the information you may need to this email. Let me know if you need something I didn't include.

I reinstalled windows in February... I've started getting the bsod again after 2 months. I'm considering installing Windows 10 to see if that will fix it, but do not have much hope. I've updated drivers, but not sure if I've hit them all. Went to Dell, where I purchased the computer and updated what drivers they suggested.

Any help will be appreciated. Nothing I have done seems to fix the problem. I'm computer savvy, but not an expert by any stretch. I'm about ready to throw this computer through a window.

 

[SickOfTheBSOD]

I'm not having the same BSOD problems as you but I've also used BlueScreen View to diagnose BSODs on my A-Ware PC. It also reads that there is a problem with "ntoskrnl.exe", so perhaps this is just BSV's way of saying:

"I don't know what the problem is".

Just thought I'd mention that.

Have you tried WhoCrashed? Might get better results.

 

[mwr1113]

I'm not having the same BSOD problems as you but I've also used BlueScreen View to diagnose BSODs on my A-Ware PC. It also reads that there is a problem with "ntoskrnl.exe", so perhaps this is just BSV's way of saying:

"I don't know what the problem is".

Just thought I'd mention that.

Have you tried WhoCrashed? Might get better results.

No I haven't but I will... thanks for the suggestion!

 

[axe0]

Ntoskrnl.exe is the Windows kernel, never the cause as it is being marked as the cause by default when nothing else is available to blame.

There haven't been BSODs since 2 months according to the logs.
Configure your system to NOT restart when a BSOD occurs to ensure that you can verify it saves a dump succesful.
http://www.sevenforums.com/tutorials/174459-dump-files-configure-windows-create-bsod.html
View attachment 385506

 

[mwr1113]

It does not appear to be saving the .DMP file in the minidump folder under windows, which is where the other files are located. I just did what you suggested above and tried to shutdown. I got the bsod, but when I was able to log in couldn't find the .dmp file after the BSOD.

I'm using BlueScreen Viewer to view the dump files. It says the same... nothing is saving since February, but I just had one again this morning.

 

[axe0]

Bluescreen viewer isn't very reliable to properly find the cause of a dump.

What was the bugcheck? If you can get a picture of the BSOD that would be helpful for troubleshooting.

 

[mwr1113]

Here is the photo of the BSOD I just encountered.

 

[axe0]

Again no dump has saved I assume?

 

[mwr1113]

Correct... I checked C:/Windows/Minidump where the Feb files are located and nothing new saved.

 

[axe0]

Please remove all USB devices + update the USB drivers provided by Dell, from experience is this crash a lot being caused by USB related things (USB devices, USB ports, USB drivers).