I have had my current system for over a month now and it's been rock solid until about a week ago when I started getting issues giving the blue screen crash. The only thing that was different to say the week before was that I had installed drivers and patch editing software for my Line 6 POD HD (although this has not been connected at the time of the crashes) and a soft synth.

I uninstalled the soft synth & ran virus checks to no avail and still had issues so I did a system restore to a point just prior to the soft synth just in case it had corrupted other files while installing etc and still having issues. Initially this was mainly when working in my DAW (Sonar) but has also happened when playing music via media player and also once when the computer was merely sat idle with no programs loaded. I updated my soundcard drivers and this seemed to improve results for working in the DAW marginally (didn't crash as quickly when working). I downloaded WhoCrashed to see if the issue was hardware / software related but frankly the results are alien to me!

Is anyone able to take a look below at the WhoCrashed report and see if they can suggest next steps for me please as this has given me quite a few late nights and I have no idea what's next!!


On Fri 02/03/2012 23:30:06 GMT your computer crashed
crash dump file: C:\Windows\Minidump\030312-8377-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x71F00)
Bugcheck code: 0x50 (0xFFFFF80102ADDA30, 0x8, 0xFFFFF80102ADDA30, 0x5)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 invalid system memory has been referenced.
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 which cannot be identified at this time.


On Fri 02/03/2012 23:30:06 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x11E66)
Bugcheck code: 0x50 (0xFFFFF80102ADDA30, 0x8, 0xFFFFF80102ADDA30, 0x5)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 invalid system memory has been referenced.
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 which cannot be identified at this time.


On Fri 02/03/2012 22:05:35 GMT your computer crashed
crash dump file: C:\Windows\Minidump\030212-8299-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x71F00)
Bugcheck code: 0x1A (0x5003, 0xFFFFF70001080000, 0x14B5, 0x14B5FFFFFFFE)
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 which cannot be identified at this time.


On Mon 27/02/2012 20:57:52 GMT your computer crashed
crash dump file: C:\Windows\Minidump\022712-7924-02.dmp
This was probably caused by the following module: dxgmms1.sys (dxgmms1+0x1C60)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF8800434EC60, 0xFFFFF880060DC108, 0xFFFFF880060DB960)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\dxgmms1.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
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 which cannot be identified at this time.

--------------------
[url=http://www.facebook.com/echoesandhalos[/url]

Everything listed in the dump is a system file, so it doesn't help determining what is responsible. But you listed what had changed, and the most likely culprit is the Line 6 drivers. I would update to the latest drivers and reinstall. You might want to check out this page as well: Dxgmms1.sys BSOD Error Repair

After the most boring weekend going through all hardware and drivers (deleted the Line 6 and used Driver Sweeper to make sure all traces were gone) with crash after crash I decided to bypass my SSD and install Windows 7 on my normal hard drive... hey presto no issues system stable!!! The SSD made things a pleasure to install and use but frankly it isn't worth it I may wait a bit before dipping my toe into those waters again!!

--------------------
[url=http://www.facebook.com/echoesandhalos[/url]

This may be drivers or software, remove the recent additions and test, as the others have said.
Hopefully software is the culprit and you ahve to search no further.

But... Page Fault In Non Paged area, this almost always means RAM or Harddrive.

If you still get that error after uninstalling recent software I would strongly suspect Harddrive or the Memory. Even though it is a new PC.
Open up the PC and reseat the RAM (Take it out & put it back in again)(Reseating components works surprisingly often)
Also Grab this... Hirens 15

http://www.demonoid.me/files/details/2800530/00765334100/

It is full of tools for testing and diagnosis.
Run Memtest to check your RAM. One stick at a time.
Then use one of the HDD checking tools to test your harddrive.

You'll pinpoint the issue somewhere, but it will take time and require a methodical approach.

Totally didn't read the last post

But yeah. HDD. Send that thing back, they should replace it if it is new...

jeez well nearly a week and a half running perfectly and then it's been crashing again!! This time consistently it's been IRQL NOT LESS OR EQUAL blue screens. This was a fresh install with the latest drivers for all of my hardware. Starting to think RAM could be at fault...

--------------------
[url=http://www.facebook.com/echoesandhalos[/url]