Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

BSOD DRIVER_POWER_STATE_FAILURE (9f)


  • This topic is locked This topic is locked
21 replies to this topic

#1 greenslam

greenslam

  • Members
  • 41 posts
  • OFFLINE
  •  
  • Local time:01:13 AM

Posted 24 February 2012 - 12:43 PM

Hi all,

I am getting an annoying BSOD. I do have an unrecognized device in my device manager under the usb portion. I only have a mouse plugged into my usb slots. When I unplugged and rescanned it, the unknown device was still there. Please take a look at the info provided.

FYI, when I try to logoff/restart, the computer hangs until I shut it down the hard ware.

I have recently ran a OS repair and didn't find any issues.

Sfc/ scannow doesn't show any issues either.

rar file of logs

BC AdBot (Login to Remove)

 


#2 LucheLibre

LucheLibre

  • Members
  • 608 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Tennessee
  • Local time:02:13 AM

Posted 24 February 2012 - 03:35 PM

How does the logoff perform in Safe Mode?

Use BlueScreenView (BSV) to provide details about your error messages.

  • Download the .zip file and extract its contents to your desktop.
    Follow these instructions if you are not familiar with how to extract files from a .zip file.
  • On the desktop, double-click BlueScreenView.
  • After BSV completes its scan, click Edit > Select All.
  • Click File > Save Selected Items and save the report to your desktop as BSOD.txt
  • Open BSOD.txt in Notepad and copy/paste all of its content to your next reply.
===========================================

Use Speccy to provide details of your computer's configuration.

  • Download, install, and run.
  • After Speccy has finished gathering information, click File > Publish Snapshot.
  • Click Yes. A web address will be displayed.
  • Click Copy to Clipboard and paste it in your next post.
  • Include your computer's manufacturer and model number, if available.
=========================================

If it looks like I know what I'm doing, there's a pretty good chance the only reason for that is because
I once asked someone to run chkdsk /r and a BC Advisor smacked me in the back of the head.

~ LL ~


#3 greenslam

greenslam
  • Topic Starter

  • Members
  • 41 posts
  • OFFLINE
  •  
  • Local time:01:13 AM

Posted 24 February 2012 - 08:28 PM

speccy info

Now I can't replicate the logoff issues in normal or safe mode.

==================================================
Dump File : 021112-21968-01.dmp
Crash Time : 2/11/2012 7:46:22 PM
Bug Check String : DRIVER_POWER_STATE_FAILURE
Bug Check Code : 0x1000009f
Parameter 1 : 00000000`00000004
Parameter 2 : 00000000`00000258
Parameter 3 : fffffa80`03ce0b60
Parameter 4 : fffff800`00b9c510
Caused By Driver : Ntfs.sys
Caused By Address : Ntfs.sys+2465
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+7f4da
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\021112-21968-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 7601
Dump File Size : 502,464
==================================================Attached File  021112dmp.txt   1.75KB   1 downloads

#4 AustrAlien

AustrAlien

    Inquisitor


  • BC Advisor
  • 6,772 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Cowra NSW Australia
  • Local time:04:13 PM

Posted 25 February 2012 - 06:23 AM

Let's get rid of sptd.sys which is a well known trouble-maker/bsod-maker in Windows 7 systems, and is directly implicated in the two crash dumps from March and May of 2011. See how it is the lower-most driver listed in the crash stack below:

STACK_TEXT: 052511-157515-01.dmp

fffff880`031e6e10 fffff800`02a99f92 : fffffa80`036db040 fffffa80`036db040 00000000`00000000 00000000`00000000 : nt!KiSwapContext+0x7a
fffff880`031e6f50 fffff800`02a9c7af : 00000000`00000000 00000000`00000000 fffff880`00000000 fffff880`031e74e0 : nt!KiCommitThreadWait+0x1d2
fffff880`031e6fe0 fffff880`00d70dd1 : fffffa80`0433a100 00000000`00000000 fffff880`031e7400 fffffa80`0433a100 : nt!KeWaitForSingleObject+0x19f
fffff880`031e7080 fffff880`00d72961 : 00000000`00000000 fffff880`031e74e0 fffff880`00d7da60 00000000`00000000 : storport!RaSendIrpSynchronous+0x71
fffff880`031e70e0 fffff880`00d76191 : 00000000`00000000 fffff880`00000000 fffff880`031e7380 fffff880`031e74e8 : storport!RaidBusEnumeratorIssueSynchronousRequest+0x91
fffff880`031e71f0 fffff880`00d762be : fffffa80`03eb2cf0 fffff880`00000000 fffff880`031e72e0 fffff880`031e7380 : storport!RaidBusEnumeratorIssueReportLuns+0x71
fffff880`031e7240 fffff880`00d7c61b : 00000000`00000000 fffff800`00000000 00000000`00000000 fffff880`031e7380 : storport!RaidBusEnumeratorGetLunListFromTarget+0xae
fffff880`031e72c0 fffff880`00d7c764 : fffff880`031e73e8 fffffa80`00000000 00000000`00000000 00000000`00000000 : storport!RaidBusEnumeratorGetLunList+0x5b
fffff880`031e7350 fffff880`00d7c856 : fffffa80`04523480 00000000`00000001 00000000`00000001 fffffa80`04523480 : storport!RaidAdapterEnumerateBus+0x94
fffff880`031e74c0 fffff880`00dba7f2 : 00000000`00000f00 fffff880`00d63a01 00000000`00000000 00000000`00000000 : storport!RaidAdapterRescanBus+0x76
fffff880`031e75d0 fffff880`00dbaa00 : fffffa80`07b44650 00000000`00000000 fffffa80`04523480 fffffa80`07b44650 : storport!RaidAdapterQueryDeviceRelationsIrp+0xa2
fffff880`031e7610 fffff880`00dbab94 : fffffa80`043b7000 fffff880`00d80110 fffffa80`04523330 fffff880`031e7800 : storport!RaidAdapterPnpIrp+0x150
fffff880`031e7670 fffff880`0110c599 : fffffa80`043b7000 fffffa80`04191307 00000000`00000001 fffffa80`03fc8000 : storport!RaDriverPnpIrp+0x94
fffff880`031e76b0 fffffa80`043b7000 : fffffa80`04191307 00000000`00000001 fffffa80`03fc8000 fffffa80`0371d0c0 : sptd+0x41599
fffff880`031e76b8 fffffa80`04191307 : 00000000`00000001 fffffa80`03fc8000 fffffa80`0371d0c0 00001f80`00000000 : 0xfffffa80`043b7000
fffff880`031e76c0 00000000`00000001 : fffffa80`03fc8000 fffffa80`0371d0c0 00001f80`00000000 fffffa80`0371f8c0 : 0xfffffa80`04191307
fffff880`031e76c8 fffffa80`03fc8000 : fffffa80`0371d0c0 00001f80`00000000 fffffa80`0371f8c0 fffffa80`06081048 : 0x1
fffff880`031e76d0 fffffa80`0371d0c0 : 00001f80`00000000 fffffa80`0371f8c0 fffffa80`06081048 fffffa80`00000000 : 0xfffffa80`03fc8000
fffff880`031e76d8 00001f80`00000000 : fffffa80`0371f8c0 fffffa80`06081048 fffffa80`00000000 fffffa80`0371f930 : 0xfffffa80`0371d0c0
fffff880`031e76e0 fffffa80`0371f8c0 : fffffa80`06081048 fffffa80`00000000 fffffa80`0371f930 00000000`000000ca : 0x1f80`00000000
fffff880`031e76e8 fffffa80`06081048 : fffffa80`00000000 fffffa80`0371f930 00000000`000000ca fffffa80`036db040 : 0xfffffa80`0371f8c0
fffff880`031e76f0 fffffa80`00000000 : fffffa80`0371f930 00000000`000000ca fffffa80`036db040 00000000`00000000 : 0xfffffa80`06081048
fffff880`031e76f8 fffffa80`0371f930 : 00000000`000000ca fffffa80`036db040 00000000`00000000 fffffa80`03fc8001 : 0xfffffa80`00000000
fffff880`031e7700 00000000`000000ca : fffffa80`036db040 00000000`00000000 fffffa80`03fc8001 fffffa80`0371d0c0 : 0xfffffa80`0371f930
fffff880`031e7708 fffffa80`036db040 : 00000000`00000000 fffffa80`03fc8001 fffffa80`0371d0c0 00000000`000000ca : 0xca
fffff880`031e7710 00000000`00000000 : fffffa80`03fc8001 fffffa80`0371d0c0 00000000`000000ca 00000000`00000000 : 0xfffffa80`036db040


sptd.sys is usually associated with the CD/DVD-ROM emulation software Daemon Tools or Alcohol 120%. Do you still have one of these software programs installed (I didn't see evidence of either program still being installed and running)? If so, please uninstall the program in the usual way ... and then check to make sure that the file sptd.sys is no longer present on your system. Unfortunately the sptd.sys file is usually left behind after uninstalling the program, and it needs to be removed manually or using the following method:
  • Download and run the SPTD setup file: http://www.duplexsecure.com/en/downloads

    Note: Running this file will enable you to either uninstall sptd.sys or to install it.
  • Choose to uninstall/remove sptd.sys
When you have done this restart the computer and check that the file sptd.sys is no longer present on your system. One way to verify this is to perform a search for the file (ensure that you use the 64 bit version of SystemLook).
Please download SystemLook.exe and save it to your Desktop.
  • alternate download link
    For users of Windows 64 bit systems: SystemLook (64-bit)
  • Double-click SystemLook.exe to run it.
  • Copy the content of the following code box and paste into the main text field:
    :filefind
    sptd.sys
    
  • Click the Look button to start the scan.
    Please be patient, as it may take a little time.
  • When finished, a Notepad window will open with the results of the scan.
  • Please copy & paste the entire content of this log in your next reply.
Note: The log, SystemLook.txt, is saved on your Desktop.

Let's see what the situation is like after doing that.

Looking at the Event logs, there is a lot of stuff being reported there that doesn't seem quite right ... and may give some clue as to the problem you have reported about the system being reluctant to shut down as it should. But, let's see if you still have the problem after removing sptd.sys.

============================
BSOD BUGCHECK SUMMARY
................................................................
Loading Dump File [C:\CactusIsland\greenslam_BC\Windows_NT6_BSOD_jcgriff2\021112-21968-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Sun Feb 12 12:43:22.865 2012 (UTC + 11:00)
System Uptime: 4 days 2:09:47.162
*** WARNING: Unable to verify timestamp for nvstor.sys
*** ERROR: Module load completed but symbols could not be loaded for nvstor.sys
Probably caused by : nvstor.sys
DRIVER_POWER_STATE_FAILURE (9f)
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x9F
PROCESS_NAME: System
FAILURE_BUCKET_ID: X64_0x9F_4_disk_IMAGE_nvstor.sys
Bugcheck code 1000009F
Arguments 00000000`00000004 00000000`00000258 fffffa80`03ce0b60 fffff800`00b9c510
Identifier = REG_SZ AMD64 Family 16 Model 6 Stepping 2
ProcessorNameString = REG_SZ AMD Athlon™ II X2 250 Processor
BiosVersion = P1.10
BiosReleaseDate = 04/12/2010
BaseBoardManufacturer = ASRock
BaseBoardProduct = N68C-S UCC
................................................................
Loading Dump File [C:\CactusIsland\greenslam_BC\Windows_NT6_BSOD_jcgriff2\020312-151140-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Sat Feb 4 15:33:51.703 2012 (UTC + 11:00)
System Uptime: 2 days 12:05:14.115
*** WARNING: Unable to verify timestamp for nvstor.sys
*** ERROR: Module load completed but symbols could not be loaded for nvstor.sys
Probably caused by : nvstor.sys
DRIVER_POWER_STATE_FAILURE (9f)
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x9F
PROCESS_NAME: System
FAILURE_BUCKET_ID: X64_0x9F_4_disk_IMAGE_nvstor.sys
Bugcheck code 1000009F
Arguments 00000000`00000004 00000000`00000258 fffffa80`03cfc680 fffff800`00ba2740
................................................................
Loading Dump File [C:\CactusIsland\greenslam_BC\Windows_NT6_BSOD_jcgriff2\012412-31953-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Wed Jan 25 06:52:21.028 2012 (UTC + 11:00)
System Uptime: 6 days 20:03:48.396
*** WARNING: Unable to verify timestamp for nvstor.sys
*** ERROR: Module load completed but symbols could not be loaded for nvstor.sys
Probably caused by : nvstor.sys
DRIVER_POWER_STATE_FAILURE (9f)
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x9F
PROCESS_NAME: System
FAILURE_BUCKET_ID: X64_0x9F_4_disk_IMAGE_nvstor.sys
Bugcheck code 1000009F
Arguments 00000000`00000004 00000000`00000258 fffffa80`03ce0b60 fffff800`04191510
................................................................
Loading Dump File [C:\CactusIsland\greenslam_BC\Windows_NT6_BSOD_jcgriff2\061211-148750-01.dmp]
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Mon Jun 13 09:51:02.364 2011 (UTC + 11:00)
System Uptime: 0 days 2:44:06.708
Unable to load image \SystemRoot\system32\DRIVERS\nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+119cf8 )
VIDEO_TDR_FAILURE (116)
DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_TDR_FAULT
BUGCHECK_STR: 0x116
PROCESS_NAME: System
FAILURE_BUCKET_ID: X64_0x116_IMAGE_nvlddmkm.sys
Bugcheck code 00000116
Arguments fffffa80`042e3110 fffff880`0f3dbcf8 00000000`00000000 00000000`00000002
................................................................
Loading Dump File [C:\CactusIsland\greenslam_BC\Windows_NT6_BSOD_jcgriff2\052511-157515-01.dmp]
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Thu May 26 11:51:48.439 2011 (UTC + 11:00)
System Uptime: 2 days 1:18:01.783
Unable to load image \SystemRoot\System32\Drivers\sptd.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for sptd.sys
*** ERROR: Module load completed but symbols could not be loaded for sptd.sys
Probably caused by : storport.sys ( storport!RaSendIrpSynchronous+71 )
DRIVER_POWER_STATE_FAILURE (9f)
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x9F
PROCESS_NAME: System
FAILURE_BUCKET_ID: X64_0x9F_4_storport!RaSendIrpSynchronous+71
Bugcheck code 1000009F
Arguments 00000000`00000004 00000000`00000258 fffffa80`036db040 fffff800`0418c510
................................................................
Loading Dump File [C:\CactusIsland\greenslam_BC\Windows_NT6_BSOD_jcgriff2\030511-21156-01.dmp]
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Sat Mar 5 17:17:30.857 2011 (UTC + 11:00)
System Uptime: 4 days 3:14:46.435
Unable to load image \SystemRoot\System32\Drivers\sptd.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for sptd.sys
*** ERROR: Module load completed but symbols could not be loaded for sptd.sys
Probably caused by : storport.sys ( storport!RaSendIrpSynchronous+71 )
DRIVER_POWER_STATE_FAILURE (9f)
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x9F
PROCESS_NAME: System
FAILURE_BUCKET_ID: X64_0x9F_4_storport!RaSendIrpSynchronous+71
Bugcheck code 1000009F
Arguments 00000000`00000004 00000000`00000258 fffffa80`036f9040 fffff800`04182510
................................................................



BlueScreenView report: total of 6 minidumps
Spoiler

Edited by AustrAlien, 25 February 2012 - 06:29 AM.

AustrAlien
Google is my friend. Make Google your friend too.

Posted Image

#5 jcgriff2

jcgriff2

  • BSOD Kernel Dump Expert
  • 1,052 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:New Jersey Shore
  • Local time:02:13 AM

Posted 25 February 2012 - 07:56 AM

Agree 100% on sptd.sys - it's even named as probable cause.

I see you updated NVIDIA video between BSODs. NVIDIA nForce drivers need to be updated too -
nvlddmkm.sys    Sat Oct 15 02:07:55 2011 (4E99233B)
nvlddmkm.sys    Thu May 14 16:48:07 2009 (4A0C8387)

nvstor.sys      Fri Mar 19 16:45:11 2010 (4BA3E257)
nvm62x64.sys    Fri Oct 17 17:01:06 2008 (48F8FD12)
nvmf6264.sys    Thu Aug 12 07:46:06 2010 (4C63DEFE)

http://sysnative.com/drivers/driver.php?id=nvstor.sys
http://sysnative.com/drivers/driver.php?id=nvmf6264.sys
http://sysnative.com/drivers/driver.php?id=nvm62x64.sys

Regards. . .

jcgriff2


Microsoft MVP 2009-2015

#6 greenslam

greenslam
  • Topic Starter

  • Members
  • 41 posts
  • OFFLINE
  •  
  • Local time:01:13 AM

Posted 25 February 2012 - 06:27 PM

Alright,

I updated my Nvidia drivers to GeForce 295.73 WHQL for desktop GPUs:. All 3 links brought me eventually to the same place.

Daemon tools has been uninstalled. Side note on this one. Is there a preferred DVD/CD emulation software for Win 7?
Sptd has been uninstalled.

SystemLook 30.07.11 by jpshortstuff
Log created at 17:04 on 25/02/2012 by owner
Administrator - Elevation successful
WARNING: SystemLook running under WOW64. Use SystemLook_x64 for accurate results.

========== filefind ==========

Searching for "sptd.sys"
No files found.

-= EOF =-

When I rebooted after uninstalling the sptd file, My computer would not start up again. It hung at the flag screen during boot up for 20 minutes. Eventually I tried a OS repair and that couldn't even fix the problem. It locked up and I couldn't send the issue to MS as prompted. It locked up 2x during the repair attempt.

Eventually it started up under normal login. I have attached a recent system events viewerlink. I seem to get a lot of kernel power failure. I hope my PSU is not dying.

PS. LEt me know if I need to attach it as that extx (sp?)format.

#7 greenslam

greenslam
  • Topic Starter

  • Members
  • 41 posts
  • OFFLINE
  •  
  • Local time:01:13 AM

Posted 25 February 2012 - 08:01 PM

used the wrong system look. Reran with the 64 version.

SystemLook 30.07.11 by jpshortstuff
Log created at 19:00 on 25/02/2012 by owner
Administrator - Elevation successful

========== filefind ==========

Searching for "sptd.sys"
No files found.

-= EOF =-

#8 AustrAlien

AustrAlien

    Inquisitor


  • BC Advisor
  • 6,772 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Cowra NSW Australia
  • Local time:04:13 PM

Posted 26 February 2012 - 05:59 AM

When I rebooted after uninstalling the sptd file, My computer would not start up again. It hung at the flag screen during boot up for 20 minutes. Eventually I tried a OS repair and that couldn't even fix the problem. It locked up and I couldn't send the issue to MS as prompted. It locked up 2x during the repair attempt.

Eventually it started up ...

Ouch ... that wasn't supposed to happen!

Yes, as I said earlier there's a lot of stuff happening (reported in the Event logs) that isn't quite right. We'll have to work on that some more. For now, let us know how things are faring at your end after getting to shutdown/start the computer a few times, and using it as normal. Are there any problems evident?
AustrAlien
Google is my friend. Make Google your friend too.

Posted Image

#9 greenslam

greenslam
  • Topic Starter

  • Members
  • 41 posts
  • OFFLINE
  •  
  • Local time:01:13 AM

Posted 26 February 2012 - 09:12 AM

Will keep you up to date on the machine behaves.

Only got one error showing up in my application event viewer now in the past 12 hours. I'll have to search up the issue later. It's "Activation context generation failed for "c:\program files\microsoft security client\MSESysprep.dll".Error in manifest or policy file "c:\program files\microsoft security client\MSESysprep.dll" on line 10. The element imaging appears as a child of element urn:schemas-microsoft-com:asm.v1^assembly which is not supported by this version of Windows."

Solved my issue of "Failed extract of third-party root list from auto update cab at: <http://www.download.windowsupdate.com/msdownload/update/v3/static/trustedr/en/authrootstl.cab> with error: A required certificate is not within its validity period when verifying against the current system clock or the timestamp in the signed file." by running the msi fixit provided by MS at link. That was popping up constantly.
.

I got an error "There was an error while attempting to read the local hosts file." Should I simply create a new local hosts file as per instructions at Seven Forums I don't see a file labelled hosts in that folder.

The hosts file doesn't disappear on its own. That file should be unaffected unless you modify it or you have a security program that modifies it to prevent you from going to malicious web sites. So, as a precaution, do a full malware scan with the resident AV as well as MBAM.

Then you can just recreate the hosts file. Open Notepad as admin (right click on notepad icon or shortcut and click Run as admin) and type the following information in it:

127.0.0.1 localhost
::1 localhost

The "1" in the "127.0.0.1" must be at the first column of the line and there must be at least one space between "127.0.0.1" and "localhost". In the second line, there must be at least one space between "::1" and "localhost".


Save the file with the name "hosts" in C:\windows\system32\drivers\etc folder.

Edited by greenslam, 26 February 2012 - 09:14 AM.


#10 greenslam

greenslam
  • Topic Starter

  • Members
  • 41 posts
  • OFFLINE
  •  
  • Local time:01:13 AM

Posted 26 February 2012 - 05:17 PM

Latest BSOD. Seems to be related to storport.sys

==================================================
Dump File : 022612-146046-01.dmp
Crash Time : 2/26/2012 3:55:57 PM
Bug Check String : DRIVER_IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x000000d1
Parameter 1 : 00000000`00000030
Parameter 2 : 00000000`00000002
Parameter 3 : 00000000`00000000
Parameter 4 : fffff880`01104c3d
Caused By Driver : storport.sys
Caused By Address : storport.sys+2c3d
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+7cc40
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\022612-146046-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 7601
Dump File Size : 290,648
==================================================
My link
Looking at the driver refence page it says to get it from windows update.

#11 AustrAlien

AustrAlien

    Inquisitor


  • BC Advisor
  • 6,772 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Cowra NSW Australia
  • Local time:04:13 PM

Posted 26 February 2012 - 05:44 PM

Please zip up the last minidump and attach to your reply so I can have a closer look.
  • Navigate to C:\Windows\Minidump <<< folder
  • Right-click on the most recent minidump file > Send to ... > Compressed (zipped) Folder.
    The zip file will be located in the same place (the Minidump folder).
  • Attach the zip file to your next reply.
    When you click on Add Reply, you will see the facility to attach a file just below the box where you type your message.
Note: You will need to zip the file. The BC forums will not allow you to attach a .rar file.
AustrAlien
Google is my friend. Make Google your friend too.

Posted Image

#12 AustrAlien

AustrAlien

    Inquisitor


  • BC Advisor
  • 6,772 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Cowra NSW Australia
  • Local time:04:13 PM

Posted 26 February 2012 - 05:50 PM

Please double-check that the file HOSTS is no longer present on your system.

One way to verify this is to perform a search for the file (ensure that you use the 64 bit version of SystemLook).
Please download SystemLook.exe and save it to your Desktop.
  • alternate download link
    For users of Windows 64 bit systems: SystemLook (64-bit)
  • Double-click SystemLook.exe to run it.
  • Copy the content of the following code box and paste into the main text field:
    :filefind
    hosts
    
  • Click the Look button to start the scan.
    Please be patient, as it may take a little time.
  • When finished, a Notepad window will open with the results of the scan.
  • Please copy & paste the entire content of this log in your next reply.
Note: The log, SystemLook.txt, is saved on your Desktop.
AustrAlien
Google is my friend. Make Google your friend too.

Posted Image

#13 greenslam

greenslam
  • Topic Starter

  • Members
  • 41 posts
  • OFFLINE
  •  
  • Local time:01:13 AM

Posted 26 February 2012 - 06:49 PM

I did create a hosts file this afternoon but here is the result of the lookup

SystemLook 30.07.11 by jpshortstuff
Log created at 17:47 on 26/02/2012 by owner
Administrator - Elevation successful

========== filefind ==========

Searching for "hosts"
C:\Windows\System32\drivers\etc\hosts --a---- 34 bytes [20:56 26/02/2012] [20:56 26/02/2012] E783206E6142140F56EFE1CCBEFA5F00
C:\Windows\winsxs\amd64_microsoft-windows-w..nfrastructure-other_31bf3856ad364e35_6.1.7600.16385_none_6079f415110c0210\hosts --a---- 824 bytes [21:00 10/06/2009] [21:00 10/06/2009] 3688374325B992DEF12793500307566D

-= EOF =-
dump file is attached.

Attached Files



#14 greenslam

greenslam
  • Topic Starter

  • Members
  • 41 posts
  • OFFLINE
  •  
  • Local time:01:13 AM

Posted 27 February 2012 - 03:07 AM

@AustrAlien
I haven't said this yet, but thank you for all the assistance so far.

With my two latest BSOD's, do you want me to run jcgriff's handy bsod collection app again? In reviewing my event viewer logs, IIRC (due to being at work) the culprits as per that was the hard drive controller and the cd rom controller for the last two crashes. I don't know if the event viewer logs are helpful in solving the issue.

I should add that the latest BSOD was very scary because it would not go to window loading on the first few attempts of restarting. After the BIOS loaded, all I got was blinking underscore in the top left corner of my monitor. I was fearful that I completely bricked my system.

I think in the future, I need to let the pc sit and rest for 10 + minutes before attempting to restart it after experiencing a BSOD/hang.

Edited by greenslam, 27 February 2012 - 03:15 AM.


#15 AustrAlien

AustrAlien

    Inquisitor


  • BC Advisor
  • 6,772 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Cowra NSW Australia
  • Local time:04:13 PM

Posted 27 February 2012 - 03:11 AM

I don't know if the event viewer logs are helpful in solving the issue.

Sometimes they are helpful, especially when you can't work out what is going on any other way.

Yes, I was waiting a day or two before asking you to run the jcgriff2 tool again, so that I would have some new Event logs to look at over the past couple of days, so you could do that now for me. Thanks.
AustrAlien
Google is my friend. Make Google your friend too.

Posted Image




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users