BSOD and Black Screen at random intervals

EdwinR · 09 Apr 2012

Dear experts!

I receive BSOD and black screens at random interval. Even if I have done a clean install. I also changed from Norton to AVG, because the Norton driver could have given me memory problems according to program 'whocrashed'.

Memtest gives at random a fault. Sometimes 1 times in 6 hours or nothing...

I have attached the required logs. I hope someone can take a look at it. I believe the problem is bad memory or the motherboard... I hope it will be just bad memory.

Thanks in advance!

Edwin

-------------------------------------------------------------------------------------------
Is Windows 7 Ultimate
- x86 (32-bit) or x64 ? x64
- the original installed OS on the system? Vista
- an OEM or full retail version? Full retail
- OEM = came pre-installed on system Vista OEM (HP system)
- Full Retail = you purchased it from retailer

- What is the age of system (hardware)? +/- 3 years

- What is the age of OS installation (have you re-installed the OS?) 6 weeks
-----------------------------------------------------------------------------------------

Who Crashed:
Crash Dump Analysis
</B>
Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Mon 9-4-2012 7:56:43 GMT your computer crashed
crash dump file: C:\Windows\Minidump\040912-42650-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CD40)
Bugcheck code: 0xA (0x400000000000, 0x2, 0x0, 0xFFFFF80002CA48B2)
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 which cannot be identified at this time.

JMH · 09 Apr 2012

*Did you remove Norton via the Uninstall Tool?
{Symantec is a frequent cause of BSOD's.}

http://us.norton.com/support/kb/web_...080710133834EN

* I note you now have AVG.

AVG can be a contributing cause of BSOD'S .

Please remove and replace with Microsoft Security Essentials AT LEAST TO TEST

Download tools and utilities | AVG Worldwide

Microsoft Security Essentials - Free Antivirus for Windows

zigzag3143 · 09 Apr 2012

In addition to JMH's suggestions

Please remove any CD visualization programs such as Daemon Tools and Alcohol 120%.

They use a driver, found in your dmp, called sptd.sys (or dtsoftbus01.sys), that is notorious for causing BSODs.

Use this SPTD uninstaller DuplexSecure - Downloads DuplexSecure - FAQ

when you're done you can use this Freeware:

MagicISO Virtual CD/DVD-ROM (MagicDisc) in its place

Using MagicISO to create ISO image files

EdwinR · 09 Apr 2012

I have uninstalled Norton via the Uninstall Tool. I will replace AVG with MS security essentials. Thanks.

JMH · 09 Apr 2012

EdwinR said:

I have uninstalled Norton via the Uninstall Tool. I will replace AVG with MS security essentials. Thanks.

At least for testing purposes... { I too use AVG.}

EdwinR · 09 Apr 2012

Thanks for your input zigzag. I did not install SPTD during the install of Daemon. This was confirmed when I tried to uninstall it with th X64 uninstaller. It displayed no uninstall button. I will try MagicIso.

zigzag3143 · 09 Apr 2012

EdwinR said:

Thanks for your input zigzag. I did not install SPTD during the install of Daemon. This was confirmed when I tried to uninstall it with th X64 uninstaller. It displayed no uninstall button. I will try MagicIso.

Related to dtsoftbus01.sys Virtual Bus Driver from DT Soft Ltd

Um this is installed, and from dtsoft (the makers of daemon tools.)

EdwinR · 09 Apr 2012

zigzag3143 said:

EdwinR said:

Thanks for your input zigzag. I did not install SPTD during the install of Daemon. This was confirmed when I tried to uninstall it with th X64 uninstaller. It displayed no uninstall button. I will try MagicIso.

Related to dtsoftbus01.sys Virtual Bus Driver from DT Soft Ltd

Um this is installed, and from dtsoft (the makers of daemon tools.)

...........I must have clicked it via an update of the software or I am confused with my notebook. Anyway, you're absolutely right!!! I removed Daemon tools via configuration screen. I could not click uninstall button of SPDT uninstaller. I have now MagicISO installed.

My desktop hasn't crashed since. Let's keep my fingers crossed!

zigzag3143 · 09 Apr 2012

EdwinR said:

zigzag3143 said:

EdwinR said:

Thanks for your input zigzag. I did not install SPTD during the install of Daemon. This was confirmed when I tried to uninstall it with th X64 uninstaller. It displayed no uninstall button. I will try MagicIso.

Related to dtsoftbus01.sys Virtual Bus Driver from DT Soft Ltd

Um this is installed, and from dtsoft (the makers of daemon tools.)

...........I must have clicked it via an update of the software or I am confused with my notebook. Anyway, you're absolutely right!!! I removed Daemon tools via configuration screen. I could not click uninstall button of SPDT uninstaller. I have now MagicISO installed.

My desktop hasn't crashed since. Let's keep my fingers crossed!

You know daemon tools arent the devil incarnate but on some systems they are pure evil.

Fingers crossed;

Ken

EdwinR · 12 Apr 2012

Unfortunately a BSOD happened again. Please see attachment and information below. Memory/motherboard problems?

Crash Dump Analysis
</B>
Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Thu 12-4-2012 8:12:49 GMT your computer crashed
crash dump file: C:\Windows\Minidump\041212-23509-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC80)
Bugcheck code: 0x19 (0x20, 0xFFFFFA8003F23910, 0xFFFFFA8003F23A60, 0x4150007)
Error: BAD_POOL_HEADER
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 a pool header is corrupt.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.