Windows 7: Random BSOD on new laptop now screen blank upon startup

Hi,i took my new laptop out of the box yesterday,i have been having an issue with it a bsod randomly,it even happens in safe mode,I was trying to get some files off of it to reset it again but another bsod happened,now the laptop turns on but the screen does not turn on what so ever,luckily i managed to get the who crashed reading copied to text file and the minidump files to my external hdd before the screen went completely.

Laptop specs:16GB ram
intel core i7
AMD Radeon™ HD6970 2GB
Windows 7

Who crashed reading :

Crash dump directory: C:\windows\Minidump



Crash dumps are enabled on your computer.

On Sat 12/01/2013 20:20:48 GMT your computer crashed
crash dump file: C:\windows\Minidump\011213-19546-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x48D8)
Bugcheck code: 0x24 (0x1904FB, 0xFFFFF88009811C28, 0xFFFFF88009811480, 0xFFFFF8000309790E)
Error: NTFS_FILE_SYSTEM
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 a problem occurred in the NTFS file system.
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 Sat 12/01/2013 20:20:48 GMT your computer crashed
crash dump file: C:\windows\memory.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x48D8)
Bugcheck code: 0x24 (0x1904FB, 0xFFFFF88009811C28, 0xFFFFF88009811480, 0xFFFFF8000309790E)
Error: NTFS_FILE_SYSTEM
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 a problem occurred in the NTFS file system.
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 Sat 12/01/2013 20:16:16 GMT your computer crashed
crash dump file: C:\windows\Minidump\011213-21886-01.dmp
This was probably caused by the following module: ndproxy.sys (NDProxy+0xF0E7)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF8800690E0E7, 0x0, 0xC00000BB)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\windows\system32\drivers\ndproxy.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NDIS Proxy
Bug check description: This indicates that a kernel-mode program 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.
Google query: Microsoft Corporation KMODE_EXCEPTION_NOT_HANDLED



On Sat 12/01/2013 19:59:55 GMT your computer crashed
crash dump file: C:\windows\Minidump\011213-22495-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0xCF077)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF9600017F077, 0xFFFFF8800823ECF0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\windows\system32\win32k.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Multi-User Win32 Driver
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 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 Sat 12/01/2013 19:55:57 GMT your computer crashed
crash dump file: C:\windows\Minidump\011213-22042-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x48D8)
Bugcheck code: 0x24 (0x1904FB, 0xFFFFF8800A15DA88, 0xFFFFF8800A15D2E0, 0xFFFFF880014B35B7)
Error: NTFS_FILE_SYSTEM
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 a problem occurred in the NTFS file system.
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 Sat 12/01/2013 19:53:20 GMT your computer crashed
crash dump file: C:\windows\Minidump\011213-27019-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x48D8)
Bugcheck code: 0x24 (0x1904FB, 0xFFFFF88003754128, 0xFFFFF88003753980, 0xFFFFF800030A75FD)
Error: NTFS_FILE_SYSTEM
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 a problem occurred in the NTFS file system.
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 Sat 12/01/2013 00:38:20 GMT your computer crashed
crash dump file: C:\windows\Minidump\011213-29827-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x48D8)
Bugcheck code: 0x24 (0x1904FB, 0xFFFFF88003776EC8, 0xFFFFF88003776720, 0xFFFFF800031F7B05)
Error: NTFS_FILE_SYSTEM
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 a problem occurred in the NTFS file system.
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

I have the mindump files but can only upload them to sendspace in a rar file if this ok to post??

Any help small or large would be greatful.

Thanks,
Brady

http://www.sevenforums.com/crashes-d...tructions.html
But why bother take it back to the shop if its BSODing out of the box chances are it has problems, probably hardware, get another one

It happened with a new sony laptop i had also within the last 4 months that had to be returned,i am using the same software as i was using in the previous laptop i had for 4 years,i stupidly put some files on the new laptop and i need them back,I was hoping for some insight so i could have some hope to recover them.

Do you see anything on screen when you first turn on, does the machine POST ?
Can you access bios ?
Can you boot from recovery/install media ?

No I don't see anything at all when i turn it on,nothing what so ever,it's as blank as when the laptop is turned off,so there is no chance of me recovery from install media or even getting into bios.

Dont know what else to suggest mate if it wont turn on what can you do, saturday trip to the shops ?

lol it came from UK to Ireland and their helpline isn't open till Monday,I am thinking it might be the ram as they upgraded it from 8GB to 16GB in shop,but then again if it won't turn on could it possibly be the video driver or video ram?I am a bit of a noob so i am just spit balling.Thank you for your help tho.

Hi,
Just to Note: (I dont wish to step on toes):

If BSOD is occuring is safe mode then its pointing towards Hardware issues

You have an ntfs.sys error which is usually caused by a faulty or corrupt hard drive or possibly Malware.


You have a win32k.sys error, so it is a good bet that the problem is hardware and the first suspect is the RAM.


You also have ndproxy.sys error indicates that you got infected by malware (Adware, Worms, Viruses, Trojan and Spyware) and ndproxy.sys related files are removed by your antivirus software. As usual, your system will display error messages like ndproxy.sys is missing, ndproxy.sys Not Found, Can not find ndproxy.sys.




Hope this helps,

Cheers

Dave

Thanks very much for your reply Dave,no toes stepped on at all,that helps allot,hardware issues was my first thought,i did not get any display error messages by my system stating any of those things,i don't know how i could have gotten infected by a virus or malware,but then again anything can happen,is microsoft security essential good enough then if i got infected my malware or a virus???

Hi,

Its just an indication...doesnt mean you have been infected, depends on your error messages (which you said you did not get....so belay that )

Microsoft Security Essentials is good from a Strict BSOD perspective, its stable, reliable and has a small footprint and should do the job...I use it and its hassle free.

I know this sounds obvious...but have you tried plugging in an external monitor? (For the blank screen problem)

Failing that Take it back to the shop if you can and Demand a replacement.

Hope this helps

Cheers

Dave