Alienware M14X r2 blue screen already?

[xGeorgexBP]

I've had my Alienware m14x r2 for less then a month and I've had a couple blue screen errors already. First, I thought it was just the heat from my long BF3 sessions, so I bought a cooling pad. I thought it solved the problem because I didn't get it after that. I few days later (now), I'm getting them more frequent. I'm updated all the current drivers too. Any suggestions on how I should pursue to tackle this problem?
The info analyzed by the program 'whocrashed:'
System Information (local)
--------------------------------------------------------------------------------

computer name: GEORGE-PC
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
CPU: GenuineIntel Intel(R) Core(TM) i7-3610QM CPU @ 2.30GHz Intel586, level: 6
8 logical processors, active mask: 255
RAM: 6340014080 total



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

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.


On Sat 6/9/2012 8:19:04 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\060912-43274-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0x50 (0xFFFFF880886E5000, 0x1, 0xFFFFF8800F7F1B76, 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 Sat 6/9/2012 8:19:04 AM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: nvlddmkm.sys (nvlddmkm+0x1ECB76)
Bugcheck code: 0x50 (0xFFFFF880886E5000, 0x1, 0xFFFFF8800F7F1B76, 0x5)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\drivers\nvlddmkm.sys
product: NVIDIA Windows Kernel Mode Driver, Version 296.16
company: NVIDIA Corporation
description: NVIDIA Windows Kernel Mode Driver, Version 296.16
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.
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: nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 296.16 , NVIDIA Corporation).
Google query: nvlddmkm.sys NVIDIA Corporation PAGE_FAULT_IN_NONPAGED_AREA




On Sat 6/9/2012 7:24:27 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\060912-44912-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0x50 (0xFFFFF88088EE5000, 0x1, 0xFFFFF8800F7F4B76, 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 Sat 6/9/2012 6:16:36 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\060812-30825-01.dmp
This was probably caused by the following module: netwsw00.sys (Netwsw00+0x3D472)
Bugcheck code: 0xDEADDEAD (0xF010012, 0x125025B, 0x12BC22CE, 0x68EC005E)
Error: MANUALLY_INITIATED_CRASH1
file path: C:\Windows\system32\drivers\netwsw00.sys
product: Intel® Wireless WiFi Link Adapter
company: Intel Corporation
description: Intel® Wireless WiFi Link Driver
Bug check description: This indicates that the user deliberately initiated a crash dump from either the kernel debugger or the keyboard.
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: netwsw00.sys (Intel® Wireless WiFi Link Driver, Intel Corporation).
Google query: netwsw00.sys Intel Corporation MANUALLY_INITIATED_CRASH1




On Sat 6/9/2012 4:14:48 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\060812-45599-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0x50 (0xFFFFF88088EE5000, 0x1, 0xFFFFF8800F81EB76, 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 Mon 6/4/2012 11:08:17 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\060412-48360-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0x50 (0xFFFFF88088AE5000, 0x1, 0xFFFFF8800F819B76, 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.

 

[adityadragoniyer]

still occurring after you updated? Especially windows updates and nvidia drivers since they appear to be having problems in your query.
Heating causes issues but never heard of this.

 

[xGeorgexBP]

I was about to reply when it crashed again, TWICE! Omg.. I checked the drivers again (installing them again), majority of the time using the repair or re-installing option. The only difference I noticed was that I didn't have the new BIOS version that was just released 6/1/12, when I check it was towards the end of May. I noticed that I had one more 'Optional' Windows 7 update for the Intel HD Graphics 4000 after these two recent crashes I happen. I just downloaded and installed it, which required a reboot.

 

[adityadragoniyer]

ok so are you facing the problem again after installing them?

 

[xGeorgexBP]

Yes. I also ran CHKDSK and got these results:

Checking file system on C:
The type of the file system is NTFS.
Volume label is OS.

A disk check has been scheduled.
Windows will now check the disk.

CHKDSK is verifying files (stage 1 of 5)...
151296 file records processed. File verification completed.
232 large file records processed. 0 bad file records processed. 0 EA records processed. 124 reparse records processed. CHKDSK is verifying indexes (stage 2 of 5)...
204230 index entries processed. Index verification completed.
0 unindexed files scanned. 0 unindexed files recovered. CHKDSK is verifying security descriptors (stage 3 of 5)...
151296 file SDs/SIDs processed. Cleaning up 569 unused index entries from index $SII of file 0x9.
Cleaning up 569 unused index entries from index $SDH of file 0x9.
Cleaning up 569 unused security descriptors.
Security descriptor verification completed.
26468 data files processed. CHKDSK is verifying Usn Journal...
36170120 USN bytes processed. Usn Journal verification completed.
CHKDSK is verifying file data (stage 4 of 5)...
151280 files processed. File data verification completed.
CHKDSK is verifying free space (stage 5 of 5)...
89285712 free clusters processed. Free space verification is complete.
CHKDSK discovered free space marked as allocated in the
master file table (MFT) bitmap.
CHKDSK discovered free space marked as allocated in the volume bitmap.
Windows has made corrections to the file system.

468702207 KB total disk space.
111218904 KB in 118288 files.
72260 KB in 26469 indexes.
0 KB in bad sectors.
268191 KB in use by the system.
65536 KB occupied by the log file.
357142852 KB available on disk.

4096 bytes in each allocation unit.
117175551 total allocation units on disk.
89285713 allocation units available on disk.

Internal Info:
00 4f 02 00 81 35 02 00 47 02 04 00 00 00 00 00 .O...5..G.......
ad 01 00 00 7c 00 00 00 00 00 00 00 00 00 00 00 ....|...........
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................

Windows has finished checking your disk.
Please wait while your computer restarts.

 

[adityadragoniyer]

I'm clueless on what you should mate. Try contacting an Tommy or some admin at AWA? If I find anything to help you will let you know

 

[AeonSoul]

Well seems your checkdisk found something, althrough I'm not very familiar with that.
Try running a RAM test aswell, when I had bsods on my desktop it was due to a defective ram module, althrough it might seem like a long shot in this case.

 

[BlackJair]

When i got my laptop i had about 3 BSOD in less than a month, but after i updated to BIOS A10 i haven't got anyone since then; About 5 months ago.

 

[xGeorgexBP]

I have all the latest drivers, including BIOS (A03 released 6/1/12 for M14X r2), and windows 7 update. I'm planning to call tech support if it continues since I bought it less than a month.