new np9262 problem

I just put in two brand new RAM sticks and got the main drive wiped clean and re-installed Win 7.

Everything seems to be working fine except I am getting random BSODs. I am wondering if it is the power supply that is sending some funky current to the laptop which is causing it to crash. I haven't been able to test my theory much (I've been running it for the past couple hours just off battery, I am afraid of trying to recreate the problem too much for fear of frying my memory again)

Anybody think it is likely to be the PSU that is causing the crashes? Is this known to happen?

Ian

 

download Who Crashed and post the dump report on here and hopefully we can then help you out.

 

Thanks for the reply! Here is the report

Edit: BTW, this last time it crashed it was not plugged into the psu.


System Information (local)
--------------------------------------------------------------------------------

computer name: MINI-EXPLOSION
windows version: Windows 7 , 6.1, build: 7600
windows dir: C:\Windows
CPU: GenuineIntel Intel(R) Core(TM)2 Quad CPU Q9550 @ 2.83GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 4292923392 total
VM: 2147352576, free: 2002829312



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

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.


On Wed 1/26/2011 7:44:43 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\012611-21578-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x71F00)
Bugcheck code: 0x4E (0x99, 0x9B766, 0x2, 0x49F65)
Error: PFN_LIST_CORRUPT
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 the page frame number (PFN) list is corrupted.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 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 Wed 1/26/2011 7:44:43 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: 0x4E (0x99, 0x9B766, 0x2, 0x49F65)
Error: PFN_LIST_CORRUPT
Bug check description: This indicates that the page frame number (PFN) list is corrupted.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 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 Wed 1/26/2011 3:51:03 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\012611-35609-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x71F00)
Bugcheck code: 0x4E (0x7, 0x85587, 0x80000, 0x0)
Error: PFN_LIST_CORRUPT
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 the page frame number (PFN) list is corrupted.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 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 Wed 1/26/2011 3:47:37 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\012611-41546-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x71F00)
Bugcheck code: 0x4E (0x7, 0xC8587, 0x80000, 0x0)
Error: PFN_LIST_CORRUPT
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 the page frame number (PFN) list is corrupted.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 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.



--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

4 crash dumps have been found and analyzed.
Read the topic general suggestions for troubleshooting system crashes for more information.

Note that it's not always possible to state with certainty whether a reported driver is actually responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.

 

I might throw the suggestion out there to test the RAM first since this is one of the easiest things to diagnose. Go get memtest86+ and let that bad boy run a few laps.

Of course, the bug description says it may NOT be a RAM issue, so you may want to review all the software you've recently installed to make sure it isn't a program.

Any other thoughts?

 

I will try a memtest tonight. If the memory is bad, is it more likely that I was shipped faulty memory or that my system has screwed it up?

Here are a couple updates. These crashes are after uninstalling the nvidia drivers for the 1600m, which is the only thing I had installed on the computer (besides firefox) before I started seeing blue screens.

On Wed 1/26/2011 9:58:10 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\012611-20515-01.dmp
This was probably caused by the following module: hal.dll (hal+0x3295E)
Bugcheck code: 0x7F (0x8, 0x80050031, 0x6F8, 0xFFFFF8000284C95E)
Error: UNEXPECTED_KERNEL_MODE_TRAP
file path: C:\Windows\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
Bug check description: This bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap.
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 Wed 1/26/2011 9:58:10 PM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: hal.dll (hal!KdComPortInUse+0xA546)
Bugcheck code: 0x7F (0x8, 0x80050031, 0x6F8, 0xFFFFF8000284C95E)
Error: UNEXPECTED_KERNEL_MODE_TRAP
file path: C:\Windows\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
Bug check description: This bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap.
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 Wed 1/26/2011 9:56:33 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\012611-23140-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x71F00)
Bugcheck code: 0x4E (0x7, 0x9F277, 0x80000, 0x0)
Error: PFN_LIST_CORRUPT
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 the page frame number (PFN) list is corrupted.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 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.

 

sorry i know nothing about kernel or pfn errors.
hopefully someone will be able to advise.
might be worth contacting your suppliers technical help as its a new machine.

 

Thanks for the advice

Actually just the RAM is new. I got the machine in September 08 from Sager.

 

The more and more I look at those error reports and their descriptions, I keep getting the feeling a driver is causing the crashes. I assume you've already updated all the drivers from the manufacturer's website though...

Edit: Oh, and if the RAM is faulty, usually means you were shipped faulty RAM. The only time the system can mess it up is if you plug it in while there's any power or a static discharge of some sort. Good thing is, either the RAM is good and you get no errors with memtest86+ or there is an error with it and it is bad. No gray areas with RAM.

 

Thanks, JP. So even if memtest shows just one error then the RAM is bad? I'm not too sure how memtest works specifically.

I remember when I first got this computer when it had vista, Sager stated that the drivers had to be installed in a specific order for it to work properly. When I moved to win 7 I remember the driver installation process not going very smoothly for some reason, but I got it working without installing all the drivers (I think). If the RAM is ok I might try reinstalling windows and updating drivers the way they were originally intended to be installed.

Any chance somebody knows of a specific driver set / order to install for NP9262 on Win 7 64 that is supposed to work well? Or is it just the one set of drivers that you can still get from Sager's website?

 

So I just started a memtest and this is is what it is showing. Is it usually like this? Either all errors or all passes?

And if it is showing all errors like this how is it that windows was even running at all?

 

Means your RAM is bad. If you want to, you can test with one stick of RAM in at a time to figure out which one is bad....unless of course both are bad

 

Thanks, do you think newegg will take it back?

 

Yes, if you have purchased it in the last 30 days. If not, then you will have to contact whoever made your RAM and get it replaced under warranty.

 

hmm, my computer just booted into windows again. Does this mean that one of the memory sticks is good and the other bad? Can this machine run off just one stick?

 

If the RAM has some bad bits, it is possible that it just runs until it uses those bits. Do what zeuswsu suggested. Redo the test with each of the stick in to see which one is the broken one. Do the test for several hours for each of the memory sticks.

 

Those are definitely errors. You will see MemTest detected over 1300 of them. I recommend taking all ram out and start testing the modules by themselves so you can isolate the bad Ram Module(s)

Windows can still run with RAM Errors but obviously provide you problems.

 

Thanks for the replies guys! I will check each ram stick and post back.

 

OK. Just tested both sticks. The first one ran for one and a half passes, no errors. The second one was all errors as soon as I started the test.

Is there really a need to run the good one for a few hours? Seems pretty clear which is the bad one. And I think I have to return both to newegg anyway to get new ones.

EDIT:

I also just tested one of the old sticks and it seems to be good. I guess I will try to run windows off of this one stick for a while and see if I get any more blue screens.

I submitted the RMA to newegg. I am thinking about getting a 8GB set instead of 4GB. The manual says NP9262 only accepts up to 4GB, but I have heard it can take 8. Can anyone confirm this?

Looking at G.SKILL 8GB (2 x 4GB) 200-Pin DDR2 SO-DIMM DDR2 667 (PC2 5300) Laptop Memory Model F2-5300CL5D-8GBSQ

 

An easy way to find out is Crucial's System Scanner at http://www.crucial.com/systemscanner/index.aspx

 

I am using 8GB without problems. I have the latest revision of the motherboard.

By the way test them each of them in each slot, maybe there is some problem with the memory slot.

 

I am using the good RAM stick in the slot that had the bad one previously, and so far no BSODs!

How do you install the latest revision of the mobo? I thought I read somewhere that it is risky to change it.

 

I bought like that. You might also have it. Check in cpuz program the latest revision of the mother board is D.

 

This is the latest revision?

 

It seems you have the latest one. What is your current system?