BSOD after Hibernation

sefanana · 18 Jun 2012

About a month ago my laptop has been getting the BSOD after I resume it from sleep/hibernation. To my knowledge I have not added any software installations outside of system updates during this time frame. Attached are the required files.

My Specs are:

-x64
-Original OEM Windows 7 Home Edition
-Laptop is almost 2 years old

Willing to provide any more information if needed.

Please and thanks for the help.

usasma · 19 Jun 2012

The volume dirty bit is set on your C: drive
Please do this:

CHKDSK /R /F:
Run CHKDSK /R /F from an elevated (Run as adminstrator) Command Prompt. Please do this for each hard drive on your system.
FWIW - I know that the /F is supposed to be redundant, but I prefer to have it run anyway.
When it tells you it can't do it right now - and asks you if you'd like to do it at the next reboot - answer Y (for Yes) and press Enter. Then reboot and let the test run. It may take a while for it to run, but keep an occasional eye on it to see if it generates any errors. See "CHKDSK LogFile" below in order to check the results of the test.

Elevated Command Prompt:
Go to Start and type in "cmd.exe" (without the quotes)
At the top of the Search Box, right click on Cmd.exe and select "Run as administrator"

The run another perfmon report to see if the Volume Dirty Bit error is still there.
If it is, the only other solution is a full format of your hard drive (which will wipe out everything on it - both Windows and all your data).

Also, run this free hard drive diagnostic in case the hard drive is starting to die: Hard Drive Diagnostic Procedure

SP1 isn't installed, please do the following:

Installing Windows 7 Service Pack 1
1. Visit the PC manufacturer's website and update ALL drivers. DO NOT use Windows Update or the "Update drivers" function of Device Manager.
2. Check Device Manager for any unknown/disabled devices - if there are unknown/disabled devices, fix them with the latest drivers from the device manufacturer's website (not the PC Manufacturer)
3. Visit Windows Update and get all updates (may take repeated visits)
4. Visit Windows Update and get Service Pack 1 (usually under Important Updates). Read these notes for installing SP1: Steps to follow before you install Windows 7 SP1 and Windows Server 2008 R2 SP1 from the Microsoft Download Center
NOTE: For Vista, read these notes:

Read these notes for installing Vista SP1: Learn how to install Windows Vista Service Pack 1 (SP1)
Read these notes for installing Vista SP2: Learn how to install Windows Vista Service Pack 2 (SP2)

5. Visit Windows Update and get any other available updates. May take repeated visits, but keep it up until you get several "Windows is updated" results.
If you're having difficulties with installing a Service Pack, please use the SURTool from this link: What is the System Update Readiness Tool?
Also, check out this troubleshooting link from Microsoft: Troubleshoot problems installing Service Pack 1 (SP1) for Windows 7 and Windows Server 2008 R2

I have had limited success in installing updates/Service Packs when using a "clean boot". I suspect that I'm just bypassing the problem - and that it can come back to bite me in the butt later on.

The WER section of MSINFO32 shows one BSOD that blames OrbLauncher. Please uninstall this application to see if that stops the errors.

Daemon Tools (and Alcohol % software) are known to cause BSOD's on some Win7 systems (mostly due to the sptd.sys driver, although I have seen dtsoftbus01.sys blamed on several occasions).
Please uninstall the program, then use the following free tool to ensure that the troublesome sptd.sys driver is removed from your system (pick the 32 or 64 bit system depending on your system's configuration): DuplexSecure - FAQ

All of the memory dumps also seem to implicate OrbLauncher.exe (most likely from the Orb Networks program in your Start Menu). Please uninstall it. If it's needed, please uninstall it anyway - then download and install a fresh copy from the manufacturer's website.

Numerous HP drivers date from 2009 or earlier. Please visit the HP website and update them all. Check the table below for those drivers dated 2009 and earlier. There's a listing of links beneath it that'll give info about these drivers when you click on them.

Symantec drivers date from 2009 or earlier, please do this:

Anti-Virus Removal:
Please do the following:
- download a free antivirus for testing purposes: Free AntiVirus
- uninstall the Norton from your system (you can reinstall it, if so desired, when we're done troubleshooting)
- remove any remnants of Norton using this free tool: http://us.norton.com/support/kb/web_...080710133834EN
- IMMEDIATELY install and update the free antivirus, then check to ensure that the Windows Firewall is turned on.
- check to see if this fixes the BSOD's
NOTE: NEVER run more than 1 anti-virus, firewall, Internet Security/Security Center application at the same time.

Cyberlink drivers date from 2008 or earlier, please uninstall it.

June Fabrics Technology/PdaNet Modem dates from 2007 and must either be updated or removed from your system.
More info on this driver here: Driver Reference Table - pnetmdm64.sys

The following info is just FYI, I've already addressed the issues that I saw in the above paragraphs

- Further info on BSOD error messages available at: http://www.carrona.org/bsodindx.html
- Info on how to troubleshoot BSOD's (DRAFT): http://www.carrona.org/userbsod.html
- How I do it: http://www.carrona.org/howidoit.html

3RD PARTY DRIVERS PRESENT IN THE DUMP FILES

Code:


000.fcl                 Fri Sep 26 09:11:22 2008 (48DCDF7A)
Accelerometer.sys       Wed Jul 08 14:41:38 2009 (4A54E862)
AtiHdmi.sys             Thu May 06 05:20:39 2010 (4BE289E7)
AtiPcie.sys             Mon Aug 24 04:25:26 2009 (4A924E76)
ENG64.SYS               Fri Jul 29 09:17:51 2011 (4E32B2FF)
ENG64.SYS               Wed Apr 25 05:29:25 2012 (4F97C3F5)
EX64.SYS                Fri Jul 29 09:15:11 2011 (4E32B25F)
EX64.SYS                Wed Apr 25 05:27:28 2012 (4F97C380)
EraserUtilDrv11210.sys  Tue May 15 20:36:03 2012 (4FB2F673)
EraserUtilRebootDrv.sys Fri Jan 20 18:39:49 2012 (4F19FB45)
EraserUtilRebootDrv.sys Tue May 15 20:36:03 2012 (4FB2F673)
GEARAspiWDM.sys         Mon May 18 08:17:04 2009 (4A1151C0)
RimSerial_AMD64.sys     Wed Jul 06 19:20:01 2011 (4E14EDA1)
SCDEmu.SYS              Mon Nov 14 22:18:27 2011 (4EC1DA03)
SRTSP64.SYS             Thu Mar 04 22:21:57 2010 (4B9078D5)
SRTSPX64.SYS            Thu Mar 04 22:22:14 2010 (4B9078E6)
SYMEVENT64x86.SYS       Wed Jun 24 16:19:12 2009 (4A428A40)
SynTP.sys               Fri Apr 09 17:43:53 2010 (4BBF9F99)
WmBEnum.sys             Tue Apr 27 16:10:19 2010 (4BD744AB)
WmXlCore.sys            Tue Apr 27 16:09:26 2010 (4BD74476)
a0aij0dd.SYS            Wed Apr 07 21:00:58 2010 (4BBD2ACA)
a218h592.SYS            Wed Apr 07 21:00:58 2010 (4BBD2ACA)
a3c4mk6l.SYS            Wed Apr 07 21:00:58 2010 (4BBD2ACA)
a84v0xui.SYS            Wed Apr 07 21:00:58 2010 (4BBD2ACA)
aa6lhi06.SYS            Wed Apr 07 21:00:58 2010 (4BBD2ACA)
aczkn0vx.SYS            Wed Apr 07 21:00:58 2010 (4BBD2ACA)
aeweqvh1.SYS            Wed Apr 07 21:00:58 2010 (4BBD2ACA)
ag273nkt.SYS            Wed Apr 07 21:00:58 2010 (4BBD2ACA)
agfm40cn.SYS            Wed Apr 07 21:00:58 2010 (4BBD2ACA)
ajt4yrgw.SYS            Wed Apr 07 21:00:58 2010 (4BBD2ACA)
amdxata.sys             Fri Mar 19 12:18:18 2010 (4BA3A3CA)
athrx.sys               Mon Sep 21 22:47:11 2009 (4AB83AAF)
atikmdag.sys            Tue Sep 28 21:41:26 2010 (4CA29946)
atikmpag.sys            Tue Sep 28 21:14:49 2010 (4CA29309)
azninm8d.SYS            Wed Apr 07 21:00:58 2010 (4BBD2ACA)
dvmio.sys               Tue Nov 10 23:38:32 2009 (4AFA3FC8)
eeCtrl64.sys            Fri Jan 20 18:39:48 2012 (4F19FB44)
eeCtrl64.sys            Tue May 15 20:36:03 2012 (4FB2F673)
hpdskflt.sys            Wed Jul 08 14:41:38 2009 (4A54E862)
pnetmdm64.sys           Wed Mar 07 13:13:19 2007 (45EF00BF)
povrtdev.sys            Wed Feb 24 05:51:44 2010 (4B8504C0)
sptd.sys                Wed Apr 07 21:29:00 2010 (4BBD315C)
stwrt64.sys             Mon Feb 01 02:34:43 2010 (4B668413)
usbfilter.sys           Tue Dec 22 03:26:22 2009 (4B3082AE)

Code:


Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\051512-92680-01.dmp]
Built by: 7600.16988.amd64fre.win7_gdr.120401-1505
Debug session time: Tue May 15 07:59:53.939 2012 (UTC - 4:00)
System Uptime: 1 days 16:54:44.212
BugCheck F4, {3, fffffa8004bcd040, fffffa8004bcd320, fffff8000337b720}
Probably caused by : smss.exe
PROCESS_NAME:  OrbLauncher.ex
BUGCHECK_STR:  0xF4_OrbLauncher.ex
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
FAILURE_BUCKET_ID:  X64_0xF4_OrbLauncher.ex_IMAGE_smss.exe
Bugcheck code 000000F4
Arguments 00000000`00000003 fffffa80`04bcd040 fffffa80`04bcd320 fffff800`0337b720
BiosVersion = F.23
BiosReleaseDate = 11/11/2010
SystemManufacturer = Hewlett-Packard
SystemProductName = HP Pavilion dv7 Notebook PC
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\052312-97157-01.dmp]
Built by: 7600.16988.amd64fre.win7_gdr.120401-1505
Debug session time: Wed May 23 09:04:54.556 2012 (UTC - 4:00)
System Uptime: 1 days 6:42:25.491
BugCheck F4, {3, fffffa80049ceb30, fffffa80049cee10, fffff800033c3720}
Probably caused by : smss.exe
PROCESS_NAME:  OrbLauncher.ex
BUGCHECK_STR:  0xF4_OrbLauncher.ex
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
FAILURE_BUCKET_ID:  X64_0xF4_OrbLauncher.ex_IMAGE_smss.exe
Bugcheck code 000000F4
Arguments 00000000`00000003 fffffa80`049ceb30 fffffa80`049cee10 fffff800`033c3720
BiosVersion = F.23
BiosReleaseDate = 11/11/2010
SystemManufacturer = Hewlett-Packard
SystemProductName = HP Pavilion dv7 Notebook PC
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\053012-88390-01.dmp]
Built by: 7600.16988.amd64fre.win7_gdr.120401-1505
Debug session time: Wed May 30 08:49:59.618 2012 (UTC - 4:00)
System Uptime: 1 days 14:41:59.511
BugCheck F4, {3, fffffa8004c7b9f0, fffffa8004c7bcd0, fffff80003389720}
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : smss.exe
PROCESS_NAME:  OrbLauncher.ex
BUGCHECK_STR:  0xF4_OrbLauncher.ex
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
FAILURE_BUCKET_ID:  X64_0xF4_OrbLauncher.ex_IMAGE_smss.exe
Bugcheck code 000000F4
Arguments 00000000`00000003 fffffa80`04c7b9f0 fffffa80`04c7bcd0 fffff800`03389720
BiosVersion = F.23
BiosReleaseDate = 11/11/2010
SystemManufacturer = Hewlett-Packard
SystemProductName = HP Pavilion dv7 Notebook PC
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\060312-75769-01.dmp]
Built by: 7600.16988.amd64fre.win7_gdr.120401-1505
Debug session time: Sun Jun  3 12:26:36.204 2012 (UTC - 4:00)
System Uptime: 4 days 3:36:06.320
BugCheck F4, {3, fffffa8004c62b30, fffffa8004c62e10, fffff8000338d720}
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : smss.exe
PROCESS_NAME:  OrbLauncher.ex
BUGCHECK_STR:  0xF4_OrbLauncher.ex
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
FAILURE_BUCKET_ID:  X64_0xF4_OrbLauncher.ex_IMAGE_smss.exe
Bugcheck code 000000F4
Arguments 00000000`00000003 fffffa80`04c62b30 fffffa80`04c62e10 fffff800`0338d720
BiosVersion = F.23
BiosReleaseDate = 11/11/2010
SystemManufacturer = Hewlett-Packard
SystemProductName = HP Pavilion dv7 Notebook PC
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\060512-85348-01.dmp]
Built by: 7600.16988.amd64fre.win7_gdr.120401-1505
Debug session time: Tue Jun  5 17:21:15.731 2012 (UTC - 4:00)
System Uptime: 2 days 4:53:39.361
BugCheck F4, {3, fffffa8004fd2730, fffffa8004fd2a10, fffff800033d3720}
Probably caused by : smss.exe
PROCESS_NAME:  OrbLauncher.ex
BUGCHECK_STR:  0xF4_OrbLauncher.ex
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
FAILURE_BUCKET_ID:  X64_0xF4_OrbLauncher.ex_IMAGE_smss.exe
Bugcheck code 000000F4
Arguments 00000000`00000003 fffffa80`04fd2730 fffffa80`04fd2a10 fffff800`033d3720
BiosVersion = F.23
BiosReleaseDate = 11/11/2010
SystemManufacturer = Hewlett-Packard
SystemProductName = HP Pavilion dv7 Notebook PC
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\060612-102851-01.dmp]
Built by: 7600.16988.amd64fre.win7_gdr.120401-1505
Debug session time: Wed Jun  6 18:28:48.633 2012 (UTC - 4:00)
System Uptime: 1 days 1:06:58.568
BugCheck F4, {3, fffffa8004c4ab30, fffffa8004c4ae10, fffff80003383720}
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : smss.exe
PROCESS_NAME:  OrbLauncher.ex
BUGCHECK_STR:  0xF4_OrbLauncher.ex
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
FAILURE_BUCKET_ID:  X64_0xF4_OrbLauncher.ex_IMAGE_smss.exe
Bugcheck code 000000F4
Arguments 00000000`00000003 fffffa80`04c4ab30 fffffa80`04c4ae10 fffff800`03383720
BiosVersion = F.23
BiosReleaseDate = 11/11/2010
SystemManufacturer = Hewlett-Packard
SystemProductName = HP Pavilion dv7 Notebook PC
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\060812-90823-01.dmp]
Built by: 7600.16988.amd64fre.win7_gdr.120401-1505
Debug session time: Fri Jun  8 00:21:42.722 2012 (UTC - 4:00)
System Uptime: 1 days 5:52:19.392
BugCheck F4, {3, fffffa8004f4cb30, fffffa8004f4ce10, fffff800033db720}
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : smss.exe
PROCESS_NAME:  OrbLauncher.ex
BUGCHECK_STR:  0xF4_OrbLauncher.ex
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
FAILURE_BUCKET_ID:  X64_0xF4_OrbLauncher.ex_IMAGE_smss.exe
Bugcheck code 000000F4
Arguments 00000000`00000003 fffffa80`04f4cb30 fffffa80`04f4ce10 fffff800`033db720
BiosVersion = F.23
BiosReleaseDate = 11/11/2010
SystemManufacturer = Hewlett-Packard
SystemProductName = HP Pavilion dv7 Notebook PC
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\061112-91354-01.dmp]
Built by: 7600.16988.amd64fre.win7_gdr.120401-1505
Debug session time: Mon Jun 11 17:28:02.235 2012 (UTC - 4:00)
System Uptime: 3 days 17:05:51.155
BugCheck F4, {3, fffffa8004d22b30, fffffa8004d22e10, fffff800033da720}
Probably caused by : smss.exe
PROCESS_NAME:  OrbLauncher.ex
BUGCHECK_STR:  0xF4_OrbLauncher.ex
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
FAILURE_BUCKET_ID:  X64_0xF4_OrbLauncher.ex_IMAGE_smss.exe
Bugcheck code 000000F4
Arguments 00000000`00000003 fffffa80`04d22b30 fffffa80`04d22e10 fffff800`033da720
BiosVersion = F.23
BiosReleaseDate = 11/11/2010
SystemManufacturer = Hewlett-Packard
SystemProductName = HP Pavilion dv7 Notebook PC
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\061212-89918-01.dmp]
Built by: 7600.16988.amd64fre.win7_gdr.120401-1505
Debug session time: Tue Jun 12 22:26:29.115 2012 (UTC - 4:00)
System Uptime: 1 days 4:57:53.179
BugCheck F4, {3, fffffa8004c51150, fffffa8004c51430, fffff800033c7720}
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : smss.exe
PROCESS_NAME:  OrbLauncher.ex
BUGCHECK_STR:  0xF4_OrbLauncher.ex
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
FAILURE_BUCKET_ID:  X64_0xF4_OrbLauncher.ex_IMAGE_smss.exe
Bugcheck code 000000F4
Arguments 00000000`00000003 fffffa80`04c51150 fffffa80`04c51430 fffff800`033c7720
BiosVersion = F.23
BiosReleaseDate = 11/11/2010
SystemManufacturer = Hewlett-Packard
SystemProductName = HP Pavilion dv7 Notebook PC
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\061412-83881-01.dmp]
Built by: 7600.16988.amd64fre.win7_gdr.120401-1505
Debug session time: Thu Jun 14 18:07:42.299 2012 (UTC - 4:00)
System Uptime: 1 days 19:40:43.234
BugCheck F4, {3, fffffa8004dd3040, fffffa8004dd3320, fffff80003379720}
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : smss.exe
PROCESS_NAME:  OrbLauncher.ex
BUGCHECK_STR:  0xF4_OrbLauncher.ex
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
FAILURE_BUCKET_ID:  X64_0xF4_OrbLauncher.ex_IMAGE_smss.exe
Bugcheck code 000000F4
Arguments 00000000`00000003 fffffa80`04dd3040 fffffa80`04dd3320 fffff800`03379720
BiosVersion = F.23
BiosReleaseDate = 11/11/2010
SystemManufacturer = Hewlett-Packard
SystemProductName = HP Pavilion dv7 Notebook PC
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\061812-108077-01.dmp]
Built by: 7600.16988.amd64fre.win7_gdr.120401-1505
Debug session time: Mon Jun 18 17:46:57.630 2012 (UTC - 4:00)
System Uptime: 2 days 22:35:59.300
BugCheck F4, {3, fffffa8004af8b30, fffffa8004af8e10, fffff800033db720}
Probably caused by : smss.exe
PROCESS_NAME:  OrbLauncher.ex
BUGCHECK_STR:  0xF4_OrbLauncher.ex
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
FAILURE_BUCKET_ID:  X64_0xF4_OrbLauncher.ex_IMAGE_smss.exe
Bugcheck code 000000F4
Arguments 00000000`00000003 fffffa80`04af8b30 fffffa80`04af8e10 fffff800`033db720
BiosVersion = F.23
BiosReleaseDate = 11/11/2010
SystemManufacturer = Hewlett-Packard
SystemProductName = HP Pavilion dv7 Notebook PC
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

sefanana · 20 Jun 2012

Thanks for your quick response. After running the chkdsk, the "A logical disk has the dirty bit set." that was in the original perfmon was not in it after I ran it again. Hopefully the problem is solved. I'll let you know within the next week. Again thanks for the quick solution. Beats going to best buy and paying them to run command prompts.

Thanks John

usasma · 21 Jun 2012

If you haven't made them, now is a good time to attempt to make the system recovery disks for your system.
This is just in case the dirty bit thing is a warning that the hard drive is having problems.