[Philippe007]

Hi all !
I do have a problem : I get a blue screen when shutting down Vista. If I start in protective mode I can restart with no blue screen it also works with protective mode with the lan parameters activated.
My computer is a HP Pavillon dv6 Notebook PC Intel Core 2 Duo CPU 2,4 Ghz Ram 4 Giga 32 bit OS
I slowly get nuts ! I can't re-install my printer : Brother MFCN 5840 CN
Can you help ?

PS Sorry for my bad english my mother tongue is french...

[Advertisements]

Welcome to GeekstoGo

Your English is very much better than my French.
Bienvenue


Please download this
http://www.resplende...rashedSetup.exe
and run the program click on the analyse tab and if you receive the message scroll down for the results please do so.
Then copy those results by highlighting and right click copy and then on your reply right click and paste please.

[Macboatmaster]

Welcome to GeekstoGo

Your English is very much better than my French.
Bienvenue


Please download this
http://www.resplende...rashedSetup.exe
and run the program click on the analyse tab and if you receive the message scroll down for the results please do so.
Then copy those results by highlighting and right click copy and then on your reply right click and paste please.

[Philippe007]

Thanks for your early answer. You'll find below the report. I think that the other mentionned dumps are not really relevant : old stories. But if you want me to send them dont hesitate to ask for. Thanks for your help
Philippe

--------------------------------------------------------------------------------
System Information (local)
--------------------------------------------------------------------------------

computer name: PC-DE-MALAGNY
windows version: Windows Vista Service Pack 2, 6.0, build: 6002
windows dir: C:\Windows
CPU: GenuineIntel Intel® Core™2 Duo CPU P8600 @ 2.40GHz Intel586, level: 6
2 logical processors, active mask: 3
RAM: 3217297408 total
VM: 2147352576, free: 1960402944



--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.


On Mon 07.11.2011 17:13:40 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini110711-10.dmp
This was probably caused by the following module: tcpip.sys (tcpip+0x9D065)
Bugcheck code: 0xD1 (0x14, 0x2, 0x0, 0xFFFFFFFF8BAA7065)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\tcpip.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: TCP/IP Driver
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.


On Mon 07.11.2011 17:13:40 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: tcpip.sys (tcpip+0x9D065)
Bugcheck code: 0xD1 (0x14, 0x2, 0x0, 0xFFFFFFFF8BAA7065)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\tcpip.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: TCP/IP Driver
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.


On Mon 07.11.2011 15:06:48 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini110711-09.dmp
This was probably caused by the following module: tcpip.sys (tcpip+0x9D065)
Bugcheck code: 0xD1 (0x14, 0x2, 0x0, 0xFFFFFFFF8B7AE065)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\tcpip.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: TCP/IP Driver
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.


On Mon 07.11.2011 14:37:56 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini110711-08.dmp
This was probably caused by the following module: tcpip.sys (tcpip+0x9D065)
Bugcheck code: 0xD1 (0x14, 0x2, 0x0, 0xFFFFFFFF8BAA2065)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\tcpip.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: TCP/IP Driver
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.


On Mon 07.11.2011 13:56:51 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini110711-07.dmp
This was probably caused by the following module: tcpip.sys (tcpip+0x9D065)
Bugcheck code: 0xD1 (0x14, 0x2, 0x0, 0xFFFFFFFF8BAA0065)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\tcpip.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: TCP/IP Driver
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.


On Mon 07.11.2011 13:34:48 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini110711-06.dmp
This was probably caused by the following module: tcpip.sys (tcpip+0x9D065)
Bugcheck code: 0xD1 (0x14, 0x2, 0x0, 0xFFFFFFFF8B7AD065)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\tcpip.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: TCP/IP Driver
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.


On Mon 07.11.2011 13:11:27 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini110711-05.dmp
This was probably caused by the following module: tcpip.sys (tcpip+0x9D065)
Bugcheck code: 0xD1 (0x14, 0x2, 0x0, 0xFFFFFFFF8B7AF065)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\tcpip.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: TCP/IP Driver
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.


On Mon 07.11.2011 12:34:03 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini110711-04.dmp
This was probably caused by the following module: tcpip.sys (tcpip+0x9D065)
Bugcheck code: 0xD1 (0x14, 0x2, 0x0, 0xFFFFFFFF8BAA9065)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\tcpip.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: TCP/IP Driver
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.


On Mon 07.11.2011 09:35:30 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini110711-03.dmp
This was probably caused by the following module: tcpip.sys (tcpip+0x9D065)
Bugcheck code: 0xD1 (0x14, 0x2, 0x0, 0xFFFFFFFF8B7AF065)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\tcpip.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: TCP/IP Driver
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.


On Mon 07.11.2011 09:05:44 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini110711-02.dmp
This was probably caused by the following module: tcpip.sys (tcpip+0x9D065)
Bugcheck code: 0xD1 (0x14, 0x2, 0x0, 0xFFFFFFFF8BFAA065)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\tcpip.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: TCP/IP Driver
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.


On Mon 07.11.2011 08:20:41 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini110711-01.dmp
This was probably caused by the following module: tcpip.sys (tcpip+0x9D065)
Bugcheck code: 0xD1 (0x14, 0x2, 0x0, 0xFFFFFFFF8BFA7065)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\tcpip.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: TCP/IP Driver
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.


On Sun 06.11.2011 21:28:17 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini110611-02.dmp
This was probably caused by the following module: tcpip.sys (tcpip+0x9D065)
Bugcheck code: 0xD1 (0x14, 0x2, 0x0, 0xFFFFFFFF8C29D065)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\tcpip.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: TCP/IP Driver
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.


On Sat 05.11.2011 18:26:47 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini110611-01.dmp
This was probably caused by the following module: tcpip.sys (tcpip+0x9D065)
Bugcheck code: 0xD1 (0x14, 0x2, 0x0, 0xFFFFFFFF8BFA9065)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\tcpip.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: TCP/IP Driver
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.


On Sat 05.11.2011 09:03:27 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini110511-02.dmp
This was probably caused by the following module: tcpip.sys (tcpip+0x9D065)
Bugcheck code: 0xD1 (0x14, 0x2, 0x0, 0xFFFFFFFF8C2A4065)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\tcpip.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: TCP/IP Driver
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.


On Sat 05.11.2011 08:53:36 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini110511-01.dmp
This was probably caused by the following module: tcpip.sys (tcpip+0x9D065)
Bugcheck code: 0xD1 (0x14, 0x2, 0x0, 0xFFFFFFFF8BFAA065)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\tcpip.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: TCP/IP Driver
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.



--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

49 crash dumps have been found and analyzed. Only 15 are included in this report.
Read the topic general suggestions for troubleshooting system crashes for more information.

Note that it's not always possible to state with certainty whether a reported driver is actually responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.

[Macboatmaster]

Run a system file check
Here is how

Use the System File Checker tool (SFC.exe) to determine which file is causing the issue, and then replace the file. To do this, follow these steps:

• Open an elevated command prompt. To do this, click Start, click All Programs, click Accessories, right-click Command Prompt, and then click Run as administrator. If you are prompted for an administrator password or for a confirmation, type the password, or click Allow.
• Type the following command, and then press ENTER: sfc /scannow. The sfc /scannow command scans all protected system files and replaces incorrect versions with correct Microsoft versions.

To leave the command prompt type EXIT and key enter.


If that does not solve the problem please go to Device Manager, that is click the Windows button (Start) right click Computer, click Properties and then click Device Manager on the left pane.
On the View tab click Show hidden devices.
On the Non plug and play entries, expand and on the TCP/IP entries are there any warning marks - probably yellow.

Edited by Macboatmaster, 08 November 2011 - 07:23 AM.

[Philippe007]

Thanks again.
I did procedure 1. and 2. Got a message saying that not all files had been repaired, but there is a CBS.log log file where on can find details ! I can't ! I did attached the log file for your inspection.
I then went to the non plug and play driver and found only one yellow mark on a driver called SRTSPX. No other yellow mark. If you need this driver I can send it to you (I have no idea what it is).
Thanks for helping

[Macboatmaster]

RUN THE SFC again, sometimes it will repair what it could not the first time on the next run

The next step is a little complicated please take your time and ensure youn type the cmds correctly

To determine which files could not be repaired by the System File Checker tool, follow these steps:

• Open an elevated command prompt.
• Type the following command, and then press ENTER: findstr /c:"[SR]" %windir%\Logs\CBS\CBS.log >%userprofile%\Desktop\sfcdetails.txt
• Note 4 below
• The Sfcdetails.txt file contains details from every time that the System File Checker tool has been run on the computer. The file includes information about files that were not repaired by the System File Checker tool. Verify the date and time entries to determine the problem files that were found the last time that you ran the System File Checker tool.
• Type sfcdetails.txt in Search programs and files and press Enter.
  
  The Sfcdetails.txt file uses the following format: Date/Time SFC detail

The following sample log file contains an entry for a file that could not be repaired:2007-01-12 12:10:42, Info CSI 00000008 [SR] Cannot repair member file [l:34{17}]"Accessibility.dll" of Accessibility, Version = 6.0.6000.16386, pA = PROCESSOR_ARCHITECTURE_MSIL (8), Culture neutral, VersionScope neutral, PublicKeyToken = {l:8 b:b03f5f7f11d50a3a}, Type neutral, TypeName neutral, PublicKey neutral in the store, file is missing

If the System File Checker tool cannot repair a file, follow these steps:

• At an elevated command prompt, type the following command, and then press ENTER: takeown /f Path_And_File_NameFor example, type takeown /f E:\windows\system32\jscript.dll.
• Type the following command, and then press ENTER to grant administrators full access to the file: icacls Path_And_File_Name /GRANT ADMINISTRATORS:F For example, type icacls E:\windows\system32\jscript.dll /grant administrators:F.
• Type the following command to replace the file with a known good copy of the file: Copy Path_And_File_Name_Of_Source_File Path_And_File_Name_Of_DestinationFor example, type copy E:\temp\jscript.dll E:\windows\system32\jscript.dll.

I am sure you know but the long cmds listed can of course be copied and pasted from this post.

OR from the Microsoft article
http://support.microsoft.com/kb/929833


An easier copy and paste for you
findstr /c:"[SR]" %windir%\Logs\CBS\CBS.log >%userprofile%\Desktop\sfcdetails.txt

Edited by Macboatmaster, 08 November 2011 - 10:04 AM.

[Macboatmaster]

yellow mark on a driver called SRTSPX

Do you have
Norton Internet Security?

[Philippe007]

Hi,
Ihad no time to follow the proceduresw, will do that this afternoon.
No, I don't have Norton. I have Zonealarm pro

[Macboatmaster]

That HP notebook came with a Norton trial, that warning on SRTSPX is a Norton driver. It is I am sure left over from when the Norton trial was uninstalled.
Do not worry about it for the time being..
It is not the cause of the problem

Here will confirm what I am telling you
http://h30434.www3.h...oot/td-p/184724

Edited by Macboatmaster, 09 November 2011 - 08:19 AM.

[Philippe007]

Sorry but unable to find : sfcdetails.txt.... What am I doing wrong ?
Thanks.

[Macboatmaster]

findstr /c:"[SR]" %windir%\Logs\CBS\CBS.log >%userprofile%\Desktop\sfcdetails.txt

Start - in search type cmd.
DO NOT key enter.
At the cmd above right click and click run as admin.
PASTE that line above at the cmd prompt.

Key enter.
Wait for the cmd window to return to the prompt
Type exit.
Key enter.

The results are in a notepad file on your desktop.

Did you see my advice to RUN SFC again, as sometimes what cannot be fixed the first run is the second.

[Philippe007]

Hi,
1. I did ran the SFC 3 times with no success
2. I can't paste anything in the "cmd" screen I have to type
3. When I type this command : findstr /c:"[SR]" %windir%\Logs\CBS\CBS.log >%userprofile%\Desktop\sfcdetails.txt I get a message saying that the "road access" is not found.
Hence I am stuck.
Thanks for helping.

[Macboatmaster]

When you are in the cmd prompt you simply right click and click paste.
Having right clicked on the entry I sent you in post 11 and then clicked copy.
Then at the cmd prompt when you right click, is paste available or is it greyed out.
If it is available, and you click it does that cmd appear, when you then key Enter.
What is the exact message please.


If that still does not work, ignore the files that cannot be found and run a chkdsk.
Here is how
1. Open an elevated cmd prompt, that is as you did for the sfc.
2. Type at the prompt
chkdsk /r - note space between chkdsk and /r.
3. Agree to run on restart.
Type exit and key enter.
Restart and please do NOT interrupt the chkdsk.

If you watch the results, check that there are no bad sectors and no bad file records.
If you miss the results
See this and then check the results.
They are in Event Viewer, Application, Wininit.
http://www.sevenforu...viewer-log.html

[Philippe007]

For now :
For pasting : Thanks it works with the right click but not with the ctrl-v !
But it does not work I still get the same message.
The exact message is :Le chemin d'accès spécifié est introuvable. Yes in french ! That's why I sent you an approximate translation.
I will run the check disk now

[Macboatmaster]

I have it now the translation is

The specified path was not found


1. That would usually indicate that you were typing it incorrectly, but if you HAVE copied and pasted it that cannot be the case.

Leave that for the time being, we will return to it if we have to.

2. After the chkdsk has completed AND you have either watched the results or checked them and there ARE no bad sectors found and NO file errors found then proceed as below. at 3.

IF THERE were file errors found test again NOW and se if you still get the blue screen.

IF there are bad sectors found send me a copy of the test results please.

3. Please Run the PCPitstop.com OverDrive Full Tests

Here's how:

You must use your Internet Explorer for this procedure. (doesn't work so well in Firefox or others).

Go to: http://www.pcpitstop.com
Click on "Free Computer Check-up" listed below PC Pitstop OverDrive
In the User Login - Click on "Sign up FREE!" OR YOU CAN RUN THE TEST ANON. without signing up. - you will see that at the end of that screen. The results will still be saved long enough for me to look at them.
You'll need to submit a valid email address and create your own password, then click - Create Account(button)

Now enter your email address and password to Log in, Select - Scan this system Now!(button)
You will then be asked to download an ActiveX component and allow it to install.
It is safe and does not compromise your privacy.
Follow the on-screen prompts to install the ActiveX and to allow the Full Tests to be run on your machine.

The Full Tests take about 2 1/2 - 3 minutes on most machines.
When complete, a Results - Summary - Recommended Fixes will be displayed.

Please post the URL internet address, from your Results, back here into this Topic Thread so that we can review the configuration.

Note: During the graphics 2D and graphics 3D testing, your screen will display some rapidly moving objects.
If you are sensitive to visual flashing, it may cause dizziness. Therefore, look away from the screen during that portion of the testing.


While PCPitstop does offer a variety of Paid Products, the PCPitstop OverDrive testing is FREE. Please ignore the references to Paid Products. We prefer to provide manual solution instructions that you can apply directly to your machine.

Edited by Macboatmaster, 10 November 2011 - 12:52 PM.