| Forum Home | ||||
| Press F1 | ||||
| Thread ID: 90455 | 2008-06-03 22:00:00 | BLUE SCREEN PROBLEM! | almightynugget (13536) | Press F1 |
| Post ID | Timestamp | Content | User | ||
| 675365 | 2008-06-03 22:00:00 | hey guys i have a blue screen problem it happens whenever i boot up my pc. i have windows vista ultimate 32bit. and now im having problems! this is what it says when it successfully boots. (after trying to boot like 10 times) Literally! Problem signature: Problem Event Name: BlueScreen OS Version: 6.0.6000.2.0.0.256.1 Locale ID: 1033 Additional information about the problem: BCCode: d1 BCP1: 1A552C6D BCP2: 00000002 BCP3: 00000000 BCP4: 8C4920CD OS Version: 6_0_6000 Service Pack: 0_0 Product: 256_1 Files that help describe the problem: C:\Windows\Minidump\Mini060308-02.dmp C:\Users\Jeremiah\AppData\Local\Temp\WER-82774-0.sysdata.xml C:\Users\Jeremiah\AppData\Local\Temp\WERAA33.tmp.v ersion.txt and this morning like just a few minutes ago the names changed but same problem! Problem signature: Problem Event Name: BlueScreen OS Version: 6.0.6000.2.0.0.256.1 Locale ID: 1033 Additional information about the problem: BCCode: d1 BCP1: 1CC22D6D BCP2: 00000002 BCP3: 00000000 BCP4: 8FE790CD OS Version: 6_0_6000 Service Pack: 0_0 Product: 256_1 Files that help describe the problem: C:\Windows\Minidump\Mini060408-03.dmp C:\Users\Jeremiah\AppData\Local\Temp\WER-56597-0.sysdata.xml C:\Users\Jeremiah\AppData\Local\Temp\WER10A2.tmp.v ersion.txt Please Help me out guys! Thanx |
almightynugget (13536) | ||
| 675366 | 2008-06-03 22:51:00 | Does it only crash when / after you boot into Vista?? Does it say the name of a file or driver?? |
Speedy Gonzales (78) | ||
| 675367 | 2008-06-03 23:09:00 | A BSOD will give you something like: STOP: 0x00000019: BAD_POOL_HEADER What was yours? |
pctek (84) | ||
| 675368 | 2008-06-03 23:12:00 | umm i dont know actually.. lol im in a lecture at the moment. but umm yes it only gives me blue screen when im typing or after i have typed my password. but it doesnt crash when it has already logged me onto my desktop. i havent noticed any names of drivers but it says this: Files that help describe the problem: C:\Windows\Minidump\Mini060408-03.dmp C:\Users\Jeremiah\AppData\Local\Temp\WER-56597-0.sysdata.xml C:\Users\Jeremiah\AppData\Local\Temp\WER10A2.tmp.v ersion.txt dunno if it helps u or not. sorry i dnt know 2 much about blue screens :( |
almightynugget (13536) | ||
| 675369 | 2008-06-03 23:25:00 | You'll probably need something like this (www.microsoft.com) to see what those dmp files mean. Depending on whether your system, is 32 or 64 bit |
Speedy Gonzales (78) | ||
| 675370 | 2008-06-04 00:22:00 | hey thanx a lot i will take a look at it when i get home this evening. thanx 4 the help guys! really appreciate it. :D will get back if it works or if anything happens |
almightynugget (13536) | ||
| 675371 | 2008-06-04 02:18:00 | I would put SP1 on it for a start...An update must of overwritten a hardware driver.....you can change your automatic update setting so that only Vista O/S updates are collected, not hardware drivers... | SolMiester (139) | ||
| 675372 | 2008-06-04 03:16:00 | well last time i updated it i had to reinstall vista then it said that it wasnt genuine... i spoke to microsoft and wasted 68 bucks and now im stuck with not being able to update it. i had an oem version of vista ultimate and i had to reinstall... i dont want to go through it all over again.:groan: | almightynugget (13536) | ||
| 675373 | 2008-06-04 12:02:00 | 1 . download the WindDB program from microsoft's website (ref . to the link that Speedy Gonzales has posted on his reply) 2 . To set up the debugger to analyze the dump file, verify that you have a live Internet connection and set the symbol file path in WinDbg by selecting File | Symbol File Path . Then enter the following string: SRV*c:\local cache* . microsoft . com/download/symbols" target="_blank">msdl . microsoft . com Substituting your own directory path for c:\local cache . For example, if you want the symbols to be placed in c:\symbols, then set your symbol path to SRV*c:\symbols* . microsoft . com/download/symbols" target="_blank">msdl . microsoft . com When opening a memory dump, WinDbg will look at the EXE/DLLs and extract version information . It then creates a request to the symbol server at Microsoft, which includes this version information, and locates the precise symbol tables to draw information from . If you have difficulty retrieving symbol files, check that your firewall permits access to http://msdl . microsoft . com . 3 . Open the dump file that you want to analyze, select File | Open Crash Dump . You'll be asked if you want to save workspace information . Click Yes if you want it to remember where the dump file is . WinDbg looks for the Windows symbol files . WinDbg references the symbol file path, accesses microsoft . com, and displays the results . 4 . With the dump file loaded into WinDbg, use the following command to get the diagnostic information: !analyze –v, it displays information describing the state of a system when it crashed, the fault encountered, and who is the primary suspect . 5 . Post the result back here . But remind you that if the result shows that the OS's system file/driver is the culprit, then it's very time consuming to find out what actually goes wrong . Good luck! |
aklthomas (12936) | ||
| 675374 | 2008-06-05 09:00:00 | Hey guys thanks very much for the help i am verrrrrry grateful for it. :clap and sorry didn't have any time to post back got real busy. dad helped me with sum issues as well... it was a driver file... wasnt showing up in device manager... but yes it did work very well not 1 single BSOD :banana |
almightynugget (13536) | ||
| 1 | |||||