Dell XPS L702X Crashing to Blue Screen

jsoames,

Download and install Resplendence Software - WhoCrashed

Click on analyze, then copy the information and paste it back here.

Rick

Hi Rick,

Thanks for the help.  Here is the info:

System Information (local)

computer name: ALEX-LAPTOP
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
Hardware: Dell System XPS L702X, Dell Inc. ,
CPU: GenuineIntel Intel(R) Core(TM) i7-2670QM CPU @ 2.20GHz Intel586, level: 6
8 logical processors, active mask: 255
RAM: 8478961664 total

Crash Dump Analysis

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Sun 02/11/2014 10:59:44 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\110314-28875-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x4E (0x7, 0x1122E8, 0x100000000000000, 0x0)
Error: PFN_LIST_CORRUPT
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 the page frame number (PFN) list is corrupted.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sun 02/11/2014 10:59:44 PM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x4E (0x7, 0x1122E8, 0x100000000000000, 0x0)
Error: PFN_LIST_CORRUPT
Bug check description: This indicates that the page frame number (PFN) list is corrupted.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sun 02/11/2014 10:54:29 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\110214-27861-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0xEABC)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF800034C7AC5, 0xFFFFF8800BA47A18, 0xFFFFF8800BA47270)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\ntfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT File System Driver
Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Sun 02/11/2014 5:49:08 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\110214-20576-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80003490289, 0xFFFFF8800C31E030, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 an exception happened while executing a routine that transitions from non-privileged code to privileged code.
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.

Conclusion

4 crash dumps have been found and analyzed. No offending third party drivers have been found. Connsider using WhoCrashed Professional which offers more detailed analysis using symbol resolution. Also configuring your system to produce a full memory dump may help you.

jsoames,

By chance do you have Malwarebytes Pro installed? I have seen a few posts on this causing the same results.

Rick

Rick,

Malwarebytes Pro is not installed.  I checked the add/remove programs list, searched for "malewarebytes" and mbam.exe and found nothing.

John

John,

This is an article about XP Operating systems. Not sure what operating system you're using but it may be a similar RESOLUTION.

http://support.microsoft.com/kb/822800

It tells how to replace the problem file.

Rick

Rick,

I'm on widows 7.

I followed the instructions and have successfully restored ntfs.sys from my recovery disk.

So far I'm not getting the BSOD, but I've only been running my apps for a few minutes.  I'll run the apps over the weekend and get back to you. 

John

John,

Keep me posted. If this works,then I can suggest this to others with operating systems other than XP.

Rick

jsoames,

Restart the computer and press F12 at startup.Run the full diagnostics and see if you get any error messages.

Rick

Go into BIOS setup (F2 at powerup) and under Logs (toward the bottom) clear the BIOS log.  Restart, and re-run the diagnostic (F12 at powerup).

If you see the same error come back, replace the drive.

Hi Rick,

I ran the full diagnostics.  At the start of the test I got the message below.  I answered yes to continue testing. 

After all the tests were completed there were no errors.

John

John,

2000-0146 means that your hard drive is failing. Please backup all files and folders that you cannot afford to lose. I would also get all my product keys using Belarc Advisor

If the computer is under warranty, contact Dell Tech Support with the error code and they will replace the hard drive.

If not under warranty, you'll need to replace the hard drive.

Rick

John,

Wish I could find the Dell Article but since they changed the website, I cannot locate it. I have an image I saved with the error codes. When you ran the diagnostics, you did NOT have any usb attached devices, correct?

DST contains previous errors, means the hard drive is failing. I would backup the files and folders that you cannot afford to lose. It could be soon, a few days, a month, but your hard drive is failing. That is the reason for the issues. You could try reinstalling the operating system, but it will be a matter of time, the hard drive will still fail.

Rick

Hi Rick,

Sorry for the delay in responding I've been busy with work.

I researched error 2000-0146 and found this article. The last entry says to run the disk diagnostics.  If they pass the disk is fine.  I ran the tests twice and got no errors.  This seams to contradict the 2000-0146 error or am I missing something?

Also, I have 2 hard drives.  I'm assuming both are tested when I run the diagnostics.

My computer is no longer under warranty so I would have to pay for the new drive(s) my self.

John

John,

It would be the one with the operating system installed.

Rick