Windows 7 bluescreen!
Discussion
I'm surprised nobody has slated Apple yet for producing crappy hardware and shoddy Windows drivers - hell, it's Apple's *duty* to make sure Windows is as stable as possible FFS!!!111!11oneone
BSOD are often hardware, yeah. But they can also be caused by duff code in the hardware drivers.
Make sure your RAM works first (reseat it, memtest it, etc.), install the correct drivers (presumably iTunes is ratified for Windows 7? I don't use it so can't say) and try again.
The iPod / iPhone all run over USB. So the core driver is the USB driver and that'll be Microsoft's code, and shouldn't be unreliable (if the bog standard USB driver in Win7 was flaky then EVERYONE would know about it). Then Apple bung something called the usbmuxd over the top (in *nix systems anyway, but a similar driver is likely to be running under Windows) and if this is 'driver' level (ring 0?) and Apple's code is crap, then yeah you'll get BSOD.
But if this was the case, EVERYONE would know about it (lots of Windows users with iPods, after all). Did you build this PC yourself? Make sure all the hardware works properly first.
One *really* nice thing about Mac boxes is that Apple includes a 'hardware test' bootable system on the restore DVDs - and it's pretty good at testing the entire machine and making sure hardware is OK - and if not, an error code that you can translate into meaningful diagnostics. Not sure about the PC world because there are so many different combinations of hardware you can build, but if you've at least got a memory tester then use that. Most hardware 'failures' are bad RAM...
BSOD are often hardware, yeah. But they can also be caused by duff code in the hardware drivers.
Make sure your RAM works first (reseat it, memtest it, etc.), install the correct drivers (presumably iTunes is ratified for Windows 7? I don't use it so can't say) and try again.
The iPod / iPhone all run over USB. So the core driver is the USB driver and that'll be Microsoft's code, and shouldn't be unreliable (if the bog standard USB driver in Win7 was flaky then EVERYONE would know about it). Then Apple bung something called the usbmuxd over the top (in *nix systems anyway, but a similar driver is likely to be running under Windows) and if this is 'driver' level (ring 0?) and Apple's code is crap, then yeah you'll get BSOD.
But if this was the case, EVERYONE would know about it (lots of Windows users with iPods, after all). Did you build this PC yourself? Make sure all the hardware works properly first.
One *really* nice thing about Mac boxes is that Apple includes a 'hardware test' bootable system on the restore DVDs - and it's pretty good at testing the entire machine and making sure hardware is OK - and if not, an error code that you can translate into meaningful diagnostics. Not sure about the PC world because there are so many different combinations of hardware you can build, but if you've at least got a memory tester then use that. Most hardware 'failures' are bad RAM...
LordGrover said:
Some may consider NSFW.
Not all BSOD are bad. Link to gratuitous image: click
I stumbled across a BSOD debugger type util the other day - I'll look it out when I get back to the office. It's supposed to reliably diagnose many BSODs.
FFS. What sort of girl would wear a t-shirt like that??? Certainly not an attractive one with tits like that, IME.Not all BSOD are bad. Link to gratuitous image: click
I stumbled across a BSOD debugger type util the other day - I'll look it out when I get back to the office. It's supposed to reliably diagnose many BSODs.
I think Apple are cocks for doing it, but it still makes me laugh that the standard icon in Mac OS X for a computer sharing files over the SMB protocol is a beige CRT monitor displaying the old Windows BSOD. It's not clever enough to tell whether the machine is actually using Windows or not... if it's a Mac or Linux box only exposing SMB sharing then it'll still use the PC BSOD icon...
From a bit of googling it looks like quite a few people have been having trouble with 64 bit Win 7 and iTunes, which is supposed to be a 64 bit version but apparently it's only the installer that is 64 bit.
It's a home build machine but I've got Win 7 drivers for everything.
Only had the machine running a couple of days but printer, joystick and mouse are running fine over USB. Tempted to stick XP on a spare hard drive to see if it's a hardware thing. Probably also worth trying the iPod on Firewire too.
It's a home build machine but I've got Win 7 drivers for everything.
Only had the machine running a couple of days but printer, joystick and mouse are running fine over USB. Tempted to stick XP on a spare hard drive to see if it's a hardware thing. Probably also worth trying the iPod on Firewire too.
cyberface said:
I'm surprised nobody has slated Apple yet for producing crappy hardware and shoddy Windows drivers - hell, it's Apple's *duty* to make sure Windows is as stable as possible FFS!!!111!11oneone
It's the design and coolness that blinds people. In fact apple and adobe seem to have the most of the security flaws these days....
to the OP, post the stop codes and what computer do you have make model etc
Oh and don't get me started on the scummy tricks of apple and google to trick you into installing their scummy products (safari, chrome google toolbar)... oh wait ... to late...
Edited by lestag on Tuesday 22 December 10:29
Machine's using an Asus M4A79XTD Evo motherboard with Windows 7 home premium 64 bit, and the 64 bit version of iTunes 9.0.2.25. Presumably the cause is going to be some form of clash with either some of my hardware or another bit of software, is anyone able to make sense of the log file to the cause? I have no idea how to interpret these things. Is this what you mean by stop codes?
http://www.sevenforums.com/attachments/software/42...
http://www.sevenforums.com/attachments/software/42...
Edited by RizzoTheRat on Tuesday 22 December 10:30
dump: Probably caused by : CBUFS.sys ( CBUFS+1f7fa )
similar problem here http://social.technet.microsoft.com/Forums/en/w7it...
similar problem here http://social.technet.microsoft.com/Forums/en/w7it...
Edited by TonyToniTone on Tuesday 22 December 11:23
LordGrover said:
Some may consider NSFW.
Not all BSOD are bad. Link to gratuitous image: click
I stumbled across a BSOD debugger type util the other day - I'll look it out when I get back to the office. It's supposed to reliably diagnose many BSODs.
BSOD Debugger would be good, please post!Not all BSOD are bad. Link to gratuitous image: click
I stumbled across a BSOD debugger type util the other day - I'll look it out when I get back to the office. It's supposed to reliably diagnose many BSODs.
Rizzo, Glad you got is sorted out looks like commodo is 32bit driver, you might want to see if they have 64bit driver.
Windows debuggers http://www.microsoft.com/whdc/devtools/debugging/w... or you can use dumpchk.exe that comes with the xp support tools.
Would be interested in that link if its not for the above..
Windows debuggers http://www.microsoft.com/whdc/devtools/debugging/w... or you can use dumpchk.exe that comes with the xp support tools.
Would be interested in that link if its not for the above..
Edited by TonyToniTone on Tuesday 22 December 12:25
much appreciatedOut of interest my PC is home built too, on Win 7 64. When I installed Zonealarm Free firewall it started getting BSODs whenever there was network activity (dodgy network driver?), as soon as I uninstalled it was fine.
My motherboard is 4 years old now though, getting an upgrade soon.
My motherboard is 4 years old now though, getting an upgrade soon.
RizzoTheRat said:
I've not bothered with Zone Alarm on this machine, though I always had it on my XP machine. I ran Shields Up! with just the windows firewall and my Linksys router and it passed everything.
That'll probably do for most who are worried about what's coming in. Zonealarm and it's like are good for watching/blocking what's going out too. Can't be arsed myself but it has its place.Gassing Station | Computers, Gadgets & Stuff | Top of Page | What's New | My Stuff