Technical Discussion
  >> Windows Issues


Register (or login) on our website and you will not see this ad.


Pages in this thread: 1 | 2 | 3 | 4 | >> (show all)   Print Thread
Standard User cheshire_man
(fountain of knowledge) Fri 28-Oct-11 10:18:49
Print Post

Windows 7 BSODs continue


[link to this post]
 
I've now reinstalled Windows 7 Professional several times, both 64-bit and 32-bit. All of the resultant systems have suffered from BSODs.

2 or 3 times (less frequently than BSODs) the PC freezes / locks / stops. Nothing happens, the mouse laser goes out. Has to be powered down and rebooted.

Apart form the NIC and USB3 drivers, all were loaded by Windows itself.

The most recent install went BSOD during the actual install "Finalising Installation" phase, long before I'd had chance to do any localisation. The dumps, as far as I can see, point to any specific faulting item.

This installation BSOD made me think of hardware issues - despite the PC running XP Pro fine for 7 months.

Basic System Spec:
CPU: 2.80 gigahertz Intel Core i5 760
Motherboard: Gigabyte Technology Co., Ltd. P55-USB3
Memory: 4 Gbytes - 2 x 2Gbytes Hyperam DIMMs
Graphics Card: NVIDIA GeForce GT 430
Sound Card: Integrated
Hard Drive: 1 Tb Seagate ST31000528AS (partitioned C: 150Gb / D: rest)

I've twice run MEMTEST86 overnight - no problems found.
I've twice run Hiren's HDD Scan - no problems found.
I've reset the BIOS to Optimized Defaults - still BSODs.
I've swapped the memory modules round - still BSODs.
I've run on one of the two memory modules - still BSODs.
I've changed the BIOS Performance Enhance option from Turbo to Standard - still BSODs.
I've also reset the BIOS to 'optimized defaults'.

I'm beginning to run out of ideas as to what it might be.

A friend wondered if it was a 'bad' copy of Windows - it's the full retail version purchased from Amazon UK.

I've posted all details and diagnostics on the Windows 7 Forum, though nothing back as yet.

Any help/thoughts would be most appreciated.

Tony
Anonymous
(Unregistered)Fri 28-Oct-11 10:29:31
Print Post

Re: Windows 7 BSODs continue


[re: cheshire_man] [link to this post]
 
If you can get windows to actually start up find as many drivers for win 7 as you can from the manufacturers websites and don't rely on what windows installs.

I don't know if that will help but it should eliminate the possibility of a faulty driver being issued.
Standard User cheshire_man
(fountain of knowledge) Fri 28-Oct-11 10:44:08
Print Post

Re: Windows 7 BSODs continue


[re: Anonymous] [link to this post]
 
The BSOD frequency varies from 1 or 2 a day to once every 2 or 3 days, the longest BSOD-free period I got was 6 days. So my work is all being done on this W7 system - just having to save things regularly.

There seem to be 2 schools of thought about the best way to get drivers for a W7 system. As advocated by those on the W7 forum is to let Windows install the drivers and update them as appropriate. The other school is to use the latest drivers from the manufacturers' web sites. I've tried both and it makes no difference. Bearing in mind that one of the BSODs was during the actual W7 install before I had even got a chance to think about drivers, I'm not convinced it's a driver issue. I'll admit that all the dumps, as analysed by WhoCrashed, show the fault in one of the standard Windows modules, e.g. Kernel, NTFS File System,and the like, it smells of either a driver-like issue, however I'm still inclined to wonder about the hardware.

I've thought about reverting to XP and seeing if I get BSODs with that - if so then it points to hardware, if not then either it's not hardware or it's something to do with the way W7 interacts with the hardware that's finding the fault.

All in all very frustrating.

Tony


Register (or login) on our website and you will not see this ad.

Standard User AEP
(knowledge is power) Fri 28-Oct-11 10:57:13
Print Post

Re: Windows 7 BSODs continue


[re: cheshire_man] [link to this post]
 
It might be worth recording the error code from the BSOD. That will give an indication of where to look.
Standard User OCdragon
(experienced) Fri 28-Oct-11 10:59:56
Print Post

Re: Windows 7 BSODs continue


[re: cheshire_man] [link to this post]
 
Having seen your previous "tests" quoted, have you tried different equivalent PSU with matched DC voltage rails and DC powers? The possible reason is "glitches" in your DC rail/rails which may easily cause BSOD too!! Perhaps also a simple "reserting" EACH connector of your MD to make sure that there is NO simple "poor connections" that may cause your BSOD due to physical vibrations etc.

Intel E4300 OC with 2GB RAMs,Speedtouch 585 Modem/Router and Windows XP Pro

O2 Standard ADSL2+ Broadband!

Edited by OCdragon (Fri 28-Oct-11 11:03:45)

Standard User Pipexer
(eat-sleep-adslguide) Fri 28-Oct-11 12:19:23
Print Post

Re: Windows 7 BSODs continue


[re: cheshire_man] [link to this post]
 
I'd try swapping the HDD and SATA cable next... probably the easiest next thing to try, since you've reinstalled the OS just recently, hopefully not too much of a pain to reinstall YET again.

______________
Zen 8000 Active
Standard User alwall
(member) Fri 28-Oct-11 12:24:47
Print Post

Re: Windows 7 BSODs continue


[re: cheshire_man] [link to this post]
 
I had it happen (unusually) on a recent install on a brand new PC but the error code enabled me to find a solution. In my case it was an incorrect BIOS setting that Windows7 mistook as the lack of an OEM RAID driver.
Just Google the error code or look it up on Microsoft's website.

BTBroadband
Standard User cavillas
(knowledge is power) Fri 28-Oct-11 12:41:34
Print Post

Re: Windows 7 BSODs continue


[re: cheshire_man] [link to this post]
 
Have you checked the memory chips, I had a similar problem when I first built my machine and it was one faulty memory chip that caused the problem. Replaced that and everyhting has benn ok since.

Alf
------------------------------------
smile IDNET Happiness Online smile
I am in no way employed or connected with IDnet other than as a customer.




There are 11 kinds of people, those who understand binary, those who don't and those who don't care.
Standard User micksharpe
(eat-sleep-adslguide) Fri 28-Oct-11 13:40:42
Print Post

Re: Windows 7 BSODs continue


[re: cheshire_man] [link to this post]
 
Plug in a spare video card if you've got one. Alternatively, try installing XP drivers for your GeForce GT.

__________________________________________________________________________________________
'There are moments, Jeeves, when one asks oneself, "Do trousers matter?"'
‘The mood will pass, sir.’
P.G. Wodehouse -- The Code of the Woosters
.
It Ought to be Easy | Greasemonkey scripts
Standard User cheshire_man
(fountain of knowledge) Fri 28-Oct-11 14:22:27
Print Post

Re: Windows 7 BSODs continue


[re: AEP] [link to this post]
 
An abbreviated copy of the WhoCrashed dump analysis is below if it is useful. The only commonality is that they are all in standard MS modules rather than something that points to a faulting area.

Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.

On Thu 27/10/2011 22:49:28 GMT your computer crashed
crash dump file: C:\Windows\Minidump\102811-17113-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0x50 (0xFFFFF80001262980, 0x0, 0xFFFFF800030E98B6, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA

On Thu 27/10/2011 22:49:28 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x50 (0xFFFFF80001262980, 0x0, 0xFFFFF800030E98B6, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA

On Thu 27/10/2011 22:01:46 GMT your computer crashed
crash dump file: C:\Windows\Minidump\102711-19952-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0x1A (0x31, 0xFFFFFA8005309840, 0xFFFFF8800727B000, 0xFFFFF8A0099969A0)
Error: MEMORY_MANAGEMENT

On Wed 26/10/2011 21:10:48 GMT your computer crashed
crash dump file: C:\Windows\Minidump\102611-16161-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0x1A (0x31, 0xFFFFFA8006814C30, 0xFFFFF8800A901000, 0xFFFFF8A003106FE0)
Error: MEMORY_MANAGEMENT

On Tue 25/10/2011 21:01:41 GMT your computer crashed
crash dump file: C:\Windows\Minidump\102511-17550-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002EC721F, 0xFFFFF880091F1D10, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION

On Mon 24/10/2011 16:40:09 GMT your computer crashed
crash dump file: C:\Windows\Minidump\102411-15366-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0xF4 (0x3, 0xFFFFFA80049EF060, 0xFFFFFA80049EF340, 0xFFFFF800031948B0)
Error: CRITICAL_OBJECT_TERMINATION

On Thu 20/10/2011 22:25:53 GMT your computer crashed
crash dump file: C:\Windows\Minidump\102011-17784-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x5A88)
Bugcheck code: 0x24 (0x1904FB, 0xFFFFF88006E810B8, 0xFFFFF88006E80910, 0xFFFFF80002D16711)
Error: NTFS_FILE_SYSTEM

On Wed 19/10/2011 08:31:19 GMT your computer crashed
crash dump file: C:\Windows\Minidump\101911-24242-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0x1A (0x31, 0xFFFFFA80041BE410, 0xFFFFF880049C3000, 0xFFFFF8A01B1BA4A1)
Error: MEMORY_MANAGEMENT

On Wed 19/10/2011 08:09:52 GMT your computer crashed
crash dump file: C:\Windows\Minidump\101911-29686-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0x50 (0xFFFFFFFFFFFFFFFF, 0x1, 0xFFFFF880010BE39F, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA

On Wed 19/10/2011 05:46:12 GMT your computer crashed
crash dump file: C:\Windows\Minidump\101911-22495-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0x1A (0x31, 0xFFFFFA8005EBAC10, 0xFFFFF8800C4DB000, 0xFFFFF8A00205206C)
Error: MEMORY_MANAGEMENT

On Wed 19/10/2011 04:49:43 GMT your computer crashed
crash dump file: C:\Windows\Minidump\101911-24897-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x80640)
Bugcheck code: 0x1A (0x31, 0xFFFFFA8004CFFAF0, 0xFFFFF88000B6D000, 0xFFFFF8A00676CF01)
Error: MEMORY_MANAGEMENT


Tony
Standard User 12eason
(eat-sleep-adslguide) Fri 28-Oct-11 16:22:33
Print Post

Re: Windows 7 BSODs continue


[re: cheshire_man] [link to this post]
 
I recently started getting Bluescreens myself, mainly while playing TF2. It would restart sluggishly, sometimes with wiped bios values. Then on one occasion the 5 second timeout in grub took about 30 seconds to count down, and the clock in bios was skipping every 5 seconds. Weird stuff. After pulling out graphics, memory, cmos battery etc I eventually found it was my mouse. It has a dodgy cable and I think some wires are getting crossed. Not sure if that relates to your problem or not tbh. Try running prime95 for a few hours.

___________________________________________________________________
           Firenet - V21 - Fast4 - f·2·s - eclipseinternet - entanet - aaisp.net - plusnet
Standard User cheshire_man
(fountain of knowledge) Fri 28-Oct-11 20:26:08
Print Post

Re: Windows 7 BSODs continue


[re: 12eason] [link to this post]
 
Aye, prime95 has already been suggested on the W7 Forum. I've run it briefly with Speedfan running to monitor temperatures but I don't know what temperature is ok and at what point I call a halt to prime95.

Tony
Standard User 12eason
(eat-sleep-adslguide) Fri 28-Oct-11 20:41:28
Print Post

Re: Windows 7 BSODs continue


[re: cheshire_man] [link to this post]
 
Even before prime95 causes a heat related bsod, there will be calculation errors in the tests due to heat. As for temp, I'd say 70 is too high. The important thing to watch for is that a graph of the temperature in speedfan stays at an equilibrium level for a good while without any errors in prime95. Considering your previous bsods don't seem to have been caused by processor stress though, it is a bit of a long shot.

Aside from usb peripherals, I can only remember a built-in 56k modem and a wireless dongle causing frequent random bsods.

___________________________________________________________________
           Firenet - V21 - Fast4 - f·2·s - eclipseinternet - entanet - aaisp.net - plusnet

Edited by 12eason (Fri 28-Oct-11 20:42:29)

Standard User cheshire_man
(fountain of knowledge) Fri 28-Oct-11 21:31:41
Print Post

Re: Windows 7 BSODs continue


[re: cheshire_man] [link to this post]
 
One additional problem has occurred to me. Occasionally I'm getting Firefox crashing (V.3.6.23) on start up and no amount of restarting gets it going. The only solution so far has been a quick reinstall. Never had this problem until the last few weeks.

Don't know if it may be relevant.

Tony
Anonymous
(Unregistered)Fri 28-Oct-11 23:15:27
Print Post

Re: Windows 7 BSODs continue


[re: cheshire_man] [link to this post]
 
Windows 7 is the dumbest Microsoft Operating system when it comes to drivers.

The hardware drivers usually come with xp, vista drivers together. Windows 7 installs the xp drivers all by itself and thus crashes all the time. I had to uninstall the drivers, and go through the hard drive and delete all the xp drivers and manually install the vista/windows 7 drivers.
Standard User BP1
(committed) Sat 29-Oct-11 13:09:52
Print Post

Re: Windows 7 BSODs continue


[re: cheshire_man] [link to this post]
 
In reply to a post by cheshire_man:
I've now reinstalled Windows 7 Professional several times, both 64-bit and 32-bit. All of the resultant systems have suffered from BSODs.

2 or 3 times (less frequently than BSODs) the PC freezes / locks / stops. Nothing happens, the mouse laser goes out. Has to be powered down and rebooted.

Apart form the NIC and USB3 drivers, all were loaded by Windows itself.

The most recent install went BSOD during the actual install "Finalising Installation" phase, long before I'd had chance to do any localisation. The dumps, as far as I can see, point to any specific faulting item.

This installation BSOD made me think of hardware issues - despite the PC running XP Pro fine for 7 months.

Basic System Spec:
CPU: 2.80 gigahertz Intel Core i5 760
Motherboard: Gigabyte Technology Co., Ltd. P55-USB3
Memory: 4 Gbytes - 2 x 2Gbytes Hyperam DIMMs
Graphics Card: NVIDIA GeForce GT 430
Sound Card: Integrated
Hard Drive: 1 Tb Seagate ST31000528AS (partitioned C: 150Gb / D: rest)

I've twice run MEMTEST86 overnight - no problems found.
I've twice run Hiren's HDD Scan - no problems found.
I've reset the BIOS to Optimized Defaults - still BSODs.
I've swapped the memory modules round - still BSODs.
I've run on one of the two memory modules - still BSODs.
I've changed the BIOS Performance Enhance option from Turbo to Standard - still BSODs.
I've also reset the BIOS to 'optimized defaults'.

I'm beginning to run out of ideas as to what it might be.

A friend wondered if it was a 'bad' copy of Windows - it's the full retail version purchased from Amazon UK.

I've posted all details and diagnostics on the Windows 7 Forum, though nothing back as yet.

Any help/thoughts would be most appreciated.


I had similar problems sometime back. Replaced memory, graphics card, HDD, etc. The problem bsod would be itermitent. The only thing that wasnt replaced was the psu. The bios hardware monitor and various utils showed that the psu gave the correct voltage readings. Finally the psu was replaced and bingo the problems dissapeared. Would recommend OCdragons advice regarding psu.

Regards

BP1

BTBroadband

"When everything's coming your way, you're in the wrong lane"
Standard User cheshire_man
(fountain of knowledge) Sat 29-Oct-11 15:10:33
Print Post

Re: Windows 7 BSODs continue


[re: BP1] [link to this post]
 
You could well have a very good point. Though it begs the question of why it ran XP perfectly for 7 months or so and only started when I installed W7.

Tony
Standard User BP1
(committed) Sat 29-Oct-11 15:50:09
Print Post

Re: Windows 7 BSODs continue


[re: cheshire_man] [link to this post]
 
In reply to a post by cheshire_man:
You could well have a very good point. Though it begs the question of why it ran XP perfectly for 7 months or so and only started when I installed W7.


The psu i replaced was 500w rated. It funny how this problamatic psu works on a vista test machine without problems. Any how was really pleased when the bsods dissapeared with the replacement psu.

Regards

BP1

BTBroadband

"When everything's coming your way, you're in the wrong lane"
Standard User acting_funny
(member) Sat 29-Oct-11 16:10:22
Print Post

Re: Windows 7 BSODs continue


[re: cheshire_man] [link to this post]
 
core i5s are rated to 72°c by intel (http://ark.intel.com/products/48496/Intel-Core-i5-76...) if you want to test prime95 further.

Edited by acting_funny (Sat 29-Oct-11 16:11:08)

Standard User cheshire_man
(fountain of knowledge) Sat 29-Oct-11 17:19:52
Print Post

Re: Windows 7 BSODs continue


[re: BP1] [link to this post]
 
Just looked at the PSU.

It's a Coolermaster RS-500-PSAP-J3

DC Output   |   +3.3V   |   +5V   |  +12V1    |  +12V2  |    -12V    |  +5VSB   |
            |    22A    |   20A   |   20A     |   20A   |    0.8A    |  2.5A    |
Max.Output  |          130W       |         360W        |    9.6W    |  12.5W   |

I've no idea whether this PSU is in the good, bad or ugly category.

Tony
Standard User OCdragon
(experienced) Sun 30-Oct-11 10:26:45
Print Post

Re: Windows 7 BSODs continue


[re: cheshire_man] [link to this post]
 
In reply to a post by cheshire_man:
Just looked at the PSU.

It's a Coolermaster RS-500-PSAP-J3

DC Output   |   +3.3V   |   +5V   |  +12V1    |  +12V2  |    -12V    |  +5VSB   |
            |    22A    |   20A   |   20A     |   20A   |    0.8A    |  2.5A    |
Max.Output  |          130W       |         360W        |    9.6W    |  12.5W   |


Your existing PSU is a very branded version, around 500W, and its +12V (via its dual-rails V1&V2) has a total of 40A (not continuous) which should be good enough in most cases. However you still cannot guarantee in its "dynamic states" (i.e. spurious not measurable by ordinary multimeters due to system noises or design degradations etc) would not have caused sufficient voltage-spikes on your above DC rails, causing your MD to fail! Therefore the only way, as I see it, is to try another "known good" PSU with similar or better ratings both in terms of DC Rail-Voltages, max currents and power!
Good luck

Intel E4300 OC with 2GB RAMs,Speedtouch 585 Modem/Router and Windows XP Pro

O2 Standard ADSL2+ Broadband!
Standard User cheshire_man
(fountain of knowledge) Sun 30-Oct-11 13:40:41
Print Post

Re: Windows 7 BSODs continue


[re: OCdragon] [link to this post]
 
One minor question - what does MD mean in this context? Perhaps an alternative to mother board?

Tony
Standard User OCdragon
(experienced) Sun 30-Oct-11 17:21:19
Print Post

Re: Windows 7 BSODs continue


[re: cheshire_man] [link to this post]
 
Yeah! My finger trouble when typing this response! Should have meant "MB" which means your motherboard instead. Sorry and good luck in finding the root/s of your BSOD.

Intel E4300 OC with 2GB RAMs,Speedtouch 585 Modem/Router and Windows XP Pro

O2 Standard ADSL2+ Broadband!
Standard User Seansmit17
(eat-sleep-adslguide) Mon 31-Oct-11 01:12:03
Print Post

Re: Windows 7 BSODs continue


[re: OCdragon] [link to this post]
 
Getting a new PSU to test is a good idea.

But try and get one that has 1 12v rail and not 2 or more

something like this

http://www.ebuyer.com/264509-ocz-zs-series-550w-80-b...

or if you want cheaper

http://www.ebuyer.com/268696-coolermaster-450w-gx-ps...

BT 8MB
Standard User OCdragon
(experienced) Mon 31-Oct-11 10:43:10
Print Post

Re: Windows 7 BSODs continue


[re: Seansmit17] [link to this post]
 
In reply to a post by Seansmit17:
or if you want cheaper

http://www.ebuyer.com/268696-coolermaster-450w-gx-ps...


Does'nt mean wanted to hijack the original mail!
This particular PSU should be good and, particularly it is from Coolermaster 450W GX PSU brand as well. However the Ebuyer's still does'nt mention WHAT are the maximum current ratings, particularly the +12V rail, for each voltage rails! But there are 4+4 pins been allocated to the +12V rail in its PSU connector , which means the +12V maximum output currents may be significantly HIGH by design, or is it??

Intel E4300 OC with 2GB RAMs,Speedtouch 585 Modem/Router and Windows XP Pro

O2 Standard ADSL2+ Broadband!

Edited by OCdragon (Mon 31-Oct-11 10:47:05)

Standard User Chrysalis
(eat-sleep-adslguide) Mon 31-Oct-11 23:42:28
Print Post

Re: Windows 7 BSODs continue


[re: OCdragon] [link to this post]
 
coolermaster silent pro M line is a solid psu to choose and it has single 12v rails meaning you less likely to hit an issue with overloading a rail.
Standard User 12eason
(eat-sleep-adslguide) Tue 01-Nov-11 06:30:37
Print Post

Re: Windows 7 BSODs continue


[re: cheshire_man] [link to this post]
 
IF (big if) it's the PSU, you can monitor the voltages on the exotics tab of speedfan.

___________________________________________________________________
           Firenet - V21 - Fast4 - f·2·s - eclipseinternet - entanet - aaisp.net - plusnet
Standard User Deadbeat
(knowledge is power) Tue 01-Nov-11 23:50:27
Print Post

Re: Windows 7 BSODs continue


[re: cheshire_man] [link to this post]
 
Try disabling (If onboard) or removing the NIC and substituting with a known good PCI card.
Standard User cheshire_man
(knowledge is power) Wed 02-Nov-11 09:35:06
Print Post

Re: Windows 7 BSODs continue


[re: Deadbeat] [link to this post]
 
The NIC is on board, is a Realtek RTL8111E chip.

There is a BIOS setting "Onboard H/W LAN" currently set to Enabled. I presume set it to Disabled then the plug in card should be found and driver can be loaded.

Tony
Standard User cheshire_man
(knowledge is power) Sun 06-Nov-11 15:36:38
Print Post

Re: Windows 7 BSODs continue


[re: cheshire_man] [link to this post]
 
I'm continuing to try things, but still getting BSODs and the occasional freeze.

Some recent observations:

The PC froze today, as usual the mouse laser went out and the whole system was dead. Screen still ok but no visible disc activity or response to caps lock etc. As it happened I had headphones on at the time and as soon as it froze I realised that there was a hum through the headphones, similar to a mains hum.

Any diagnostic significance?

Having earlier today (after the freeze) reseated the memory, the graphics card, and one of the power connectors (couldn't get one of them off so didn't do that one). Then maybe an hour or so later the screen flickered and a message box appeared at bottom right saying the graphics card/driver/subsystem (can't remember which) had stopped and had recovered.

Any diagnostic significance?

I'll be talking to the local shop that built the system in the next few days, I have a very good relationship with them. I'll be asking if they can try a different graphics cards (any VERY safe recommendations?); similarly try a separate LAN card and disable the onboard LAN chip (again, any recommendations?); possibly even try another PSU.

Any other constructive thoughts gratefully received.

Tony
Standard User BP1
(committed) Sun 06-Nov-11 19:58:03
Print Post

Re: Windows 7 BSODs continue


[re: cheshire_man] [link to this post]
 
In reply to a post by cheshire_man:
I'm continuing to try things, but still getting BSODs and the occasional freeze.

Some recent observations:

The PC froze today, as usual the mouse laser went out and the whole system was dead. Screen still ok but no visible disc activity or response to caps lock etc. As it happened I had headphones on at the time and as soon as it froze I realised that there was a hum through the headphones, similar to a mains hum.

Any diagnostic significance?

Having earlier today (after the freeze) reseated the memory, the graphics card, and one of the power connectors (couldn't get one of them off so didn't do that one). Then maybe an hour or so later the screen flickered and a message box appeared at bottom right saying the graphics card/driver/subsystem (can't remember which) had stopped and had recovered.

Any diagnostic significance?

I'll be talking to the local shop that built the system in the next few days, I have a very good relationship with them. I'll be asking if they can try a different graphics cards (any VERY safe recommendations?); similarly try a separate LAN card and disable the onboard LAN chip (again, any recommendations?); possibly even try another PSU.

Any other constructive thoughts gratefully received.


I still think its psu related. Just seems simular to the problems i had which all dissapeared once the psu was replaced.

Regards

BP1

BTBroadband

"When everything's coming your way, you're in the wrong lane"
Standard User cheshire_man
(knowledge is power) Tue 22-Nov-11 13:16:58
Print Post

Re: Windows 7 BSODs continue - resolved


[re: cheshire_man] [link to this post]
 
Worthy of an update now the problem is resolved.

Monday last week I took the PC to my local shop for them to have a look at.

They ran tests on memory - passed; CPU - passed; motherboard - passed; PSU - passed. At no stage did they get a BSOD (typical!)

Then they put their collective heads together and came to the conclusion that it was a memory problem. So to include the relevant bit of their email to me:

"We believe it was your ram modules that were causing your blue screen issues; your old ram was the hyper Tec value ram 1.65v in which we have now replaced with 4 GB corsair Vengeance 1.5v Ram.

The Sandybridge motherboard you have has a maximum voltage memory controller which can handle up to 1.59v.

We could probably tweak the motherboard to give more stability with your old ram but the best way is to simply replace the Ram to the 1.5v memory controller."


I've now had it back for over a week and it has run without a hiccough - previously the longest time BSOD free was 6 days (once) more normally 1-2 days.

So, in a week or so when I've got time, I'll rebuild to get a clean system - it's got a bit messy with diagnostic software, etc.

Thanks to all who offered their advice and guidance. Clearly the new memory would have cost somewhat more than the old so they lost a little but they know I'll bring more business, where they are reasonably competitive, because their service is so good.

Tony
Pages in this thread: 1 | 2 | 3 | 4 | >> (show all)   Print Thread

Jump to