Repeated annoying BSODs troubling a beginner

[miksu]

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:

[FONT=Segoe UI, Arial]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: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x75C00)
Bugcheck code: 0xD1 (0xFFFFF7FFC57934E7, 0xD, 0x8, 0xFFFFF7FFC57934E7)
Error: [FONT=Segoe UI, Arial]DRIVER_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 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.

[/FONT]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]

Hi

Allot of information is missing from your zip, please follow http://www.sevenforums.com/bsod-help-support/96879-blue-screen-death-bsod-posting-instructions.html Grab All and upload them to the forum.

 

[koolkat77]

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

Daemon Tools/Alcohol %

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

• :warn: Do not start the free trial of MalwareBytes, unselect that option when prompted.
  
  
  
  
  
• :tip: 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.

 

[miksu]

Hi

Allot of information is missing from your zip, please follow http://www.sevenforums.com/bsod-help-support/96879-blue-screen-death-bsod-posting-instructions.html Grab All and upload them to the forum.

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

 

[miksu]

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

Daemon Tools/Alcohol %

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

• :warn: Do not start the free trial of MalwareBytes, unselect that option when prompted.
  
  
  
• :tip: 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]

Hi

Allot of information is missing from your zip, please follow http://www.sevenforums.com/bsod-help-support/96879-blue-screen-death-bsod-posting-instructions.html 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

 

[miksu]

Hi

Allot of information is missing from your zip, please follow http://www.sevenforums.com/bsod-help-support/96879-blue-screen-death-bsod-posting-instructions.html 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.

 

[koolkat77]

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.

Happy to help!
Keep us posted, good luck

 

[miksu]

Continuing BSOD 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:

[FONT=Segoe UI, Arial]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.
[/FONT]
[FONT=Segoe UI, Arial]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

[/FONT]

 

[koolkat77]

Your processor doesn't seem to be overclocked to me.

[I]CPUID:        "Intel(R) Core(TM) i7-3770K CPU @ 3.50GHz"
MaxSpeed:     3500
CurrentSpeed: 3500
[/I]

It's hard to say anything from the current dumps so please proceed with memtest and hard drive test and let us know the results.

 

[miksu]

Severe problems while analyzing conditions of hard draives

Ok, sorry I thought my computer was overclocked. I've tried to perform diverse diagnostics on hard drives using CristalDisc, HDTune pro, WD diagnostics tool. But performing these tests have crashed my computer or they have resulted in other program crashes. As far I understood I had some problems with my old, portable hard drive E. It had "too many bad sectors to be anayzed". Not a good sign? The booting windows drive C: seemed to be OK, but analyzing the data was quite challenging to me. Hopefully you can figure out something of them I'll attach the analytics results, which I could perform. Some tests took over 4 hours, and because my computer BSODed every now and then results could not be gathered. Not even in safe mode could the tests be done correctly. I will continue with RAM diagnostics and possibly wider HD analysis. Hopefully the info this far could give some idea of the status of my hard drives.

Thank you in advance!

Miksu

 

[Britton30]

Yes, "too many bad sectors to be anayzed" is a bad sign and that drive may fail unexpectedly.
Check for a firmware update for your SSD, but be careful, some updates will wipe your drive.
Go in your UEFI/BIOS, hardware section and let us know what the volt readings are for 12V, 5V, and 3.3V.

 

[miksu]

Problems with entering the bios

Thanks, I'll try to investigate the BIOS readings. But, sorry, a stupid question again: I tried to enter the BIOS after booting (del button??), but it required a password? F******G what, which password?! I don't recall ever editing my BIOS nor changing any password. Is there a general one that could work even here? Gosh, I'm getting tired of asking stupid, simple questions...I'm sorry for that. This is just a new territory for me, all this stupid tech fun I've been forced to go through Thanks for your patience with a total computer-dummy...

 

[Britton30]

did you build this or buy from someone? There is no "general" BIOS password. You could try removing the coin battery (CMOS battery) for 30 seconds with power OFF and re-try. This will reset the board to default settings though.

 

[miksu]

did you build this or buy from someone? There is no "general" BIOS password. You could try removing the coin battery (CMOS battery) for 30 seconds with power OFF and re-try. This will reset the board to default settings though.

This computer was bought from and assembled by a computer store. Well, I have to try this trick you suggested. I'll have to check the motherboard blueprints. Thanks for the tip.

 

[miksu]

Yes, "too many bad sectors to be anayzed" is a bad sign and that drive may fail unexpectedly.
Check for a firmware update for your SSD, but be careful, some updates will wipe your drive.
Go in your UEFI/BIOS, hardware section and let us know what the volt readings are for 12V, 5V, and 3.3V.

So, with the help of you guys I was able to open BIOS. I checked all the voltage readings and they seemed to be normal: 3,3V = +3,360V, 5V=+5,040V, 12V=12,192V. Or at least I think so. There was no available firm ware update on Kingston website.

Miksu

 

[essenbe]

Once tou replace the CMOS battery, first boot go into bios, press F5 (reset to defaults, answer yes whe it asks ), set your sata controller to AHCI (should be by default) Set the boot order to CD/DVD drive 1st boot device and SSD to second boot device, go into the extreme tweeker section and set AI Overclock tuner to XMP, make sure the dram frequency is correct for your ram, go to the dram timings and set the first 4 timings to manufacturers specs (it should already be set to that, but check) close that by hitting the arrow button in the top left corner, you should be back at the main menu. In the main menu scroll down to Dram voltage and set that to manufacturer's specs. If you don't know the frequency, timings and voltage it will be on the package the ram came in and on a sticker on the side of the ram sticks inside the machine. Leave everything else set to default values. In the top right click Exit, it will ask whether to save and exit or several other options. Click save and exit. see how it runs now. and check back with us. Between all of us, we will try to straighten you out. Who overclocked your board and do you know what settings he used and if it was stress tested before you received it? What was it overclocked to? If you don't already have them, please download and install CPUz, GPUz, and Core Temp. When you install these programs, uncheck all the junk software they want to install with it. Please advise what CPU cooler you have and what brand and wattage Power supply unit you are using.

 

[essenbe]

That's good. See how it runs, we can worry about bios later. For right now please answer the questions above and download and install the programs I asked, some of which you may already have. The links may provide updated versions of those programs.

 

[miksu]

That's good. See how it runs, we can worry about bios later. For right now please answer the questions above and download and install the programs I asked, some of which you may already have. The links may provide updated versions of those programs.

Sure thing, I'll get into that right away. Let's see how it goes. It might take some time...

 

[Britton30]

Yup, don't try to hurry through the steps and make things worse, we'll be here.