Solved BSOD and Black Screen at random intervals

[EdwinR]

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

[FONT=Segoe UI, Arial][FONT=Segoe UI, Arial]Crash dumps are enabled on your computer.[/FONT]
[/FONT]

[FONT=Segoe UI, Arial]On Mon 9-4-2012 7:56:43 GMT your computer crashed[/FONT]
[FONT=Segoe UI, Arial]crash dump file: C:\Windows\Minidump\040912-42650-01.dmp[/FONT]
[FONT=Segoe UI, Arial]This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x7CD40)
Bugcheck code: 0xA (0x400000000000, 0x2, 0x0, 0xFFFFF80002CA48B2)
Error: [FONT=Segoe UI, Arial]IRQL_NOT_LESS_OR_EQUAL[/FONT]
file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
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.
[/FONT]

 

[JMH]

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

http://us.norton.com/support/kb/web_view.jsp?wv_type=public_web&docurl=20080710133834EN

* 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]

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]

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

 

[JMH]

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]

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]

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]

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]

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]

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

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

[FONT=Segoe UI, Arial][FONT=Segoe UI, Arial]Crash dumps are enabled on your computer.
[/FONT][/FONT]

[FONT=Segoe UI, Arial]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: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x7CC80)
Bugcheck code: 0x19 (0x20, 0xFFFFFA8003F23910, 0xFFFFFA8003F23A60, 0x4150007)
Error: [FONT=Segoe UI, Arial]BAD_POOL_HEADER[/FONT]
file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
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.
[/FONT]

 

[zigzag3143]

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

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

[FONT=Segoe UI, Arial][FONT=Segoe UI, Arial]Crash dumps are enabled on your computer.
[/FONT][/FONT]

[FONT=Segoe UI, Arial]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: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x7CC80)
Bugcheck code: 0x19 (0x20, 0xFFFFFA8003F23910, 0xFFFFFA8003F23A60, 0x4150007)
Error: [FONT=Segoe UI, Arial]BAD_POOL_HEADER[/FONT]
file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
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.
[/FONT]

In this rare instance who crashed is correct. The driver is un-named at the moment.

 

[EdwinR]

Yes, but do you think it is a driver problem and not a hardware problem?

 

[zigzag3143]

Yes, but do you think it is a driver problem and not a hardware problem?

Probably a driver and you can find out which by running verifier.

I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.

 

[EdwinR]

At the moment I will wait with the stress test. The motherboard made some tones.

I have looked inside the desktop and removed the memory modules. One seemed to be not inserted in a stable manner.

I also ran memtest per module for 5 passes. Nothing seen.

No BSOD since. So I hope it is over...

 

[kaybee327]

Hi Folks

Can I join the band wagon please ?

I am having the same problems (multi BSOD and also random reboots )

Attach snip 1 and snip2 are grabs from Bluescreenview and the dump.pdf need rename to dump.dmp due validity of upload extensions ( all three are from the last BSOD). This is all since a reformat of HDD and a clean install. I know I am a bit thick but I do not understand any of this.

Have used mem86 to test ram (2 x 1Gb) with no problems all passes also removed one stick and swapped so any pointers / help please

Keith

 

[JMH]

Hi Folks

Can I join the band wagon please ?

Keith

kaybee327,

Please start your own thread with your unique problem.
That way you will get individual attention.

Thank you for your co operation...

 

[EdwinR]

The computer runs without crashes since last post. I will mark the problem as solved. Thanks for all the help!