BSOD during sleep state 0x0000009f

Hello Staric and welcome to Sevenforums.

Things we need

• A nfo file
  
  • To get this: Start Menu -> Type msinfo32 into the Search programs and files box -> When it opens, go to File, Save -> Save as msinfo32.nfo and save in a place you will remember -> Let it finish the process of gathering and saving the system info -> Right click the .nfo file, click send to compressed (zipped) folder -> Upload the .zip file here.
  
  

BSOD Analyse

Since your dump files are pointing to different kernel-based Windows 7 files, I'd suggest you to run the command SFC /scannow

We usually ask people to do this command to check if Windows is corrupted. It's the most common used one to check if the Windows files are corrupted. If it'll find errors, it'll restore them.

   Tip

If you're having a custom customization layer on your Aero, it's likely to get restored to default.

Press Start | search 'cmd' | Right-click it
| open as Admin | type SFC /SCANNOW

SFC /SCANNOW Command - System File Checker

Firewall

sbwtis.sys Tue Jan 17 09:06:18 2012 (4F152BFA)
Driver Reference Table (DRT)

Make sure that you don't run Sunbelt Firewall along with another Antivirus that has a firewall already. Also you have a large amount of 3rd party drivers, instead of diagnosing those first, run a Memtest86+.

Code:

mcdbus.sys Tue Feb 24 11:34:07 2009 (49A3CD1F)
GEARAspiWDM.sys Mon May 18 14:17:04 2009 (4A1151C0)
mcupdate.dll Tue Jul 14 03:29:09 2009 (4A5BDF65)
usbfilter.sys Tue Dec 22 09:26:22 2009 (4B3082AE)
rrnetcap.sys Thu Feb 18 15:18:44 2010 (4B7D4C44)
AtiPcie64.sys Wed Mar 10 15:33:45 2010 (4B97ADC9)
amdxata.sys Fri Mar 19 17:18:18 2010 (4BA3A3CA)
netr28x.sys Wed Jul 21 13:39:22 2010 (4C46DC6A)
hiber_amd_sata.sys Sat Aug 14 01:35:02 2010 (4C65D6A6)
amd_sata.sys Sat Aug 14 01:35:02 2010 (4C65D6A6)
amd_xata.sys Sat Aug 14 01:35:04 2010 (4C65D6A8)
psi_mf.sys Wed Sep 1 09:53:14 2010 (4C7E066A)
RTKVHD64.sys Tue Sep 7 13:17:23 2010 (4C861F43)
Rt64win7.sys Wed Jan 26 14:34:03 2011 (4D4022CB)
SDCRapidStart.sys Wed Apr 20 18:48:20 2011 (4DAF0E54)
hiber_storport.sys Fri Apr 22 22:04:32 2011 (4DB1DF50)
appliand.sys Fri May 20 12:20:42 2011 (4DD6407A)
nvBridge.kmd Sat May 21 05:58:23 2011 (4DD7385F)
Sftvollh.sys Fri Sep 30 18:42:46 2011 (4E85F186)
Sftplaylh.sys Fri Sep 30 18:43:05 2011 (4E85F199)
Sftfslh.sys Fri Sep 30 18:43:06 2011 (4E85F19A)
Sftredirlh.sys Fri Sep 30 18:43:14 2011 (4E85F1A2)
SBREdrv.sys Wed Oct 26 18:41:21 2011 (4EA83831)
sbapifs.sys Tue Nov 29 03:18:16 2011 (4ED440E8)
usbaapl64.sys Wed Jan 11 01:56:04 2012 (4F0CDE24)
sbwtis.sys Tue Jan 17 09:06:18 2012 (4F152BFA)
nvhda64v.sys Wed Apr 18 19:07:54 2012 (4F8EF4EA)
nvlddmkm.sys Tue May 15 09:35:36 2012 (4FB20748)

mcdbus.sys
GEARAspiWDM.sys
mcupdate.dll
usbfilter.sys
rrnetcap.sys
AtiPcie64.sys
amdxata.sys
netr28x.sys
hiber_amd_sata.sys
amd_sata.sys
amd_xata.sys
psi_mf.sys
RTKVHD64.sys
Rt64win7.sys
SDCRapidStart.sys
hiber_storport.sys
appliand.sys
nvBridge.kmd
Sftvollh.sys
Sftplaylh.sys
Sftfslh.sys
Sftredirlh.sys
SBREdrv.sys
sbapifs.sys
usbaapl64.sys
sbwtis.sys
nvhda64v.sys
nvlddmkm.sys

Memtest86+ why & how

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

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.