Blue screens

Status
Not open for further replies.

Josho495

Posts: 34   +0
I've recently got a few BSOD.

I have not installed any new hardware or drivers.

When the BS occurred, I was playing a game, before that I was on the internet.

I downloaded WhoCrashed and posted the following minidumps.

Cheers.

Any help appreciated.


On Tue 3/03/2009 1:52:57 PM your computer crashed
This was likely caused by the following module: intelppm.sys
Bugcheck code: 0x1000000A (0x7F0C624, 0x1C, 0x0, 0x80545076)
Error: Unknown
file path: C:\WINDOWS\system32\drivers\intelppm.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Processor Device Driver
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



On Tue 3/03/2009 9:56:56 AM your computer crashed
This was likely caused by the following module: sptd.sys
Bugcheck code: 0x1000000A (0x7E4FEB4, 0x1C, 0x1, 0x80502386)
Error: Unknown
file path: C:\WINDOWS\system32\drivers\sptd.sys



On Mon 2/03/2009 1:12:14 PM your computer crashed
This was likely caused by the following module: sptd.sys
Bugcheck code: 0x1000000A (0x7C8E4DC, 0x1C, 0x1, 0x80502386)
Error: Unknown
file path: C:\WINDOWS\system32\drivers\sptd.sys



On Sun 1/03/2009 2:27:29 PM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1000000A (0x7A0F324, 0x1C, 0x1, 0x80502386)
Error: Unknown
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.
 
0xA errors are strong indicators of hardware issues but also drivers trying to access a higher IRQ Level they have no right to. The information you provided also cited Windows drivers in two minidumps that are too general to be of much help.

However, two specifically cite sptd.sys and this driver belongs to Daemon Tools. Try updating and tell us if this brings stability.
 
I uninstalled Daemon tools. Haven't had a problem since. Hope it stays that way.

I'll see how it goes.

Cheers.
 
Unfortunately I received some more errors.

On Sun 15/03/2009 12:07:53 AM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x10000050 (0xF53F88A5, 0x1, 0x8B0F320B, 0x2)
Error: Unknown
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



On Thu 12/03/2009 1:37:53 PM your computer crashed
This was likely caused by the following module: cmdguard.sys
Bugcheck code: 0x1000000A (0x55C9E4, 0x1C, 0x1, 0x80502386)
Error: Unknown
file path: C:\WINDOWS\system32\drivers\cmdguard.sys
product: COMODO Internet Security Sandbox Driver
company: COMODO
description: COMODO Internet Security Sandbox Driver

The first error occurred during boot up.


Any help appreciated.

Cheers.
 
Your probable cause is listed in your information: This was likely caused by the following module: cmdguard.sys

This driver belongs to COMODO.
 
Status
Not open for further replies.
Back