New
#21
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
BSOD already > 40 times on not even 1 day
-
-
New #22
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
-
New #23
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
-
New #24
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
-
New #25
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
-
New #26
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
-
New #27
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
-
-
New #29
ok already thnx
-
New #30
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
Extract Files from Windows 7 Installation DVD
Quote
Related Discussions