MBAM Crashes Windows XP
Started by
K1500
, Apr 11 2010 08:07 PM
#1
Posted 11 April 2010 - 08:07 PM
#2
Posted 11 April 2010 - 09:36 PM
to start with completly uninstall mbam
then reboot after usingthe machine for this session download the newest version of mbam and installit this should fix the issue
then reboot after usingthe machine for this session download the newest version of mbam and installit this should fix the issue
#3
Posted 12 April 2010 - 12:24 AM
No good, I've tried that a few times and just tried it again to no avail. I got the BSOD and 0x000000F4 error.
#4
Posted 12 April 2010 - 03:23 AM
OK then it would seem to methat somethi9ng else is causing the BSOD and we have to figure out what
I have a program here atht can search for what causes it and gives you a report on exactly what swoftweare or hardware is cauing this so sne dme an email to
I willthen send you the program nand you can seee whats caugin it once we determine whats doin ti we can then work on fixing the issue once and for all
I have a program here atht can search for what causes it and gives you a report on exactly what swoftweare or hardware is cauing this so sne dme an email to
I willthen send you the program nand you can seee whats caugin it once we determine whats doin ti we can then work on fixing the issue once and for all
Edited by Rorschach112, 12 April 2010 - 01:48 PM.
removed email
#5
Posted 12 April 2010 - 06:21 AM
Can you just post the link to the program's website?
#6
Posted 12 April 2010 - 06:32 AM
Tpneer2 Pursuant to the Terms of USE no support is given via email or pm's.
Download WhoCrashed from the link in my signature below
This program checks for any drivers which may have been causing your computer to crash....
Click on the file you just downloaded and run it.
Put a tick in Accept then click on Next
Put a tick in the Don't create a start menu folder then click Next
Put a tick in Create a Desktop Icon then click on Install and make sure there is a tick in Launch Whocrashed before clicking Finish
Click Analyze
It will want to download the Debugger and install it Say Yes
WhoCrashed will create report but you have to scroll down to see it
Copy and paste it into your next reply
Download WhoCrashed from the link in my signature below
This program checks for any drivers which may have been causing your computer to crash....
Click on the file you just downloaded and run it.
Put a tick in Accept then click on Next
Put a tick in the Don't create a start menu folder then click Next
Put a tick in Create a Desktop Icon then click on Install and make sure there is a tick in Launch Whocrashed before clicking Finish
Click Analyze
It will want to download the Debugger and install it Say Yes
WhoCrashed will create report but you have to scroll down to see it
Copy and paste it into your next reply
Edited by rshaffer61, 12 April 2010 - 06:33 AM.
#7
Posted 12 April 2010 - 02:37 PM
Thanks, I thought that was a bit fishy.
I was never asked to download and install the Debugger, but here's the report, anyhow:
Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\WINDOWS\Minidump
Crash dumps are enabled on your computer.
No valid crash dumps have been found on your computer
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
Crash dumps are enabled and no valid crash dumps have been found on your computer. In case your computer does experience sudden reboots it is likely these are caused by malfunctioning hardware, power failure or a thermal issue. To troubleshoot a thermal issue, check the temperature using your BIOS setup program, check for dust in CPU and motherboard fans and if your computer is portable make sure it's located on a hard surface. Otherwise it's suggested you contact the support department of the manufacturer of your system or test your system with a memory test utility for further investigation.
I was never asked to download and install the Debugger, but here's the report, anyhow:
Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\WINDOWS\Minidump
Crash dumps are enabled on your computer.
No valid crash dumps have been found on your computer
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
Crash dumps are enabled and no valid crash dumps have been found on your computer. In case your computer does experience sudden reboots it is likely these are caused by malfunctioning hardware, power failure or a thermal issue. To troubleshoot a thermal issue, check the temperature using your BIOS setup program, check for dust in CPU and motherboard fans and if your computer is portable make sure it's located on a hard surface. Otherwise it's suggested you contact the support department of the manufacturer of your system or test your system with a memory test utility for further investigation.
Edited by K1500, 12 April 2010 - 02:37 PM.
#8
Posted 12 April 2010 - 05:23 PM
Not a driver issue from what I can see.
Either:
- Please download the Event Viewer Tool by Vino Rosso VEW and save it to your Desktop:
- Double-click VEW.exe
- Under 'Select log to query', select (as appropriate):
- Application
- System
- Under 'Select type to list', select (as appropriate):
- Error
- Information
- Warning
Either:
- Click the radio button for 'Number of events'
Type 3 in the 1 to 20 box (or any number from 1 to 20)
Then click the Run button.
Notepad will open with the output log.
- Click the radio button for 'Date of events'
In the From: boxes type today's date (presuming the crash happened today) 13 07 2009
In the To: boxes type today's date (presuming the crash happened today) 13 07 2009
Then click the Run button.
Notepad will open with the output log.
#9
Posted 12 April 2010 - 07:32 PM
Vino's Event Viewer v01c run on Windows XP in English
Report run at 12/04/2010 8:31:44 PM
Note: All dates below are in the format dd/mm/yyyy
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'Application' Log - error Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'Application' Date/Time: 12/04/2010 8:21:47 PM
Type: error Category: 3
Event: 3013 Source: Windows Search Service
The entry <F:\MY DOCUMENTS\MY MUSIC\ITUNES\TEMP FILE.TMP> in the hash map cannot be updated.
Context: Application, SystemIndex Catalog
Details:
A device attached to the system is not functioning. (0x8007001f)
Log: 'Application' Date/Time: 12/04/2010 8:21:47 PM
Type: error Category: 3
Event: 3013 Source: Windows Search Service
The entry <F:\MY DOCUMENTS\MY MUSIC\ITUNES\TEMP FILE.TMP> in the hash map cannot be updated.
Context: Application, SystemIndex Catalog
Details:
A device attached to the system is not functioning. (0x8007001f)
Log: 'Application' Date/Time: 12/04/2010 8:21:45 PM
Type: error Category: 3
Event: 3013 Source: Windows Search Service
The entry <F:\MY DOCUMENTS\MY MUSIC\ITUNES\IT.TMP> in the hash map cannot be updated.
Context: Application, SystemIndex Catalog
Details:
A device attached to the system is not functioning. (0x8007001f)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'Application' Log - information Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'Application' Date/Time: 12/04/2010 8:21:13 PM
Type: information Category: 0
Event: 0 Source: iPod Service
The event description cannot be found.
Log: 'Application' Date/Time: 12/04/2010 8:21:06 PM
Type: information Category: 3
Event: 3044 Source: Windows Search Service
The gatherer index resumed.
Context: Application, SystemIndex Catalog
Log: 'Application' Date/Time: 12/04/2010 8:20:52 PM
Type: information Category: 0
Event: 0 Source: PDAgent
PerfectDisk Scheduler started.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'Application' Log - warning Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'Application' Date/Time: 12/04/2010 8:20:15 PM
Type: warning Category: 0
Event: 1015 Source: EvntAgnt
TraceLevel parameter not located in registry; Default trace level used is 32.
Log: 'Application' Date/Time: 12/04/2010 8:20:15 PM
Type: warning Category: 0
Event: 1003 Source: EvntAgnt
TraceFileName parameter not located in registry; Default trace file used is .
Log: 'Application' Date/Time: 12/04/2010 6:57:26 AM
Type: warning Category: 0
Event: 1015 Source: EvntAgnt
TraceLevel parameter not located in registry; Default trace level used is 32.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'System' Log - error Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'System' Date/Time: 12/04/2010 8:20:19 PM
Type: error Category: 44
Event: 45062 Source: ati2mtag
CRT invalid display type
Log: 'System' Date/Time: 12/04/2010 8:20:09 PM
Type: error Category: 0
Event: 23 Source: Print
Printer Fax failed to initialize because a suitable Microsoft Shared Fax Driver driver could not be found.
Log: 'System' Date/Time: 12/04/2010 8:12:57 PM
Type: error Category: 0
Event: 9 Source: iastor
The device, \Device\Ide\iaStor0, did not respond within the timeout period.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'System' Log - information Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'System' Date/Time: 12/04/2010 8:21:20 PM
Type: information Category: 0
Event: 7036 Source: Service Control Manager
The COM+ System Application service entered the running state.
Log: 'System' Date/Time: 12/04/2010 8:21:20 PM
Type: information Category: 0
Event: 7035 Source: Service Control Manager
The COM+ System Application service was successfully sent a start control.
Log: 'System' Date/Time: 12/04/2010 8:21:13 PM
Type: information Category: 0
Event: 7036 Source: Service Control Manager
The iPod Service service entered the running state.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'System' Log - warning Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'System' Date/Time: 12/04/2010 8:12:57 PM
Type: warning Category: 0
Event: 51 Source: Disk
An error was detected on device \Device\Harddisk0\D during a paging operation.
Log: 'System' Date/Time: 12/04/2010 8:12:46 PM
Type: warning Category: 0
Event: 51 Source: Disk
An error was detected on device \Device\Harddisk0\D during a paging operation.
Log: 'System' Date/Time: 12/04/2010 8:12:46 PM
Type: warning Category: 0
Event: 51 Source: Disk
An error was detected on device \Device\Harddisk0\D during a paging operation.
Report run at 12/04/2010 8:31:44 PM
Note: All dates below are in the format dd/mm/yyyy
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'Application' Log - error Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'Application' Date/Time: 12/04/2010 8:21:47 PM
Type: error Category: 3
Event: 3013 Source: Windows Search Service
The entry <F:\MY DOCUMENTS\MY MUSIC\ITUNES\TEMP FILE.TMP> in the hash map cannot be updated.
Context: Application, SystemIndex Catalog
Details:
A device attached to the system is not functioning. (0x8007001f)
Log: 'Application' Date/Time: 12/04/2010 8:21:47 PM
Type: error Category: 3
Event: 3013 Source: Windows Search Service
The entry <F:\MY DOCUMENTS\MY MUSIC\ITUNES\TEMP FILE.TMP> in the hash map cannot be updated.
Context: Application, SystemIndex Catalog
Details:
A device attached to the system is not functioning. (0x8007001f)
Log: 'Application' Date/Time: 12/04/2010 8:21:45 PM
Type: error Category: 3
Event: 3013 Source: Windows Search Service
The entry <F:\MY DOCUMENTS\MY MUSIC\ITUNES\IT.TMP> in the hash map cannot be updated.
Context: Application, SystemIndex Catalog
Details:
A device attached to the system is not functioning. (0x8007001f)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'Application' Log - information Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'Application' Date/Time: 12/04/2010 8:21:13 PM
Type: information Category: 0
Event: 0 Source: iPod Service
The event description cannot be found.
Log: 'Application' Date/Time: 12/04/2010 8:21:06 PM
Type: information Category: 3
Event: 3044 Source: Windows Search Service
The gatherer index resumed.
Context: Application, SystemIndex Catalog
Log: 'Application' Date/Time: 12/04/2010 8:20:52 PM
Type: information Category: 0
Event: 0 Source: PDAgent
PerfectDisk Scheduler started.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'Application' Log - warning Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'Application' Date/Time: 12/04/2010 8:20:15 PM
Type: warning Category: 0
Event: 1015 Source: EvntAgnt
TraceLevel parameter not located in registry; Default trace level used is 32.
Log: 'Application' Date/Time: 12/04/2010 8:20:15 PM
Type: warning Category: 0
Event: 1003 Source: EvntAgnt
TraceFileName parameter not located in registry; Default trace file used is .
Log: 'Application' Date/Time: 12/04/2010 6:57:26 AM
Type: warning Category: 0
Event: 1015 Source: EvntAgnt
TraceLevel parameter not located in registry; Default trace level used is 32.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'System' Log - error Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'System' Date/Time: 12/04/2010 8:20:19 PM
Type: error Category: 44
Event: 45062 Source: ati2mtag
CRT invalid display type
Log: 'System' Date/Time: 12/04/2010 8:20:09 PM
Type: error Category: 0
Event: 23 Source: Print
Printer Fax failed to initialize because a suitable Microsoft Shared Fax Driver driver could not be found.
Log: 'System' Date/Time: 12/04/2010 8:12:57 PM
Type: error Category: 0
Event: 9 Source: iastor
The device, \Device\Ide\iaStor0, did not respond within the timeout period.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'System' Log - information Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'System' Date/Time: 12/04/2010 8:21:20 PM
Type: information Category: 0
Event: 7036 Source: Service Control Manager
The COM+ System Application service entered the running state.
Log: 'System' Date/Time: 12/04/2010 8:21:20 PM
Type: information Category: 0
Event: 7035 Source: Service Control Manager
The COM+ System Application service was successfully sent a start control.
Log: 'System' Date/Time: 12/04/2010 8:21:13 PM
Type: information Category: 0
Event: 7036 Source: Service Control Manager
The iPod Service service entered the running state.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'System' Log - warning Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'System' Date/Time: 12/04/2010 8:12:57 PM
Type: warning Category: 0
Event: 51 Source: Disk
An error was detected on device \Device\Harddisk0\D during a paging operation.
Log: 'System' Date/Time: 12/04/2010 8:12:46 PM
Type: warning Category: 0
Event: 51 Source: Disk
An error was detected on device \Device\Harddisk0\D during a paging operation.
Log: 'System' Date/Time: 12/04/2010 8:12:46 PM
Type: warning Category: 0
Event: 51 Source: Disk
An error was detected on device \Device\Harddisk0\D during a paging operation.
#10
Posted 14 April 2010 - 07:17 PM
Sorry I have been dealing with real life.
Go to
Start and then to Run
Type in Chkdsk /r Note the space between k and /
Click Enter ...It will probably ask if you want to do this on the next reboot...click Y
If the window doesn't shutdown on its own then reboot the system manually. On reboot the system will start the chkdsk operation
This one will take longer then chkdsk /f
Note... there are 5 stages...
It may appear to hang at a certain percent for a hour or more or even back up and go over the same area...this is normal...
DO NOT SHUT YOUR COMPUTER DOWN WHILE CHKDSK IS RUNNING OR YOU CAN HAVE SEVERE PROBLEMS
This can take several hours to complete.
When completed it will boot the system back into windows.
Let me know if this fixes the problem
Go to
Start and then to Run
Type in Chkdsk /r Note the space between k and /
Click Enter ...It will probably ask if you want to do this on the next reboot...click Y
If the window doesn't shutdown on its own then reboot the system manually. On reboot the system will start the chkdsk operation
This one will take longer then chkdsk /f
Note... there are 5 stages...
It may appear to hang at a certain percent for a hour or more or even back up and go over the same area...this is normal...
DO NOT SHUT YOUR COMPUTER DOWN WHILE CHKDSK IS RUNNING OR YOU CAN HAVE SEVERE PROBLEMS
This can take several hours to complete.
When completed it will boot the system back into windows.
Let me know if this fixes the problem
#11
Posted 14 April 2010 - 07:28 PM
I understand, sorry if I was impatient! I'll give that a go and get back to you. Thanks a lot!
#12
Posted 14 April 2010 - 08:33 PM
Not a problem and I understand when your system isn't working it may seem stressful.
#13
Posted 14 April 2010 - 09:24 PM
Well, unfortunately that didn't work.
#14
Posted 15 April 2010 - 04:16 AM
Hello again it seems like efforts so far have not helped so I went and searched forth program in question
did not have it avalible before, I beta test software and at times my bookmarks give me grief so here is the link to the thing
run it and when bsod occurs it will generate a report to tell you EXACTLY what is causing it
http://www.mydigital...sh-information/
nothing fishy about it the program is in my folder I use to remote admin and help people with
did not have it avalible before, I beta test software and at times my bookmarks give me grief so here is the link to the thing
run it and when bsod occurs it will generate a report to tell you EXACTLY what is causing it
http://www.mydigital...sh-information/
nothing fishy about it the program is in my folder I use to remote admin and help people with
#15
Posted 15 April 2010 - 06:49 AM
Download BlueScreenView
No installation required.
Double click on BlueScreenView.exe file to run the program.
When scanning is done, go Edit>Select All.
Go File>Save Selected Items, and save the report as BSOD.txt.
Open BSOD.txt in Notepad, copy all content, and paste it into your next reply.
Thanks to Broni for the instructions and program
No installation required.
Double click on BlueScreenView.exe file to run the program.
When scanning is done, go Edit>Select All.
Go File>Save Selected Items, and save the report as BSOD.txt.
Open BSOD.txt in Notepad, copy all content, and paste it into your next reply.
Thanks to Broni for the instructions and program
Similar Topics
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users