First bsod, computer was idle. I'm diagnosing it now.
-
-
Well crap, the minidump folder is empty no log of it. I should have written down the error code right away. Oh well, Dookie, looks like you're not alone in r3 bsods.
EDIT: Nvm found it, its a 0x0000003b error:
0x0000003b (0x00000000c0000005, 0xfffff88004d45267, 0xfffff8800c3417a0, 0x0000000000000000)
Its going to take awhile to figure out since it could be anything hardware related at this point. -
I got one too :/ and it,s the second time. It's occure when I'm playing with fraps, after like 10-15mn ingame, Fps drow to 5-15 so i close de game and my pc run slowly after that, bsod...
That,s my screen:
http://img858.imageshack.us/img858/7921/img0780p.jpg
Someone can help me ?? -
pattern with BSODS seems to be when anything is updating, windows - games - drivers etc could this be a Windows 7 SP1 problem ? perhaps not installing SP1 might be a good idea right now
http://www.winmatrix.com/forums/ind...e-screen-of-death-bsod-due-to-language-packs/
http://windows7forums.com/blue-screen-death-bsod/59732-bsod-after-windows-7-sp1-update.html
http://www.downloadatoz.com/driver/...-of-death-error-caused-by-language-packs.html -
But I don't have installed yet.
-
can you guys list your specs, so we can see if there is anything in common with people getting this problem.
-
-
It,s occur when i play with fraps on bfbc2 and Crysis2.
When i was playing without fraps, all good, but it's start again with fraps activated when i was screening. I had time to close all software and games and no bsod.
So, i think it's due of a software but which one, I don,t know :/ -
I am avoiding W7 SP1 for a while on all of my machines. Too many issues with it right now.
-
not saying these bsods are all due to Updates or W7 but I wouldn't lay blame with R3, after doing a google search of bsods and W7, I'm a lot happier that Alienware R3 is nothing to do with 99% of these errors, Windows 7 seems to be very unstable, maybe SP1 solves some of these if you can actually get it installed -
My only upgrades over stock are intel 6300, AMD 6970m, 8GB HyperX, 2720qm, and a seagate momentus XT.
-
Remember to uninstall all unused language packs before attempting to install SP1 or anything else for that matter
-
Yes but I never had these before... Why??? I thinks it's began when I just remove my gpu but I don,t put over the heatsink...
i just hope it,s not any problems due of the bugging chipset :/ -
I got 1 SSd where all my games are and one HDD where windows is installed; I look that there are soft running: intel rapid storage.
it can be that u think?? Because I know that soft can cause bsod with SSD... :? -
I had the 3d R3, 2720qm ,750 gb hardrive. It blue screened causing the hard drive to become unreadable. Once windows 7 was able to be re-installed it always crashed when the nvidia drivers were installed. I also have another dell computer that has service pack 1 with zero problems. The problem lies with the R3. Dookie has a 6970 and his BSOD'd as well meaning that its the R3 not just the graphics card driver for nvidia.
-
The Nvidia driver from Dell for R3 cause bsod, I had the same issue.
-
did you uninstall language packs as recommended by microsoft ?
-
There are 3 gaming machines in my house all with SP1, never a bsod. R3 is running Dell's stock OS install.
-
look i'm just relating to what i found on a google search, did these machine have sp1 or did you update them. are there language packs installed, there are variables here - are you trying to say the R3 is faulty in some way, I'm reading by MS's own admission they have bsod issues, perhaps sp1 fixes some of them if you manage to get it installed (repeated twice now)
i'm done here, I'm satisfied MS has a few things they need to sort out with windows 7, I've nothing more to contribute here. -
OKay guys, it is NOT sp1... so please do not blame it on windows 7. It's a tech issue that needs to be resolved on a tech level. Be prepared to reinstall windows and be on the phone with tech support for a little while. Keep this thread going and see how many people who upgraded (would say 90%) and have this problem.... not I says the gamer, so it's something else.
-
I don,t have sp1.. and i saw that i had bsod when i screen with Fraps
-
I wonder why he is so defensive about R3 and absolutely blaming windows as if he has rock solid evidence. I have observed his posts in previous threads too...super over the top insistence that his version of R3 is the right buy. nvidia 485m and now over the cause of bsod.
Neurotic. -
99% of BSOD's are caused by hardware failure or bad drivers. In this case I would guess the RAM is bad or the nvidia drivers are bad. If you install from scratch it seems the nvidia causes BSOD immediately, so that would be my first guess. INF mod the latest stock drivers from NVIDIA and use those for testing. I would run a boot cd and leave RAM test running for an hour per stick in the machine, 4 sticks = 4 hours, if you get errors start pulling sticks out one by one, or test them one by one.
-
-
No language packs. Stock installs. Did you clean format? -
I am not being defensive mate, I only deal with facts and when Microsoft admit they have a problem then I regard that as fact, and NV - you are half right - bsods can be caused by hardware or like I believe in many instances here - with windows 7 or poor drivers or conflicts with drivers and windows, MS already admits problems so I'll go with that. -
Forget it Captain! I know birds of a flock squeak together too! The need for reassurance over one's own purchase shouldn't be garnered by badgering others...
Originally Posted by Geoffxx
" pattern with BSODS seems to be when anything is updating, windows - games - drivers etc could this be a Windows 7 SP1 problem ? perhaps not installing SP1 might be a good idea right now"
Originally Posted by Geoffxx
" not saying these bsods are all due to Updates or W7 but I wouldn't lay blame with R3, after doing a google search of bsods and W7, I'm a lot happier that Alienware R3 is nothing to do with 99% of these errors, Windows 7 seems to be very unstable, maybe SP1 solves some of these if you can actually get it installed "
Originally Posted by Geoffxx
" look i'm just relating to what i found on a google search, did these machine have sp1 or did you update them. are there language packs installed, there are variables here - are you trying to say the R3 is faulty in some way, I'm reading by MS's own admission they have bsod issues, perhaps sp1 fixes some of them if you manage to get it installed (repeated twice now)
i'm done here, I'm satisfied MS has a few things they need to sort out with windows 7, I've nothing more to contribute here."
Hmmmm....I leave it to you to understand your psychology. But I would be happy if you can still smile and not be grumpy...BUT I can tell you 2 things for sure. The BSOD caused in R3 has very little to do with Windows 7 and by God, Windows 7 is one the most stable OS released by Microsoft. I am running it since beta release and its phenomenal... -
lol
amazing
-
nvidia drivers with 3d setup cause bsod all over the place.
nvidia drivers with optimus caused 2 bsod out-of-box, before reinstalling windows (they didn't cause bsod again after this).
For me, having any usb device plugged into right side usb 2.0 ports on startup causes bsod
Installing and using SP1 for 2+ weeks = no bsod at all, so I doubt it has anything to do with 7sp1
original specs:
2630, 460 + optimus +1080p 60hz, ssd + 320gb hdd @ahci, aftermarket ram (8-16gb hyperX) -
Mechanized Menace Lost in the MYST
Download details: Windows Service Pack Blocker Tool Kit
you can install that to block it from auto updating through windows update,
it wont stop you from installing it from cd/dvd/downloaded installer. Just windows update -
http://forum.notebookreview.com/ali...7xr3-w-460m-dell-oem-nvidia-driver-issue.html -
Which is why I posted it (I never have and never will own a 3d r3)
-
-
lets not get into the whole ati vs nvidia thing.
can you guys run this to see what it says.
Resplendence Software - WhoCrashed, automatic crash dump analyzer
also try going into the bios and set your ram frequency -
My WhoCrashed report:
Home Edition Notice
--------------------------------------------------------------------------------
This version of WhoCrashed is free for use at home only. If you would like to use this software at work or in a commercial environment you should ge the professional edition of WhoCrashed which also allows analysis of crashdumps on remote drives and computers on the network and offers a range of additional features.
Click here for more information on the professional edition.
Click here to buy the the professional edition of WhoCrashed.
--------------------------------------------------------------------------------
System Information (local)
--------------------------------------------------------------------------------
computer name: RENEGADE
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
CPU: GenuineIntel Intel(R) Core(TM) i7-2720QM CPU @ 2.20GHz Intel586, level: 6
8 logical processors, active mask: 255
RAM: 8535224320 total
VM: 2147352576, free: 1939054592
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Sun 4/3/2011 7:29:00 AM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: Unknown (0x00000000)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF88004D39267, 0xFFFFF8800A9AD7A0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: Unknown .
Google query: Unknown SYSTEM_SERVICE_EXCEPTION
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
1 crash dumps have been found and analyzed. A third party driver has been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:
unknown
If no updates for these drivers are available, try searching with Google on the names of these drivers in combination the errors that have been reported for these drivers and include the brand and model name of your computer as well in the query. This often yields interesting results from discussions from users who have been experiencing similar problems.
Read the topic general suggestions for troubleshooting system crashes for more information.
Note that it's not always possible to state with certainty whether a reported driver is actually responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.
_______________
The results are pretty funny, especially where it says to google the company "Unknown", but it did conclude that its not hardware. -
MSDN article: Bug Check 0x3B: SYSTEM_SERVICE_EXCEPTION
-
Whatever you read between the lines is out of my control. -
-
if you want to see what's bsoding....
click windows orb thinggy and type
reliability history
run the program it finds via that search
click on one of the red circle with an x in it
double click on one of the programs listed under "critical events"
copy/pasta the info -
Pasta that info...mmm pasta
-
Nice.
-
1st BSOD while updating to SP1 (the update never finished).
Source
Windows
Summary
Shut down unexpectedly
Date
3/26/2011 9:14 PM
Status
Not reported
Problem signature
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.768.3
Locale ID: 1033
Files that help describe the problem
032611-41730-01.dmp
sysdata.xml
WERInternalMetadata.xml
Extra information about the problem
BCCode: 3b
BCP1: 00000000C0000005
BCP2: FFFFF88004B0A267
BCP3: FFFFF8800997C8B0
BCP4: 0000000000000000
OS Version: 6_1_7600
Service Pack: 0_0
Product: 768_1
----------------
2nd BSOD while updating BFBC2:
Source
Windows
Summary
Shut down unexpectedly
Date
3/27/2011 10:25 AM
Status
Report sent
Problem signature
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.768.3
Locale ID: 1033
Extra information about the problem
BCCode: 3b
BCP1: 00000000C0000005
BCP2: FFFFF88004B4A267
BCP3: FFFFF880072398B0
BCP4: 0000000000000000
OS Version: 6_1_7600
Service Pack: 0_0
Product: 768_1
Bucket ID: X64_0x3B_atikmdag!DisplayManager2::NotifyModeChangeOccured+47
Server information: 2507a906-c6ba-4b17-9daa-d2399fabaebe
Could you tell me what's the problem ? Or should I try that program? -
that program will say something like "blablakernel.dll" which is what 99.99999% of BSOD fall under, so it's completely useless.
the .dmp files that they describe will contain more info tho. -
EDIT: NM, just ran WhoCrashed, and here's the results:
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Sun 3/27/2011 5:22:43 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\032711-55957-01.dmp
This was probably caused by the following module: atikmdag.sys (atikmdag+0x91267)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF88004B4A267, 0xFFFFF880072398B0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\drivers\atikmdag.sys
product: ATI Radeon Family
company: ATI Technologies Inc.
description: ATI Radeon Kernel Mode Driver
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: atikmdag.sys (ATI Radeon Kernel Mode Driver, ATI Technologies Inc.).
Google query: atikmdag.sys ATI Technologies Inc. SYSTEM_SERVICE_EXCEPTION
On Sun 3/27/2011 5:22:43 PM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: atikmdag.sys (atikmdag+0x91267)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF88004B4A267, 0xFFFFF880072398B0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\drivers\atikmdag.sys
product: ATI Radeon Family
company: ATI Technologies Inc.
description: ATI Radeon Kernel Mode Driver
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: atikmdag.sys (ATI Radeon Kernel Mode Driver, ATI Technologies Inc.).
Google query: atikmdag.sys ATI Technologies Inc. SYSTEM_SERVICE_EXCEPTION
On Sun 3/27/2011 4:12:42 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\032611-41730-01.dmp
This was probably caused by the following module: atikmdag.sys (atikmdag+0x91267)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF88004B0A267, 0xFFFFF8800997C8B0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\drivers\atikmdag.sys
product: ATI Radeon Family
company: ATI Technologies Inc.
description: ATI Radeon Kernel Mode Driver
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: atikmdag.sys (ATI Radeon Kernel Mode Driver, ATI Technologies Inc.).
Google query: atikmdag.sys ATI Technologies Inc. SYSTEM_SERVICE_EXCEPTION
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
3 crash dumps have been found and analyzed. 3 third party drivers have been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:
atikmdag.sys (ATI Radeon Kernel Mode Driver, ATI Technologies Inc.)
If no updates for these drivers are available, try searching with Google on the names of these drivers in combination the errors that have been reported for these drivers and include the brand and model name of your computer as well in the query. This often yields interesting results from discussions from users who have been experiencing similar problems.
Read the topic general suggestions for troubleshooting system crashes for more information.
Note that it's not always possible to state with certainty whether a reported driver is actually responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.
Supposedly it's the ATI drivers. (And this report doesn't indicate BSOD). So does this mean I should only be using Reliability History to check for BSODs? Or is it the same and doesn't have to say "BSOD" -
I was referring to whocrashed because I find the program utterly useless.
-
-
Hahahah.....I share the same view...but I was holding myself from saying the same....!
-
-
Guess I missed those links or something.
So how does one go about uninstalling language packs? -
Yeah whocrashed didn't tell me anything relibabilty history didn't. Still confused as to what do do about the bsods.
r3 bsod
Discussion in 'Alienware 17 and M17x' started by shadowyani, Apr 2, 2011.