Why does there seem to be more BSODs with Win 7?

Microsoft cannot install the NIC/modem/LAN driver because it isn't on line yet after initial install.
So that is one of the first if not the first driver you need to install after Win7 is installed.

You would have the same problem with XP or Vista.
My old XP with dial up wouldn't call out without the XP modem driver first.
Sort of like you can't dial a phone without the keypad. The "driver" is the keypad to "dial out". ;) :D
 

My Computer My Computer

At a glance

Windows7 Pro 64bit SP-1; Windows XP Pro 32bitIntel Core i7-870 Lynnfield 2.93GHz LGA 1156 ...8GB@1400MHz Crucial Ballistix DDR3-1600 4x2GBASUS ENGTX460 DirectCU/2DI/1GD5 1GB 256-bit G...
Computer Manufacturer/Model Number
Hopalong/ Godzilla
OS
Windows7 Pro 64bit SP-1; Windows XP Pro 32bit
CPU
Intel Core i7-870 Lynnfield 2.93GHz LGA 1156 95W Quad-Core
Motherboard
ASUS P7P55D-E PRO
Memory
8GB@1400MHz Crucial Ballistix DDR3-1600 4x2GB
Graphics Card(s)
ASUS ENGTX460 DirectCU/2DI/1GD5 1GB 256-bit GDDR5
Sound Card
VIA Onboard
Monitor(s) Displays
Asus VS248H-P 24"; Samsung SyncMaster 941BW 19"ws
Screen Resolution
1920x1080; 1440x900
Hard Drives
Samsung 830 120GB SSD
Intel 320 120GB SSD
Western Digital Caviar Black WD7501AALS 750GB 7200 RPM SATA 3.0Gb/s
Western Digital Caviar Black WD6401AALS 640GB 7200 RPM SATA 3.0Gb/s
PSU
COOLER MASTER Silent Pro RS850-AMBAJ3-US 850W Modular
Case
COOLER MASTER HAF 932 RC-932-KKN5-GP Black
Cooling
Scythe "Mugen-2 Rev.B" (2 ScytheKaze-Jyuni PWM fans)
Keyboard
Logitech K-320
Mouse
Kensington
Antivirus
Avast Inernet Suite
Browser
IE 9 ; Chrome
The problem is resolved.
biggrin.gif


Although I've posted much of this on the thread on the Crashes and Debugging forum it may be helpful to post similarly here. I'll apologise in advance if I shouldn't have done this.

Nearly 2 weeks ago I got my PC back from my local shop where it had been for them to investigate.

They'd runn 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 nearly 2 weeks and it has run without a hiccough - previously the longest time BSOD free was 6 days (once) more normally 1-2 days.
biggrin.gif


So, in a few days 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.

I wholeheartedly withdraw my view that Windows 7 is more BSOD prone than XP. The more I use it the more I like it.
 

My Computer My Computer

At a glance

Windows 7 Professional 64-bit2.80 gigahertz Intel Core i5 7604 GbytesNVIDIA GeForce GT 430
Computer Manufacturer/Model Number
Local PC Shop
OS
Windows 7 Professional 64-bit
CPU
2.80 gigahertz Intel Core i5 760
Motherboard
Gigabyte Technology Co., Ltd. P55-USB3
Memory
4 Gbytes
Graphics Card(s)
NVIDIA GeForce GT 430
Sound Card
Integrated
Monitor(s) Displays
Relisys 17"
Screen Resolution
1280x1024
Hard Drives
1 Tb Seagate ST31000528AS
PSU
Not known
Case
Not known
Cooling
Not known
Keyboard
DEC standard office, wired
Mouse
Basic Microsoft optical wheel mouse, wired
Internet Speed
8Mbits/second
Back
Top