BSOD at random times, even after repair.

[bellinibean]

Hello all, I'm new here but I've read several helpful threads. Here's my issue:

I bought my Ideapad Y580 from Lenovo in August. Around the middle of September, I started getting the BSOD after updating my Nvidia driver (which it prompted me to do) So I did the typical system restore and reset to the old driver. This did not fix the problem. So I called Lenovo, who determined my motherboard may have a problem and I sent the laptop in for repair. I get it back last night and STILL BSOD! This time for multiple things. I call Lenovo back and after it was determined that the pre-installed mcaffee was to blame. (drivers) So, It was uninstalled and windows update ran until completion with the tech on the phone. I thought all was well, but about 10 minutes after i get off the phone I get another BSOD for a completely different problem. I will post my last 3 or 4 bsod reports below.

I will say this, there are NO third party programs on this computer right now. Everything install came from Lenovo as is. And yes, Lenovo replaced the motherboard when it was sent for repair. Any help would be appreciated. a brand new 1000+ dollar machine shouldn't be giving me these headaches.

Without further ado:

Latest Crash:

On Wed 10/24/2012 9:21:23 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\102412-22604-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)
Bugcheck code: 0xA (0x54, 0x2, 0x0, 0xFFFFF8000308F8BB)
Error: IRQL_NOT_LESS_OR_EQUAL
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 Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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.

Next Crash:

On Wed 10/24/2012 9:09:56 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\102412-20389-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF8000337E444, 0x1, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
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 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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

...and again

On Wed 10/24/2012 9:21:23 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: 0xA (0x54, 0x2, 0x0, 0xFFFFF8000308F8BB)
Error: IRQL_NOT_LESS_OR_EQUAL
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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.

...and again again

On Wed 10/24/2012 2:16:41 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\102412-23758-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)
Bugcheck code: 0x1A (0x41287, 0x7B3FFFFFFF, 0x0, 0x0)
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.

last one!

On Wed 10/24/2012 1:31:37 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\102412-21528-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CD40)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8000308DD71, 0xFFFFF8800AF5CC40, 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.

 

[zap514]

I have had pretty much the exact same problem with my new machine with a lot of errors pointing towards ntoskrnl.exe (nt+0x7EFC0). sent it back for repair 3 times, still the same problem, even after they swapped the motherboard.
I've tried reinstalling the OS, every driver is up to date, memtest86 shows no errors in ram (passed 8 times). HD tune pro show no errors in hard drive.

If you find out what is wrong and how to fix it, please post back, hope you solve this thing

 

[bellinibean]

Well i talked to lenovo again and explained the multiple hardware and software errors (even on a fresh OS install) and i requested to be sent a completely new Y580 and not continued repairs. My request was elevated to a senior tech who authorized the replacement. I bought an Asus G75 friday and I will sell this new-in-the-box Y580 once it gets shipped to me.