• Competitor rules

    Please remember that any mention of competitors, hinting at competitors or offering to provide details of competitors will result in an account suspension. The full rules can be found under the 'Terms and Rules' link in the bottom right corner of your screen. Just don't mention competitors in any way, shape or form and you'll be OK.

Alienware Area-51 Random BSOD after 2 reformats

Associate
Joined
10 Jan 2009
Posts
854
Location
Now live in Scotland !
hi guys

thought i would ask these questions here as graphics section gets more views .

Had this computer nearly 5 full days and all i have had is problem after problem after problem after problem .




will skip the first few problems i had with the display ports and cables as i managed to get it working with full DVI cable.


my main issue is bugging the hell out of me .

after i had the problems with the display ports on graphics cards i started getting random

PFN_FILE_CORRUPT
MEMORY_MANAGMENT_ERROR
POOL_CORRUPTION_ERROR
BAD_POOL_HEADER
FLTMGR_FILE_SYSTEM_ERROR

i have also been gettig other blue screen when it doesn't even go to blue screen it just reboots the computer .

mostly these blue screen can happen while playing a game or installing a program and on a few occasions just complete froze . ive also had black screen of death just by playing a few games , mainly COD:AW or FC4 .


so i decided to do a fresh instal and get rid of all the things dell on the computer .


did this loaded the drivers i need , lan driver (killer) , Soundblaster (on the motherboard, bluetooth driver, command center . all these were dell drivers .

then loaded my own , nvidia 3,47 drivers , and my steam , origin, uplay , and other programs.

but this didnt change anything as i kept getting PFN_FILE_CORRUPT and the odd MEMORY_MANAGEMENT_ERROR .

I found out how i could read the DMP file and couldn't understand any of it apart from win8driverfault .

I then decided to do windows update and there was a lot of updates to instal , must have been east 4gb .

but this was another problem ,, some updates would just not instal and fail and on reboot it would roll back the updates and take 20 minutes then reboot again and then start the rolling back thing .

I had enough so i took out the hard drive and reformatted a different SSD drive from my old Alienware and tried instal windows 7 from a dell disc from old system ..wooot dvd drive wouldn't even recognize the disc to even instal it , so after reformatting my other SSD it said can not instal windows on the drive . it had to be another format , i couldn't remember what but managed to find a youtube video of the instructions on how to get it to the right format .

well installed windows 8.1 and this time i decided i was going to do windows update first after installing only one drive , the Gigabit lan driver so i could download the updates .

we god dam , after an hour downloading the updates it says can not instal updates , so had a look and it was 2 updates out of about 20 million updates .so skipped these and restarted pc . then did another windows update check and there is another 1.2gb to download . downloaded these and installed , rebooted and then checked again , another 1.2 .. damn these updates are not installing as the first 2 were the same windows defender updates . I actually did this by accident as after the 3rd attempt windows would go back to the desktop after going to setting on the right hand side of the pull down bar on desktop , change pc settings , then update and recover , it would just crash that page and throw me back to the desktop . went into control panel and went into windows update from there and it found 1.6gb of updates , it it tuned out i need the famous KB2919355 then those other 2 updates that wouldn't instal before would instal now . managed to get all updates installed after 3 hours and after a few refused instals . during this time i had 2 blue screen while doing the updates . a PFN_FILE_CORRUPT and this was this had no drivers even though it says on DMP file that its a driver issue . and i had the FLTMGR_FILE_SYSTEM_ERROR.

This was just drving me mad , no drivers installed apart from one , i do know you are supposed to instal all drivers before windows update but i tried that and didnt work . this all started from when i had the problems with the display port and screen going into standby before it gets to windows 8 login screen .



so i then decide to put all my drivers on and my programs , no crashes yet , installed my steam folder (separate drive ) along with programs like cpuz, gpuz , msi afterburner

all fine until i fire up a game far cry 4 and it just goes black and reboots . same with COD , i can play COD single player for about 10 minutes then would randomize either blue screen with memory management error or the pfn file corrupt error and now i got a different one where i couldn't catch it .


im now at my wits end to why this is happening and i have never ran into such problems like this even with my old system , i have tried malware removal , antivirus removal . took out all 3 graphics cards just used one card and same happens . did a test through windows diagnostic tool and so with dells version . and no memory problems . I will do a memtest on each stick over the weekend .

anybody have same issues .?

P.S if this dont make any sense then sorry iv had no sleep for 4 days ..grrrrrrr


there will be lots of other things i have missed out and perhaps i will remember once i have had some sleep .
 



it done the last crash only 10 minutes ago when i installed the intel pro wireless and pro bluetooth drivers . they both managed to instal it was when i restarted . im convinced its a driver for something but what i dont have a clue .










computer name: HOME-PC
windows version: Windows 8.1 , 6.2, build: 9200
windows dir: C:\Windows
Hardware: Alienware Area-51 R2, Alienware, 0XJKKD
CPU: GenuineIntel Intel(R) Core(TM) i7-5960X CPU @ 3.00GHz Intel586, level: 6
16 logical processors, active mask: 65535
RAM: 17061912576 total




--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Fri 16/01/2015 08:16:44 GMT your computer crashed
crash dump file: C:\Windows\Minidump\011615-7437-01.dmp
This was probably caused by the following module: fltmgr.sys (fltmgr+0x3FC9F)
Bugcheck code: 0xF5 (0x68, 0xFFFFC000CBE8FB50, 0xFFFFC000CBE8FBA0, 0x0)
Error: FLTMGR_FILE_SYSTEM
file path: C:\Windows\system32\drivers\fltmgr.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Microsoft Filesystem Filter Manager
Bug check description: This indicates that an unrecoverable failure occurred in the Filter Manager.
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 Fri 16/01/2015 08:16:44 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: fltmgr.sys (fltmgr!FltGetFilterFromName+0x236F)
Bugcheck code: 0xF5 (0x68, 0xFFFFC000CBE8FB50, 0xFFFFC000CBE8FBA0, 0x0)
Error: FLTMGR_FILE_SYSTEM
file path: C:\Windows\system32\drivers\fltmgr.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Microsoft Filesystem Filter Manager
Bug check description: This indicates that an unrecoverable failure occurred in the Filter Manager.
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 Fri 16/01/2015 05:53:01 GMT your computer crashed
crash dump file: C:\Windows\Minidump\011615-7265-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x150AA0)
Bugcheck code: 0x4E (0x99, 0x32527B, 0x3, 0x1)
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 Fri 16/01/2015 05:22:54 GMT your computer crashed
crash dump file: C:\Windows\Minidump\011615-8546-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x150AA0)
Bugcheck code: 0x4E (0x99, 0x1E3CF2, 0x3, 0x1)
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 Thu 15/01/2015 17:07:48 GMT your computer crashed
crash dump file: C:\Windows\Minidump\011515-3671-01.dmp
This was probably caused by the following module: fltmgr.sys (fltmgr+0x3FC9F)
Bugcheck code: 0xF5 (0x68, 0xFFFFC000BDBC4800, 0xFFFFC000BDBC4850, 0x0)
Error: FLTMGR_FILE_SYSTEM
file path: C:\Windows\system32\drivers\fltmgr.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Microsoft Filesystem Filter Manager
Bug check description: This indicates that an unrecoverable failure occurred in the Filter Manager.
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 Thu 15/01/2015 16:04:17 GMT your computer crashed
crash dump file: C:\Windows\Minidump\011515-3843-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x153FA0)
Bugcheck code: 0x1A (0x411, 0xFFFFF68027DE0198, 0xE4B000047168F886, 0xFFFFF68027DE0099)
Error: MEMORY_MANAGEMENT
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 a severe memory management error occurred.
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 Thu 15/01/2015 15:52:05 GMT your computer crashed
crash dump file: C:\Windows\Minidump\011515-9468-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14DCA0)
Bugcheck code: 0x4E (0x99, 0x1D790D, 0x2, 0x800017000079D68)
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 Thu 15/01/2015 15:27:58 GMT your computer crashed
crash dump file: C:\Windows\Minidump\011515-4046-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14DCA0)
Bugcheck code: 0x1A (0x401, 0xFFFFF6FB7DAFFFD8, 0x5180000127341867, 0xFFFFF6FB7DAFFED8)
Error: MEMORY_MANAGEMENT
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 a severe memory management error occurred.
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.





--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

8 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.
 
Last edited:
yea but it's driver issues they know nothung about there own drivers .

question if i instal the qualcomm killer network driver and windows defender is on by default will this cause the problem ? as I just went it no safe mode and uninstalled said driver after it says uninstall successful but it's still there and I tried uninstalling the Intel pro wireless too and it wouldn't let me get rid .doing a restore point from when I installed the pro wireless .
 
i have now restored the computer from 6.53pm last night and its a bare system with just the qualcomm killer lan installed and now uninstalled correctly by turning off windows firewall and defender . im going to try and instal the driver from QUALCOMM and not from dell and then not instal it and just use the basic intel wireless that's working right now without any drivers . I have a feeling as I ignored the killer network driver being installed to turn off any anti virus or malware that this might be the problem , if its not then I will slit my own wrists .
 
ugh; Intel's wireless drivers....are so crap. I've had to deal with this at work many; many times......honestly you get on dell on this; as there were a massive amount of defective intel wireless controllers pretty much dumped on the market. Its literally a crap shoot if you get a working one or not.

If wireless is working......don't mess with it plain and simple. Its been known for a long time installing intel wireless drivers can and usually is very bad for a system's health :)
 
Get Dell on it as the guys above said.

I also think the problem may be a hardware one again something that Dell needs to sort.
 
Get Dell on it as the guys above said.

I also think the problem may be a hardware one again something that Dell needs to sort.

you have never contacted dell then who read from a script and know nothing about there own computers . I have not got one problem I have about 4 or 5 different driver issues with this computer . and getting dell on the phone and then getting shoved pillar to post and then getting a hefty phone bill in the process .



ive just blue screened again with MEMORY_MANAGMENT_ERROR

used the tool to read the dump files and here

On Fri 16/01/2015 12:31:01 GMT your computer crashed
crash dump file: C:\Windows\Minidump\011615-7578-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x153FA0)
Bugcheck code: 0x1A (0x411, 0xFFFFF68018784598, 0xB5A00001067A6886, 0xFFFFF68018784499)
Error: MEMORY_MANAGEMENT
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 a severe memory management error occurred.
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 Fri 16/01/2015 12:31:01 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: 0x1A (0x411, 0xFFFFF68018784598, 0xB5A00001067A6886, 0xFFFFF68018784499)
Error: MEMORY_MANAGEMENT
Bug check description: This indicates that a severe memory management error occurred.
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 Fri 16/01/2015 10:09:04 GMT your computer crashed
crash dump file: C:\Windows\Minidump\011615-6968-01.dmp
This was probably caused by the following module: e22w8x64.sys (0xFFFFF80143C830F5)
Bugcheck code: 0xD1 (0xFFFFCF81B05D4E80, 0x2, 0x0, 0xFFFFF80143C830F5)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
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.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: e22w8x64.sys .
Google query: e22w8x64.sys DRIVER_IRQL_NOT_LESS_OR_EQUAL
 
please help me guys , it will take weeks for dell to help me as if I phone them it will be a circus and I have already emailed them 4 times with the problems and no response , if they do respond they do so once a day .
 
you have never contacted dell then who read from a script and know nothing about there own computers . I have not got one problem I have about 4 or 5 different driver issues with this computer . and getting dell on the phone and then getting shoved pillar to post and then getting a hefty phone bill in the process .

I have and they are totally useless

Having said that I owe them a great deal as if they had been more efficient I would never have got into building my own.

As to your problem contacting them, I found the best thing to do was phone them first thing in the morning as soon as their tech people were available and would usually get them straight away. If you wait a few minutes until after they have been open you have no chance whatsoever.

I would also recommend after this PC you have at the moment that you avoid Dell like the plague. For now though if there is the slightest thing wrong with your PC get Dell on it and get them to earn their money.
 
Why the hell are you persisting with this PC?

It's broken and needs to be returned. People can't help you, the PC is the problem.

And Dell support is very good now, especially if you ring, and Alienware support is even better. If it's less than 30 days old and they refuse to help, return it and get your money back.
 
Last edited:
I'm speaking to them through Facebook and with all the DMP files I have sent them it looks like a operating system error that's on the disc they sent me . so they have confirmed they will be sending me a brand new hard drive with the factory operating system on with all drivers .

I stopped mesing with it when i had this last BSOD.

On Fri 16/01/2015 18:57:33 GMT your computer crashed
crash dump file: C:\Windows\Minidump\011615-5500-01.dmp
This was probably caused by the following module: cthda.sys (cthda+0xA751)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF80021431751, 0xFFFFD000261EA028, 0xFFFFD000261E9830)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\cthda.sys
product: Creative Audio Product
company: Creative Technology Ltd
description: Creative High Definition Audio Device 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.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: cthda.sys (Creative High Definition Audio Device Driver, Creative Technology Ltd).
Google query: Creative Technology Ltd SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M


it was the only driver i had installed .
 
Why the hell are you persisting with this PC?

It's broken and needs to be returned. People can't help you, the PC is the problem.

And Dell support is very good now, especially if you ring, and Alienware support is even better. If it's less than 30 days old and they refuse to help, return it and get your money back.

Yeah, I was pretty sure Alienware support was effectively the same service as Dell's next business next day onsite response with English/Irish phone support so it should be top notch!

I'd give Dell a call and tell then you want to return it as faulty for a refund. That should get them on the case.....!

Worryingly I've just ordered an Area-51 from Dell so I'm hoping I don't run into similar issues :eek:

I bought pre-built this time (after putting together my last 2 rigs myself) as I don't have time to worry about compatibility and thought an off the shelf system with NBD onsite would be a safer and more reliable bet........!
 
Guys it's a 4 grand system . replacement system from a 18 month old R4 Aurora. so in didn't pay that 4k and they did offer me a refund from old system of just over £900 . so as you see in chose to have a £4000 system rather than a percentage refund from my old system that's in my sig .

They have also now confirmed despatch of new hard drive .
 
All in all if the new hard drive works with no multiple bsods then my trust in them will be regained . and being facebook i wasn't expecting to get a reply . but to be honest I feel it's either a faulty wifi card , sound card or Ethernet port which is all connnected to the motherboard and being a generic motherboard in wouldn't be suprised if it is the motherboard as i had a few replacements from old system .
 
They have just confirmed it's a technician coming out on Tuesday . oh well my faith in that has gone down hill . in bet it's a empty drive when technicain brings it as it won't be a dell technician it will be a contactor who knows nothing about the system .
 
Back
Top Bottom