[yabu]

Dear,

I don't have a lot of knowledge of computers and my English is also not excellent but I will try to explain as good as possbile my problem. The last few months I have troubles with at random blue screens. Suddenly my computer shuts down and shows a blue screen with some white text. I googled it and it seems to be a blue screen of death(?). At first sight , I dont know what the problem is. I want to give more information about the blue screen but I don't have the knowledge to analyze the blue screen or what the cause is. I hope somebody can help me to solve the problem.

Many thanks,
Yannick

[Advertisements]

Download BlueScreenView
No installation required.
Double click on BlueScreenView.exe file to run the program.
When scanning is done, go Edit>Select All.
Go File>Save Selected Items, and save the report as BSOD.txt.
Open BSOD.txt in Notepad, copy all content, and paste it into your next reply.

Thanks to Broni for the instructions and program

[rshaffer61]

Download BlueScreenView
No installation required.
Double click on BlueScreenView.exe file to run the program.
When scanning is done, go Edit>Select All.
Go File>Save Selected Items, and save the report as BSOD.txt.
Open BSOD.txt in Notepad, copy all content, and paste it into your next reply.

Thanks to Broni for the instructions and program

[yabu]

Here is the BSOD.txt

Attached Files

•  BSOD.txt   11.88KB   219 downloads

[rshaffer61]

All but one of your errors is a )A bugcheck. Below is the explanation of that error.

0x0000000A: IRQL_NOT_LESS_OR_EQUAL
Typically due to a bad driver, or faulty or incompatible hardware or software. Technically, this error condition means that a kernel-mode process or driver tried to access a memory location to which it did not have permission, or at a kernel Interrupt ReQuest Level (IRQL) that was too high. (A kernel-mode process can access only other processes that have an IRQL lower than, or equal to, its own.)

First question is have you updated any hardware or instaled any new software just prior to this issue starting?

[yabu]

I really can't remember because it's already a long time ago that I had my first blue screen.

When I look back to the installed software, these are the programs that I installed the period when I had my first blue screen :

Microsoft Visual C++ 2010 x64 Redistributable 10.0.40219
Microsoft Visual C++ 2010 x86 Redistributable 10.0.40219
Bullguard
HiJackThis

I don't know what are the first two programs are but I think it's an update from windows.

[rshaffer61]

Your oldest BSOD is from the 15th of this month.
The first two files you posted are windows update files and the last two are actual programs.

Please do the following which will tell me if it is a driver issue or not.


Download WhoCrashed from the link in my signature below
This program checks for any drivers which may have been causing your computer to crash....

Click on the file you just downloaded and run it.
Put a tick in Accept then click on Next
Put a tick in the Don't create a start menu folder then click Next
Put a tick in Create a Desktop Icon then click on Install and make sure there is a tick in Launch Whocrashed before clicking Finish
Click Analyze
It will want to download the Debugger and install it Say Yes
WhoCrashed will create report but you have to scroll down to see it
Copy and paste it into your next reply

http://www.resplendence.com/downloads

[yabu]

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

computer name: YANNICK-PC
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
CPU: GenuineIntel Intel® Core™ i5-2410M CPU @ 2.30GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 4202860544 total
VM: 2147352576, free: 1973858304




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

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Sun 24/02/2013 14:03:31 GMT your computer crashed
crash dump file: C:\Windows\Minidump\022413-12916-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C40)
Bugcheck code: 0xA (0x0, 0x2, 0x0, 0xFFFFF80002C81F52)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sun 24/02/2013 14:03:31 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: dxgmms1.sys (dxgmms1!VidMmInterface+0x9AAB)
Bugcheck code: 0xA (0x0, 0x2, 0x0, 0xFFFFF80002C81F52)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\dxgmms1.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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 that cannot be identified at this time.



On Sat 23/02/2013 20:00:15 GMT your computer crashed
crash dump file: C:\Windows\Minidump\022313-12277-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C40)
Bugcheck code: 0xA (0x0, 0x2, 0x0, 0xFFFFF80002CC6F52)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Fri 22/02/2013 16:28:47 GMT your computer crashed
crash dump file: C:\Windows\Minidump\022213-13244-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C40)
Bugcheck code: 0xA (0x0, 0x2, 0x0, 0xFFFFF80002CD4F52)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Thu 21/02/2013 0:23:18 GMT your computer crashed
crash dump file: C:\Windows\Minidump\022113-13244-01.dmp
This was probably caused by the following module: ndis.sys (0xFFFFF88001964AC4)
Bugcheck code: 0xD1 (0x10, 0x2, 0x0, 0xFFFFF88001964AC4)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\ndis.sys
product: Besturingssysteem Microsoft® Windows®
company: Microsoft Corporation
description: NDIS 6.20-stuurprogramma
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 that cannot be identified at this time.



On Tue 19/02/2013 10:02:43 GMT your computer crashed
crash dump file: C:\Windows\Minidump\021913-11902-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C40)
Bugcheck code: 0xA (0x0, 0x2, 0x0, 0xFFFFF80002C99F52)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Mon 18/02/2013 20:03:56 GMT your computer crashed
crash dump file: C:\Windows\Minidump\021813-12620-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C40)
Bugcheck code: 0xA (0x0, 0x2, 0x0, 0xFFFFF80002CD6F52)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Fri 15/02/2013 21:34:28 GMT your computer crashed
crash dump file: C:\Windows\Minidump\021513-12043-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C40)
Bugcheck code: 0xA (0x0, 0x2, 0x0, 0xFFFFF80002C81F52)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.




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

8 crash dumps have been found and analyzed. No offending third party drivers have been found. Consider configuring your system to produce a full memory dump for better analysis.


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.

[rshaffer61]

OK now we know it is a windows component causing the issue so we will start there.

SFC /Scannow Win7

Go HERE and read the tutorial that shows how to do SFC or System File Checker and running in a Elevated Command Prompt in Vista and Win7.

[yabu]

I scanned it but he didn't find any violations.

[rshaffer61]

OK then lets take a look at what might auto starting and see if there is a issue there.


Download Autoruns from the link in my signature below:

1: Extract the Autoruns Zip file contents to a folder.
2: Double-click the "Autoruns.exe".
3: Click on the "Everything" tab
4: Click the Options at the top of the Window. In the new little window click the box that states Hide Microsoft Services
5: Go to File then to Export As or Save in some versions.
6: Save the file as AutoRuns.txt file instead of the default .arn to a known location like your Desktop.
7: Attach to your next reply.
8: DO NOT do anything till we have had a chance to study the log and reply with suggestions as to what to remove.

[yabu]

I attached the file but I'm not sure I scanned it correctly because I didn't understand step 4: Click the Options at the top of the Window. In the new little window click the box that states Hide Microsoft Services.

Attached Files

•  AutoRuns.txt   77.33KB   163 downloads

[rshaffer61]

Open Autoruns, click on "Logon" tab, and UN-check:

+ "rdpclip"
+ "Adobe ARM"
+ "CitrixReceiver"
+ "QuickTime Task"
+ "SunJavaUpdateSched"





When done restart computer and then:



Download TFC by OldTimer to your desktop

• Please double-click TFC.exe to run it. (Note: If you are running on Vista, right-click on the file and choose Run As Administrator).
• It will close all programs when run, so make sure you have saved all your work before you begin.
• Click the Start button to begin the process. Depending on how often you clean temp files, execution time should be anywhere from a few seconds to a minute or two. Let it run uninterrupted to completion.
• Once it's finished it should reboot your machine. If it does not, please manually reboot the machine yourself to ensure a complete clean.

Download Auslogics Defrag from the link in my signature below. Auslogics Defrag in my opinion is better because:

It does a more comprehensive job at Defragging
It will actually show you what it is doing
At the end of working it will show you how much speed you picked up
You can view a online log of the files that Auslogics defragged
Please do not run any other Auslogics programs other then this one as they may cause unwanted results.

[yabu]

I did every thing you asked for, what should I do now or is the problem probably solved? I really appreciate your great and quick help!

[rshaffer61]

We have taken out possible causes of the issue but you won't know for sure till you run the system for awhile or if there is something specific that causes the issue you can try that.

[yabu]

Ok that's good. I will let you know in a few days of the probem still occurs.
Already many thanks for your help!

Yannick