Windows 7 BSOD errors -- New Laptop

Hi all,

Received this new laptop for Christmas:

Sony Vaio NGW-NW270F/S
Core 2 Duo T6600 2.20GHz
Graphics: Intel Media Accelerator 4500MHB
4GB mem/320 GB storage
Optical Blu-ray
Running Windows 7 Home 64bit

Worked fine the first couple of weeks. But once I finally transferred everything over and started using it regularly, I've been getting 2-3x daily BSOD. Most say System Management or Memory Management.

Prior to this some of the time (but not all the time) I would get a pop up about a Microsoft .Net framework error. Something along the lines of "unhandled exception has occurred." Haven't seen that recently, though, and the BSODs just keep coming.

I've literally not been doing anything more advanced than having Outlook and Firefox open at the same time, so there's no reason I can see for the evil BSOD.

I've attached the zip with the last dump files (two from today, three from yesterday, I think).

From what I've been reading about others with this problem, it may not be fixable. But considering the amount of time spent configuring this, before I take it back I want to be sure I have to. I'm still in the window where I can just return it, so any advice you have would be great.

Thanks!

Tally850 said:

Hi all,

Received this new laptop for Christmas:

Sony Vaio NGW-NW270F/S
Core 2 Duo T6600 2.20GHz
Graphics: Intel Media Accelerator 4500MHB
4GB mem/320 GB storage
Optical Blu-ray
Running Windows 7 Home 64bit

Worked fine the first couple of weeks. But once I finally transferred everything over and started using it regularly, I've been getting 2-3x daily BSOD. Most say System Management or Memory Management.

Prior to this some of the time (but not all the time) I would get a pop up about a Microsoft .Net framework error. Something along the lines of "unhandled exception has occurred." Haven't seen that recently, though, and the BSODs just keep coming.

I've literally not been doing anything more advanced than having Outlook and Firefox open at the same time, so there's no reason I can see for the evil BSOD.

I've attached the zip with the last dump files (two from today, three from yesterday, I think).

From what I've been reading about others with this problem, it may not be fixable. But considering the amount of time spent configuring this, before I take it back I want to be sure I have to. I'm still in the window where I can just return it, so any advice you have would be great.

Thanks!

Hi and welcome

These were caused by memory. You were correct

I would download memtestx86 and run it for 5 passes to see if the memory is bad or there is a heat problem. You may even have to test the ram a stick at a time to isolate which ones are bad.

Code:

011910-23290-01.dmp    1/19/2010 8:25:04 PM    BAD_POOL_HEADER    0x00000019    00000000`00000021    fffff900`c22d2000    00000000`00001230    00000800`00001230    win32k.sys    win32k.sys+c40d1                    x64        C:\Users\K\Desktop\Minidump\011910-23290-01.dmp    2    15    7600    
012210-25896-01.dmp    1/22/2010 12:14:14 PM    KMODE_EXCEPTION_NOT_HANDLED    0x0000001e    ffffffff`c0000005    fffff800`02cd51e6    00000000`00000000    ffffffff`ffffffff    Ntfs.sys    Ntfs.sys+10f30                    x64        C:\Users\K\Desktop\Minidump\012210-25896-01.dmp    2    15    7600    
011910-27721-01.dmp    1/19/2010 8:42:22 PM    MEMORY_MANAGEMENT    0x0000001a    00000000`00041790    fffffa80`000077d0    00000000`0000ffff    00000000`00000000    ntoskrnl.exe    ntoskrnl.exe+71f00                    x64        C:\Users\K\Desktop\Minidump\011910-27721-01.dmp    2    15    7600    
012110-23727-01.dmp    1/21/2010 7:06:10 PM    MEMORY_MANAGEMENT    0x0000001a    00000000`00041790    fffffa80`000077a0    00000000`0000ffff    00000000`00000000    ntoskrnl.exe    ntoskrnl.exe+71f00                    x64        C:\Users\K\Desktop\Minidump\012110-23727-01.dmp    2    15    7600    
012110-24538-01.dmp    1/21/2010 5:58:48 PM    MEMORY_MANAGEMENT    0x0000001a    00000000`00041790    fffffa80`00007740    00000000`0000ffff    00000000`00000000    ntoskrnl.exe    ntoskrnl.exe+71f00                    x64        C:\Users\K\Desktop\Minidump\012110-24538-01.dmp    2    15    7600    
012210-21340-01.dmp    1/22/2010 5:11:52 AM    MEMORY_MANAGEMENT    0x0000001a    00000000`00041790    fffffa80`00007740    00000000`0000ffff    00000000`00000000    ntoskrnl.exe    ntoskrnl.exe+71f00                    x64        C:\Users\K\Desktop\Minidump\012210-21340-01.dmp    2    15    7600    
012110-26114-01.dmp    1/21/2010 12:20:04 AM    PAGE_FAULT_IN_NONPAGED_AREA    0x00000050    ffff9900`c24da1b8    00000000`00000000    fffff960`0005da6a    00000000`00000007    ntoskrnl.exe    ntoskrnl.exe+71f00                    x64        C:\Users\K\Desktop\Minidump\012110-26114-01.dmp    2    15    7600    
012010-28095-01.dmp    1/20/2010 11:39:00 PM    SYSTEM_SERVICE_EXCEPTION    0x0000003b    00000000`c0000005    fffff800`02f6ee1f    fffff880`09794020    00000000`00000000    win32k.sys    win32k.sys+19421                    x64        C:\Users\K\Desktop\Minidump\012010-28095-01.dmp    2    15    7600

OLD DRIVERS--NEED UPDATING

Code:

mdmxsdk.sys        fffff880`023f6000    fffff880`023fa280    0x00004280    0x449716be    6/19/2006 4:27:26 PM                        
secdrv.SYS        fffff880`0451b000    fffff880`04526000    0x0000b000    0x4508052e    9/13/2006 8:18:38 AM                        
regi.sys        fffff880`04513000    fffff880`0451b000    0x00008000    0x462393ee    4/16/2007 10:19:10 AM                        
SFEP.sys        fffff880`041fc000    fffff880`041fec80    0x00002c80    0x46b2beb9    8/3/2007 12:35:53 AM                        
RimSerial_AMD64.sys        fffff880`03e6b000    fffff880`03e72c00    0x00007c00    0x492addcd    11/24/2008 12:01:01 PM