User Tag List

Page 1 of 2 1 2 LastLast
Results 1 to 20 of 28

Thread: What does this error mean?

  1. #1

    Default What does this error mean?

    Problem signature:
    Problem Event Name: BlueScreen
    OS Version: 6.1.7601.2.1.0.256.1
    Locale ID: 2057


    Additional information about the problem:
    BCCode: 7f
    BCP1: 0000000000000008
    BCP2: 0000000080050033
    BCP3: 00000000000406F8
    BCP4: FFFFF800030E4059
    OS Version: 6_1_7601
    Service Pack: 1_0
    Product: 256_1


    Files that help describe the problem:
    C:\Windows\Minidump\120312-14398-01.dmp
    C:\Users\kawsar\AppData\Local\Temp\WER-41387-0.sysdata.xml


    In order to fix it, Win reinstall?

  2. #2
    Member
    • shoryuken-x's Gadgets
      • Motherboard:
      • msi
      • CPU:
      • frio die dheke rakha Fx 6300
      • RAM:
      • 8gb ( to power black x)
      • Hard Drive:
      • 1/2 tb
      • Graphics Card:
      • Radeon HD 7950
      • Display:
      • 21.5 lcd
      • Sound Card:
      • lagano hoy ni
      • Speakers/HPs:
      • Genius Gx Sw-1250
      • Keyboard:
      • Delux t15s
      • Mouse:
      • Mowa A40 Game Master (600tk) ^_^
      • Controller:
      • venge gese
      • Power Supply:
      • Tt toughpower XT 675
      • Optical Drive:
      • oikhane fan bosai disi tape method
      • USB Devices:
      • few here nd there
      • UPS:
      • 600va
      • Operating System:
      • win 8 evolution 2014 X64 /Win 8.1 heavier edition
      • Benchmark Scores:
      • jana nei
      • Comment:
      • silent htpc
      • ISP:
      • antbd
      • Download Speed:
      • 60+
      • Upload Speed:
      • Do
    shoryuken-x's Avatar
    Join Date
    Aug 2012
    Location
    Dhaka
    Posts
    893

    Default

    Quote Originally Posted by REVx View Post
    Problem signature:
    Problem Event Name: BlueScreen
    OS Version: 6.1.7601.2.1.0.256.1
    Locale ID: 2057


    Additional information about the problem:
    BCCode: 7f
    BCP1: 0000000000000008
    BCP2: 0000000080050033
    BCP3: 00000000000406F8
    BCP4: FFFFF800030E4059
    OS Version: 6_1_7601
    Service Pack: 1_0
    Product: 256_1


    Files that help describe the problem:
    C:\Windows\Minidump\120312-14398-01.dmp
    C:\Users\kawsar\AppData\Local\Temp\WER-41387-0.sysdata.xml


    In order to fix it, Win reinstall?
    bhaia error ta kivabe ki kaj korte jaye holo seta ektu bolen

    which OS ?

  3. #3
    Member
    • Fox Mulder's Gadgets
      • Motherboard:
      • Gigabyte GA-Z77-D3H Rev 1.1 (Currently dead) | Intel DH55TC
      • CPU:
      • Core i5 3470 @ 3.8 Ghz (Currently not used) | intel Core i7 860 @ 3.3 GHz
      • RAM:
      • Corsair Vengeance 1600 MHz 2x4GB
      • Hard Drive:
      • Western Digital Blue 1 Terrabyte
      • Graphics Card:
      • Sapphire HD 7950 Vapor-X OC With Boost 3GB GDDR5 || Gigabyte GTX 680 Windforce 4GB
      • Display:
      • Philips 191EL 19" LED @77 Hz
      • Sound Card:
      • Creative Sound Blaster Live! 24 Bit
      • Keyboard:
      • Corsair K70 RGB
      • Mouse:
      • A4Tech 2X Click
      • Power Supply:
      • Thermaltake Smart 650W Modular
      • Optical Drive:
      • Samsung DVD Writer
      • UPS:
      • Spark Power (!) 1200VA
      • Operating System:
      • Windows 10 Build 10162
      • Comment:
      • It gets the job done!
      • ISP:
      • BracNet
      • Download Speed:
      • 1 Mbps
      • Upload Speed:
      • 1 Mbps
    Fox Mulder's Avatar
    Join Date
    Jul 2009
    Location
    I don't live in a city.
    Posts
    5,182

    Default

    Quote Originally Posted by genocide_cutter View Post

    which OS ?
    Here's your answer:

    OS Version: 6_1_7601
    Service Pack: 1_0


    Windows 7 SP1

  4. #4

    Default

    Well, obviously it is a BSOD. I am worried what caused it. Over the last 1.5 months, this is the 6th time. Will need to check it further.

  5. #5
    Member
    • Dee's Gadgets
      • Motherboard:
      • Asus Maximus VIII Ranger
      • CPU:
      • Intel Core i5 6600k
      • RAM:
      • G.Skill Ripjaws V 2x8GB DDR4 2400MHz
      • Hard Drive:
      • Samsung 830 128GB SSD; Crucial M500 960GB SSD
      • Display:
      • Dell S2216H
      • Keyboard:
      • Cooler Master Quick Fire Rapid-i Cherry MX Brown
      • Mouse:
      • Cooler Master MasterKeys Lite L
      • Power Supply:
      • Cooler Master V650 Gold
      • Operating System:
      • Windows 10 x64
      • ISP:
      • Link3 GATI
      • Download Speed:
      • 2Mib/s
      • Upload Speed:
      • 2Mib/s
    Dee's Avatar
    Join Date
    Aug 2010
    Location
    Dhaka
    Posts
    4,646

    Default

    Can you upload this file?
    C:\Windows\Minidump\120312-14398-01.dmp

  6. #6
    Member
    • Fox Mulder's Gadgets
      • Motherboard:
      • Gigabyte GA-Z77-D3H Rev 1.1 (Currently dead) | Intel DH55TC
      • CPU:
      • Core i5 3470 @ 3.8 Ghz (Currently not used) | intel Core i7 860 @ 3.3 GHz
      • RAM:
      • Corsair Vengeance 1600 MHz 2x4GB
      • Hard Drive:
      • Western Digital Blue 1 Terrabyte
      • Graphics Card:
      • Sapphire HD 7950 Vapor-X OC With Boost 3GB GDDR5 || Gigabyte GTX 680 Windforce 4GB
      • Display:
      • Philips 191EL 19" LED @77 Hz
      • Sound Card:
      • Creative Sound Blaster Live! 24 Bit
      • Keyboard:
      • Corsair K70 RGB
      • Mouse:
      • A4Tech 2X Click
      • Power Supply:
      • Thermaltake Smart 650W Modular
      • Optical Drive:
      • Samsung DVD Writer
      • UPS:
      • Spark Power (!) 1200VA
      • Operating System:
      • Windows 10 Build 10162
      • Comment:
      • It gets the job done!
      • ISP:
      • BracNet
      • Download Speed:
      • 1 Mbps
      • Upload Speed:
      • 1 Mbps
    Fox Mulder's Avatar
    Join Date
    Jul 2009
    Location
    I don't live in a city.
    Posts
    5,182

    Default

    Quote Originally Posted by REVx View Post
    Well, obviously it is a BSOD. I am worried what caused it. Over the last 1.5 months, this is the 6th time. Will need to check it further.
    Mind filling in your gadgets?

  7. #7

    Default

    Quote Originally Posted by BFG9000 View Post
    Mind filling in your gadgets?
    Happened to an office PC that was upgraded abt 2 months ago with Intel 2nd gen proc and MSI mobo.
    O/S win 7 64 bit; 4gb ram
    Has a HD5450 for custom software resolution requirement.
    The machine has a variety of utility software on it. Machine is also connected to the internet.


    It is a very key compy in the network, so doing a re-install will be possible but a p-i-t-b.

    Someone installed a pdf software around the time this problem occurred. When initiated, the pdf software wud hang, there'd b a memory dump and a restart. After I spotted it, I had the s/w removed and the BSODs stopped. We installed business edition AV on all office machines. These r the 2 things that I remember r significant.

    What the machine has been doing is to go on dumps and restarts automatically. Even when I am midway work! Happened in total of 6 times over the last 1.5 months. To day I got rid of some useless programs.

    - - - Updated - - -

    Quote Originally Posted by Dee View Post
    Can you upload this file?
    C:\Windows\Minidump\120312-14398-01.dmp
    Will try to do it tomorrow.

  8. #8
    Member
    • alucard's Gadgets
      • Motherboard:
      • intel-DG33FB && gigabyte-EP43T-USB3
      • CPU:
      • intel-core2-Q6600-3.01 GHz with tt-V1
      • RAM:
      • 2Gb-DDR2-800 MHz
      • Hard Drive:
      • 400gb
      • Graphics Card:
      • ATI Radeon HD 4850_512mb-GDDR3_XFX
      • Display:
      • asus-MS228H LED
      • Sound Card:
      • Built-in
      • Speakers/HPs:
      • karaoke-140w
      • Keyboard:
      • Delux,Lexma
      • Mouse:
      • Razer Lachesis+goliathus speed edition pad
      • Controller:
      • Xbox 360 pc controller
      • Power Supply:
      • 550W-[Thermaltake]
      • Optical Drive:
      • samsung-22x-dvd-R+RW
      • USB Devices:
      • phdd-80gb
      • UPS:
      • apolo-1200v
      • Operating System:
      • win 7 64 bit
      • Comment:
      • Rock on........:D
      • ISP:
      • BTCL ADSL
      • Download Speed:
      • 50-60KB
      • Upload Speed:
      • 30KB
    alucard's Avatar
    Join Date
    Dec 2008
    Location
    dhaka,mirpur
    Posts
    54

    Default

    did u upgraded your ram (2 to 4)gb [2x2=4gb or 4x1=4gb] abt 2 months ago
    The bird of hermes is my name
    Eating my wings to make me tame

  9. #9
    Member
    • shoryuken-x's Gadgets
      • Motherboard:
      • msi
      • CPU:
      • frio die dheke rakha Fx 6300
      • RAM:
      • 8gb ( to power black x)
      • Hard Drive:
      • 1/2 tb
      • Graphics Card:
      • Radeon HD 7950
      • Display:
      • 21.5 lcd
      • Sound Card:
      • lagano hoy ni
      • Speakers/HPs:
      • Genius Gx Sw-1250
      • Keyboard:
      • Delux t15s
      • Mouse:
      • Mowa A40 Game Master (600tk) ^_^
      • Controller:
      • venge gese
      • Power Supply:
      • Tt toughpower XT 675
      • Optical Drive:
      • oikhane fan bosai disi tape method
      • USB Devices:
      • few here nd there
      • UPS:
      • 600va
      • Operating System:
      • win 8 evolution 2014 X64 /Win 8.1 heavier edition
      • Benchmark Scores:
      • jana nei
      • Comment:
      • silent htpc
      • ISP:
      • antbd
      • Download Speed:
      • 60+
      • Upload Speed:
      • Do
    shoryuken-x's Avatar
    Join Date
    Aug 2012
    Location
    Dhaka
    Posts
    893

    Default

    Quote Originally Posted by REVx View Post
    Happened to an office PC that was upgraded abt 2 months ago with Intel 2nd gen proc and MSI mobo.
    O/S win 7 64 bit; 4gb ram
    Has a HD5450 for custom software resolution requirement.
    The machine has a variety of utility software on it. Machine is also connected to the internet.


    It is a very key compy in the network, so doing a re-install will be possible but a p-i-t-b.

    Someone installed a pdf software around the time this problem occurred. When initiated, the pdf software wud hang, there'd b a memory dump and a restart. After I spotted it, I had the s/w removed and the BSODs stopped. We installed business edition AV on all office machines. These r the 2 things that I remember r significant.

    What the machine has been doing is to go on dumps and restarts automatically. Even when I am midway work! Happened in total of 6 times over the last 1.5 months. To day I got rid of some useless programs.

    - - - Updated - - -



    Will try to do it tomorrow.
    bhaia , do u still have that bsod .. office pc u say ...so format window drive nd reinstall iwndows ?

    edit .. AV causes this most of the time ... uninstall antivirus

  10. #10

    Default

    Quote Originally Posted by alucard View Post
    did u upgraded your ram (2 to 4)gb [2x2=4gb or 4x1=4gb] abt 2 months ago
    This PC was made 2 months ago - completely new. Ram was not upgraded, 4gb was put in during the building.

    - - - Updated - - -

    Quote Originally Posted by genocide_cutter View Post
    bhaia , do u still have that bsod .. office pc u say ...so format window drive nd reinstall iwndows ?

    edit .. AV causes this most of the time ... uninstall antivirus
    I wud like to observe it b4 we do anything else with it. Cud b a temporary hiccup. Reinstalling is not a prob, rebuilding it is (this PC has a number of software configured for diff things).
    AV shudn't do it; it is licensed AV. Previous machine was a celeron had ESET on it - there were no probs at all.

  11. #11
    Member
    • shoryuken-x's Gadgets
      • Motherboard:
      • msi
      • CPU:
      • frio die dheke rakha Fx 6300
      • RAM:
      • 8gb ( to power black x)
      • Hard Drive:
      • 1/2 tb
      • Graphics Card:
      • Radeon HD 7950
      • Display:
      • 21.5 lcd
      • Sound Card:
      • lagano hoy ni
      • Speakers/HPs:
      • Genius Gx Sw-1250
      • Keyboard:
      • Delux t15s
      • Mouse:
      • Mowa A40 Game Master (600tk) ^_^
      • Controller:
      • venge gese
      • Power Supply:
      • Tt toughpower XT 675
      • Optical Drive:
      • oikhane fan bosai disi tape method
      • USB Devices:
      • few here nd there
      • UPS:
      • 600va
      • Operating System:
      • win 8 evolution 2014 X64 /Win 8.1 heavier edition
      • Benchmark Scores:
      • jana nei
      • Comment:
      • silent htpc
      • ISP:
      • antbd
      • Download Speed:
      • 60+
      • Upload Speed:
      • Do
    shoryuken-x's Avatar
    Join Date
    Aug 2012
    Location
    Dhaka
    Posts
    893

    Default

    Quote Originally Posted by REVx View Post
    This PC was made 2 months ago - completely new. Ram was not upgraded, 4gb was put in during the building.

    - - - Updated - - -


    I wud like to observe it b4 we do anything else with it. Cud b a temporary hiccup. Reinstalling is not a prob, rebuilding it is (this PC has a number of software configured for diff things).
    AV shudn't do it; it is licensed AV. Previous machine was a celeron had ESET on it - there were no probs at all.
    sharing one thing , i had bsod uninstalled avg av, Ms office nd some media players ,, then bsod was still there but week e ekbar duibar emon
    windows drive formatted used driver cleaner worked fine then

  12. #12

    Default

    That is why the machine is under observation.
    Ghono ghono prob hotey thakley, dibo antibiotic.

    Ekhon apatoto painkiller choluk.

  13. #13
    Member
    • optimus prime's Gadgets
      • Motherboard:
      • MSI K9A2C-ff v1
      • CPU:
      • AMD 64X2 5200+
      • RAM:
      • Transend 4GB DDR2 800MHz
      • Hard Drive:
      • 1T Hitachi+750GB Samsung+500GB Hitachi
      • Graphics Card:
      • Sapphire ATI 4850 512MB DDR3 & 4830 512MB DDR3 in Xfire
      • Display:
      • ASUS MS228
      • Sound Card:
      • Built-in Realtek
      • Speakers/HPs:
      • F&D F6000(5:1)
      • Keyboard:
      • A4TECH
      • Mouse:
      • A4TECH 747H
      • Controller:
      • Chinese
      • Power Supply:
      • Valuetop 500W
      • Optical Drive:
      • ASUS
      • UPS:
      • MICRO 1000VA(Customized)
      • ISP:
      • BTCL
      • Download Speed:
      • 1024
      • Upload Speed:
      • 256

    Join Date
    Feb 2011
    Posts
    350

    Default

    tried swapping the rams??

  14. #14
    Global Moderator
    • Codex's Gadgets
      • Motherboard:
      • Asus P8Z77-V
      • CPU:
      • Intel Core i7 3770k
      • RAM:
      • G.Skill Sniper 2x8G (9-9-9-24 Kits)
      • Hard Drive:
      • Samsung 850 PRO 256G SSD, Geil 512G SSD, HDDs: 2TBx1, 1TBx1, 500Gx1, 165Gx1
      • Graphics Card:
      • Sapphire R9 280x (Dual-x edition)
      • Display:
      • Triple monitors: Samsung S24300B + Dell E2210 x2
      • Sound Card:
      • CEntrance DACport Slim
      • Speakers/HPs:
      • Sennheiser HD598 / FLC 8s
      • Keyboard:
      • Thermaltek Challenger Pro
      • Mouse:
      • Logitech MX Master w/ Razer Goliathus Mid.
      • Controller:
      • Don't have one
      • Power Supply:
      • Inwin 750 watts w/ 80+ Bronze Certification
      • Optical Drive:
      • Asus DRW24B3ST
      • USB Devices:
      • 2TB Seagate External USB 3.0 drive
      • UPS:
      • Mercury 1.2KVA
      • Operating System:
      • Genuine Windows 10 Pro
      • Benchmark Scores:
      • Over nine thousand!
      • Comment:
      • ISP:
      • AntBD + AmberIT Dual Homed
      • Download Speed:
      • ~ 1200 KB/s
      • Upload Speed:
      • ~ 1200 KB/s

    Join Date
    Nov 2008
    Location
    Under your bed.
    Posts
    7,983

    Default

    Run a memtest, sounds like bad kits to me. And I'm afraid without the dump file, the only suggestion I can give is the process of elimination.

  15. #15
    Member
    • Rakin7's Gadgets
      • Motherboard:
      • ASUS Z77 Sabertooth
      • CPU:
      • Watercooled Intel Sandy Bridge Core i5 2500k
      • RAM:
      • Corsair Vengeance 1600MHz 2x4GB
      • Hard Drive:
      • Samsung F4 2TB and Crucial M4 128GB SSD
      • Graphics Card:
      • Sapphire HD7970 Vapor-X 3GB GHz Edition flashed to R9 280X
      • Display:
      • Asus MS228H 21.5 LED Full HD 1080p and Sony Bravia CX520 32
      • Sound Card:
      • ASUS Xonar Essence STX
      • Speakers/HPs:
      • Beyerdynamic DT770 Pro 250 Ohms
      • Keyboard:
      • Thermaltake Meka G1 Mechnical Keyboard
      • Mouse:
      • Razer Deathadder 2013
      • Power Supply:
      • Thermaltake Smart M850
      • UPS:
      • Powerpac 1200VA backed up by Generator
      • Operating System:
      • Windows 8 x64 with Media Center
      • ISP:
      • Link3 2.5 Mbps
      • Download Speed:
      • 325 KB/s
      • Upload Speed:
      • 325 KB/s
    Rakin7's Avatar
    Join Date
    Apr 2011
    Location
    Dhaka
    Posts
    3,840

    Default

    Upload the Minidump, that will help pinpointing the exact cause.

  16. #16

    Default

    Quote Originally Posted by eXcavator View Post
    Upload the Minidump, that will help pinpointing the exact cause.

    Tried but cannot upload. Seems like there is no way to attach a file from computer in the reply consoles.

  17. #17
    Member
    • Rakin7's Gadgets
      • Motherboard:
      • ASUS Z77 Sabertooth
      • CPU:
      • Watercooled Intel Sandy Bridge Core i5 2500k
      • RAM:
      • Corsair Vengeance 1600MHz 2x4GB
      • Hard Drive:
      • Samsung F4 2TB and Crucial M4 128GB SSD
      • Graphics Card:
      • Sapphire HD7970 Vapor-X 3GB GHz Edition flashed to R9 280X
      • Display:
      • Asus MS228H 21.5 LED Full HD 1080p and Sony Bravia CX520 32
      • Sound Card:
      • ASUS Xonar Essence STX
      • Speakers/HPs:
      • Beyerdynamic DT770 Pro 250 Ohms
      • Keyboard:
      • Thermaltake Meka G1 Mechnical Keyboard
      • Mouse:
      • Razer Deathadder 2013
      • Power Supply:
      • Thermaltake Smart M850
      • UPS:
      • Powerpac 1200VA backed up by Generator
      • Operating System:
      • Windows 8 x64 with Media Center
      • ISP:
      • Link3 2.5 Mbps
      • Download Speed:
      • 325 KB/s
      • Upload Speed:
      • 325 KB/s
    Rakin7's Avatar
    Join Date
    Apr 2011
    Location
    Dhaka
    Posts
    3,840

    Default

    Quote Originally Posted by REVx View Post
    Tried but cannot upload. Seems like there is no way to attach a file from computer in the reply consoles.
    Try : Go Advanced > Manage Attachments > browse > attach.
    See if that works.

  18. #18
    Global Moderator
    • Codex's Gadgets
      • Motherboard:
      • Asus P8Z77-V
      • CPU:
      • Intel Core i7 3770k
      • RAM:
      • G.Skill Sniper 2x8G (9-9-9-24 Kits)
      • Hard Drive:
      • Samsung 850 PRO 256G SSD, Geil 512G SSD, HDDs: 2TBx1, 1TBx1, 500Gx1, 165Gx1
      • Graphics Card:
      • Sapphire R9 280x (Dual-x edition)
      • Display:
      • Triple monitors: Samsung S24300B + Dell E2210 x2
      • Sound Card:
      • CEntrance DACport Slim
      • Speakers/HPs:
      • Sennheiser HD598 / FLC 8s
      • Keyboard:
      • Thermaltek Challenger Pro
      • Mouse:
      • Logitech MX Master w/ Razer Goliathus Mid.
      • Controller:
      • Don't have one
      • Power Supply:
      • Inwin 750 watts w/ 80+ Bronze Certification
      • Optical Drive:
      • Asus DRW24B3ST
      • USB Devices:
      • 2TB Seagate External USB 3.0 drive
      • UPS:
      • Mercury 1.2KVA
      • Operating System:
      • Genuine Windows 10 Pro
      • Benchmark Scores:
      • Over nine thousand!
      • Comment:
      • ISP:
      • AntBD + AmberIT Dual Homed
      • Download Speed:
      • ~ 1200 KB/s
      • Upload Speed:
      • ~ 1200 KB/s

    Join Date
    Nov 2008
    Location
    Under your bed.
    Posts
    7,983

    Default

    Or just use a external file host?

    http://fileeasy.co.uk/ is easy to use.

  19. #19

  20. #20
    Member
    • Rakin7's Gadgets
      • Motherboard:
      • ASUS Z77 Sabertooth
      • CPU:
      • Watercooled Intel Sandy Bridge Core i5 2500k
      • RAM:
      • Corsair Vengeance 1600MHz 2x4GB
      • Hard Drive:
      • Samsung F4 2TB and Crucial M4 128GB SSD
      • Graphics Card:
      • Sapphire HD7970 Vapor-X 3GB GHz Edition flashed to R9 280X
      • Display:
      • Asus MS228H 21.5 LED Full HD 1080p and Sony Bravia CX520 32
      • Sound Card:
      • ASUS Xonar Essence STX
      • Speakers/HPs:
      • Beyerdynamic DT770 Pro 250 Ohms
      • Keyboard:
      • Thermaltake Meka G1 Mechnical Keyboard
      • Mouse:
      • Razer Deathadder 2013
      • Power Supply:
      • Thermaltake Smart M850
      • UPS:
      • Powerpac 1200VA backed up by Generator
      • Operating System:
      • Windows 8 x64 with Media Center
      • ISP:
      • Link3 2.5 Mbps
      • Download Speed:
      • 325 KB/s
      • Upload Speed:
      • 325 KB/s
    Rakin7's Avatar
    Join Date
    Apr 2011
    Location
    Dhaka
    Posts
    3,840

    Default

    Quote Originally Posted by REVx View Post
    Code:
    Loading Dump File [C:\Users\ZaerZubabAhmed\Desktop\120312-14398-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    
    Symbol search path is: *** Invalid ***
    ****************************************************************************
    * Symbol loading may be unreliable without a symbol search path.           *
    * Use .symfix to have the debugger choose a symbol path.                   *
    * After setting your symbol path, use .reload to refresh symbol locations. *
    ****************************************************************************
    Executable search path is: 
    *********************************************************************
    * Symbols can not be loaded because symbol path is not initialized. *
    *                                                                   *
    * The Symbol Path can be set by:                                    *
    *   using the _NT_SYMBOL_PATH environment variable.                 *
    *   using the -y <symbol_path> argument when starting the debugger. *
    *   using .sympath and .sympath+                                    *
    *********************************************************************
    Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for ntoskrnl.exe
    *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
    Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
    Machine Name:
    Kernel base = 0xfffff800`03051000 PsLoadedModuleList = 0xfffff800`03296e90
    Debug session time: Mon Dec  3 13:16:32.512 2012 (UTC + 6:00)
    System Uptime: 0 days 3:40:23.931
    *********************************************************************
    * Symbols can not be loaded because symbol path is not initialized. *
    *                                                                   *
    * The Symbol Path can be set by:                                    *
    *   using the _NT_SYMBOL_PATH environment variable.                 *
    *   using the -y <symbol_path> argument when starting the debugger. *
    *   using .sympath and .sympath+                                    *
    *********************************************************************
    Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for ntoskrnl.exe
    *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ...................
    Loading User Symbols
    Loading unloaded module list
    .......
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 7F, {8, 80050033, 406f8, fffff800030e4059}
    
    ***** Kernel symbols are WRONG. Please fix symbols to do analysis.
    
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    Either you specified an unqualified symbol, or your debugger   ***
    ***    doesn't have full symbol information.  Unqualified symbol      ***
    ***    resolution is turned off by default. Please either specify a   ***
    ***    fully qualified symbol module!symbolname, or enable resolution ***
    ***    of unqualified symbols by typing ".symopt- 100". Note that   ***
    ***    enabling unqualified symbol resolution with network symbol     ***
    ***    server shares in the symbol path may cause the debugger to     ***
    ***    appear to hang for long periods of time when an incorrect      ***
    ***    symbol name is typed or the network symbol server is down.     ***
    ***                                                                   ***
    ***    For some commands to work properly, your symbol path           ***
    ***    must point to .pdb files that have full type information.      ***
    ***                                                                   ***
    ***    Certain .pdb files (such as the public OS symbols) do not      ***
    ***    contain the required information.  Contact the group that      ***
    ***    provided you with these symbols if you need this command to    ***
    ***    work.                                                          ***
    ***                                                                   ***
    ***    Type referenced: nt!_KPRCB                                     ***
    ***                                                                   ***
    *************************************************************************
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    Either you specified an unqualified symbol, or your debugger   ***
    ***    doesn't have full symbol information.  Unqualified symbol      ***
    ***    resolution is turned off by default. Please either specify a   ***
    ***    fully qualified symbol module!symbolname, or enable resolution ***
    ***    of unqualified symbols by typing ".symopt- 100". Note that   ***
    ***    enabling unqualified symbol resolution with network symbol     ***
    ***    server shares in the symbol path may cause the debugger to     ***
    ***    appear to hang for long periods of time when an incorrect      ***
    ***    symbol name is typed or the network symbol server is down.     ***
    ***                                                                   ***
    ***    For some commands to work properly, your symbol path           ***
    ***    must point to .pdb files that have full type information.      ***
    ***                                                                   ***
    ***    Certain .pdb files (such as the public OS symbols) do not      ***
    ***    contain the required information.  Contact the group that      ***
    ***    provided you with these symbols if you need this command to    ***
    ***    work.                                                          ***
    ***                                                                   ***
    ***    Type referenced: nt!KPRCB                                      ***
    ***                                                                   ***
    *************************************************************************
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    Either you specified an unqualified symbol, or your debugger   ***
    ***    doesn't have full symbol information.  Unqualified symbol      ***
    ***    resolution is turned off by default. Please either specify a   ***
    ***    fully qualified symbol module!symbolname, or enable resolution ***
    ***    of unqualified symbols by typing ".symopt- 100". Note that   ***
    ***    enabling unqualified symbol resolution with network symbol     ***
    ***    server shares in the symbol path may cause the debugger to     ***
    ***    appear to hang for long periods of time when an incorrect      ***
    ***    symbol name is typed or the network symbol server is down.     ***
    ***                                                                   ***
    ***    For some commands to work properly, your symbol path           ***
    ***    must point to .pdb files that have full type information.      ***
    ***                                                                   ***
    ***    Certain .pdb files (such as the public OS symbols) do not      ***
    ***    contain the required information.  Contact the group that      ***
    ***    provided you with these symbols if you need this command to    ***
    ***    work.                                                          ***
    ***                                                                   ***
    ***    Type referenced: nt!_KPRCB                                     ***
    ***                                                                   ***
    *************************************************************************
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    Either you specified an unqualified symbol, or your debugger   ***
    ***    doesn't have full symbol information.  Unqualified symbol      ***
    ***    resolution is turned off by default. Please either specify a   ***
    ***    fully qualified symbol module!symbolname, or enable resolution ***
    ***    of unqualified symbols by typing ".symopt- 100". Note that   ***
    ***    enabling unqualified symbol resolution with network symbol     ***
    ***    server shares in the symbol path may cause the debugger to     ***
    ***    appear to hang for long periods of time when an incorrect      ***
    ***    symbol name is typed or the network symbol server is down.     ***
    ***                                                                   ***
    ***    For some commands to work properly, your symbol path           ***
    ***    must point to .pdb files that have full type information.      ***
    ***                                                                   ***
    ***    Certain .pdb files (such as the public OS symbols) do not      ***
    ***    contain the required information.  Contact the group that      ***
    ***    provided you with these symbols if you need this command to    ***
    ***    work.                                                          ***
    ***                                                                   ***
    ***    Type referenced: nt!KPRCB                                      ***
    ***                                                                   ***
    *************************************************************************
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    Either you specified an unqualified symbol, or your debugger   ***
    ***    doesn't have full symbol information.  Unqualified symbol      ***
    ***    resolution is turned off by default. Please either specify a   ***
    ***    fully qualified symbol module!symbolname, or enable resolution ***
    ***    of unqualified symbols by typing ".symopt- 100". Note that   ***
    ***    enabling unqualified symbol resolution with network symbol     ***
    ***    server shares in the symbol path may cause the debugger to     ***
    ***    appear to hang for long periods of time when an incorrect      ***
    ***    symbol name is typed or the network symbol server is down.     ***
    ***                                                                   ***
    ***    For some commands to work properly, your symbol path           ***
    ***    must point to .pdb files that have full type information.      ***
    ***                                                                   ***
    ***    Certain .pdb files (such as the public OS symbols) do not      ***
    ***    contain the required information.  Contact the group that      ***
    ***    provided you with these symbols if you need this command to    ***
    ***    work.                                                          ***
    ***                                                                   ***
    ***    Type referenced: nt!_KPRCB                                     ***
    ***                                                                   ***
    *************************************************************************
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    Either you specified an unqualified symbol, or your debugger   ***
    ***    doesn't have full symbol information.  Unqualified symbol      ***
    ***    resolution is turned off by default. Please either specify a   ***
    ***    fully qualified symbol module!symbolname, or enable resolution ***
    ***    of unqualified symbols by typing ".symopt- 100". Note that   ***
    ***    enabling unqualified symbol resolution with network symbol     ***
    ***    server shares in the symbol path may cause the debugger to     ***
    ***    appear to hang for long periods of time when an incorrect      ***
    ***    symbol name is typed or the network symbol server is down.     ***
    ***                                                                   ***
    ***    For some commands to work properly, your symbol path           ***
    ***    must point to .pdb files that have full type information.      ***
    ***                                                                   ***
    ***    Certain .pdb files (such as the public OS symbols) do not      ***
    ***    contain the required information.  Contact the group that      ***
    ***    provided you with these symbols if you need this command to    ***
    ***    work.                                                          ***
    ***                                                                   ***
    ***    Type referenced: nt!_KPRCB                                     ***
    ***                                                                   ***
    *************************************************************************
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    Either you specified an unqualified symbol, or your debugger   ***
    ***    doesn't have full symbol information.  Unqualified symbol      ***
    ***    resolution is turned off by default. Please either specify a   ***
    ***    fully qualified symbol module!symbolname, or enable resolution ***
    ***    of unqualified symbols by typing ".symopt- 100". Note that   ***
    ***    enabling unqualified symbol resolution with network symbol     ***
    ***    server shares in the symbol path may cause the debugger to     ***
    ***    appear to hang for long periods of time when an incorrect      ***
    ***    symbol name is typed or the network symbol server is down.     ***
    ***                                                                   ***
    ***    For some commands to work properly, your symbol path           ***
    ***    must point to .pdb files that have full type information.      ***
    ***                                                                   ***
    ***    Certain .pdb files (such as the public OS symbols) do not      ***
    ***    contain the required information.  Contact the group that      ***
    ***    provided you with these symbols if you need this command to    ***
    ***    work.                                                          ***
    ***                                                                   ***
    ***    Type referenced: nt!_KPRCB                                     ***
    ***                                                                   ***
    *************************************************************************
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    Either you specified an unqualified symbol, or your debugger   ***
    ***    doesn't have full symbol information.  Unqualified symbol      ***
    ***    resolution is turned off by default. Please either specify a   ***
    ***    fully qualified symbol module!symbolname, or enable resolution ***
    ***    of unqualified symbols by typing ".symopt- 100". Note that   ***
    ***    enabling unqualified symbol resolution with network symbol     ***
    ***    server shares in the symbol path may cause the debugger to     ***
    ***    appear to hang for long periods of time when an incorrect      ***
    ***    symbol name is typed or the network symbol server is down.     ***
    ***                                                                   ***
    ***    For some commands to work properly, your symbol path           ***
    ***    must point to .pdb files that have full type information.      ***
    ***                                                                   ***
    ***    Certain .pdb files (such as the public OS symbols) do not      ***
    ***    contain the required information.  Contact the group that      ***
    ***    provided you with these symbols if you need this command to    ***
    ***    work.                                                          ***
    ***                                                                   ***
    ***    Type referenced: nt!_KPRCB                                     ***
    ***                                                                   ***
    *************************************************************************
    Probably caused by : ntoskrnl.exe ( nt+80640 )
    
    Followup: MachineOwner
    ---------
    
    0: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    UNEXPECTED_KERNEL_MODE_TRAP (7f)
    This means a trap occurred in kernel mode, and it's a trap of a kind
    that the kernel isn't allowed to have/catch (bound trap) or that
    is always instant death (double fault).  The first number in the
    bugcheck params is the number of the trap (8 = double fault, etc)
    Consult an Intel x86 family manual to learn more about what these
    traps are. Here is a *portion* of those codes:
    If kv shows a taskGate
            use .tss on the part before the colon, then kv.
    Else if kv shows a trapframe
            use .trap on that value
    Else
            .trap on the appropriate frame will show where the trap was taken
            (on x86, this will be the ebp that goes with the procedure KiTrap)
    Endif
    kb will then show the corrected stack.
    Arguments:
    Arg1: 0000000000000008, EXCEPTION_DOUBLE_FAULT
    Arg2: 0000000080050033
    Arg3: 00000000000406f8
    Arg4: fffff800030e4059
    
    Debugging Details:
    ------------------
    
    ***** Kernel symbols are WRONG. Please fix symbols to do analysis.
    
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    Either you specified an unqualified symbol, or your debugger   ***
    ***    doesn't have full symbol information.  Unqualified symbol      ***
    ***    resolution is turned off by default. Please either specify a   ***
    ***    fully qualified symbol module!symbolname, or enable resolution ***
    ***    of unqualified symbols by typing ".symopt- 100". Note that   ***
    ***    enabling unqualified symbol resolution with network symbol     ***
    ***    server shares in the symbol path may cause the debugger to     ***
    ***    appear to hang for long periods of time when an incorrect      ***
    ***    symbol name is typed or the network symbol server is down.     ***
    ***                                                                   ***
    ***    For some commands to work properly, your symbol path           ***
    ***    must point to .pdb files that have full type information.      ***
    ***                                                                   ***
    ***    Certain .pdb files (such as the public OS symbols) do not      ***
    ***    contain the required information.  Contact the group that      ***
    ***    provided you with these symbols if you need this command to    ***
    ***    work.                                                          ***
    ***                                                                   ***
    ***    Type referenced: nt!_KPRCB                                     ***
    ***                                                                   ***
    *************************************************************************
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    Either you specified an unqualified symbol, or your debugger   ***
    ***    doesn't have full symbol information.  Unqualified symbol      ***
    ***    resolution is turned off by default. Please either specify a   ***
    ***    fully qualified symbol module!symbolname, or enable resolution ***
    ***    of unqualified symbols by typing ".symopt- 100". Note that   ***
    ***    enabling unqualified symbol resolution with network symbol     ***
    ***    server shares in the symbol path may cause the debugger to     ***
    ***    appear to hang for long periods of time when an incorrect      ***
    ***    symbol name is typed or the network symbol server is down.     ***
    ***                                                                   ***
    ***    For some commands to work properly, your symbol path           ***
    ***    must point to .pdb files that have full type information.      ***
    ***                                                                   ***
    ***    Certain .pdb files (such as the public OS symbols) do not      ***
    ***    contain the required information.  Contact the group that      ***
    ***    provided you with these symbols if you need this command to    ***
    ***    work.                                                          ***
    ***                                                                   ***
    ***    Type referenced: nt!KPRCB                                      ***
    ***                                                                   ***
    *************************************************************************
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    Either you specified an unqualified symbol, or your debugger   ***
    ***    doesn't have full symbol information.  Unqualified symbol      ***
    ***    resolution is turned off by default. Please either specify a   ***
    ***    fully qualified symbol module!symbolname, or enable resolution ***
    ***    of unqualified symbols by typing ".symopt- 100". Note that   ***
    ***    enabling unqualified symbol resolution with network symbol     ***
    ***    server shares in the symbol path may cause the debugger to     ***
    ***    appear to hang for long periods of time when an incorrect      ***
    ***    symbol name is typed or the network symbol server is down.     ***
    ***                                                                   ***
    ***    For some commands to work properly, your symbol path           ***
    ***    must point to .pdb files that have full type information.      ***
    ***                                                                   ***
    ***    Certain .pdb files (such as the public OS symbols) do not      ***
    ***    contain the required information.  Contact the group that      ***
    ***    provided you with these symbols if you need this command to    ***
    ***    work.                                                          ***
    ***                                                                   ***
    ***    Type referenced: nt!_KPRCB                                     ***
    ***                                                                   ***
    *************************************************************************
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    Either you specified an unqualified symbol, or your debugger   ***
    ***    doesn't have full symbol information.  Unqualified symbol      ***
    ***    resolution is turned off by default. Please either specify a   ***
    ***    fully qualified symbol module!symbolname, or enable resolution ***
    ***    of unqualified symbols by typing ".symopt- 100". Note that   ***
    ***    enabling unqualified symbol resolution with network symbol     ***
    ***    server shares in the symbol path may cause the debugger to     ***
    ***    appear to hang for long periods of time when an incorrect      ***
    ***    symbol name is typed or the network symbol server is down.     ***
    ***                                                                   ***
    ***    For some commands to work properly, your symbol path           ***
    ***    must point to .pdb files that have full type information.      ***
    ***                                                                   ***
    ***    Certain .pdb files (such as the public OS symbols) do not      ***
    ***    contain the required information.  Contact the group that      ***
    ***    provided you with these symbols if you need this command to    ***
    ***    work.                                                          ***
    ***                                                                   ***
    ***    Type referenced: nt!KPRCB                                      ***
    ***                                                                   ***
    *************************************************************************
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    Either you specified an unqualified symbol, or your debugger   ***
    ***    doesn't have full symbol information.  Unqualified symbol      ***
    ***    resolution is turned off by default. Please either specify a   ***
    ***    fully qualified symbol module!symbolname, or enable resolution ***
    ***    of unqualified symbols by typing ".symopt- 100". Note that   ***
    ***    enabling unqualified symbol resolution with network symbol     ***
    ***    server shares in the symbol path may cause the debugger to     ***
    ***    appear to hang for long periods of time when an incorrect      ***
    ***    symbol name is typed or the network symbol server is down.     ***
    ***                                                                   ***
    ***    For some commands to work properly, your symbol path           ***
    ***    must point to .pdb files that have full type information.      ***
    ***                                                                   ***
    ***    Certain .pdb files (such as the public OS symbols) do not      ***
    ***    contain the required information.  Contact the group that      ***
    ***    provided you with these symbols if you need this command to    ***
    ***    work.                                                          ***
    ***                                                                   ***
    ***    Type referenced: nt!_KPRCB                                     ***
    ***                                                                   ***
    *************************************************************************
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    Either you specified an unqualified symbol, or your debugger   ***
    ***    doesn't have full symbol information.  Unqualified symbol      ***
    ***    resolution is turned off by default. Please either specify a   ***
    ***    fully qualified symbol module!symbolname, or enable resolution ***
    ***    of unqualified symbols by typing ".symopt- 100". Note that   ***
    ***    enabling unqualified symbol resolution with network symbol     ***
    ***    server shares in the symbol path may cause the debugger to     ***
    ***    appear to hang for long periods of time when an incorrect      ***
    ***    symbol name is typed or the network symbol server is down.     ***
    ***                                                                   ***
    ***    For some commands to work properly, your symbol path           ***
    ***    must point to .pdb files that have full type information.      ***
    ***                                                                   ***
    ***    Certain .pdb files (such as the public OS symbols) do not      ***
    ***    contain the required information.  Contact the group that      ***
    ***    provided you with these symbols if you need this command to    ***
    ***    work.                                                          ***
    ***                                                                   ***
    ***    Type referenced: nt!_KPRCB                                     ***
    ***                                                                   ***
    *************************************************************************
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    Either you specified an unqualified symbol, or your debugger   ***
    ***    doesn't have full symbol information.  Unqualified symbol      ***
    ***    resolution is turned off by default. Please either specify a   ***
    ***    fully qualified symbol module!symbolname, or enable resolution ***
    ***    of unqualified symbols by typing ".symopt- 100". Note that   ***
    ***    enabling unqualified symbol resolution with network symbol     ***
    ***    server shares in the symbol path may cause the debugger to     ***
    ***    appear to hang for long periods of time when an incorrect      ***
    ***    symbol name is typed or the network symbol server is down.     ***
    ***                                                                   ***
    ***    For some commands to work properly, your symbol path           ***
    ***    must point to .pdb files that have full type information.      ***
    ***                                                                   ***
    ***    Certain .pdb files (such as the public OS symbols) do not      ***
    ***    contain the required information.  Contact the group that      ***
    ***    provided you with these symbols if you need this command to    ***
    ***    work.                                                          ***
    ***                                                                   ***
    ***    Type referenced: nt!_KPRCB                                     ***
    ***                                                                   ***
    *************************************************************************
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    Either you specified an unqualified symbol, or your debugger   ***
    ***    doesn't have full symbol information.  Unqualified symbol      ***
    ***    resolution is turned off by default. Please either specify a   ***
    ***    fully qualified symbol module!symbolname, or enable resolution ***
    ***    of unqualified symbols by typing ".symopt- 100". Note that   ***
    ***    enabling unqualified symbol resolution with network symbol     ***
    ***    server shares in the symbol path may cause the debugger to     ***
    ***    appear to hang for long periods of time when an incorrect      ***
    ***    symbol name is typed or the network symbol server is down.     ***
    ***                                                                   ***
    ***    For some commands to work properly, your symbol path           ***
    ***    must point to .pdb files that have full type information.      ***
    ***                                                                   ***
    ***    Certain .pdb files (such as the public OS symbols) do not      ***
    ***    contain the required information.  Contact the group that      ***
    ***    provided you with these symbols if you need this command to    ***
    ***    work.                                                          ***
    ***                                                                   ***
    ***    Type referenced: nt!_KPRCB                                     ***
    ***                                                                   ***
    *************************************************************************
    
    ADDITIONAL_DEBUG_TEXT:  
    You can run '.symfix; .reload' to try to fix the symbol path and load symbols.
    
    MODULE_NAME: nt
    
    FAULTING_MODULE: fffff80003051000 nt
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4ce7951a
    
    BUGCHECK_STR:  0x7f_8
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    
    CURRENT_IRQL:  0
    
    LAST_CONTROL_TRANSFER:  from fffff800030d0be9 to fffff800030d1640
    
    STACK_TEXT:  
    fffff800`00ba4d28 fffff800`030d0be9 : 00000000`0000007f 00000000`00000008 00000000`80050033 00000000`000406f8 : nt+0x80640
    fffff800`00ba4d30 00000000`0000007f : 00000000`00000008 00000000`80050033 00000000`000406f8 fffff800`030e4059 : nt+0x7fbe9
    fffff800`00ba4d38 00000000`00000008 : 00000000`80050033 00000000`000406f8 fffff800`030e4059 00000000`00000000 : 0x7f
    fffff800`00ba4d40 00000000`80050033 : 00000000`000406f8 fffff800`030e4059 00000000`00000000 00000000`00000000 : 0x8
    fffff800`00ba4d48 00000000`000406f8 : fffff800`030e4059 00000000`00000000 00000000`00000000 00000000`00000000 : 0x80050033
    fffff800`00ba4d50 fffff800`030e4059 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x406f8
    fffff800`00ba4d58 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt+0x93059
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    nt+80640
    fffff800`030d1640 48894c2408      mov     qword ptr [rsp+8],rcx
    
    SYMBOL_STACK_INDEX:  0
    
    SYMBOL_NAME:  nt+80640
    
    FOLLOWUP_NAME:  MachineOwner
    
    IMAGE_NAME:  ntoskrnl.exe
    
    BUCKET_ID:  WRONG_SYMBOLS
    
    Followup: MachineOwner
    ---------
    Probably caused by : ntoskrnl.exe ( nt+80640 )
    Last edited by Rakin7; December 6th, 2012 at 12:40.

Page 1 of 2 1 2 LastLast

Similar Threads

  1. Hdd error??
    By MaDDy in forum Technical Support
    Replies: 7
    Last Post: October 28th, 2012, 23:11
  2. Error:IP looking UP .
    By HeLL]deathknight in forum Garena Central
    Replies: 3
    Last Post: July 6th, 2011, 17:18
  3. crc error
    By CHR.Overload in forum Technical Support
    Replies: 0
    Last Post: March 21st, 2009, 01:58
  4. Cpu Fan error
    By shahriar in forum Others PC Hardware
    Replies: 9
    Last Post: February 20th, 2009, 13:52
  5. Error
    By Coming back to life in forum Feedback
    Replies: 6
    Last Post: May 27th, 2008, 03:31

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
Page generated in 0.30670 seconds with 14 queries.