Random BSOD Screen and DMP attached

[Danielhuber]

I'm have a "random" crash, that occurs at different times, sometimes when in IE, othertimes in Word, and other times when doing nothing! Or simply don't initialize. Sometimes the computer crashes but maintain the screen, only freezes all. Other times the BSOD comes.

When system re-starts, try the "initialization recovery", but nothing.

I have installed (formated) the Windows 2 times (last this week) , it's a fresh install, Windows 7 retail and updated to SP1, x64. Drivers are all updated and all devices have their drivers correctly installed. It's a clean system, with Avira (antivirus) and no overclock or something like. Normal use. I used memtest86 for 10 hours and all it's ok.

This is the last BSOD screen:

View attachment 182431

The part above don't have any information, only Windows saying that "if occurs many times, i have to contact the administrator"...

Attached the required (dump and perfmon files).

Thanks for your help, this forums is the last way to solve my problem...

And sorry for my bad english write, i'm from Brasil.

 

[zigzag3143]

Three possible issues


1-KORGUM64.SYS. I can find no information on this in google (in english). Just to be sure download Malwarebytes and run it.


2-sptd.sys

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

They use a driver, found in your dmp, called sptd.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.



3-PaeFireStudioMidi. Was active in this crash. Especially if it is USB.

 

[Danielhuber]

Thanks zigzag3143.

1-KORGUM64.SYS. I can find no information on this in google (in english). Just to be sure download Malwarebytes and run it.

It's a driver for this controllers (i think), they are USB attached. Anyway, i will use malwarebytes on it and disconnect them to see if the problem persists.

2-sptd.sys

Yes i will do. But i'm using Daemon for many years and the problem never occurs.

3-PaeFireStudioMidi. Was active in this crash. Especially if it is USB.

It's the MIDI driver of my Audio interface (that is firewire 400). This instals with the interface driver as one package and is dificult to remove only (i don't use the MIDI part of the interface). But since i'm using this same driver and interface for years and the problem appear only 3-4 weeks ago, i will let this and try first the other 2 options you say me.

Well, thanks again, i will try and come back here with the results.

Daniel

 

[Danielhuber]

Hi all!

I make the changes sugested by zigzag3143 but no sucess... As i have mentioned, sometimes is a BSOD adn sometimes the computer freezes at all, no CTRL+ALT+DEL and nothing works, i have to restart manually.

This morning, this (freeze) happens.

I THINK these freezes and BSODS have the same cause, but, what?

 

[zigzag3143]

Hi all!

I make the changes sugested by zigzag3143 but no sucess... As i have mentioned, sometimes is a BSOD adn sometimes the computer freezes at all, no CTRL+ALT+DEL and nothing works, i have to restart manually.

This morning, this (freeze) happens.

I THINK these freezes and BSODS have the same cause, but, what?

Freezes you check in event viewer

There are several ways to find what the problem is. The best is to go into event viewer (type eventvwr in search). Event viewer (local) and look for errors listed in the last day, week, etc. Then go to the windows log>application tab. Finally the windows Logs>system tabs.

You want to look for all errors (they have red in the left column ).

When you find them you want to look for critical errors that say app hang, app crash, or anything that relates to the problem.

When you find them please note the event ID, and the source codes and tell us what they are.


BSOD's you upload the DMP's

 

[Danielhuber]

MANY errors today, specially in the moments that the PC freezes are related to this:

ID: 5
Source: BTHUSB

"The Bluetooth driver expected an HCI event with a certain size, but not received."

This appear in all the freezes i have today. In the same minute before.

Have some other errors, but in times that the machine don't freezes.

I have a generic bluetooth USB adapter in a USB slot, will this is the cause?

 

[Danielhuber]

AT 22:19 another freeze.

Restarted and in the Event viewer > Windows Logs > System:

View attachment 182578

(I have only disconnected that USB Bluetooth adapter hours ago)

 

[Danielhuber]

Other freezes today, and nothing strange in event viewer (is like the post above)

 

[Danielhuber]

Another BSOD now.

The screen:

View attachment 183246

The Event at the time BSOD occurs:

View attachment 183248

And the other files are attached.

View attachment 183249

 

[zigzag3143]

Another BSOD now.

The screen:

View attachment 183246

The Event at the time BSOD occurs:

View attachment 183248

And the other files are attached.

View attachment 183249

These crashes were caused by memory corruption. Please run these two tests to verify your memory and find which driver is causing the problem.


1-Memtest.

*Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Memtest86+ - Advanced Memory Diagnostic Tool

*Boot from the CD, and leave it running for at least 5 or 6 passes.

Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot.

Test the sticks individually, and if you find a good one, test it in all slots.

http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html



2-Driver verifier

I'd suggest that you first backup your data 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.

http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html