Clevo P170EM random BSOD ntoskrnl.exe

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

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!

Attachment 259141Attachment 259142

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

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

Attachment 259145

Code:

BugCheck 4E, {99, 5d42ef, 0, 5d476f}

Probably caused by : memory_corruption ( nt!MiBadShareCount+4c )

Code:

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.

writhziden said:

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:

• Disk Check

Use this command with Disk Check:

Code:

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:

• RAM - Test with Memtest86+

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.

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.

Attachment 259199

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?

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.

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.