BSOD on Startup

[stevejma]

Unfortunately I do not have the BSOD error code that shows up; I had to do a restart when configuring the dump files. But this problem only seems to occur on a fresh start up. After I restart the computer and the "Windows has recovered from an error" message is displayed, I don't get it. It's only when I shut down the computer again and boot it up that I get it.

It's only started in the past week and I thought it would be a passing thing since it's never happened before and I haven't installed anything new on my PC (i.e. drivers, etc).

 

[YoYo155]

Welcome to 7F .

Only one bugcheck is present in the file uploaded if you have more please upload them as they provide
more information which is always a good thing.
Please look in the minidump folder if files are present copy them to the desktop and upload them as well.

C:\Windows\minidump

The main (as logged in the system event log) bug check code your are getting is
0x50 PAGE FAULT IN NONPAGED AREA.

Usual causes: Defective hardware (particularly memory - but not just RAM), Faulty system service, Antivirus, Device driver, NTFS corruption, BIOS

The stack from the uploaded dump doesn't hold enough information to incriminate a 3rd party driver
which are the usual cause of BSOD.

0xfffff88008656528 : 0xfffff88001ae5f9d : Ntfs!LfsResetUndoTotal+0x17d
0xfffff88008656568 : 0xfffff8000347fcee : nt!KiPageFault+0x16e
0xfffff88008656570 : 0x0000000000000000 :  Trap @ fffff88008656570
0xfffff880086565d8 : 0xfffff800034929cc : nt!IopFreeIrp+0x11c
0xfffff88008656648 : 0xfffff88001ac2589 : Ntfs!NtfsSetEndOfFileInfo+0x319
0xfffff880086566a8 : 0xfffff880018e5132 : fltmgr!GetContextFromStreamList+0x192
0xfffff880086566d8 : 0xfffff88001a35d8a : Ntfs!NtfsAcquireExclusiveFcb+0x16a
0xfffff88008656748 : 0xfffff88001ac159d : Ntfs!NtfsCommonSetInformation+0x3ed
0xfffff880086567e8 : 0xfffff88001a3627e : Ntfs!NtfsInitializeTopLevelIrp+0x3e
0xfffff88008656828 : 0xfffff88001a33f84 : Ntfs!NtfsFsdSetInformation+0x11c
0xfffff880086568a8 : 0xfffff880018e2bcf : fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x24f
0xfffff88008656938 : 0xfffff880018e16df : fltmgr!FltpDispatch+0xcf
0xfffff88008656948 : 0xfffff800034c6261 : nt!CcWriteBehind+0x2f1
0xfffff88008656998 : 0xfffff80003467143 : nt!CcSetValidData+0x11b
0xfffff880086569b8 : 0xfffff800035fce80 : nt!KiInitialPCR+0x180
0xfffff880086569d8 : 0xfffff88001aea766 : Ntfs!NtfsReleaseScbFromLazyWrite+0x6a
0xfffff88008656a08 : 0xfffff800034c6261 : nt!CcWriteBehind+0x2f1
0xfffff88008656a68 : 0xfffffa8010b5f8f8 : 0xfffff80003627288 : nt!ExWorkerQueue+0x8
0xfffff88008656a88 : 0xfffff800035fce00 : nt!KiInitialPCR+0x100
0xfffff88008656a98 : 0xfffff80003688920 : nt!CcRegularWorkQueue
0xfffff88008656aa8 : 0xfffff80003627280 : nt!ExWorkerQueue
0xfffff88008656ab8 : 0xfffff800034c6af8 : nt!CcWorkerThread+0x1c8
0xfffff88008656b60 : 0xfffff800034c6930 : nt!CcWorkerThread
0xfffff88008656b68 : 0xfffff8000348b261 : nt!ExpWorkerThread+0x111
0xfffff88008656b78 : 0xfffff80003778101 : nt!ObpWaitForMultipleObjects+0x42b
0xfffff88008656b80 : 0xfffff80003688920 : nt!CcRegularWorkQueue
0xfffff88008656be0 : 0xfffff8000348b150 : nt!ExpWorkerThread
0xfffff88008656bf8 : 0xfffff8000371e2ea : nt!PspSystemThreadStartup+0x5a
0xfffff88008656c38 : 0xfffff800034728e6 : nt!KxStartSystemThread+0x16

All we get is some activity regarding Ntfs and Fltmgr which are both Windows components
but are being called by various applications, mainly by Anti-Virus software.

I can see you have Kaspersky installed, I don't want to blame it on it without evidence
so we'll leave it for now but keep that in the back of our mind.

Looking at the loaded modules, I see some outrageously old drivers that pre-dates Windows 7.

scmndisp.sys Wed Jan 17 09:48:03 2007
jswpslwfx.sys Thu May 15 13:28:50 2008
adfs.SYS     Thu Jun 26 23:52:37 2008
spldr.sys    Mon May 11 19:56:27 2009
LHidFilt.Sys Wed Jun 17 19:49:39 2009
LMouFilt.Sys Wed Jun 17 19:49:43 2009
uxpatch.sys  Mon Jul 13 08:09:18 2009

• Driver Reference Table - scmndisp.sys
• Driver Reference Table - jswpslwfx.sys
• Driver Reference Table - adfs.SYS
• Driver Reference Table - LHidFilt.Sys
  
• Driver Reference Table - LMouFilt.Sys
• Driver Reference Table - uxpatch.sys

Their location and usage on your PC:


uxpatch.sys

UnsignedThemesSvc The Within Network, LLC    c:\windows\unsignedthemessvc.exe

My guess is this software utilizes this service.

DesktopDock64 Stardock    c:\program files (x86)\stardock\fences\desktopdock64.dll

Please remove it completely.

---

LMouFilt.Sys / LHidFilt.Sys

setpointii.exe    c:\program files\logitech\setpoint ii\setpointii.exe

Device Name: [U][B]G500[/B][/U]
         Attached: 1
    Controller ID: 0x0
Vendor/Product ID: 0x046D, 0xC068

Please remove or update the software.

---

jswpslwfx.sys
The driver isn't specified in the MSINFO32 file, so my best guess this is a D-Link brand?

150Mbps Wireless 802.11b/g/n Nano USB Adapter

If it is, please update the driver or remove if not in use.

   Note

If you are unsure upload a picture of the device containing the FCC-ID.

---

scmndisp.sys

NETGEAR WNDA3100v2 N600 Wireless Dual Band USB Adapter

Please update the driver or remove if not in use.

   Note

If you are unsure upload a picture of the device containing the FCC-ID.

---

adfs.SYS - Adobe File System Driver.
A part of the Adobe software installed, in your case.

c:\program files\adobe\[B]adobe photoshop cs4 (64 bit)\photoshop.exe[/B]

Please look for an update to the software via the built in updater.

---

Once all of the above is done, please follow the quote below detailing the ins and outs
of enabling Driver Verifier.

Driver Verifier - Enable and Disable
Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

   Information

Why Driver Verifier:
It puts a stress on the drivers, ans so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.

How Can we know that DV is enabled:
It will make the system bit of slow, laggy.

   Warning

Before enabling DV, make it sure that you have earlier System restore points made in your computer. You can check it easily by using CCleaner looking at Tools > System Restore.

If there is no points, make a System Restore Point manually before enabling DV.

   Tip

• If you fail to get on the Desktop because of DV, Boot into Advanced Boot Options > Safe mode. Disable DV there. Now boot normally again, and try following the instruction of enabling DV again.
• If you cannot boot in Safe mode too, do a System Restore to a point you made earlier.

Let us know the results, with the subsequent crash dumps, if any.

Keep us posted with the results.

 

[stevejma]

I experienced another blue screen before I could start following those directions. Here is the zip file of that crash though I don't know how much it will help.

I'll post again as soon as everything is done updating.

 

[YoYo155]

No dumps at all are in the file uploaded .

 

[stevejma]

I have no idea why it's not in there. >.< Sorry. Well if it's any consolation I followed all your recommendations for those drivers and I've had very clean start ups since. No BSOD so the problem must've been solved.

 

[YoYo155]

That's good to hear .
If you enabled Driver verifier, please disable it | http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html.
Post back with updates, which ever way things turn out to be.