Random different BSOD's tried many things

[Blikkie]

Hi Sevenforums,

I have been getting random BSOD's for quite a long time now and I can't seem to find what causes them. After doing many google searches, hardware tests, driver updates and shouting at my laptop I decided to register at this forum. I think you guys do an excellent job in helping people out, and I really admire that. I hope you can help me out as well.

I get the following BSOD crashes:

Most Frequent:
irql_not_less_or_equal 0x0000000A

A different one shown recently:
A driver corrupted pool memory for holding pages destined for disk
0x000000DE

The most recent one:
An attempt was made to write to read-only memory
0x0000000BE

What I have already done:
1. memtest86 (4 passes, no errors)
2. Intel processor diagnostic tool (no errors)
3. Successfully ran VGA stress test
4. Succesfully ran seagate HDD test and command CHKDSK
3. SFC /scannow (found an error in "iassdo.dll.mui" that it couldn't repair)
4. Driver verifier (crashes instantly in a BSOD)
5. Downgraded VGA drivers to version specified on Mboard manufacturer website
6. Re-installed WIFI drivers from windows update
7. Re-installed adobe flash player and uninstalled deamon tools (helped some other user on the forum)
8. Maleware bytes and AVG antivirus scan (found nothing)

In the attachments I've added the SF Diagnostic tools results and the DM log collector results. I will also attach the SFC scannow results as it returned an error.

Edit:
The BSOD's seem to appear more often when I am watching movies.

I would really appreciate your help!

Much thanks in advance

 

[HarriePateman]

It seems that you have tried many things.

Can you run Memtest for 9 passes.

And enable Driver Verifer when you get your BSOD upload your most recent DMP File.

 

[Blikkie]

Thanks for replying,

Somehow the Dump folder is empty after a BSOD. I followed all the instructions in the sticky post.
I have set the drop-down box in the start up and recovery settings to small memory dump (256 KB). The total paging file is also set to 16273 MB.

Any idea?:sarc:

Edit:
I ran driver verifier again but the result was an instant crash before windows could finish loading. I had to use a system restore point to recover windows. this time I recieved a BAD POOL CALLER BSOD.
I still cant find a dump file :S

 

[Blikkie]

Ok. I downloaded and added the .reg file for creating the settings needed to generate a minidump file, did a reboot and still no dumpfile after a BSOD.

Somehow the "automatically restart" option doesn't work as well. I waited for an hour but it sticks at the bluescreen.

The last line in the BSOD says "Physical memory dump complete" though.

Update:

While I was searching the web for an answer about the missing dump files I came across a post about a guy that has the same problem. He was getting BSOD's after installing the Intel Rapid Storage Technology driver. He also uses the same hard disk as I (SSHD Seagate Momentus XT).

On another forum I've read that the RST cannot be used with a hybrid HDD. I will uninstall the intel software and see if it helps.

One more question about memtest86: Can I run the test in different segments? (first night 3 passes, second night 3 passes etc.)

 

[HarriePateman]

Okay brilliant keep us updated.

 

[Boozad]

One more question about memtest86: Can I run the test in different segments? (first night 3 passes, second night 3 passes etc.)

No, it has to be all in one go.

 

[Blikkie]

When I enter Computer Management and click on 'Performance' in the left menu I get a strange error.
I stumbled upon it by accident. Is there a possibility it has something to do with the situation?

I have attached a screenshot of the error.

Thanks again for helping me solve the problem!

 

[HarriePateman]

Can you enable Driver Verifier and when you get your BSOD, upload the DMP.

 

[Blikkie]

No I can't because when I enable driver verifier and then do a reboot to complete the setup. It will cause an instant BSOD at windows start-up! I dont even get to see the desktop. It loads and than BAM: BAD_POOL_CALLER.

Then I have to load a restore point to a previous working configuration.

Must be a driver issue than right? :huh:

 

[Blikkie]

I have decided to re-install windows.

Is this the correct order for installing?

1. Windows
2. Chip-set
3. VGA
4. Audio
5. Ethernet
6. Wifi
7. Other drivers

And when Should I do windows update? Before or after installing the drivers?

 

[HarriePateman]

No I can't because when I enable driver verifier and then do a reboot to complete the setup. It will cause an instant BSOD at windows start-up! I dont even get to see the desktop. It loads and than BAM: BAD_POOL_CALLER.

Then I have to load a restore point to a previous working configuration.

Must be a driver issue than right? :huh:

Thats the idea, so we can see what is causing the BSOD.

Once you receive your BSOD, upload the new DMP Files

 

[Blikkie]

Ok. I think there's a misunderstanding here.

I cannot upload .DMP files because they do not appear in the folder "minidump" or anywhere else on my HDD. There is no 'minidump.dmp' or MEMORY.dmp file anywhere on my computer. My computer simply does NOT write a dump file after a crash even though message in the BSOD says "Physical memory dump complete".

I tried everything to fix this but nothing helped.

 

[HarriePateman]

Okay sorry i missed that have a read of this

   Information

If your computer is not creating DMP Files please follow this link: http://www.sevenforums.com/tutorials/174459-dump-files-configure-windows-create-bsod.html

I look Forward to Helping you.

 

[Blikkie]

As I mentioned before, I also followed those instructions. I even downloaded the Create_Minidump_on_BSOD.reg file which also has no effect.

As you can see in the attached image all settings are registered correct. I also Added a D_WORD entry AlwaysKeepMemoryDump to prevent windows 7 from removing the file at start-up. But that also doesn't work.

I give up

 

[HarriePateman]

As I mentioned before, I also followed those instructions. I even downloaded the Create_Minidump_on_BSOD.reg file which also has no effect.

As you can see in the attached image all settings are registered correct. I also Added a D_WORD entry AlwaysKeepMemoryDump to prevent windows 7 from removing the file at start-up. But that also doesn't work.

I give up

Once you have changed the settings you will need to restart the computer, then next time you have a BSOD you will be able to use the SevenFoums tool to retrieve the DMP Files.

 

[Blikkie]

I did fresh install of Windows 7, installed all drivers and updates. I hoped for the problem to disappear but I got a BSOD during the installation of updates.

But!, after the fresh installation my computer does write dump files!!!

Here's the link to the DUMP file:
https://drive.google.com/file/d/0BzxffJHnewwVOXJlZEctR1pTNEE/edit?usp=sharing

I really hope you can help me solve this Harrie! Thank you for all the effort.

 

[Blikkie]

Sorry for the double post. I attached another dump file. This time a minidump.

 

[Blikkie]

In the meanwhile I ran memtest86 for another 8 passes. It found no errors so I think the RAM is fine.

I downloaded Bluescreenview to check my own dumpfiles. It seems that the errors are completely random.
Also the .sys files tagged by the application are different.

Most of the times the error is: IRQL_NOT_LESS_OR_EQUAL but there also different errors: DRIVER_PORTION_MUST_BE_NON_PAGED, MEMORY_MANAGEMENT, SYSTEM_THREAD_EXCEPTION_NOT_HANDLED.

I am going to return the laptop to my retailer to have it cleaned up. I think dust is the problem. I will let you guys know if the problem is solved by then.

 

[Golden]

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {411, fffff683ff804df0, 8ee00002f0260886, fffff683bf804df1}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+6061 )

Followup: MachineOwner
---------

7: kd> !thread
GetPointerFromAddress: unable to read from fffff80002eb9000
THREAD fffffa800ca93040  Cid 0004.009c  Teb: 0000000000000000 Win32Thread: 0000000000000000 RUNNING on processor 7
Not impersonating
GetUlongFromAddress: unable to read from fffff80002df8ba4
Owning Process            fffffa800ca76040       Image:         <Unknown>
Attached Process          fffffa8010551900       Image:         [COLOR="Red"][B]CCC.exe[/B][/COLOR]
fffff78000000000: Unable to get shared data

The .dmp file is inconclusive, but there is a small clue : please uninstall Catalyst Control Center, reboot and do the following:

Please do the following:

Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.
http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html

Driver Verifier will cause your computer to run very sluggishly - this is normal. What it is trying to do is force your system to BSOD and isolate the offending driver/s. When it does, reboot, disable driver verifier, reboot as normal and upload the new dmp file/s here.

I recommend creating a system restore point before turning on driver verifier:
http://www.sevenforums.com/tutorials/697-system-restore-point-create.html

If your system fails to boot to desktop once driver verifier is enabled, turn it off by booting into Safe Mode:
http://www.sevenforums.com/tutorials/69585-safe-mode.html

 

[Blikkie]

The .dmp file is inconclusive, but there is a small clue : please uninstall Catalyst Control Center, reboot and do the following:

Please do the following:

Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.
http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html

Driver Verifier will cause your computer to run very sluggishly - this is normal. What it is trying to do is force your system to BSOD and isolate the offending driver/s. When it does, reboot, disable driver verifier, reboot as normal and upload the new dmp file/s here.

I recommend creating a system restore point before turning on driver verifier:
http://www.sevenforums.com/tutorials/697-system-restore-point-create.html

If your system fails to boot to desktop once driver verifier is enabled, turn it off by booting into Safe Mode:
http://www.sevenforums.com/tutorials/69585-safe-mode.html

Thank you so much for analyzing my dump file! I did a fresh install of windows 7 (again) because all the crashes corrupted Windows Updates and my system files.

I installed the most important components: chipset driver, Intel Management Engine, LAN driver and USB 3.0 drivers. I left the other components as well as the AMD Radeon Graphics driver uninstalled.
I then successfully installed all windows update and had no BSOD for the past 6 hours!!

I will now make a system restore point and try to install the AMD graphics driver as well.

But first I have a couple of more questions:

1. Is it okay to update all components to the latest version using Windows update?

2. The AMD Graphics Auto detect tool says its best to download driver version 14. But, on the motherboard manufacturers website (CLEVO) the latest version available is version 9. Which one should I use?

3. My laptop also has an on board graphics chip; Intel graphics 4000 family. I haven't installed the on board Intel switchable graphics driver yet. Should I do this first, before installing the AMD driver?
And should I download the latest version from the Intel website or should I download the driver offered by CLEVO (older version)?

I hope you can answer my questions, thanks again!