Bluescreens

Hi,

I'm having some troubles whith bluescreens recently.
My laptop is a Clevo M761SUN
It's currently running Windows 7 (64 bit)
It has a Intel T4200 2.0 GHz dualcore processor
Nvidea G105M 512Mb graphics card
About two weeks ago I've put in diffrent RAM memmory because I thougt that might solve the bluescreens. Because I used to have 2 diffrent RAM modules. So I bougt a set of 2 x 2GB Kingston hyper X modules and about a week later when I was still having problems, swapped my harddrive for a SSD (OCZ VERTEX 3)
I've collected as much of the dumpfiles and .sysdata as I could but some of them are missing. Since the first bluescreens windows has installed some updates and I don't know whether that makes any diffrence.
Also since my RAM is as new I wonder whether I should still run memtest86?
Any ideas are welcome, because I ran out of them.

Here's my system info:
Tech Support Guy System Info Utility version 1.0.0.2
OS Version: Microsoft Windows 7 Professional, Service Pack 1, 64 bit
Processor: Pentium(R) Dual-Core CPU T4200 @ 2.00GHz, Intel64 Family 6 Model 23 Stepping 10
Processor Count: 2
RAM: 4093 Mb
Graphics Card: NVIDIA GeForce G 105M, 512 Mb
Hard Drives: C: Total - 114370 MB, Free - 44265 MB;
Motherboard: clevo, M7X0SUN
Antivirus: AVG Anti-Virus 2012, Updated and Enabled

And here are the bluescreen messages:


Probleemhandtekening:
Gebeurtenisnaam van probleem: BlueScreen
Versie van besturingssysteem: 6.1.7600.2.0.0.256.48
Landinstelling-id: 1043

Aanvullende informatie over dit probleem:
BCCode: 1a
BCP1: 0000000000041287
BCP2: 0000000000000058
BCP3: 0000000000000000
BCP4: 0000000000000000
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1

Bestanden die helpen bij het beschrijven van het probleem:
C:\Windows\Minidump\110811-10375-01.dmp
C:\Users\Erwin\AppData\Local\Temp\WER-12750-0.sysdata.xml

Lees de onlineprivacyverklaring:
http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0413

Als de onlineprivacyverklaring niet beschikbaar is, lees dan onze offlineprivacyverklaring:
C:\Windows\system32\nl-NL\erofflps.txt



Probleemhandtekening:
Gebeurtenisnaam van probleem: BlueScreen
Versie van besturingssysteem: 6.1.7600.2.0.0.256.48
Landinstelling-id: 1043

Aanvullende informatie over dit probleem:
BCCode: 1a
BCP1: 0000000000041287
BCP2: 0000000000000030
BCP3: 0000000000000000
BCP4: 0000000000000000
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1

Bestanden die helpen bij het beschrijven van het probleem:
C:\Windows\Minidump\110811-9921-01.dmp
C:\Users\Erwin\AppData\Local\Temp\WER-13406-0.sysdata.xml

Lees de onlineprivacyverklaring:
http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0413

Als de onlineprivacyverklaring niet beschikbaar is, lees dan onze offlineprivacyverklaring:
C:\Windows\system32\nl-NL\erofflps.txt



Probleemhandtekening:
Gebeurtenisnaam van probleem: BlueScreen
Versie van besturingssysteem: 6.1.7601.2.1.0.256.48
Landinstelling-id: 1043

Aanvullende informatie over dit probleem:
BCCode: 1a
BCP1: 0000000000041284
BCP2: 000007FF012CA001
BCP3: 0000000000000F68
BCP4: FFFFF70001080000
OS Version: 6_1_7601
Service Pack: 1_0
Product: 256_1

Bestanden die helpen bij het beschrijven van het probleem:
C:\Windows\Minidump\111011-27484-01.dmp
C:\Users\Erwin\AppData\Local\Temp\WER-36140-0.sysdata.xml

Lees de onlineprivacyverklaring:
http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0413

Als de onlineprivacyverklaring niet beschikbaar is, lees dan onze offlineprivacyverklaring:
C:\Windows\system32\nl-NL\erofflps.txt

 

Update:
I forgot to mention that the bleuscreens come up completely random.
Also, I opened the minidump files with bluescreenview.
4 of the bluescreens seem to be caused by ntoskrnl.exe
The other one (8-11-2011 23:14:03) seems to be caused by fltmgr.sys but ntoskrnl.exe is also in the stack of the crash, so I think it caused that one too.

 

The two drivers you refer to in your second post are both windows drivers which are very unlikely to be the cause, minidumps can be very misleading. This is more likely to be a hardware issue especially taking into account the fresh install of the OS.

Please supply the model number of the present RAM sticks.

 

Thanks a lot for your reply, the model is:

Kingston HyperX

Modelname
KHX5300S2LLK24G
Series
HyperX
Totalcapacity
4096 MB
number of modules
2
buid type
SO-DIMM
Type
SDRAM-DDR2
Standard
DDR2 - 667 (PC2 - 5300)
Timings
CAS Latency (CL) 4
RAS-to-CAS-Delay (tRCD) 4
RAS-Precharge-Time (tRP) 4
Row-Active-Time (tRAS) 12
Connection
200-Pin
Organisation
128Mx8
Voltage
1,8 Vol

On the sticks itself it sais:
99U5295-035.A00LF
0000005478204
and then on stick 1:
P9LPY-V90CT2-HWEJB
and on stick 2:
2CLD6-K9QCXA-WWPYB

 

All but one of the minidumps states Memory Management which (if you had not just replaced the RAM) I would have said it's most likely a RAM problem, but the same fault can indicate a problem with a driver.

I can see in the minidumps a new driver installed on 7th October which belongs to AVG Anti Virus, is that about the time the problem began?

If it was then uninstall AVG, follow this by running the Uninstall tool which will clean out all the remnants AVG Removal tool

Then install this Microsoft Security Essentials and see if it improves the problem.

 

Don't you mean 7th November, because 5th November I put a new SSD in it, so could it be possible you could look back to my old HDD?
Anyways, I don't know which day exacly anymore, but AVG installed a new version (the 2012 version) because there was an update available. This didn't went smoothly, the installer seized two times before it went right the third time.
I will try the microsoft security essentials. but how do I know if it's really fixed? because there has been a week between my last two bluescreens.

 

I've made a c**k up. The date of the driver is when it was released not when it was installed.

Was the AVG update installed on the old drive before the problem started? if not then it is unlikely to be a suspect.

I have not had any other ideas on this case but as the minidumps do hint at a memory fault it may be worth running Memtest just to be sure. Even though you have new RAM there is always a slim chance that there could be a motherboard fault in the circuitry connected to the RAM slots which should show up in Memtest as a RAM fault.

Use this guide Windows 7 Event Viewer to help you navigate around event viewer and see if you can find some critical errors that may contain some hint as to what is going on.

 

When I just tried to start my laptop, before it even loaded windows, it gave the error:
Error 0701
USB OVER Current on HC
(Bus:00H Dev:03H Fun:00H)
I shut it down and when it started back up again everything was fine.

Anyway, I have gone through the system log file, but it only shows errors and criticals after the crash at startup. And there are so many warnings at some times, that I don't know whether they caused it, I think a lot of those are just a result of the crash.
I have listed the times/dates of the crashes so you know where to look

6-11-2011:
21:47:41 BSOD
21:49 startup

8-11-2011:
13:36:48 BSOD
13:38 startup

8-11-2011:
23:12:38 BSOD
23:14 startup

10-11-2011
8:34:09 BSOD
8:35 startup

22-11-2011
0:01:31 BSOD
0:02 startup

I've uploaded the log file here:
https://lno0ig.blu.livefilestore.co...TTwZatUCb2i7rw/System Log.zip?download&psid=1

 

The Event Viewer isn't saying much.

The error 0701 USB over current would suggest you might have a damaged USB port. Take a close look at all the USB ports to make sure there are no pins bent out of place and touching each other.

Have you run Memtest86+ yet?

 

I'm going to run it today seperate for both sticks

 

You can run Memtest on all sticks at the same time, then if it shows errors you can run it on single sticks to find which one is faulty. Make sure you run the test for at least 8 passes to get a reliable result. This will take many hours to complete.

I would suggest that you first check the USB ports as a fault in one of the ports may just be the route of the problem.

 

I ran memtest today for 3 passes, took about 7 hours. I will run it for 8 passes this weekend, because I didn't have the time anymore today. But for the 3 passes it didn't show a single error.
I checked my usb ports and nothing has been bent. The weird thing is that it happend again today and now it showed al three USB ports to be at fault, but when i continue tot start the bios and after that windows, nothing is wrong at all.
I wonder whether my mainboard could be the problem, if it had a mechanical failure of some sort?

 

Memtest does need to be run for at least 8 passes to be conclusive.

The USB error repeating itself is a worry, have you got anything connected to any of your USB ports.

 

usually I have a mouse, cooling and an external harddrive in my USB ports. but when it starts nothing is in it. I only conect everyting when it has started up. And it only seems to do it when it's running on it's battery.
Can it be that it's not visible from the outside but I need to open up my laptop and check the connections of the USB ports on my mainboard?

 

Do you get overheating problems if the cooling is not connected?