Windows 7 starts and flashes to a bsod and restarts
- Thread starter colers
- Start date
colers
Posts: 19 +0
*facepalm*
I thought I already answered that
let me spell it out for you: I got confirmation of the gaming pc shop that I am allowed to open the casing without voiding the warranty. why? because normally you have warranty on the computer entirely, and once you open the casing, you breach warranty. my pc however, was built by this shop by my specifications, and because it cannot be considered a single product, the warranty is not applied on the machine, but on every individual part I bought.
the warranty WILL however void under 2 circumstances:
1. if I was to remove multiple parts, and then incorrectly reassemble them, causing error, it surpasses "normal usage" and makes the warranty void
2. if I was to break a part by means of direct interference, then the warranty will void because the damage is self inflicted.
and even then, all the other warranties will remain, since only the warranty on the ram goes away.
a secondary e mail from from the company confirmed that I am allowed to remove, reseat and put my ram in another ram slot (again, are you 100% sure it cannot be put in another slot than A1, since all my other sources say otherwise) without ever losing the warranty. I would gladly include a the mail in my post, but it is in dutch so you might not understand it anyway
Cycloid Torus
Posts: 4,892 +1,711
That is a LOT of errors. I gather from your earlier remarks that you can run Win7 32-bit. If you have a single stick and the clean / reseat RAM does not get you error free, then I would pack it up for a Sunday drive.
Frankly, I do not know. You might look the RAM up on the manufacturer's website to confirm what it should be.
colers
Posts: 19 +0
I already know that , a crucial ballistix 8 gb DDR3 1600. not sure what the composition of the 8 gb is though.
anyways, I tried another thing, namely using the verifier to stress my drives by putting all non-windows drivers on low resource simulation, and when I did, 32 bit generated the exact same error as 64 bit. however, other than the 64 bit, it did create a .dmp file. might it be of any benefit if I post the dmp file?
Cycloid Torus
Posts: 4,892 +1,711
Sorry, but I'm not up on dmp files..maybe you could email to your pc shop.
colers
Posts: 19 +0
here it is
colers
Posts: 19 +0
Yes, I have daemon tools.
Tmagic650
Posts: 17,233 +234
It may be causing the PC's problems. It is flagged as a problem in the minidump.Try downloading this free program to replace Daemon Tools:
http://www.slysoft.com/en/virtual-clonedrive.html
http://www.slysoft.com/en/virtual-clonedrive.html
colers
Posts: 19 +0
deleting it does not fix the problem. at least not the 64 bit problem. not sure whether it affects the crash in 32 bit when low resource mode is toggled on all non-windows drivers. but I doubt there is point in testing it, because, if the 32 bit crash is caused by deamon tools only but does not affect 64 bit after fixing it, I might just end up poking around in stuff on my pc I shouldnt poke around in.
I am hoping that me and my dad have time to open up my pc and try reseats and reslots to see if that fixes the problem (which I hope it does, since the way the errors show up (all above 7.3 gb if ram), I really get the feeling my ram card might just be a bit loose or that one of the connector chips in the RIMM-slot is damaged. this is rather possible since my pc is not standing on a stable platform. it is slightly too long for it and it might have slipped out a centimeter at some occasions)
if that doesnt, I will send 1 last mail to the pc shop to see if:
1. should I only resend the ram for repairs or the entire pc
and 2: is it possible (without losing guarantee)(and ofc if it is compatible according to mb manual) to use a 4gb ram card of another pc so I can still just my valued, pimped out gaming pc over my old pc which has been running all the games of the last 5 years on low spec.
anyways, since this is most likely the most any of you can help me (unless someone else finds something in the dmp that completely fixes everything) I might as well say good bye. this entire problem has been extremely educational (aside from this site, I also spent about 10 hours trying to trouble shoot my problem on the internet and 2 hours reading ram-related sections of my mobo manual). cannot say it really was that horrible; I am a student in IT, and every knowledge I gather around stuff like this can only prove benificial at some point of my study. short ago we even had our first lesson of our hardware book and I knew 80 % of the first chapter due to what I've been through this month. always look at the bright side of life.
Similar threads
