Archived

This topic is now archived and is closed to further replies.

vybhav

Blue Screen :(

Recommended Posts

Hello Jim and others

 

I have been experiencing Blue Screens from by other FSX computer. I am not sure if it is a hardware problem and if it is which hardware. Could you guys help

 

1st Error

Version=1
EventType=BlueScreen
EventTime=130159421186228195
ReportType=4
Consent=1
ReportIdentifier=0d66059c-d741-11e2-8dd8-c8600014af5d
IntegratorReportIdentifier=061713-9438-01
Response.type=4
DynamicSig[1].Name=OS Version
DynamicSig[1].Value=6.1.7601.2.1.0.256.1
DynamicSig[2].Name=Locale ID
DynamicSig[2].Value=1033
UI[2]=C:\Windows\system32\wer.dll
UI[3]=Windows has recovered from an unexpected shutdown
UI[4]=Windows can check online for a solution to the problem the next time you go online.
UI[5]=&Check for solution
UI[6]=&Check later
UI[7]=Cancel
UI[8]=Windows has recovered from an unexpected shutdown
UI[9]=A problem caused Windows to stop working correctly.  Windows will notify you if a solution is available.
UI[10]=Close
Sec[0].Key=BCCode
Sec[0].Value=124
Sec[1].Key=BCP1
Sec[1].Value=0000000000000000
Sec[2].Key=BCP2
Sec[2].Value=FFFFFA800FD5A028
Sec[3].Key=BCP3
Sec[3].Value=00000000BE000000
Sec[4].Key=BCP4
Sec[4].Value=0000000000800400
Sec[5].Key=OS Version
Sec[5].Value=6_1_7601
Sec[6].Key=Service Pack
Sec[6].Value=1_0
Sec[7].Key=Product
Sec[7].Value=256_1
File[0].CabName=061713-9438-01.dmp
File[0].Path=061713-9438-01.dmp
File[0].Flags=589826
File[0].Type=2
File[0].Original.Path=C:\Windows\Minidump\061713-9438-01.dmp
File[1].CabName=sysdata.xml
File[1].Path=WER-12027-0.sysdata.xml
File[1].Flags=589826
File[1].Type=5
File[1].Original.Path=C:\Windows\Temp\WER-12027-0.sysdata.xml
File[2].CabName=Report.cab
File[2].Path=Report.cab
File[2].Flags=196608
File[2].Type=7
File[2].Original.Path=Report.cab
FriendlyEventName=Shut down unexpectedly
ConsentKey=BlueScreen
AppName=Windows
AppPath=C:\Windows\System32\WerFault.exe

 

 
 
 

2nd Error
Version=1
EventType=BlueScreen
EventTime=130158476573060242
ReportType=4
Consent=1
ReportIdentifier=1d3d17d3-d665-11e2-ac99-c8600014af5d
IntegratorReportIdentifier=061613-9313-01
Response.type=4
DynamicSig[1].Name=OS Version
DynamicSig[1].Value=6.1.7601.2.1.0.256.1
DynamicSig[2].Name=Locale ID
DynamicSig[2].Value=1033
UI[2]=C:\Windows\system32\wer.dll
UI[3]=Windows has recovered from an unexpected shutdown
UI[4]=Windows can check online for a solution to the problem the next time you go online.
UI[5]=&Check for solution
UI[6]=&Check later
UI[7]=Cancel
UI[8]=Windows has recovered from an unexpected shutdown
UI[9]=A problem caused Windows to stop working correctly.  Windows will notify you if a solution is available.
UI[10]=Close
Sec[0].Key=BCCode
Sec[0].Value=9c
Sec[1].Key=BCP1
Sec[1].Value=0000000000000000
Sec[2].Key=BCP2
Sec[2].Value=FFFFF88003508B70
Sec[3].Key=BCP3
Sec[3].Value=0000000000000000
Sec[4].Key=BCP4
Sec[4].Value=0000000000000000
Sec[5].Key=OS Version
Sec[5].Value=6_1_7601
Sec[6].Key=Service Pack
Sec[6].Value=1_0
Sec[7].Key=Product
Sec[7].Value=256_1
File[0].CabName=061613-9313-01.dmp
File[0].Path=061613-9313-01.dmp
File[0].Flags=589826
File[0].Type=2
File[0].Original.Path=C:\Windows\Minidump\061613-9313-01.dmp
File[1].CabName=sysdata.xml
File[1].Path=WER-13322-0.sysdata.xml
File[1].Flags=589826
File[1].Type=5
File[1].Original.Path=C:\Windows\Temp\WER-13322-0.sysdata.xml
File[2].CabName=Report.cab
File[2].Path=Report.cab
File[2].Flags=196608
File[2].Type=7
File[2].Original.Path=Report.cab
FriendlyEventName=Shut down unexpectedly
ConsentKey=BlueScreen
AppName=Windows
AppPath=C:\Windows\System32\WerFault.exe

 

 

Regards
Vybhav

Share this post


Link to post
Share on other sites
Help AVSIM continue to serve you!
Please donate today!

Stop Code 0124 indicates a driver issue or hardware problem. A common BSOD. If you just recently updated a driver, that could be the issue.  Uninstall/reinstall.  You can download and run a program called BlueScreenView - http://www.nirsoft.net/utils/blue_screen_view.html.  It might provide you more information about the BSOD.  I do not see a Stop Code for the second BSOD but it is probably related.  A piece of hardware may not be seated properly in the MB too.  Unfortunately there are a lot of issues.

 

To check for driver problems, I run a program about twice a week called Driver Scanner.  It is freeware to run and check for outdated drivers and payware if you want them to download and install the updates.  But at least you'll see if you have a problem with a driver.

 

You can also try running a scan on your system to look for corrupted files - http://pcsupport.about.com/od/toolsofthetrade/ht/sfc-scannow.htm.  If it finds corrupted system files, the program will replace them.  Good luck!

 

Best regards,

Jim

Share this post


Link to post
Share on other sites