But AidenShaw's brochure says Windows BSOD is only a myth these days???
BSODs are as rare as kernel panics.
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Google Launches Nexus One: T-Mobile Plan Available Now, Verizon and Vodafone Coming Soon
- Thread starter QCassidy352
- Start date
- Sort by reaction score
BSODs are as rare as kernel panics.
In accordance to the scripture of a devout Mojave's Witness.But AidenShaw's brochure says Windows BSOD is only a myth these days???
So rare, that Windows actually has an event/error called "BlueScreen."
Not if you do that registry hack on all the computers at school using a VB script which the computer admins forgot to put restrictions on and it BSODs whenever you use IE.
Comp Tech was fun.
---
BSODs are rarer now, but Windows 7 is still windows.
Had another one yesterday but I have no ideas why they are happening.
I've sent the reports off but there is no solution from Microsoft so far.
I shall await a response for one of my crash reports. Thanks for asking!
Had another one yesterday but I have no ideas why they are happening.
I've sent the reports off but there is no solution from Microsoft so far.
I shall await a response for one of my crash reports. Thanks for asking!
One thing to try - Windows has a "verifier" mode where it performs lots of extra consistency checks on the way that kernel APIs are called. If it finds a problem, you'll blue-screen in the verifier with the bad driver called out.
I helped a friend build a Win7 Core i7 system - it ran fine for about two weeks, then started randomly crashing (sometimes while in use, sometimes he'd turn the monitor on in the morning and a BSOD would be there). Memory testing (both with Windows built-in memory tester, and with Memtest86+) showed no problems.
Turned on the verifier, and it wouldn't even boot - crashed every time early in boot (at the fuzzy flag logo). The bluescreen said "error during verification" and showed the name of a driver for a gaming mouse. Removed, then updated that driver - happy now.
The verifier has a clever command name - "verifier". Read about it at http://msdn.microsoft.com/en-us/library/ms792861.aspx
Just pick the standard options - the optional tests are torture tests for out-of-memory and other conditions.
Note that if you're lucky enough to get an immediate bluescreen everytime on booting, you'll need to boot into safe mode and either turn the verifier off or uninstall the bad driver to fix it.
Dohoho.... virtually every BSOD is caused by third party drivers OR bad hardware.
I would tell you to look it up but it's not like if you were able to make sense out of this.
And "Windows 7 runs fine in boot camp but OSX kernel panics" or "OSX runs fine but
Windows 7 BSODs constantly" does not mean that it's not hardware.
When I worked at Digital in the '80s one of the mainstream MicroVAX systems would run VMS
without issues, but would crash frequently when running UNIX (Ultrix).
It turned out to be a hardware design error in the memory system, not a UNIX bug.
(SDRAM needs to be refreshed periodically or the memory cells lose state. A bug in the MicroVAX
memory controller would forget to refresh banks of memory that weren't touched for a second or so.
It turned out that VMS allocated physical pages of memory quite randomly, so it was very
unlikely that a bank of memory (containing many pages) wouldn't be touched.
UNIX was more "orderly" about allocating physical pages (even though there was no benefit to
doing that), and would frequently end up with big regions of physical memory allocated to a
single process. If that process were idle for a few seconds, it could wake up to find large
chunks of memory reset to zeroes. This would cause an application crash for userland memory,
or a system kernel panic if it were process-specific kernel memory.
The "fix" wasn't to change the hardware, but to put code into the timer routines (on both VMS
and UNIX) to touch each bank of memory often enough to force a refresh before data was lost.)
memory controller would forget to refresh banks of memory that weren't touched for a second or so.
It turned out that VMS allocated physical pages of memory quite randomly, so it was very
unlikely that a bank of memory (containing many pages) wouldn't be touched.
UNIX was more "orderly" about allocating physical pages (even though there was no benefit to
doing that), and would frequently end up with big regions of physical memory allocated to a
single process. If that process were idle for a few seconds, it could wake up to find large
chunks of memory reset to zeroes. This would cause an application crash for userland memory,
or a system kernel panic if it were process-specific kernel memory.
The "fix" wasn't to change the hardware, but to put code into the timer routines (on both VMS
and UNIX) to touch each bank of memory often enough to force a refresh before data was lost.)
Long anecdote, but it shows that the crashing OS can be blameless.
Do you really want those of us in the loyal opposition to bring up Mac OS 8/9 horror
stories about cooperative multi-tasking and lack of memory protection? Or even the
public alpha known as 10.0?
I didn't think so.
"Childhood memories" include wetting the bed and diapers - butwe grow out of that. (usually)
Let's keep the talk about 10.6 (and maybe 10.5) and Win7 (and maybe Vista) only - not
systems that were replaced ages ago.
Both Apple and Microsoft continually improve the product - let's focus on the current
offerings.
Do you really want those of us in the loyal opposition to bring up Mac OS 8/9 horror
stories about cooperative multi-tasking and lack of memory protection? Or even the
public alpha known as 10.0?
I didn't think so.
Let's keep the talk about 10.6 (and maybe 10.5) and Win7 (and maybe Vista) only - not
systems that were replaced ages ago.
Both Apple and Microsoft continually improve the product - let's focus on the current
offerings.
To be accurate you should include XP. Still more XP around than anything else.
Do you really want those of us in the loyal opposition to bring up Mac OS 8/9 horror
stories about cooperative multi-tasking and lack of memory protection? Or even the
public alpha known as 10.0?
I didn't think so.
we grow out of that. (usually)
Let's keep the talk about 10.6 (and maybe 10.5) and Win7 (and maybe Vista) only - not
systems that were replaced ages ago.
Both Apple and Microsoft continually improve the product - let's focus on the current
offerings.
The point of that flew right over your head.
Why dont we talk about redundant coupling water-cooling systems for virtualization clusters instead.
XP is around, but can you really criticize Microsoft for issues with XP
that have been corrected in the current version? (For example, the loonies
who complain that "you click 'Start' to shutdown the system" - when the label
"Start" disappeared two years ago.)
I think not - it is unfair to criticize either Apple or Microsoft for issues
that do not exist in their latest releases.
It absolutely flew over my head, and it still does. What the heck are you talking about? Cryptic four word comments with
incorrect punctuation make it hard to completely understand the totality of your thoughts.
On the surface, one could take your comment to mean "Windows 7 sucks because Win98SE BSOD'd
if you sneezed while using it" - an idea expressed here often enough. A few more words to explain
your comment would help us understand you. If you meant "Win98SE BSOD'd if you sneezed - thank goodness
Microsoft has improved a lot since then" then please give us all a clue.
Two kernel panics a week is pretty rare - have you checked your Apple for memory errors or other hardware problems?
Or, for example, the ignorant loony who complained that dragging a disk icon to the trash was counter intuitive, not realizing that the trash can itself morphs into an 'Eject' icon, a change which had been in effect since Tiger.
Had another one yesterday but I have no ideas why they are happening.
I've sent the reports off but there is no solution from Microsoft so far.
I shall await a response for one of my crash reports. Thanks for asking!
Hey Chaz, I see you've got the Archos 5 with Android; how is it? Can you access the Android Market from it? Looks cool!
No android market but there are methods to add it to the device.
If I want anything paid or not from the market I just download and buy it from the market, back up the app to the SD card on my Hero and transfer the APK to my Archos.
I think the thing is great but if you were looking into an Android tablet, the Dell Streak as that looks like a fine little machine!
No android market but there are methods to add it to the device.
If I want anything paid or not from the market I just download and buy it from the market, back up the app to the SD card on my Hero and transfer the APK to my Archos.
I think the thing is great but if you were looking into an Android tablet, the Dell Streak as that looks like a fine little machine!
Device looks cool and all, but what the **** is up with that music.
Wirelessly posted (Mozilla/5.0 (Linux; U; Android 1.6; en-us; Archos5 Build/Donut) AppleWebKit/528.5+ (KHTML, like Gecko) Version/3.1.2 Mobile Safari/525.20.1)
I was more worried.about his extra thumb!
cumanzor said:No android market but there are methods to add it to the device.
If I want anything paid or not from the market I just download and buy it from the market, back up the app to the SD card on my Hero and transfer the APK to my Archos.
I think the thing is great but if you were looking into an Android tablet, the Dell Streak as that looks like a fine little machine!
Device looks cool and all, but what the **** is up with that music.
I was more worried.about his extra thumb!