BSOD already > 40 times on not even 1 day

[usasma]

The red stuff is memory errors - you either have a memory or a motherboard problem.

Follow the steps (starting at Step 7) here to figure out where the problem is: Memory Diagnostics

 

[copypoesje]

ok, trying that now, but is it normal that when the memtest is running and you touch the mouse the pc reboots? ( also when there are no errors displayed on that ram stick?)


tyvm for the help!


Tom

 

[copypoesje]

hey all,

I am still doing memtests,
but so far there is 1 of the 2 sticks that gives errors so think that one must be the broken one =)

I will let you guys know if i still get bsod.

And i already wane thank you all very much for all the help tips and time.

thank you very much!

kind regards,

Tom

 

[copypoesje]

ok so all my memscans are done, i found one bar that spammed me with errors, then 1 bar that seems to have 00 errors,

But when i started windows again i had imideadly bsod =(
i added the dump files in the zip,

I also did a sfc/scannow thingy and that sayd this:

C:\Windows\system32>sfc/scannow

Systeemcontrole wordt gestart. Dit proces kan enkele minuten duren.

Verificatiefase van systeemscan wordt gestart.
Verificatie is 100% voltooid.
Er zijn beschadigde bestanden gevonden, maar deze kunnen niet allemaal worden he
rsteld.
De details zijn opgenomen in CBS.Log windir\Logs\CBS\CBS.log. Bijvoorbeeld
C:\Windows\Logs\CBS\CBS.log

C:\Windows\system32>

in english that means that there were damaged files but that they couldnt be repaired all.

i also added the cbs file in the attachment.


i dont know or it is becouse i only got 2gb ram now or something else, i also looked around a bit it could point to heating or something, i cant rlly see temrature becouse there is no utlity program for the mainboard yet, but i dont think its that becouse its not overclocked and its in a cool place, and it doesnt feel rlly hot in the pc.


already thnx,

and sorry for the new problems =)

kind regards
Tom


so in the attached zip is:
- cbs thing from sfc/scannow
- 2 dump files

 

[usasma]

There's multiple problems - so we've gotta find them and diagnose them one-by-one.

These seem to be the corrupted files that SFC.EXE couldn't fix - I don't have any idea what to do with them.
PINTLGT.IMD
wcnwiz.dll
NlsLexicons0010.dll

No specific issues noted in the memory dump files - so I'd have to suggest running Driver Verifier using these instructions:

Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

So, I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out.

Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.
If that doesn't work, post back and we'll have to see about fixing the registry entry off-line.

More info on this at this link: Using Driver Verifier to identify issues with Windows drivers for advanced users

 

[copypoesje]

ok will try that, tyvm

i also noticed something weird, i got no clue or it means something, but when i first did mem test 1 stick had 00 errors, i had a bsod and i did a new memtest and then i had memerrors, a bit later i did a new memtest again no errors, i logg back in get a bsod and again i see ramerrors.

so what i mean is there are no mem errors but if i look to memtest after a bsod it does detect errors, is that normal or also means something?

(its in all sockets of my motherbord)

i try the things you sayd, thank you very much

kind regards,
Tom

 

[copypoesje]

Hey guys,

i did run the verifier thingy, but i got a small problem.

i had bluescreens before the verifier and during setting it up and during disabling it.
so i am not really sure what ones of the dump files are with or withouth it.

in the zip i putted the ones from today, so not sure what ones it are but i believe there were atleast 3 from when it was turned on.

already thnx

kind regards,
Tom

 

[usasma]

Not a problem. Running the dump files now, will be right back with the results.....

 

[copypoesje]

ok already thnx

 

[Pauly]

Half the dumps are still saying memory corruption, from what your saying it sounds like all the ram maybe bad, and if it is, its hard to fix other stuff when your geting random crashes from the ram.
I would exchange all the ram before proceeding

Also the sfc scan found multiple errors which means the scan needs to be run several times it cannot fix all errors at once
Any system files that sfc scan cannot fix will need to be replaced from your win dvd, have a read thru this
http://www.sevenforums.com/tutorials/42776-extract-files-windows-7-installation-dvd.html

 

[usasma]

Because of the large amount of memory errors that you faced, and the large number of differing BSOD errors that you have (even with Driver Verifier) - I have to suspect a hardware problems. Do you recall having a voltage surge or lightning storm around the time that these problems started?

I would next suggest running Driver Verifier - but this time enable it for ALL drivers on the system. This will drastically slow the system down - but it will also verify the Windows driver files. If my suspicions are correct, the results of a couple of BSOD's will show different results also - which will help to confirm hardware damage (rather than Windows corruption).

Here's a summary of the BSOD's:

Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sun Jan  3 03:55:43.596 2010 (GMT-5)
System Uptime: 0 days 0:02:23.063
BugCheck 7F, {8, 80050033, 6f8, fffff80002ac0e90}
Probably caused by : memory_corruption
DEFAULT_BUCKET_ID:  CODE_CORRUPTION
PROCESS_NAME:  dllhost.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sun Jan  3 03:51:02.935 2010 (GMT-5)
System Uptime: 0 days 0:02:06.012
BugCheck 1E, {ffffffffc0000006, fffff80002acad70, 0, fffff88007f8ad18}
Probably caused by : memory_corruption
DEFAULT_BUCKET_ID:  CODE_CORRUPTION
PROCESS_NAME:  sdclt.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sun Jan  3 04:38:32.577 2010 (GMT-5)
System Uptime: 0 days 0:00:11.029
BugCheck 3B, {c0000005, fffff880049e7800, fffff88003dd4120, 0}
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+13c800 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  csrss.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sat Jan  2 14:44:01.210 2010 (GMT-5)
System Uptime: 0 days 0:04:32.677
BugCheck 1A, {41287, c1e418, 0, 0}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+42c75 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  explorer.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sun Jan  3 04:12:01.906 2010 (GMT-5)
System Uptime: 0 days 0:02:10.357
BugCheck A, {fffffa8d810fba90, 2, 1, fffff80002ab28a7}
Probably caused by : memory_corruption ( nt!MiDeletePteRun+4b7 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  svchost.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sun Jan  3 04:22:17.373 2010 (GMT-5)
System Uptime: 0 days 0:00:12.450
BugCheck 1000007E, {ffffffffc0000005, 102a29943, fffff88003186d48, fffff880031865a0}
Probably caused by : dxgkrnl.sys ( dxgkrnl!DpiGetDeviceRegistryPaths+309 )
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME:  System
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sun Jan  3 04:28:45.612 2010 (GMT-5)
System Uptime: 0 days 0:00:09.689
BugCheck C5, {fffff8a005cf6000, 2, 1, fffff80002c0a6fb}
Probably caused by : fileinfo.sys ( fileinfo!FIStreamGetInfo+11f )
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME:  System
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sun Jan  3 04:33:00.904 2010 (GMT-5)
System Uptime: 0 days 0:02:07.981
BugCheck FE, {5, fffffa8003b0c1a0, 80863b34, fffffa8003f02c50}
Probably caused by : usbehci.sys ( usbehci!EHCI_sMode_PollEndpointSlot+67 )
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME:  System
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sun Jan  3 04:00:46.516 2010 (GMT-5)
System Uptime: 0 days 0:01:41.983
BugCheck 50, {fffff880071f7000, 0, fffff88000d32ac4, 0}
Probably caused by : CI.dll ( CI!SHATransform+24 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  SkyTel.exe

 

[ickymay]

I wonder if the memory type you are using might be incompatible with the motherboard ?

could you download and run CPUZ and post a screenshot of the memory tab ?

the motherboard spec pdf says

The board has four DIMM sockets and supports the following memory features:
• 1.5 V DDR3 SDRAM DIMMs with gold plated contacts, with the option to raise the voltage to support higher performance DDR3 SDRAM DIMMs.
• Support for 1.35V Low Voltage DDR3 (New JEDEC Specification)
• Two independent memory channels with interleaved mode support
• Unbuffered, single-sided or double-sided DIMMs with the following restriction: Double-sided DIMMs with x16 organization are not supported.
• 16 GB maximum total system memory (with 2 Gb memory technology). Refer to
Section 2.1.1 on page 35 for information on the total amount of addressable memory.
• Minimum recommended total system memory: 512 MB
• Non-ECC DIMMs
• Serial Presence Detect
• DDR3 1333 MHz, and DDR3 1066 MHz SDRAM DIMMs

link to tested memory :huh:

 

[copypoesje]

Hey all,

I sorry for answering so late,

I did check or it is the right memory, i also brought back the memory and got 2 new sticks, as soon as i started up i did memtest, this came back back with no errors.

But now i start my pc back up i still get bsod, also when i start up the place where you see intel and some options where you can chose boot menu, or bios sometimes comes back for like 4 times.

I also did repair with the windows cd, this sayd there were boot errors, and also sayd it did repair it.

I also did sfc/scannow this always keeps saying there are damaged files but can not repair all.

I also noticed that the pc doesnt always crashes everytime with bsod now, i think he crashed like 8 times so far but only 3 minidump files i could find.

I added the minidump files in the zip.


already thank you ( again )

kind regards,

Tom

 

[Pauly]

Dumps still talk of memory corruption if your sure the ram is good then i would check bios settings for ram timings/voltage settings, auto is not always the best
Check for timings on the memory packing/instructions and enter them manually in bios or even underclock the ram to see if it can improve stability, memcheck can only check the ram itself is not faulty this does mean there isnt a problem between ram & motherboard

As far as the sfc /scannow now goes any files that are corrupted and cannot be rectified can be replaced from the win 7 disc, have a read through this tutorial and see if it can help
http://www.sevenforums.com/tutorials/42776-extract-files-windows-7-installation-dvd.html
If you do go down this road make sure to make a restore point before you begin as you will be changing system files and possibly permissions so be sure to have a backup, also if you do change permissions on a file to swap it be sure to change permissions back as they were on the new file once its in situ or you may have problems on a reboot

 

[copypoesje]

Hey all,

I wane thank you all a lot it was idd corruption only wasnt RAM but was mothrboard that is changed now and everything works oke!

there is only 1 thing that still happens that is from time to time a bsod, or just a freeze.
the freeze is kind of weird becouse i hear the last seccond of sound repeating itself like a 10000 times very fast. Also when it just freezes there is no dump file created.
On a bsod there is a dump i got 1 here in the attach.

it doesnt happen at always same moment but i got the feeling it happens more when i am doing things in firefox or avant browser in internet explorer sometimes too but not that frequently.
Its not rlly important becouse it normally doesnt happen that often just like 10times on a day but can still game and do things so aint the spam as it was before =P


things i already tryd to solve this is:
-reinstall all drivers
-put new bios on ( had last one already but still tryd)
-did memtest was clean
-did hd test was good
-tryd difrend keyboard, mouse headset
-unplugged my 2th hd
-changed my sata cables in my pc
-hmm what else thats it i think =)
already ty.
Tom

 

[chev65]

Ten crashes a day is far from being fixed my friend. You should not be seeing any crashes at all on your system if everything is working correctly. In other words your system is simply not stable and it won't be unless you change out something, probably faulty hardware.

You should try running the Windows version of Memtest. It finds problems with the memory that the Memtest CD just won't find. You will need to run one instance of this test per CPU core. With 4 cores and 4 threads you need to run 8 instances of this test then divide the unused memory into each test and run them all at the same time. I defy you to run this test as directed then come back here and tell us that nothing is wrong. :sarc:

This version of Memtest loads up the CPU and the memory in an operating system environment which tends to find any possible memory problems very quickly, usually in the first ten minutes. You should run this test overnight if possible. MemTest for Windows Download Page

 

[copypoesje]

hmm ok will run that,
but thing is at store when i did go back with the ram and cpu and mothrboard and sayd something was wrong they replaced ram first withouth testing still had bsod then they tested it self and found out the mothrboard was broke so they gave me a new motrboard and then they tested it again and that was all oke.
so ram, cpu, mothrboard seems bit weird if it would be that tbh.

but will run the tests =)

kind regards,

tom

 

[chev65]

It may just be improper memory settings or something else set incorrectly in bios, not always bad hardware. If you get that many BSOD still something is definately wrong.

 

[ickymay]

Hey all,

I wane thank you all a lot it was idd corruption only wasnt RAM but was mothrboard that is changed now and everything works oke!

there is only 1 thing that still happens that is from time to time a bsod, or just a freeze.
the freeze is kind of weird becouse i hear the last seccond of sound repeating itself like a 10000 times very fast. Also when it just freezes there is no dump file created.
On a bsod there is a dump i got 1 here in the attach.

it doesnt happen at always same moment but i got the feeling it happens more when i am doing things in firefox or avant browser in internet explorer sometimes too but not that frequently.
Its not rlly important becouse it normally doesnt happen that often just like 10times on a day but can still game and do things so aint the spam as it was before =P


things i already tryd to solve this is:
-reinstall all drivers
-put new bios on ( had last one already but still tryd)
-did memtest was clean
-did hd test was good
-tryd difrend keyboard, mouse headset
-unplugged my 2th hd
-changed my sata cables in my pc
-hmm what else thats it i think =)
already ty.
Tom

10 times a day would drive me mad

If you can reproduce that freeze I would take it back to the shop and ask them to solve it

 

[copypoesje]

memtest thingy clean, but i also cant bring back to shop due to its self creation so i can go back with parts but not just say hey here is my pc fix it plz =P

10 times seems much but compared to what it is before i rlly happy becouse before i had like under 1min every time i putted it on before a bsod would pop up so now i still can do a few things.

A mate of me told me it can be something with sound codecs or something like that is that posibl?

well already ty

Tom