BSOD ntoskrnl.exe + 7flc0, error 0x0000009f

[SwiftFox]

I've been getting DRIVER_POWER_STATE shutdowns on my comp recently when I leave it running for a day or overnight. I have about 5 dmp files showing the same ntoskrnl.exe.

Please let me know if I need to include more information.

Thanks

 

[JaidynM]

You don't have your msinfo file attached. If you deleted it or misplace the file, please re-attach it.

Drivers

The following drivers need to be updated:

lmimirr.sys                 Wed Apr 11 08:32:45 2007 (461C108D)
RaInfo.sys                  Sat Jan  5 05:57:14 2008 (477E818A)
AmdTools64.sys              Tue Apr 29 03:03:39 2008 (4816036B)
LMIRfsDriver.sys            Tue Jul 15 02:26:56 2008 (487B7E50)
dne64x.sys                  Tue Nov 11 12:01:24 2008 (4918D964)

These drivers can be found by searching them in Google and then finding the associated software or driver. Finally, find the latest version of this driver or software and download and install it. Some of the drivers may also be found here (if the driver says 'Windows Update' simply make sure all Windows Updates are installed).

You should also update any other drivers you can think of including graphics, audio, chipset, SSD etc.

Your dumps pointed to either NETwNs64.sys (associated with Intel(R) Wireless WiFi Link 5000 Series Adapter Driver for Windows 7) or k57nd60a.sys (associated with Broadcom NetLink Gigabit Ethernet NDIS6.x Unified Driver). Please update the two drivers from the below links or from your manufacturer website.
Ethernet NIC Driver Downloads | Broadcom
http://downloadcenter.intel.com/Default.aspx
​

 

[SwiftFox]

I updated a large quanitity of my driver a week ago and I had no problems with crashes until today when I got the same type of crash report. Can you take a look again and see if something is still troublesome?

Thank you

 

[Tobias]

The latest BSOD was caused by the Intel(R) Centrino(R) Wireless-N 1000 driver.

fffff880`0685f000 fffff880`073a3000 Netwsw00 Mon Mar 12 22:06:43 2012 (4F5E6563)

 

[SwiftFox]

Manually updated the broadcom ethernet, and the intel wifi appears to be up to date.

 

[JaidynM]

Enable Driver Verifier. Enabling this should hopefully crash your system and then point to the faulty driver that is causing problems. However before you do, it is advised that you create a system restore point and backup first.
http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html

 

[SwiftFox]

When i enable driver verifier, my computer freezes at startup and i need to run startup repair to restore my comp. I don't feel like that is the intended purpose.

 

[JaidynM]

It might be. After using Startup Repair, can you boot into Windows? If not, try booting in safe mode. Afterwards. post the latest dumps.

 

[SwiftFox]

Diring thr startup repair, it asks me if I was to system restore, and if I don't do it, it jus continues to freeze at the startup. I'll do the process over again and post the dump tomorrow.

Thanks for all your help so far

 

[SwiftFox]

Anything look promising in there?

 

[FredeGail]

   Information

Jumping in for a short while - Do the already suggested troubleshooting steps if you haven't already.

• If you're able to get into Windows 7 sometime, type MSCONFIG, select Startup and disable everything except Microsoft software.
• Ubuntu
  For a trial, try downloading a copy of Ubuntu and see if your system will crash.
  By that, we'd have an idea if Windows 7's drivers and system is broken. You can try it out on a
  flash drive if you so desire.
  Go to Ubuntu.com | Download the image | See how to create a bootable flash drive
  • Leave it running for some time and report your results.
• Looking at your bugcheck it's likely that a memory corruption event was triggered. Though a driver could be causing the memory to be borked, but we're usually suggesting a memory test before moving forward. Do a scan with Memtest86+. Memtest is a scanner that'll check your sticks for errors.
  
  
     Warning

  :info: Note that the below instructions may break your WARRANTY rules. If you're unsure check manuals, separated warranty papers, stickers on computer for secure permission.
  
  To ensure that we'll know if it's the slots on the motherboard that's broken, or the sticks itself - we have a little procedure we'll recommend. Remove 1 stick, scan the other with Memtest in the current slot. After 7 passes, move the stick to another slot and scan, and so on and so forth until you've scanned all the sticks, and all the slots, one by one.
  
  Memtest86+ - Advanced Memory Diagnostic Tool

Best Regards,
Frederik.

 

[SwiftFox]

I ran the memtest86+ scan and it came back clean. I have a laptop so getting to the motherboard to test the slots would be a real pain, and I don't really feel comfortable doing it.

I am currently running Unbuntu 12.04.1 to see if the problem still occurs.

Thanks

 

[FredeGail]

No, then you shouldn't do it. It wouldn't be the issue.

Good luck in Ubuntu.

Best Regards,
Frederik.