Page 1 of 1
driver error/bsod
Posted: Sat May 27, 2006 12:09 am
by sethypoo26
I have a new t60p, and everynow and then right as the log in screen comes up I get the dreaded blue screen of death. I then restart it, and it usually boots up fine, rarely a consecutive bsod. But when I get back logged windows says it recovered from a serios system error and the technical info has a BCCode: 22 error and when i send the error report it says its a driver error. Anyone have any ideas or know what driver(s) its is?
Hex code for error
Posted: Sat May 27, 2006 11:39 am
by jonathan98342
You wouldn't happen to have the full hex code for the error, would you (something like 10000e2 or similar)?
FILE_SYSYTEM
Posted: Sat May 27, 2006 8:56 pm
by sethypoo26
I think the hex is
Stop: 0x00000022 (0x0002030B, 0x89185E28, 0x89185D70, 0x86DE5A20) Hopefully that can help
Posted: Mon May 29, 2006 7:54 pm
by sethypoo26
any suggestions?
Posted: Wed May 31, 2006 6:48 am
by Hamid
STOP 0x00000022 FILE_SYSTEM "
Maybe its a file system error. Try a defrag and a scan disk for bad sectors.
Also take a look the the following URL, it might help:
http://msdn.microsoft.com/library/defau ... s/1149.asp
HTH,
Hamid
Error signature
Posted: Wed May 31, 2006 10:15 am
by sethypoo26
I will try a disk defrag, but it happened again right as the login scrreen came up, and i restarted and the windows error signature is this: BCCode : 22 BCP1 : 0002030B BCP2 : 890BA4D8 BCP3 : 890BA420
BCP4 : 8925DE70 OSVer : 5_1_2600 SP : 2_0 Product : 256_1
Posted: Thu Jun 01, 2006 8:38 am
by Aszu
Your hard disk may have a damage and the part of Windows system program may be on that damaged block.
Scandisk program will detect that block and remap it to a spare block, but data or code written on that block can't be restored.
The error you have seems to be caused by a disk read failure of an important file.
Try PC Doctor drive test.