και ξαφνικά blue screen : (

[LuLa69]

λίγη βοήθεια ρε παιδιά ορίστε τα αποτελέσματα από το WhoCrashed

 

 

System Information (local)

computer name: XXX-PC
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
CPU: GenuineIntel Intel® Core i5-2500K CPU @ 3.30GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 4277264384 total
VM: 2147352576, free: 1914040320


 

Crash Dump Analysis

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Tue 22/10/2013 10:04:38 πμ GMT your computer crashed
crash dump file: C:\Windows\Minidump\102213-40419-01.dmp
This was probably caused by the following module: intelppm.sys (intelppm+0x2F46)
Bugcheck code: 0xD1 (0xFFFFF80000ED7645, 0x2, 0x1, 0xFFFFF88004202F46)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\intelppm.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Processor Device 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 that cannot be identified at this time.



On Tue 22/10/2013 10:04:38 πμ GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: intelppm.sys (intelppm+0x2F46)
Bugcheck code: 0xD1 (0xFFFFF80000ED7645, 0x2, 0x1, 0xFFFFF88004202F46)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\intelppm.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Processor Device 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 that cannot be identified at this time.



On Tue 22/10/2013 9:53:40 πμ GMT your computer crashed
crash dump file: C:\Windows\Minidump\102213-23556-01.dmp
This was probably caused by the following module: tcpip.sys (tcpip+0x7F869)
Bugcheck code: 0xD1 (0xFFFFF87F848AAAF2, 0x2, 0x8, 0xFFFFF87F848AAAF2)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\tcpip.sys
product: Λειτουργικό σύστημα Microsoft® Windows®
company: Microsoft Corporation
description: Πρόγραμμα οδήγησης TCP/IP
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 Mon 21/10/2013 11:19:34 πμ GMT your computer crashed
crash dump file: C:\Windows\Minidump\102113-15818-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)
Bugcheck code: 0x50 (0xFFFFFA806F4A8270, 0x1, 0xFFFFF80002C685E7, 0x5)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 invalid system memory has been referenced.
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

4 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.

 

 

[thomasG4]

Ακολούθησε τις οδηγίες στο post του Gi0

 

http://www.insomnia.gr/topic/434908-bsod%CE%BA%CE%B1%CE%B9-%CE%BC%CE%B5%CF%84%CE%AC-%CF%84%CE%B9/