• Lots of bluescreens, Windows ultimately being a dick
    14 replies, posted
Ok so I posted this in the main forum because I'm aware not everyone is going to know whats happening here so I need to get as many peoples opinions as possible. Sorry for the long post but I felt it was important to highlight all my problems. Specs: Windows 7 Pro 64bit Intel i5 2500k Asus P8P67 8GB DDR3 Corsair Dominator 1600mhz GTX 570 2x WD Velociraptor 300GB It all started 2 days ago when programs on my Windows 7 Pro 64bit install, started randomly crashing, and to the point where I would click an exe and it would crash instantly, a bit later on my computer started to bluescreen a lot, with ntfs.sys being the apparent culprit. Windows would try to check the disk for consistency every boot, which lead me to the decision that somehow Windows had broken itself, something had got corrupted, so I decided to reinstall. Once I'd downloaded the ISO (legally, I have a student copy) I burned it to a disc using Imgburn, popped it in my computer and attempted to reinstall, I was reinstalling to a brand new (received that day) WD Velociraptor 300gb, this is a completely separate drive to where my old install was. I was greeted by an error message on expanding files saying something along the lines of the data not being able to be read/was corrupted etc. So I though great, either the disc hadn't burned properly or the ISO was corrupt, so I redownloaded it and burned another disc and was greeted by the exact same message again. After trying literally everything, removing RAM, installing to a different drive, swapping the CD drive, using different brands of disc, different burning tools, it seemed to be clearing my CMOS which did the trick. I have no idea why, I did get a bluescreen once during the install but the 2nd time round the install went almost perfectly, I got a blue screen when clicking the next button on the CD key entry screen (spsys.sys being the stated issue) after a reboot everything booted up fine and the install finished. So now with my new Windows install the constant ntfs.sys bluescreens have stopped, all my applications run fine but now I've just recently started getting a different bluescreen which says "Memory Management" I assumed this meant something to do with my RAM, I confirmed it quickly with google and people suggested I ran Prime95 for 3 hours to see if any problems occured. I have never used Prime95 before or any other testing tool like this so excuse my ignorance but once I ran the test almost instantly worker #1 reported: [code]FATAL ERROR: Rounding was 0.5 expected less than 0.4 Hardware failure detected, consult stress.txt file. Torture Test completed 0 tests in 0 minutes - 1 errors, 0 warnings. Worker stopped.[/code] That's basically as far as I've got, if anyone could offer some help/advice I would appreciate it a lot, and might even give you a bit of a reward (not sexual) if you can help me out.
Check what it says in the stress.txt. It should hopefully identify what part of hardware the problem is caused by
Agreed, check stress.txt. An error while running prime95 suggests either a CPU or RAM problem though.
[QUOTE=djjkps3;30986568]Check what it says in the stress.txt. It should hopefully identify what part of hardware the problem is caused by[/QUOTE] Well I went to check stress.txt but Prime95 doesn't even appear to create the file. I've done a full search and nothing with the name stress.txt shows up anywhere. :suicide:
try run memtest too
Ok well I ran memtest and I have no idea how to use it but im guessing this isn't good? [img]http://img692.imageshack.us/img692/4103/img1086mrmo.jpg[/img] At the time of posting the tests have shown up 0 Passes and over 315,000 errors.
[QUOTE=Stunted;30987649]Ok well I ran memtest and I have no idea how to use it but im guessing this isn't good? [img]http://img692.imageshack.us/img692/4103/img1086mrmo.jpg[/img] At the time of posting the tests have shown up 0 Passes and over 315,000 errors.[/QUOTE] Try taking out one stick of RAM and boot, if the Windows BSODs, try the other stick.
[QUOTE=GoDong-DK;30987839]Try taking out one stick of RAM and boot, if the Windows BSODs, try the other stick.[/QUOTE] I have 4 sticks, you want me to try them all individually?
[QUOTE=Stunted;30987883]I have 4 sticks, you want me to try them all individually?[/QUOTE] Jep, that way you can point out the bad stick(s).
Ok well Windows boots up fine with all sticks, no BSOD's however, with one of the sticks Prime95 errors out almost immediately on all 4 workers. Whereas it doesn't with the other 3 sticks. Do you think this might mean something?
[QUOTE=Stunted;30988120]Ok well Windows boots up fine with all sticks, no BSOD's however, with one of the sticks Prime95 errors out almost immediately on all 4 workers. Whereas it doesn't with the other 3 sticks. Do you think this might mean something?[/QUOTE] It means something. Try running memtest on that stick alone.
thats nice, thanks![img]http://sn.im/27yeb9[/img]
[QUOTE=GoDong-DK;30988162]It means something. Try running memtest on that stick alone.[/QUOTE] Right think i've made a breakthrough, Memtest shows up 0 errors when I run it with with one of the other sticks but hundreds of thousands when I run it with the dodgy one. Just gotta test the other 2 sticks to make sure they aren't dodgy.
[QUOTE=Stunted;30988411]Right think i've made a breakthrough, Memtest shows up 0 errors when I run it with with one of the other sticks but hundreds of thousands when I run it with the dodgy one. Just gotta test the other 2 sticks to make sure they aren't dodgy.[/QUOTE] Just RMA the faulty ones. I doubt you've got more than one faulty stick, though.
Yep the other 3 seem to be fine. No errors showing up. So hopefully that'll be the end of my troubles. Thank fuck.
Sorry, you need to Log In to post a reply to this thread.