BSOD After Awaking from Sleep

[jeffreyabr]

I am running window 7 ultimate 64bit on my dell vostro 1520. recently, i have shut my laptop only to open it to a BSOD after it loads the login screen. it then restarts and says nothing about having crashed. only once has it restarted asking if i wanted to try and boot from that resume data or delete it and start again. I looked to this thread for reference:

http://www.sevenforums.com/crashes-debugging/9658-x64-bsod-after-sleep.html

but when I tried to get a minidump after a crash there was nothing in the folder when i rebooted. Do I need to start the computer in safe mode to get it or should I be fine booting up regularly? Is there something else that I should be doing?

 

[Capt.Jack Sparrow]

I am running window 7 ultimate 64bit on my dell vostro 1520. recently, i have shut my laptop only to open it to a BSOD after it loads the login screen. it then restarts and says nothing about having crashed. only once has it restarted asking if i wanted to try and boot from that resume data or delete it and start again. I looked to this thread for reference:

http://www.sevenforums.com/crashes-debugging/9658-x64-bsod-after-sleep.html

but when I tried to get a minidump after a crash there was nothing in the folder when i rebooted. Do I need to start the computer in safe mode to get it or should I be fine booting up regularly? Is there something else that I should be doing?

Hello,

Lets enable the MiniDump

1. Click Start, point to Settings, and then click Control Panel.
2. Double-click System.
3. Click the Advanced tab, and then click Settings under Startup and Recovery.
4. In the Write debugging information list, click Small memory dump (64k).
   
   To change the folder location for the small memory dump files, type a new path in the Dump File box

The follow this link to post dump file http://www.sevenforums.com/crash-lockup-debug-how/34900-1-novice-how-ask-help-bsod-problem.html

Hope this helps,
Captain

 

[jeffreyabr]

Thanks Captain. I will upload a minidump when it happens next.

 

[jeffreyabr]

I must be doing something wrong or have some setting incorrect because I have had two different crashes and no minidump files created.

The first crash occurred when I simply started scrolling down a new page in Firefox. My screen went black and the laptop began to reboot. There was no blue screen, just black.

The second one was a BSOD. I had closed my laptop with firefox and word open and came back maybe an hour later. The power LED was still blinking, so it hadn't gone into hibernate yet. When I opened my laptop, the login screen loaded fully for maybe two seconds, but before I could sit down the BSOD flashed on the screen and my computer began to reboot.

What's weird is that my machine doesn't seem to realize that it's crashed when it reboots. There is no Windows message that pops up upon restart that says it will send Microsoft an error message or anything. This whole thing started maybe three days ago, and I haven't installed anything new since then. I have run multiple virus scans with AVG Free and a Chkdsk, but these didn't solve it.

 

[jeffreyabr]

Should I be doing this a different way? Is there another place I should be looking for it? I am in C:\Windows\Minidump which matches the directory that's told in the Small dump Directory. I see that it should also be writing an event to the system log, is there a place I can access that and post that?

 

[Capt.Jack Sparrow]

OK Run this Tool http://www.sevenforums.com/crash-lockup-debug-how/66913-sf-diagnostic-tool.html#post596666 and post us the results. Make sure you right click and Run as administrator !!

- Captain

 

[jeffreyabr]

Here is a copy of the Event Log on my computer.

 

[jeffreyabr]

And here's the SF Diagnostic Tool output.

 

[jeffreyabr]

Can you find anything in either of those two which reveals the issue?

 

[Capt.Jack Sparrow]

And here's the SF Diagnostic Tool output.

Hello,

Lot of issues actually. Here is the Logs what it says

Old Drivers

adfs         adfs                   Kernel        11/3/2008 11:48:14 AM 
adp94xx      adp94xx                Kernel        12/5/2008 6:54:42 PM 
adpahci      adpahci                Kernel        5/1/2007 1:30:09 PM   
adpu320      adpu320                Kernel        2/27/2007 7:04:15 PM 
arc          arc                    Kernel        5/24/2007 5:27:55 PM 
BrFiltLo     Brother USB Mass-Stora Kernel        8/6/2006 9:51:06 PM
ebdrv        Broadcom NetXtreme II  Kernel        12/31/2008 11:29:28 AM
LSI_FC       LSI_FC                 Kernel        12/9/2008 5:46:09 PM 
nfrd960      nfrd960                Kernel        6/6/2006 5:11:48 PM 
OEM13Vfx     Creative Camera OEM013 Kernel        3/5/2007 5:55:47 AM   
OEM13Vid     Creative Camera OEM013 Kernel        5/28/2008 9:19:21 PM  
pcouffin     VSO Software pcouffin  Kernel        12/5/2006 9:39:30 AM  
PxHlpa64     PxHlpa64               Kernel        12/10/2007 6:49:01 PM 
SMSIVZAM5X64 SMSIVZAM5X64 NDIS Prot Kernel        10/7/2008 12:56:59 PM 
SiSRaid2     SiSRaid2               Kernel        9/24/2008 2:28:20 PM  
SiSRaid4     SiSRaid4               Kernel        10/1/2008 5:56:04 PM 
SynTP        Synaptics TouchPad Dri Kernel        6/20/2008 7:06:00 PM
usbbus       LGE CDMA Composite USB Kernel        11/11/2008 4:15:45 AM 
USBModem     LGE CDMA USB Modem     Kernel        11/11/2008 4:16:17 AM

Make sure you find the most updated drivers for the above list.

Device that can cause problem

Mass Storage Controller PCI\VEN_1217&DEV_8130&SUBSYS_02BC1028&REV_01\4&12BF0147&0&02E4  The drivers for this device are not installed.

I guess it's some USB drive or External HDD might also has issues. There is no proper drivers installed.

Event Viewer Log


Installation of the Proof of Purchase failed. 0xC004F015
Partial Pkey=Y8QH3
ACID=bfb30674-7c9a-4624-9309-9914cfd5b05c
Detailed Error[?]

Info from Genuine Windows Blog - The Windows Blog

Using KMS in Windows 7 or Windows Server 2008 R2 deployments

One of the more common questions that we are hearing about volume activation today is around how to update your existing Key Management Service (KMS) to support Windows 7 and/or Windows Server 2008 R2. This is also causing some customers issues as they attempt to use the new keys that are available on the Volume License Service Center and get a 0xC004f050 or 0xC004F015 errors, as shown here:

​

Why is this happening, and how can it be resolved?
With each release of Windows, Microsoft will issue new product keys. This is true for volume license customers as well. In order for this key to be recognized on an earlier release of Windows, it is necessary to update the license files that are used by the software license service. This is easy to do and only takes a little time to accomplish.
KMS hosted on Windows Server 2003
If you are hosting the KMS on Windows Server 2003 today, you are probably running the version 1.1 that supports both Windows Vista and Windows Server 2008 KMS keys and clients. In order to add support for Windows 7 and Windows Server 2008 R2, you’ll need to install the update found in KB 968195. The steps to install are clearly defined in the KB. Don’t forget to restart the service after the update is installed. This is a very important step because the license files won’t be installed until after the reboot. Read Updating KMS on Windows Server 2003 to support Windows 7 and Windows Server 2008 R2 for additional information.
After the update is installed (and the system is restarted), you can install the new KMS host key (for Windows 7 or Windows Server 2008 R2) using slmgr.vbs /ipk, and then activate the service using slmgr.vbs /ato. The DNS records will be refreshed and the count on the KMS host is maintained. The entire process is transparent to the KMS client systems.
KMS hosted on Windows Server 2008 (and Windows Vista)
A similar update exists for Windows Server 2008. KB 968912 has the update and clearly defined steps to follow to update the KMS host. After the update is installed (and the system is restarted), you can install the new KMS host key (for Windows 7 or Windows Server 2008 R2) using slmgr.vbs /ipk, and then activate the service using slmgr.vbs /ato. The DNS records will be refreshed and the count is maintained.
Keep in mind that the most common issue that customers are having while resolving the above is that they do not restart the system before attempting to install the new KMS host key. Without the restart, the new key will not be recognized and you will get the same error I mentioned at the beginning of the blog (0xC004F015).

Hope this helps,
Captain

 

[jeffreyabr]

OK I will go and try to download those drivers. What's the best method, just googling the names like "adfs" and "adpu320" or is there a better way?

As for the mass storage controller issue, back in like October I had an issue with my hard drive and trying to usea program called DriveImage XML to restore an image of my OS. You can see it here (I am joefuf):

(Solved) - VistaPE and DriveImage XML How-To Geek Forums

And what I accidentally did at one point was format the extra HDD in my laptop that I think is there for holding the emergency copies of programs and stuff. I didn't really have an issue when I finally relented and installed Windows 7 (if you didn't read the thread on How-To-Geek, my machine came as Vista) so I just let it be undetected. Didn't think it mattered, but if you know otherwise let me know. I'll be home on break tomorrow so I can have an IT guy look at it and help me if necessary.

As for the issue on Proof of Purchase, what exactly do I need to do? Is it just straightforward like what you have copied from that blog? I had a feeling that this was the issue when I was tracing back through the event log and saw that and remembered a Lifehacker article I recently read (Sunday Last Day for Windows 7 RC, But Upgrading Is Easy - windows 7 - Lifehacker).

I'm sure you can guess what the status of my windows copy is, but will following the steps you have lain out leave my machine useless and make it unable for meto log in and use it?

 

[jeffreyabr]

After trying to install both KB 968195 and KB 968912 I get the error that "The update is not applicable to your computer."