Windows is running slow

Honestly, you're not going to get the system much faster than that TBH. It's actually not much slower than my system I'm using right now!!

If you want to do a full reinstall, that's fine. I'm not going to guarantee any more speed, but if you want to go ahead, feel free. :)

You're most welcome, it's been a pleasure working with you. Any more issues or questions, please just reply to this thread. I'll be more than happy to assist you again. Marked as solved for now.

Kind regards,
Stephen
 
Hi there, it has been a while!

My sister just noticed me that blue screens appeared a few times.
She didn't know what to do but restart the pc, but I told her to write down the codes...here what came.

STOP 0X00000CE
0XFFFFFA6017BE1674
0X000000008

After a few attempts to find the answer on the internet, I have no clue what it is about...

Please take note that I do not have access to her computer at the moment, but will do the requested tasks ASAP.
Thanks again,
 
Hello again!

Sorry to hear you are having issues! If you can follow the posting instructions, and upload the output in your next post, I'll take a look at them for you.

Stephen
 
Thanks again for your assistance.
I have attached Windows7_Vista_jcgriff2 and PERFMON, if you need anything else, let me know.

Take note the msinfo32 wasn't complete, like last time.

Eric
 

Attachments

I have a German exam Friday, so can only make a quick post. I'll get back fully at the weekend. :)

Does the computer have a webcam? If so, is it ever used or required? The dumps are referencing the webcam driver, and without spending a little while pouring over the dump file (which I'll do at the weekend), it seems as if the webcam is causing the BSODs, or at least the driver.

Stephen
 
Yes, there's an integrated webcam. I believe my sister is using it for videos conferences, but it doesn't occur often. I guess she would like to keep it (I will confirm with her).
 
Hi,

Stephen is quite tied up at the moment so I will be assisting you. I hope you are still with us.

All of the attached DMP files are of the DRIVER_UNLOADED_WITHOUT_CANCELLING_PENDING_OPERATIONS (ce) bug check.

This indicates that a driver failed to cancel pending operations before unloading.

Overall, the driver failed to cancel lookaside lists, DPCs, worker threads, or other such items before unload.

Running a quick kv shows the call stack in which we can see:

Code: 
0: kd> kv
Child-SP          RetAddr           : Args to Child                                                           : Call Site
fffffa60`1a76fac8 fffff800`020d0a10 : 00000000`00000050 fffffa60`179e7674 00000000`00000008 fffffa60`1a76fbb0 : nt!KeBugCheckEx
fffffa60`1a76fad0 fffff800`0206acd9 : 00000000`00000008 00000000`1420cb77 00000000`00000000 fffffa80`06d7d720 : nt! ?? ::FNODOBFM::`string'+0x2d48c
fffffa60`1a76fbb0 fffffa60`179e7674 : fffff800`02278227 0000014b`c97dbacd fffff800`02066207 fffffa60`19178440 : nt!KiPageFault+0x119 (TrapFrame @ fffffa60`1a76fbb0)
fffffa60`1a76fd48 fffff800`02278227 : 0000014b`c97dbacd fffff800`02066207 fffffa60`19178440 00000001`1420cb01 : [COLOR=#ff0000][U][I][B]<Unloaded_usbvideo.sys>+0x1f674[/B][/I][/U][/COLOR]
fffffa60`1a76fd50 fffff800`020a9456 : fffff800`02188680 fffffa80`06d7d720 fffffa80`06694bb0 fffffa60`18623990 : nt!PspSystemThreadStartup+0x57
fffffa60`1a76fd80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16

The driver responsible is usbvideo.sys which is the USB Video Class system driver. Given you mentioned there's an integrated webcam, possibly faulty internally which end-result would ultimately require a repair and or replacement. However, first, let's enable Driver Verifier to see what else it may be able to tell us. Something may be conflicting:

Driver Verifier:

What is Driver Verifier?

Driver Verifier is included in Windows 8, 7, Windows Server 2008 R2, Windows Vista, Windows Server 2008, Windows 2000, Windows XP, and Windows Server 2003 to promote stability and reliability; you can use this tool to troubleshoot driver issues. Windows kernel-mode components can cause system corruption or system failures as a result of an improperly written driver, such as an earlier version of a Windows Driver Model (WDM) driver.

Essentially, if there's a 3rd party driver believed to be at issue, enabling Driver Verifier will help flush out the rogue driver if it detects a violation.

Before enabling Driver Verifier, it is recommended to create a System Restore Point:

Vista - START | type rstrui - create a restore point
Windows 7 - START | type create | select "Create a Restore Point"
Windows 8 - Restore Point - Create in Windows 8

How to enable Driver Verifier:

Start > type "verifier" without the quotes > Select the following options -

1. Select - "Create custom settings (for code developers)"
2. Select - "Select individual settings from a full list"
3. Check the following boxes -
- Special Pool
- Pool Tracking
- Force IRQL Checking
- Deadlock Detection
- Security Checks (Windows 7 & 8)
- DDI compliance checking (Windows 8)
- Miscellaneous Checks
4. Select - "Select driver names from a list"
5. Click on the "Provider" tab. This will sort all of the drivers by the provider.
6. Check EVERY box that is NOT provided by Microsoft / Microsoft Corporation.
7. Click on Finish.
8. Restart.

Important information regarding Driver Verifier:

- If Driver Verifier finds a violation, the system will BSOD.

- After enabling Driver Verifier and restarting the system, depending on the culprit, if for example the driver is on start-up, you may not be able to get back into normal Windows because Driver Verifier will flag it, and as stated above, that will cause / force a BSOD.

If this happens, do not panic, do the following:

- Boot into Safe Mode by repeatedly tapping the F8 key during boot-up.

- Once in Safe Mode - Start > type "system restore" without the quotes.

- Choose the restore point you created earlier.
If you did not set up a restore point, do not worry, you can still disable Driver Verifier to get back into normal Windows:

- Start > Search > type "cmd" without the quotes.

- To turn off Driver Verifier, type in cmd "verifier /reset" without the quotes.
・ Restart and boot into normal Windows.

How long should I keep Driver Verifier enabled for?

It varies, many experts and analysts have different recommendations. Personally, I recommend keeping it enabled for at least 24 hours. If you don't BSOD by then, disable Driver Verifier.

My system BSOD'd, where can I find the crash dumps?

They will be located in %systemroot%\Minidump

Any other questions can most likely be answered by this article:
Using Driver Verifier to identify issues with Windows drivers for advanced users

Regards,

Patrick
 
Perfect, I will do that. Thanks for helping out Stephen, I understand he's busy.
It can happend to anyone! After theses steps, I will get back to you.

Eric
 
Patrick said:
I look forward to your update.

Regards,

Patrick
Click to expand...


Hmmm, I told my sister to activate the verifier...

After she has done it, she turned off the laptop asleep and went to do other things. After a few minutes (around 5) , she realized she forgot to write down something in her document and attempted to wake it up.

There's a problem though : it wouldn't wake up (the keyboard was lighted up but no answers). After many attempts to press the power button, unplugging the charge, etc... it finally came back to life.

Just to be sure, I asked her to repeat the same thing. The problem occured again but this time, after she has shaken the mouse, it brought her to "safe mode" menu. I'm just wondering if I should let the verifier activated or if it has gathered enough informations. Usually, I know verifier shouldn't do anything but this is the first time it occur. She would use her laptop by friday for school...

Eric
 
Hi,

Keep it enabled until she needs it (so Friday). Verifier won't collect any information unless the system CRASHES (blue screens). She (or you, sorry not sure who is doing what here) can check if verifier is successfully enabled by running CMD and typing verifier /query

Regards,

Patrick
 
Patrick said:
Hi,

Keep it enabled until she needs it (so Friday). Verifier won't collect any information unless the system CRASHES (blue screens). She (or you, sorry not sure who is doing what here) can check if verifier is successfully enabled by running CMD and typing verifier /query

Regards,

Patrick
Click to expand...

Hello again,

I'll clarify this. I'm the one who's telling my sister what to do. I began the process of fixing her computer a while ago (while I was at her house) but couldn't complete it. I'm between you and my sister. But, if there's any HUGE instructions, I will go at her place.

On another hand, I cancelled the verifier. For some reasons, the blue screens haven't appeared and made the computer gone worst. In fact, it turned out asleep mode was desactivated...she was often directed to the Safe mode menu, (by shaking the mouse to cancel the sleep mode). Plus, the WIFI pilot got disable (she had no more internet)... i'll wait for further instructions and if you can't answer by friday, I will turn the verifier back on.

Thanks again,
Eric
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top