Repeated annoying BSODs troubling a beginner

These cursed bluescreencrashes have suddenly appeared and they are driving me crazy, because I´m no computer guru and my skills are limited.

So, my computer has started crashing every day, even twice a day. I've got no idea what lies beneth this diabolic behaviour. I've done memory tests which havent provided me with any information. I'll attach this dump-file here, if someone wiser than me could be helpful and say what the problem might be. I just want to know whether to drop my computer from the balcony or is it repairable.

So, attached is the SF file which should give information and following info:

On Wed 29.5.2013 16:13:38 GMT your computer crashed
crash dump file: C:\windows\Minidump\052913-9484-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)
Bugcheck code: 0xD1 (0xFFFFF7FFC57934E7, 0xD, 0x8, 0xFFFFF7FFC57934E7)
Error: DRIVER_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 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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

So I am helpless. I'd be thankful if someone wiser expert could give me hints how to fix this problem.

Thanks in advance,

Miksu

ps. this is my first post, please advise if it is missing something or so

koolkat77 said:

Hi

Allot of information is missing from your zip, please follow Blue Screen of Death (BSOD) Posting Instructions Grab All and upload them to the forum.

Sorry, my bad. Hopefully this package holds the needed information!

koolkat77 said:

Based on the one dump file uploaded, here are the recommendations:

Daemon Tools/Alcohol %

Code:

dtsoftbus01.sys             Fri Jan 13 19:45:46 2012 (4F10358A)

Daemon Tools (and Alcohol % software) are known to cause BSOD's on some Win7 systems (mostly due to the sptd.sys driver, although we have seen dtsoftbus01.sys blamed on several occasions). Please uninstall the program, then use the following free tool to ensure that the troublesome sptd.sys driver is removed from your system (pick the 32 or 64 bit system depending on your system's configuration): DuplexSecure - FAQ

• As an alternative, many people recommend the use of Total Mounter or Magic ISO

Security App

Crashes indicate Avast! and Comodo being a possible cause. Remove them and replace with Microsoft Security Essentials to see if it provides more stability. Uninstallers (removal tools) for common antivirus software. Microsoft Security Essentials and Malwarebytes are recommended from a strict BSOD perspective. They do not cause blue screens on the system as other AV products do.

Microsoft Security Essentials, Free antivirus for windows and Malwarebytes Anti-Malware Free

   Information

• Do not start the free trial of MalwareBytes, unselect that option when prompted.
  
  
• Update and make full scans with both separately.

SFC /scannow to check windows for corruption:
How to Repair Windows 7 System Files with System File Checker
1. Click Start
2. In the search box, type Command Prompt
3. In the list that appears, right-click on cmd.exe and choose Run as administrator
4. In the command window that opens, type

SFC /scannow

and hit enter.

Thank you very much for this information. I've included an updated info file here, the last one didn't hold the right info.

koolkat77 said:

miksu said:

koolkat77 said:

Hi

Allot of information is missing from your zip, please follow Blue Screen of Death (BSOD) Posting Instructions Grab All and upload them to the forum.

Sorry, my bad. Hopefully this package holds the needed information!

Thanks. Please perform the steps below in addition to the ones on post # 3

Is the firmware for your SSD up-to-date?

Check for one and see if the stability returns.

Start up
Keep less stuff at the start-up. Only anti-virus, this helps avoid driver conflicts and improves time to log in to windows.

Troubleshoot a Problem by Performing a Clean Startup in Windows 7 or Vista
How to Change, Add, or Remove Startup Programs in Windows 7

Please run these tests and report back the results

1. SFC /scannow to check windows for corruption - SFC /SCANNOW Command - System File Checker
2. Disk check for errors on the hard drive - How to Run Disk Check in Windows 7
3. Troubleshoot applications by a clean boot - Troubleshoot Application Conflicts by Performing a Clean Startup
4. Memtest86+ paying close attention to part 3 - RAM - Test with Memtest86+
5. Hard drive test from HDD mfg website - Hard Drive Diagnostic Procedure

Ok. All drivers are up-to-date. Daemon tools is removed. I changed the anti-virus and firewall to microsoft's own versions. Hard drives are checked and ok. Start-up is cleaned. I ran SFK/scannow yesterday and no problems there. I'm not able to perform tests number 4 and five at this point. Let's see if these changes are enough. Otherwise I'll continue with these last tests and report back. I´m very grateful for your help and expertise here, koolkat77. With experts like you even us computer-dummies may be able to solve these problems. :)

So, I took all the step I mentioned in my previous post but problems keep haunting me. So frustrating . In addition I ran the memory diagnostic tool mdsched which found nothing. WhoCrashedMe gave this analysys:

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

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 that cannot be identified at this time.


I've also tried to run DriverVerifier but my Windows wouldn't even start after that. So we keep narrowing the problems down..I just wondered if the reason for all this mess was my over-clocked processor? Or is it a software problem, for sure?

Well, all that's left are MemTest86 and hard drive test you mentioned before. After that I'm helpless . If the recent info in the attached file doesn't give any more helpful information, that is.

But, I'd be very grateful if you could check the file. I'll have to do the memcheck when I can.

Thanks in advance:)

Miksu