Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

BSOD ntoskrnl.exe issue?


  • Please log in to reply
15 replies to this topic

#1 cddowning

cddowning

  • Members
  • 9 posts
  • OFFLINE
  •  
  • Local time:08:13 PM

Posted 23 November 2011 - 12:00 AM

Good evening all!

I am sure that the problem that I am experiencing is old hat for most of you, but I hope that you might take the time to chime in nonetheless. I apologize in advance for my lack of technical know-how.

I have been receiving solid BSOD for a while now, and can only run my notebook in safe mode. I have tried system restore, various "Utilities", and even BlueScreenView. Trouble is, I don't know what to do with the information that I get.

It all began when I installed TrendMicro endpoint AV, and uninstalled Kaspersky. Almost instantly I began having issues.

I am running Vista Home Premium (64bit) on a Gateway MD7818u.

BlueScreenView shows:

Mini111311-01.dmp 11/13/2011 11:14:30 AM CRITICAL_OBJECT_TERMINATION 0x000000f4 00000000`00000003 fffffa80`06f40c10 fffffa80`06f40e48 fffff800`04932cf0 ntoskrnl.exe ntoskrnl.exe+5a490 x64 ntoskrnl.exe+5a490 C:\Windows\Minidump\Mini111311-01.dmp 2 15 6002 265,736

I'd like to solicit your advice, but am not even sure which additional errors/messages to post. Thank you in advance!

BC AdBot (Login to Remove)

 


#2 Lefty3120

Lefty3120

  • Members
  • 112 posts
  • OFFLINE
  •  
  • Local time:11:13 PM

Posted 23 November 2011 - 07:45 AM

Greetings,

Windows Vista can be temperamental sometimes depending on its configuration. Let's run through a few items to see whats happening.

First, I'd like you to remove any security software currently present on the machine.

Here are some tools to assist you..

1. Trend Micro -- Uninstall Tool x64

2. Kaspersky -- Uninstall tool

After running each tool reboot the system.


Next, Please follow these instructions..

1. Open an elevated command prompt. To do this, click Start, Type CMD into the search box, Right click CMD and select Run as Administrator.

2. Type the following command, sfc /scannow

**The sfc /scannow command scans all protected system files and replaces incorrect versions with correct Microsoft versions.

To determine which files could not be repaired by the System File Checker tool, follow these steps:

3. Open an elevated command prompt. Copy the following command > press Enter:

findstr /c:"[SR]" %windir%\Logs\CBS\CBS.log >%userprofile%\Desktop\sfcdetails.txt

**Note The Sfcdetails.txt file contains details from every time that the System File Checker tool has been run on the computer. The file includes information about files that were not repaired by the System File Checker tool. Verify the date and time entries to determine the problem files that were found the last time that you ran the System File Checker tool. Type sfcdetails.txt in Search programs and files and press Enter.

Paste the sfcdetails.txt into your next post.

#3 cddowning

cddowning
  • Topic Starter

  • Members
  • 9 posts
  • OFFLINE
  •  
  • Local time:08:13 PM

Posted 25 November 2011 - 03:47 PM

2011-11-24 03:33:58, Info CSI 0000019f [SR] Verify complete
2011-11-24 03:33:59, Info CSI 000001a0 [SR] Verifying 100 (0
x0000000000000064) components
2011-11-24 03:33:59, Info CSI 000001a1 [SR] Beginning Verify
and Repair transaction
2011-11-24 03:34:08, Info CSI 000001a3 [SR] Verify complete
2011-11-24 03:34:08, Info CSI 000001a4 [SR] Verifying 100 (0
x0000000000000064) components
2011-11-24 03:34:08, Info CSI 000001a5 [SR] Beginning Verify
and Repair transaction
2011-11-24 03:34:14, Info CSI 000001a7 [SR] Verify complete
2011-11-24 03:34:14, Info CSI 000001a8 [SR] Verifying 100 (0
x0000000000000064) components
2011-11-24 03:34:14, Info CSI 000001a9 [SR] Beginning Verify
and Repair transaction
2011-11-24 03:34:17, Info CSI 000001ab [SR] Verify complete
2011-11-24 03:34:17, Info CSI 000001ac [SR] Verifying 100 (0
x0000000000000064) components
2011-11-24 03:34:17, Info CSI 000001ad [SR] Beginning Verify
and Repair transaction
2011-11-24 03:34:26, Info CSI 000001af [SR] Verify complete
2011-11-24 03:34:27, Info CSI 000001b0 [SR] Verifying 100 (0
x0000000000000064) components
2011-11-24 03:34:27, Info CSI 000001b1 [SR] Beginning Verify
and Repair transaction
2011-11-24 03:34:34, Info CSI 000001b3 [SR] Verify complete
2011-11-24 03:34:34, Info CSI 000001b4 [SR] Verifying 100 (0
x0000000000000064) components
2011-11-24 03:34:34, Info CSI 000001b5 [SR] Beginning Verify
and Repair transaction
2011-11-24 03:34:40, Info CSI 000001b7 [SR] Verify complete
2011-11-24 03:34:41, Info CSI 000001b8 [SR] Verifying 100 (0
x0000000000000064) components
2011-11-24 03:34:41, Info CSI 000001b9 [SR] Beginning Verify
and Repair transaction
2011-11-24 03:34:58, Info CSI 000001bb [SR] Verify complete
2011-11-24 03:34:59, Info CSI 000001bc [SR] Verifying 100 (0
x0000000000000064) components
2011-11-24 03:34:59, Info CSI 000001bd [SR] Beginning Verify
and Repair transaction
2011-11-24 03:35:02, Info CSI 000001bf [SR] Verify complete
2011-11-24 03:35:02, Info CSI 000001c0 [SR] Verifying 100 (0
x0000000000000064) components
2011-11-24 03:35:02, Info CSI 000001c1 [SR] Beginning Verify
and Repair transaction
2011-11-24 03:35:07, Info CSI 000001c3 [SR] Verify complete
2011-11-24 03:35:07, Info CSI 000001c4 [SR] Verifying 100 (0
x0000000000000064) components
2011-11-24 03:35:07, Info CSI 000001c5 [SR] Beginning Verify
and Repair transaction
2011-11-24 03:35:15, Info CSI 000001d0 [SR] Verify complete
2011-11-24 03:35:16, Info CSI 000001d1 [SR] Verifying 100 (0
x0000000000000064) components
2011-11-24 03:35:16, Info CSI 000001d2 [SR] Beginning Verify
and Repair transaction
2011-11-24 03:35:20, Info CSI 000001d4 [SR] Verify complete
2011-11-24 03:35:21, Info CSI 000001d5 [SR] Verifying 100 (0
x0000000000000064) components
2011-11-24 03:35:21, Info CSI 000001d6 [SR] Beginning Verify
and Repair transaction
2011-11-24 03:35:25, Info CSI 000001d8 [SR] Verify complete
2011-11-24 03:35:26, Info CSI 000001d9 [SR] Verifying 100 (0
x0000000000000064) components
2011-11-24 03:35:26, Info CSI 000001da [SR] Beginning Verify
and Repair transaction
2011-11-24 03:35:34, Info CSI 000001dc [SR] Verify complete
2011-11-24 03:35:34, Info CSI 000001dd [SR] Verifying 100 (0
x0000000000000064) components
2011-11-24 03:35:34, Info CSI 000001de [SR] Beginning Verify
and Repair transaction
2011-11-24 03:35:39, Info CSI 000001e0 [SR] Verify complete
2011-11-24 03:35:39, Info CSI 000001e1 [SR] Verifying 100 (0
x0000000000000064) components
2011-11-24 03:35:39, Info CSI 000001e2 [SR] Beginning Verify
and Repair transaction
2011-11-24 03:35:40, Info CSI 000001e4 [SR] Verify complete
2011-11-24 03:35:40, Info CSI 000001e5 [SR] Verifying 100 (0
x0000000000000064) components
2011-11-24 03:35:40, Info CSI 000001e6 [SR] Beginning Verify
and Repair transaction
2011-11-24 03:35:48, Info CSI 000001ea [SR] Verify complete
2011-11-24 03:35:49, Info CSI 000001eb [SR] Verifying 100 (0
x0000000000000064) components
2011-11-24 03:35:49, Info CSI 000001ec [SR] Beginning Verify
and Repair transaction
2011-11-24 03:35:57, Info CSI 000001f1 [SR] Verify complete
2011-11-24 03:35:57, Info CSI 000001f2 [SR] Verifying 100 (0
x0000000000000064) components
2011-11-24 03:35:57, Info CSI 000001f3 [SR] Beginning Verify
and Repair transaction
2011-11-24 03:36:10, Info CSI 000001fd [SR] Verify complete
2011-11-24 03:36:11, Info CSI 000001fe [SR] Verifying 100 (0
x0000000000000064) components
2011-11-24 03:36:11, Info CSI 000001ff [SR] Beginning Verify
and Repair transaction
2011-11-24 03:36:17, Info CSI 0000020b [SR] Verify complete
2011-11-24 03:36:17, Info CSI 0000020c [SR] Verifying 100 (0
x0000000000000064) components
2011-11-24 03:36:17, Info CSI 0000020d [SR] Beginning Verify
and Repair transaction
2011-11-24 03:36:21, Info CSI 0000020f [SR] Verify complete
2011-11-24 03:36:22, Info CSI 00000210 [SR] Verifying 100 (0
x0000000000000064) components
2011-11-24 03:36:22, Info CSI 00000211 [SR] Beginning Verify
and Repair transaction
2011-11-24 03:36:25, Info CSI 00000216 [SR] Verify complete
2011-11-24 03:36:26, Info CSI 00000217 [SR] Verifying 100 (0
x0000000000000064) components
2011-11-24 03:36:26, Info CSI 00000218 [SR] Beginning Verify
and Repair transaction
2011-11-24 03:36:31, Info CSI 0000021a [SR] Verify complete
2011-11-24 03:36:31, Info CSI 0000021b [SR] Verifying 100 (0
x0000000000000064) components
2011-11-24 03:36:31, Info CSI 0000021c [SR] Beginning Verify
and Repair transaction
2011-11-24 03:36:38, Info CSI 00000241 [SR] Verify complete
2011-11-24 03:36:38, Info CSI 00000242 [SR] Verifying 100 (0
x0000000000000064) components
2011-11-24 03:36:38, Info CSI 00000243 [SR] Beginning Verify
and Repair transaction
2011-11-24 03:36:41, Info CSI 00000245 [SR] Verify complete
2011-11-24 03:36:42, Info CSI 00000246 [SR] Verifying 100 (0
x0000000000000064) components
2011-11-24 03:36:42, Info CSI 00000247 [SR] Beginning Verify
and Repair transaction
2011-11-24 03:36:46, Info CSI 00000249 [SR] Verify complete
2011-11-24 03:36:46, Info CSI 0000024a [SR] Verifying 100 (0
x0000000000000064) components
2011-11-24 03:36:46, Info CSI 0000024b [SR] Beginning Verify
and Repair transaction
2011-11-24 03:36:51, Info CSI 0000024d [SR] Verify complete
2011-11-24 03:36:51, Info CSI 0000024e [SR] Verifying 100 (0
x0000000000000064) components
2011-11-24 03:36:51, Info CSI 0000024f [SR] Beginning Verify
and Repair transaction
2011-11-24 03:36:59, Info CSI 00000260 [SR] Verify complete
2011-11-24 03:37:00, Info CSI 00000261 [SR] Verifying 100 (0
x0000000000000064) components
2011-11-24 03:37:00, Info CSI 00000262 [SR] Beginning Verify
and Repair transaction
2011-11-24 03:37:09, Info CSI 00000270 [SR] Verify complete
2011-11-24 03:37:09, Info CSI 00000271 [SR] Verifying 100 (0
x0000000000000064) components
2011-11-24 03:37:09, Info CSI 00000272 [SR] Beginning Verify
and Repair transaction
2011-11-24 03:37:13, Info CSI 00000274 [SR] Verify complete
2011-11-24 03:37:13, Info CSI 00000275 [SR] Verifying 100 (0
x0000000000000064) components
2011-11-24 03:37:13, Info CSI 00000276 [SR] Beginning Verify
and Repair transaction
2011-11-24 03:37:17, Info CSI 00000279 [SR] Verify complete
2011-11-24 03:37:18, Info CSI 0000027a [SR] Verifying 100 (0
x0000000000000064) components
2011-11-24 03:37:18, Info CSI 0000027b [SR] Beginning Verify
and Repair transaction
2011-11-24 03:37:26, Info CSI 0000027d [SR] Verify complete
2011-11-24 03:37:27, Info CSI 0000027e [SR] Verifying 100 (0
x0000000000000064) components
2011-11-24 03:37:27, Info CSI 0000027f [SR] Beginning Verify
and Repair transaction
2011-11-24 03:37:29, Info CSI 00000281 [SR] Verify complete
2011-11-24 03:37:29, Info CSI 00000282 [SR] Verifying 100 (0
x0000000000000064) components
2011-11-24 03:37:29, Info CSI 00000283 [SR] Beginning Verify
and Repair transaction
2011-11-24 03:37:35, Info CSI 00000285 [SR] Verify complete
2011-11-24 03:37:35, Info CSI 00000286 [SR] Verifying 100 (0
x0000000000000064) components
2011-11-24 03:37:35, Info CSI 00000287 [SR] Beginning Verify
and Repair transaction
2011-11-24 03:37:40, Info CSI 00000289 [SR] Verify complete
2011-11-24 03:37:40, Info CSI 0000028a [SR] Verifying 100 (0
x0000000000000064) components
2011-11-24 03:37:40, Info CSI 0000028b [SR] Beginning Verify
and Repair transaction
2011-11-24 03:37:49, Info CSI 000002a3 [SR] Verify complete
2011-11-24 03:37:49, Info CSI 000002a4 [SR] Verifying 100 (0
x0000000000000064) components
2011-11-24 03:37:49, Info CSI 000002a5 [SR] Beginning Verify
and Repair transaction
2011-11-24 03:37:56, Info CSI 000002ab [SR] Verify complete
2011-11-24 03:37:57, Info CSI 000002ac [SR] Verifying 100 (0
x0000000000000064) components
2011-11-24 03:37:57, Info CSI 000002ad [SR] Beginning Verify
and Repair transaction
2011-11-24 03:38:13, Info CSI 000002af [SR] Verify complete
2011-11-24 03:38:13, Info CSI 000002b0 [SR] Verifying 100 (0
x0000000000000064) components
2011-11-24 03:38:13, Info CSI 000002b1 [SR] Beginning Verify
and Repair transaction
2011-11-24 03:38:20, Info CSI 000002b3 [SR] Verify complete
2011-11-24 03:38:21, Info CSI 000002b4 [SR] Verifying 100 (0
x0000000000000064) components
2011-11-24 03:38:21, Info CSI 000002b5 [SR] Beginning Verify
and Repair transaction
2011-11-24 03:38:26, Info CSI 000002b7 [SR] Verify complete
2011-11-24 03:38:26, Info CSI 000002b8 [SR] Verifying 100 (0
x0000000000000064) components
2011-11-24 03:38:26, Info CSI 000002b9 [SR] Beginning Verify
and Repair transaction
2011-11-24 03:38:31, Info CSI 000002bc [SR] Verify complete
2011-11-24 03:38:31, Info CSI 000002bd [SR] Verifying 100 (0
x0000000000000064) components
2011-11-24 03:38:31, Info CSI 000002be [SR] Beginning Verify
and Repair transaction
2011-11-24 03:38:42, Info CSI 000002c0 [SR] Verify complete
2011-11-24 03:38:42, Info CSI 000002c1 [SR] Verifying 100 (0
x0000000000000064) components
2011-11-24 03:38:42, Info CSI 000002c2 [SR] Beginning Verify
and Repair transaction
2011-11-24 03:38:49, Info CSI 000002c4 [SR] Verify complete
2011-11-24 03:38:49, Info CSI 000002c5 [SR] Verifying 100 (0
x0000000000000064) components
2011-11-24 03:38:49, Info CSI 000002c6 [SR] Beginning Verify
and Repair transaction
2011-11-24 03:38:56, Info CSI 000002c8 [SR] Verify complete
2011-11-24 03:38:56, Info CSI 000002c9 [SR] Verifying 100 (0
x0000000000000064) components
2011-11-24 03:38:56, Info CSI 000002ca [SR] Beginning Verify
and Repair transaction
2011-11-24 03:39:00, Info CSI 000002cd [SR] Verify complete
2011-11-24 03:39:00, Info CSI 000002ce [SR] Verifying 100 (0
x0000000000000064) components
2011-11-24 03:39:00, Info CSI 000002cf [SR] Beginning Verify
and Repair transaction
2011-11-24 03:39:05, Info CSI 000002d1 [SR] Verify complete
2011-11-24 03:39:05, Info CSI 000002d2 [SR] Verifying 100 (0
x0000000000000064) components
2011-11-24 03:39:05, Info CSI 000002d3 [SR] Beginning Verify
and Repair transaction
2011-11-24 03:39:11, Info CSI 000002d5 [SR] Verify complete
2011-11-24 03:39:11, Info CSI 000002d6 [SR] Verifying 100 (0
x0000000000000064) components
2011-11-24 03:39:11, Info CSI 000002d7 [SR] Beginning Verify
and Repair transaction
2011-11-24 03:39:17, Info CSI 000002dc [SR] Verify complete
2011-11-24 03:39:18, Info CSI 000002dd [SR] Verifying 100 (0
x0000000000000064) components
2011-11-24 03:39:18, Info CSI 000002de [SR] Beginning Verify
and Repair transaction
2011-11-24 03:39:24, Info CSI 000002e0 [SR] Verify complete
2011-11-24 03:39:25, Info CSI 000002e1 [SR] Verifying 100 (0
x0000000000000064) components
2011-11-24 03:39:25, Info CSI 000002e2 [SR] Beginning Verify
and Repair transaction
2011-11-24 03:39:29, Info CSI 000002e5 [SR] Verify complete
2011-11-24 03:39:30, Info CSI 000002e6 [SR] Verifying 100 (0
x0000000000000064) components
2011-11-24 03:39:30, Info CSI 000002e7 [SR] Beginning Verify
and Repair transaction
2011-11-24 03:39:36, Info CSI 000002e9 [SR] Verify complete
2011-11-24 03:39:37, Info CSI 000002ea [SR] Verifying 100 (0
x0000000000000064) components
2011-11-24 03:39:37, Info CSI 000002eb [SR] Beginning Verify
and Repair transaction
2011-11-24 03:39:44, Info CSI 000002ed [SR] Verify complete
2011-11-24 03:39:44, Info CSI 000002ee [SR] Verifying 100 (0
x0000000000000064) components
2011-11-24 03:39:44, Info CSI 000002ef [SR] Beginning Verify
and Repair transaction
2011-11-24 03:39:50, Info CSI 000002f1 [SR] Verify complete
2011-11-24 03:39:50, Info CSI 000002f2 [SR] Verifying 14 (0x
000000000000000e) components
2011-11-24 03:39:50, Info CSI 000002f3 [SR] Beginning Verify
and Repair transaction
2011-11-24 03:39:50, Info CSI 000002f5 [SR] Verify complete
2011-11-24 03:39:50, Info CSI 000002f6 [SR] Repairing 1 comp
onents
2011-11-24 03:39:50, Info CSI 000002f7 [SR] Beginning Verify
and Repair transaction
2011-11-24 03:39:50, Info CSI 000002f9 [SR] Cannot repair me
mber file [l:24{12}]"settings.ini" of Microsoft-Windows-Sidebar, Version = 6.0.6
002.18005, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope
= 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName ne
utral, PublicKey neutral in the store, hash mismatch
2011-11-24 03:39:50, Info CSI 000002fb [SR] Cannot repair me
mber file [l:24{12}]"settings.ini" of Microsoft-Windows-Sidebar, Version = 6.0.6
002.18005, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope
= 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName ne
utral, PublicKey neutral in the store, hash mismatch
2011-11-24 03:39:50, Info CSI 000002fc [SR] This component w
as referenced by [l:162{81}]"Package_17_for_KB948465~31bf3856ad364e35~amd64~~6.0
.1.18005.948465-60_neutral_GDR"
2011-11-24 03:39:51, Info CSI 000002fe [SR] Repair complete
2011-11-24 03:39:51, Info CSI 000002ff [SR] Committing trans
action
2011-11-24 03:39:51, Info CSI 00000303 [SR] Verify and Repai
r Transaction completed. All files and registry keys listed in this transaction
have been successfully repaired

#4 hamluis

hamluis

    Moderator


  • Moderator
  • 56,435 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Killeen, TX
  • Local time:10:13 PM

Posted 25 November 2011 - 04:37 PM

Let's try this.

Download/install BlueScreenView, http://www.nirsoft.net/utils/blue_screen_view.html .

Double-click BlueScreenView.exe file.

When autoscan is done (screen comes up), click Edit/Select All...then File/Save Selected Items.

Save the report as BSOD.txt.

Open BSOD.txt in Notepad, copy all content and paste it into your next reply.

Louis

#5 cddowning

cddowning
  • Topic Starter

  • Members
  • 9 posts
  • OFFLINE
  •  
  • Local time:08:13 PM

Posted 25 November 2011 - 05:54 PM

Louis,

I ran an installed BlueScreenView again. The last time I ran it, it was full of info. This time, it is blank. I even restarted my PC (and got another BSOD) but it isnt reflecting in that report. :(

#6 AustrAlien

AustrAlien

    Inquisitor


  • Members
  • 6,772 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Cowra NSW Australia
  • Local time:02:13 PM

Posted 25 November 2011 - 06:40 PM

There are numerous reasons that a log may not saved after a BSOD ...

The results of running sfc /scannow that you posted look good.

Please do the following:
(the screenshots are from Windows XP, but things will be essentially the same in Vista)

Get a look at the error message presented by the BSOD (blue screen of death) ....
  • Start tapping the F8 key after you press the ON button, and continue tapping until you are presented with the "Advanced Boot Options" menu screen.

    Posted Image
  • Use the UP/DOWN arrow keys to select "Disable automatic restart on system failure" and press the <ENTER> key.
  • Your system will attempt to restart normally, but when it crashes, it will not re-start: Instead, you will see a BSOD with error message.

    Posted Image
  • Record the error message details (contained in the areas outlined in red, in the above example image), and post in your reply.

AustrAlien
Google is my friend. Make Google your friend too.

Posted Image

#7 cddowning

cddowning
  • Topic Starter

  • Members
  • 9 posts
  • OFFLINE
  •  
  • Local time:08:13 PM

Posted 26 November 2011 - 02:15 AM

You got it AustrAlien:


DRIVER_IRQL_NOT_LESS_OR_EQUAL

*** STOP: 0x000000D1 (0x0000000000000110, 0x0000000000000002, 0x0000000000000000, 0xFFFFFA60011EECEF)

*** BFRD4G.sys - Address FA660011EECEF base at FFFFFA60011E4000 DATE STAMP 4b95e89a

#8 AustrAlien

AustrAlien

    Inquisitor


  • Members
  • 6,772 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Cowra NSW Australia
  • Local time:02:13 PM

Posted 26 November 2011 - 02:58 AM

Do you have any Buffalo Technology products from BUFFALO INC. that may explain what this file (BFRD4G.sys) is doing on your system?

What happens when you repeat the process to get another look at the BSOD error message? Is the BSOD error reported exactly the same? Please post the details.

In Safe Mode (with networking), look in the following location for any minidump files:
C:\Windows\Minidump <<< folder

If so, please zip them up and attach to your reply so I can have a closer look. There's a chance I might get some more useful info from them.
  • Click on the most recent minidump file.
  • Hold down the <Ctrl> key, and click on any other minidump files to also select them.
  • Release the <Ctrl> key.
  • Now, right-click on one of the selected files > Send to ... > Compressed (zipped) Folder.
    The zip file will be located in the same place (the Minidump folder).
  • Attach the zip file to your next reply.
    When you click on Add Reply, you will see the facility to attach a file just below the box where you type your message.

Edited by AustrAlien, 26 November 2011 - 03:03 AM.

AustrAlien
Google is my friend. Make Google your friend too.

Posted Image

#9 cddowning

cddowning
  • Topic Starter

  • Members
  • 9 posts
  • OFFLINE
  •  
  • Local time:08:13 PM

Posted 26 November 2011 - 12:47 PM

I DO have a Buffalo external drive, and for a while the utility was giving me trouble when it tried to load. I tried to erase the entire program, but it seems to have stuck around. To answer your other question, I get the same BSOD each time now (I've not seen any new messages). The Minidump file is currently empty.

#10 AustrAlien

AustrAlien

    Inquisitor


  • Members
  • 6,772 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Cowra NSW Australia
  • Local time:02:13 PM

Posted 27 November 2011 - 01:12 AM

In Safe Mode with networking ...
  • Please use the 64 bit system download.

Please download SystemLook.exe and save it to your Desktop.
  • alternate download link
    For users of Windows 64 bit systems: SystemLook (64-bit)
  • Double-click SystemLook.exe to run it.
  • Copy the content of the following code box and paste into the main text field:
    :filefind
    BFRD4G.sys
    
  • Click the Look button to start the scan.
    Please be patient, as it may take a little time.
  • When finished, a Notepad window will open with the results of the scan.
  • Please copy & paste the entire content of this log in your next reply.
Note: The log, SystemLook.txt, is saved on your Desktop.

Edit: I am not sure, but in Vista you may have to right-click on SystemLook.exe and choose to Run as Administrator.

Edited by AustrAlien, 27 November 2011 - 01:16 AM.

AustrAlien
Google is my friend. Make Google your friend too.

Posted Image

#11 cddowning

cddowning
  • Topic Starter

  • Members
  • 9 posts
  • OFFLINE
  •  
  • Local time:08:13 PM

Posted 27 November 2011 - 04:03 PM

I downloaded SystemLook, and each time that I try to run it ("Look") I get an error: "Script Required!"

I downloaded it again just to be sure, and same error message. Sorry to be such a pain :(

#12 AustrAlien

AustrAlien

    Inquisitor


  • Members
  • 6,772 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Cowra NSW Australia
  • Local time:02:13 PM

Posted 27 November 2011 - 04:08 PM

I get that error when clicking on "Look" if there is nothing entered in the box for it to do!

Did you forget to "Copy the content of the following code box and paste into the main text field:"?
AustrAlien
Google is my friend. Make Google your friend too.

Posted Image

#13 cddowning

cddowning
  • Topic Starter

  • Members
  • 9 posts
  • OFFLINE
  •  
  • Local time:08:13 PM

Posted 27 November 2011 - 04:33 PM

My apologies lol.


SystemLook 30.07.11 by jpshortstuff
Log created at 04:32 on 26/11/2011 by CDD
Administrator - Elevation successful

========== filefind ==========

Searching for "BFRD4G.sys"
C:\Windows\System32\drivers\BFRD4G.sys --a---- 47232 bytes [02:39 21/03/2011] [02:30 10/03/2010] B6F7CD60EDD460D88D27D9E7FB32B877
C:\Windows\System32\DriverStore\FileRepository\bfrd4g.inf_f0e090cc\BFRD4G.sys ------- 47232 bytes [02:39 21/03/2011] [02:30 10/03/2010] B6F7CD60EDD460D88D27D9E7FB32B877

-= EOF =-

#14 AustrAlien

AustrAlien

    Inquisitor


  • Members
  • 6,772 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Cowra NSW Australia
  • Local time:02:13 PM

Posted 27 November 2011 - 04:49 PM

Let's see if you can start Windows normally after disabling (re-naming) BFRD4G.sys

In Safe Mode, navigate to:

C:\Windows\System32\drivers\BFRD4G.sys

Right-click on the file BFRD4G.sys > Rename and change the name to BFRD4G.OLD

(Vista might give you a hard time when doing this ... but I guess you are used to that by now!)

Restart the system normally. Success?
AustrAlien
Google is my friend. Make Google your friend too.

Posted Image

#15 cddowning

cddowning
  • Topic Starter

  • Members
  • 9 posts
  • OFFLINE
  •  
  • Local time:08:13 PM

Posted 27 November 2011 - 05:11 PM

Success! Are you telling me that all I had to do was rename the bloody thing? Thank you for your help, I really really appreciate it!




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users