Solved Clevo P170EM random BSOD ntoskrnl.exe

[timduke985]

I am having alot of trouble figuring this one out and would GREATLY appreciate any help. I'm about to the point of ripping my hair out! The last reply I've had from the manufacturer is that they'd look into my problem and get back to me.

I have had this computer for two months and don't want to send it back for warranty repairs because I need it for work. If I send it in I'll have to buy a replacement to use until I get it back. I've been getting random BSOD. They occur sometimes in rapid succession, then won't have another for 2 or 3 hours. I have tried just about everything I can think of to correct this problem.

I have done 2 fresh reinstalls of windows 7 professional 64 bit, completely erasing and formatting my hard drives each time. All critical windows updates have been installed each time. My blue screens point to bad memory, but I've ran memtest86+ for 10 passes and Windows Memory Diagnostic Tool for 10 passes, each with 0 errors. I've ran chkdsk 2 times with 0 errors. I've ran Furmark 1.10.5 and stress tested my GPU for an hour with 0 errors, temps all within normal range. I've ran prime95 for an hour to test the processor with 0 errors, temps within normal range. I've scanned with Malwarebytes, Spybot, and Microsoft Security Essentials numerous times.

Thank you for any time you spend looking at this and helping me with my problem!!!

 

[timduke985]

View attachment 259039

View attachment 259040

 

[Dsprague]

Please run the system file checker:

SFC.EXE /SCANNOW
Go to Start and type in "cmd.exe" (without the quotes)
At the top of the search box, right click on the cmd.exe and select "Run as adminstrator"
In the black window that opens, type "SFC.EXE /SCANNOW" (without the quotes) and press Enter.
Let the program run and post back what it says when it's done.

Once that has been run run through the Hdd Diagnostics tutorial:

Hard Drive Diagnostic Procedure

 

[timduke985]

Ran SFC.EXE /SCANNOW from the command prompt as an administrator and when it was done it said, "

Verification 100% complete.

Windows Resource Protection did not find any integrity violations. "

I'll go through the Hdd Diagnostics tutorial and post back when I'm finished. Thanks!

 

[Dsprague]

I look forward to hearing from you.

 

[timduke985]

Ok, well apparently Crucial does not have a diagnotic program for their ssd's, so I ran both the Seagate and Hitachi diagnostic tools. The one from Hitachi didn't recognize my drives, and the one from Seagate came back with 0 errors and 0 bad sectors!

 

[Dsprague]

OK this is good news it means that you don't have a failing hard drive. So please run driver verifier and allow it to run for 24 hours or until it crashes your computer

Driver Verifier - Enable and Disable

If once driver verifier is enabled you can not boot normally into windows please boot into safe mode by pressing the F8 key before the windows logo appears. Then disable driver verifier from safe mode.

Once driver verifier has caused a crash please run the SF diagnostic tool again and post the new files here.

 

[timduke985]

Will do!

 

[timduke985]

I got a crash about 10 seconds after running driver verifier, here is the new sf diagnostic file. I got the SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION message again.


View attachment 259119

 

[Dsprague]

Interesting its not pointing to any drivers, and your computer passed the memtest just fine with 10 passes and zero errors correct? perhaps it is not your system memory that is causing the problem but your videocards dedicated memory to test this please run this program:

|MG| Video Memory Stress Test 1.7.116 Download

The default settings shoutld do just fine, be sure to check the box that says continuous test when you run the program and let it run for 8 passes (this memtest is significantly faster than the memtest used to test the system memory.)

 

[timduke985]

Sounds good, I'll check it out and get back to you.

 

[timduke985]

It ran fine with the integrated intel graphics, everytime I try to run it with my Nvidia card this error kept popping up. I messed with it for about 30 minutes, can't get it to run!

View attachment 259141View attachment 259142

 

[Dsprague]

It ran fine with the integrated intel graphics, everytime I try to run it with my Nvidia card this error kept popping up. I messed with it for about 30 minutes, can't get it to run!

View attachment 259141View attachment 259142

Had a quick look through the read me file on the video memory stress test, and it seems only the nVidia GeForce 8xxx and 9xxx series cards are supported so that would explain why it wont work. BUT! That's okay because I am having other Ideas and I am going to try getting other eyes on the problem I know you said you already did virus scans but humor me here and run these two programs, they are stand alone so they should not interferer with your normal virus protection:

WDO
Tdsskiller

 

[timduke985]

Will do, thanks again for your time and effort in helping me with this.

 

[timduke985]

Just got another BSOD. PFN_LIST_CORRUPT. Here's the SF Diagnostic file.

View attachment 259145

 

[x BlueRobot]

[COLOR="Red"]BugCheck 4E[/COLOR], {[COLOR="Blue"]99[/COLOR], 5d42ef, 0, 5d476f}

Probably caused by : [COLOR="red"]memory_corruption[/COLOR] ( nt!MiBadShareCount+4c )

Usual causes:  Device driver, memory

Your Page Table Entry seems to be corrupt, this where the operating system stores mappings of virtual addresses to physical addresses.

If you have an SSD, make sure the following are up to date:

• SSD firmware
• BIOS Version
• Chipset Drivers
• Hard disk controller drivers/SATA drivers
• If you have a Marvell IDE ATA/ATAPI device, make sure the drivers are up to date from the Intel site or Marvell site and not from your motherboard/vendor support site.

Check for any file system errors and bad sectors using Option #2 of:

• http://www.sevenforums.com/tutorials/433-disk-check.html

Use this command with Disk Check:

chkdsk C: /f /r

memory_corruption doesn't necessary mean that a RAM module is faulty, it can also point to a object which corrupted the RAM at the time of the crash, for instance a corrupted driver or program. Paging files and the CPU caches can also be causes.

Memory:

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

Run Memtest86+ for least 7-8 passes, and preferably overnight as it can take a while to fully complete.

Test each RAM stick individually, if an error is found then move the same RAM stick into the next DIMM slot and test again, if errors are found for the same RAM stick in every available slot then you have a faulty RAM module. On the other hand, if no errors are found in the next slot or the other slots for the same RAM module, then you have a faulty DIMM slot.

Test each RAM stick and every motherboard DIMM slot available.

 

[timduke985]

Ran tdss killer and it came back clean. I'll post the results of the Windows Defender startup scan when I can get it downloaded. I'm offshore in the Gulf of Mexico right now and have trouble downloading large files with the satellite internet going offline from time to time. In the mean time I'll run chkdsk C: /f /r and see what happens. I'll have to check with the people I bought my computer from to see if removing the cover and swapping the ram around voids my warranty or not.

View attachment 259199

 

[timduke985]

I'm pretty sure I figured out what was wrong. Did a little research on raid controllers and found alot of people with Crucial M4 SSD's having issues with Intel Rapid Storage Technology drivers. I remember my raid setup was working before I installed the Intel RST driver that came with my oem driver cd. I uninstalled the Intel RST driver, did a reboot, started driver verifier with the check all drivers option, and did another reboot. My computer has been running with driver verifier on for about an hour and so far so good! I guess I'll leave it running for around 24 hours if it doesn't bsod and call it good if it lasts that long. Any thoughts?

 

[x BlueRobot]

You are right with the IRST drivers, they have been known to cause a few problems, especially BSODs. Leave Driver Verifier running for another 24 hours just to see if any other drivers are found.

 

[timduke985]

So far, so good! Windows has been running for 8 hours with driver verifier enabled and no bsod. I'll let it keep going and post back.