Jump to content

Welcome to Geeks to Go - Register now for FREE

Geeks To Go is a helpful hub, where thousands of volunteer geeks quickly serve friendly answers and support. Check out the forums and get free advice from the experts. Register now to gain access to all of our features, it's FREE and only takes one minute. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more.

Create Account How it Works
Photo

Computer won't boot due to Hardware change


  • Please log in to reply

#1
caitiebugg87

caitiebugg87

    Member

  • Member
  • PipPip
  • 33 posts
I got a new computer monitor for christmas, and it's a AOC 931swl. At first it worked fine, then I got the BSOD. So I rebooted, and I got the screen that says windows was shut down wrong or whatever due to hardware change. So I did system repair, which tried to load files, then froze. Tried to boot in safemode and the screen got all colorful and wonky. So I rebooted again, and it just rebooted over and over. So I gave up. Well I thought about it, and the only knew hardware I got was the monitor. So I tried to get the computer to start in safemode again, which it did...and I downloaded the drivers. Then my computer was working great for about a week, came home from work and it was frozen. Tried to reboot, and it wouldn't. Just kept freezing up. So today, I plugged my computer into my sisters monitor, and it started right up, and works just fine, hasn't given me any problems. So maybe I have the wrong driver. I tried to find one, and I couldn't. I went to device manager, and it says the driver is up to date.
My computer:
Emachines ET1221G-03w
Windows 7HOme premium 64 bit
AMD Athlon II 235e dual-core processor
NVIDIA GeForce 6150E integrated
750 GB HDD
6GB DDR2 Memory
Monitor is AOC 931swl

here is my BSODview
==================================================
Dump File : 060211-40919-01.dmp
Crash Time : 6/2/2011 7:12:40 PM
Bug Check String :
Bug Check Code : 0x00000116
Parameter 1 : fffffa80`059854e0
Parameter 2 : fffff880`0483e474
Parameter 3 : 00000000`00000000
Parameter 4 : 00000000`0000000d
Caused By Driver : dxgkrnl.sys
Caused By Address : dxgkrnl.sys+5d000
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+70740
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\060211-40919-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 7600
Dump File Size : 1,097,136
==================================================

==================================================
Dump File : 060211-40357-01.dmp
Crash Time : 6/2/2011 6:26:00 PM
Bug Check String :
Bug Check Code : 0x00000117
Parameter 1 : fffffa80`08145010
Parameter 2 : fffff880`04828474
Parameter 3 : 00000000`00000000
Parameter 4 : 00000000`00000000
Caused By Driver : netbios.sys
Caused By Address : netbios.sys+31d8a0
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : watchdog.sys+a577
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\060211-40357-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 7600
Dump File Size : 959,742
==================================================

==================================================
Dump File : 060211-44163-01.dmp
Crash Time : 6/2/2011 6:25:46 PM
Bug Check String :
Bug Check Code : 0x00000116
Parameter 1 : fffffa80`085d1010
Parameter 2 : fffff880`04828474
Parameter 3 : 00000000`00000000
Parameter 4 : 00000000`0000000d
Caused By Driver : dxgkrnl.sys
Caused By Address : dxgkrnl.sys+5d000
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+70740
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\060211-44163-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 7600
Dump File Size : 961,280
==================================================

==================================================
Dump File : 060211-44990-01.dmp
Crash Time : 6/2/2011 7:28:13 AM
Bug Check String :
Bug Check Code : 0x00000116
Parameter 1 : fffffa80`05948010
Parameter 2 : fffff880`0487e474
Parameter 3 : 00000000`00000000
Parameter 4 : 00000000`0000000d
Caused By Driver : dxgkrnl.sys
Caused By Address : dxgkrnl.sys+5d000
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+70740
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\060211-44990-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 7600
Dump File Size : 1,030,904
==================================================

It says the date of the crash was June 2, 2011, which is wrong...it never crashed before December....

Edited by caitiebugg87, 17 February 2012 - 12:44 PM.

  • 0

Advertisements


#2
Macboatmaster

Macboatmaster

    7k

  • Member
  • PipPipPipPipPipPipPipPip
  • 7,237 posts
You will NOT need to go to AOC and download and install the driver for that monitor in Windows 7.
It will be found and recognised and windows will install the drivers necessary.

Did you get a CD with the monitor.
It is not required but that will guide you throughthe setup


http://www.aocmonito...monitor_189.php

the recommended resoltuon for that monitor is

Recommended Resolution: 1366×[email protected]<LI>Display Colours: 16.7M

Have you so set it.

Control Panel
Display
left hand pane change display settings
and also on that window advanced settings.
then monitor tab
screen refresh rate and colour set as above 60Hz at 16
then Adapter tab
properties
Does it report working properly

Exit clicking apply and Ok as required.


Re the BSOD clearly the computer didi Blue Screen in June 2011 otherwise you could not have crash reports for that date -UNLESS the system time and date were/ are incorrect.

I have not addressed those reports as they are of course now 8 months old.


At first it worked fine, then I got the BSOD. So I rebooted, and I got the screen that says windows was shut down wrong or whatever due to hardware change.

When was this please - then I got the BSOD?


So I tried to get the computer to start in safemode again, which it did...and I downloaded the drivers


which drivers please and where from and for what?


Finally before you post back run a chkdsk please
Open Computer
That is Windows button (Start)
Computer
right click the C Drive - presuming C is the only hard drive or the one from which you boot
click properties
click tools
click check now on the Error checking header
click to check both boxes
click start
agree the message to run on restart and do so please.
Please do not interrupt it, it is a five stage check.

When complete
Start
Control Panel
Administrative tools
Event Viewer
Windows logs on left pane
Application
Find on right hand pane
type
chkdsk
click find next
In main window see results
click Details on the tab above the results
Click Copy right hand pane
paste to reply.
  • 0

#3
caitiebugg87

caitiebugg87

    Member

  • Topic Starter
  • Member
  • PipPip
  • 33 posts
I did get a CD with the monitor, and I used it, but there was no option for windows 7 driver, the highest it went was windows vista, so I just went with that driver, then when I went to device manager, I went the driver and updated it.

At first it worked fine, then I got the BSOD. So I rebooted, and I got the screen that says windows was shut down wrong or whatever due to hardware change.

When was this please - then I got the BSOD?


I got the BSOD probably a couple days after the monitor was plugged in.

So I tried to get the computer to start in safemode again, which it did...and I downloaded the drivers


which drivers please and where from and for what?


The driver I downloaded came from the CD, after i was able to get to boot after BSOD, I popped the CD in, and downloaded the driver, which was for vista, because they didn't have one for windows 7. Then I went to device manager and updated the driver, which there was one.

Here's my chkdsk

Log Name: Application
Source: Microsoft-Windows-Wininit
Date: 6/2/2011 8:28:38 AM
Event ID: 1001
Task Category: None
Level: Information
Keywords: Classic
User: N/A
Computer: Caitlin-PC
Description:


Checking file system on C:
The type of the file system is NTFS.
Volume label is eMachines.


One of your disks needs to be checked for consistency. You
may cancel the disk check, but it is strongly recommended
that you continue.
Windows will now check the disk.

CHKDSK is verifying files (stage 1 of 3)...
Cleaning up instance tags for file 0x27ae6.
415232 file records processed.

File verification completed.
447 large file records processed.

0 bad file records processed.

0 EA records processed.

76 reparse records processed.

CHKDSK is verifying indexes (stage 2 of 3)...
Index entry QSGB9XMA of index $I30 in file 0x1113 points to unused file 0x16dd4.
Deleting index entry QSGB9XMA in index $I30 of file 4371.
The multi-sector header signature for VCN 0x0 of index $I30
in file 0xf869 is incorrect.
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
Correcting error in index $I30 for file 63593.
The index bitmap $I30 in file 0xf869 is incorrect.
Correcting error in index $I30 for file 63593.
The down pointer of current index entry with length 0x18 is invalid.
00 00 00 00 00 00 00 00 18 00 00 00 03 00 00 00 ................
ff ff ff ff ff ff ff ff 10 41 78 73 73 ab ca 01 .........Axss...
80 d8 9f ce ac d7 cb 01 80 d8 9f ce ac d7 cb 01 ................
Sorting index $I30 in file 63593.
The multi-sector header signature for VCN 0x0 of index $I30
in file 0xff54 is incorrect.
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
Correcting error in index $I30 for file 65364.
The index bitmap $I30 in file 0xff54 is incorrect.
Correcting error in index $I30 for file 65364.
The down pointer of current index entry with length 0x18 is invalid.
00 00 00 00 00 00 00 00 18 00 00 00 03 00 00 00 ................
ff ff ff ff ff ff ff ff 10 41 78 73 73 ab ca 01 .........Axss...
80 d8 9f ce ac d7 cb 01 80 d8 9f ce ac d7 cb 01 ................
Sorting index $I30 in file 65364.
The multi-sector header signature for VCN 0x0 of index $I30
in file 0x10e01 is incorrect.
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
Correcting error in index $I30 for file 69121.
The index bitmap $I30 in file 0x10e01 is incorrect.
Correcting error in index $I30 for file 69121.
The down pointer of current index entry with length 0x18 is invalid.
00 00 00 00 00 00 00 00 18 00 00 00 03 00 00 00 ................
ff ff ff ff ff ff ff ff 10 41 78 73 73 ab ca 01 .........Axss...
80 d8 9f ce ac d7 cb 01 80 d8 9f ce ac d7 cb 01 ................
Sorting index $I30 in file 69121.
Index entry Reader9Manifest.msi of index $I30 in file 0x10ec1 points to unused file 0x19193.
Deleting index entry Reader9Manifest.msi in index $I30 of file 69313.
Index entry READER~1.MSI of index $I30 in file 0x10ec1 points to unused file 0x19193.
Deleting index entry READER~1.MSI in index $I30 of file 69313.
528700 index entries processed.

Index verification completed.
CHKDSK is scanning unindexed files for reconnect to their original directory.
Recovering orphaned file STATEC~1.LOC (5433) into directory file 77794.
Recovering orphaned file statecache.lock (5433) into directory file 77794.
Recovering orphaned file Report.wer (25140) into directory file 63593.
Recovering orphaned file Report.wer (60291) into directory file 65364.
Recovering orphaned file WD-201~1.DMP (67104) into directory file 63593.
Recovering orphaned file WD-20110513-1015-01.dmp (67104) into directory file 63593.
Recovering orphaned file WER-20~1.XML (67310) into directory file 63593.
Recovering orphaned file WER-201537-0.sysdata.xml (67310) into directory file 63593.
Recovering orphaned file WD-201~1.DMP (67383) into directory file 65364.
Recovering orphaned file WD-20110513-1015-02.dmp (67383) into directory file 65364.
Recovering orphaned file WER-21~1.XML (68771) into directory file 65364.
Recovering orphaned file WER-213846-0.sysdata.xml (68771) into directory file 65364.
Recovering orphaned file WD-201~1.DMP (69309) into directory file 69121.
Recovering orphaned file WD-20110513-1015-03.dmp (69309) into directory file 69121.
Recovering orphaned file WER147~1.XML (69324) into directory file 63593.
Recovering orphaned file WER1479.tmp.WERInternalMetadata.xml (69324) into directory file 63593.
Recovering orphaned file WER-22~1.XML (69378) into directory file 69121.
Recovering orphaned file WER-224017-0.sysdata.xml (69378) into directory file 69121.
Recovering orphaned file WER6FD~1.XML (69415) into directory file 65364.
Recovering orphaned file WER6FD2.tmp.WERInternalMetadata.xml (69415) into directory file 65364.
Recovering orphaned file WER6FD~1.XML (75040) into directory file 69121.
Recovering orphaned file WER6FD2.tmp.WERInternalMetadata.xml (75040) into directory file 69121.
13 unindexed files scanned.

Recovering orphaned file Report.wer (75072) into directory file 69121.
0 unindexed files recovered.

CHKDSK is verifying security descriptors (stage 3 of 3)...
415232 file SDs/SIDs processed.

Cleaning up 1693 unused index entries from index $SII of file 0x9.
Cleaning up 1693 unused index entries from index $SDH of file 0x9.
Cleaning up 1693 unused security descriptors.
Security descriptor verification completed.
56735 data files processed.

CHKDSK is verifying Usn Journal...
36229608 USN bytes processed.

Usn Journal verification completed.
Correcting errors in the Volume Bitmap.
Windows has made corrections to the file system.

719886335 KB total disk space.
215805736 KB in 352438 files.
153032 KB in 56736 indexes.
0 KB in bad sectors.
540567 KB in use by the system.
65536 KB occupied by the log file.
503387000 KB available on disk.

4096 bytes in each allocation unit.
179971583 total allocation units on disk.
125846750 allocation units available on disk.

Internal Info:
00 56 06 00 61 3e 06 00 28 b8 08 00 00 00 00 00 .V..a>..(.......
1c 01 01 00 4c 00 00 00 00 00 00 00 00 00 00 00 ....L...........
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................

Windows has finished checking your disk.
Please wait while your computer restarts.

Event Xml:
<Event xmlns="http://schemas.micro.../events/event">
<System>
<Provider Name="Microsoft-Windows-Wininit" Guid="{206f6dea-d3c5-4d10-bc72-989f03c8b84b}" EventSourceName="Wininit" />
<EventID Qualifiers="16384">1001</EventID>
<Version>0</Version>
<Level>4</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2011-06-02T15:28:38.000000000Z" />
<EventRecordID>19037</EventRecordID>
<Correlation />
<Execution ProcessID="0" ThreadID="0" />
<Channel>Application</Channel>
<Computer>Caitlin-PC</Computer>
<Security />
</System>
<EventData>
<Data>

Checking file system on C:
The type of the file system is NTFS.
Volume label is eMachines.


One of your disks needs to be checked for consistency. You
may cancel the disk check, but it is strongly recommended
that you continue.
Windows will now check the disk.

CHKDSK is verifying files (stage 1 of 3)...
Cleaning up instance tags for file 0x27ae6.
415232 file records processed.

File verification completed.
447 large file records processed.

0 bad file records processed.

0 EA records processed.

76 reparse records processed.

CHKDSK is verifying indexes (stage 2 of 3)...
Index entry QSGB9XMA of index $I30 in file 0x1113 points to unused file 0x16dd4.
Deleting index entry QSGB9XMA in index $I30 of file 4371.
The multi-sector header signature for VCN 0x0 of index $I30
in file 0xf869 is incorrect.
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
Correcting error in index $I30 for file 63593.
The index bitmap $I30 in file 0xf869 is incorrect.
Correcting error in index $I30 for file 63593.
The down pointer of current index entry with length 0x18 is invalid.
00 00 00 00 00 00 00 00 18 00 00 00 03 00 00 00 ................
ff ff ff ff ff ff ff ff 10 41 78 73 73 ab ca 01 .........Axss...
80 d8 9f ce ac d7 cb 01 80 d8 9f ce ac d7 cb 01 ................
Sorting index $I30 in file 63593.
The multi-sector header signature for VCN 0x0 of index $I30
in file 0xff54 is incorrect.
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
Correcting error in index $I30 for file 65364.
The index bitmap $I30 in file 0xff54 is incorrect.
Correcting error in index $I30 for file 65364.
The down pointer of current index entry with length 0x18 is invalid.
00 00 00 00 00 00 00 00 18 00 00 00 03 00 00 00 ................
ff ff ff ff ff ff ff ff 10 41 78 73 73 ab ca 01 .........Axss...
80 d8 9f ce ac d7 cb 01 80 d8 9f ce ac d7 cb 01 ................
Sorting index $I30 in file 65364.
The multi-sector header signature for VCN 0x0 of index $I30
in file 0x10e01 is incorrect.
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
Correcting error in index $I30 for file 69121.
The index bitmap $I30 in file 0x10e01 is incorrect.
Correcting error in index $I30 for file 69121.
The down pointer of current index entry with length 0x18 is invalid.
00 00 00 00 00 00 00 00 18 00 00 00 03 00 00 00 ................
ff ff ff ff ff ff ff ff 10 41 78 73 73 ab ca 01 .........Axss...
80 d8 9f ce ac d7 cb 01 80 d8 9f ce ac d7 cb 01 ................
Sorting index $I30 in file 69121.
Index entry Reader9Manifest.msi of index $I30 in file 0x10ec1 points to unused file 0x19193.
Deleting index entry Reader9Manifest.msi in index $I30 of file 69313.
Index entry READER~1.MSI of index $I30 in file 0x10ec1 points to unused file 0x19193.
Deleting index entry READER~1.MSI in index $I30 of file 69313.
528700 index entries processed.

Index verification completed.
CHKDSK is scanning unindexed files for reconnect to their original directory.
Recovering orphaned file STATEC~1.LOC (5433) into directory file 77794.
Recovering orphaned file statecache.lock (5433) into directory file 77794.
Recovering orphaned file Report.wer (25140) into directory file 63593.
Recovering orphaned file Report.wer (60291) into directory file 65364.
Recovering orphaned file WD-201~1.DMP (67104) into directory file 63593.
Recovering orphaned file WD-20110513-1015-01.dmp (67104) into directory file 63593.
Recovering orphaned file WER-20~1.XML (67310) into directory file 63593.
Recovering orphaned file WER-201537-0.sysdata.xml (67310) into directory file 63593.
Recovering orphaned file WD-201~1.DMP (67383) into directory file 65364.
Recovering orphaned file WD-20110513-1015-02.dmp (67383) into directory file 65364.
Recovering orphaned file WER-21~1.XML (68771) into directory file 65364.
Recovering orphaned file WER-213846-0.sysdata.xml (68771) into directory file 65364.
Recovering orphaned file WD-201~1.DMP (69309) into directory file 69121.
Recovering orphaned file WD-20110513-1015-03.dmp (69309) into directory file 69121.
Recovering orphaned file WER147~1.XML (69324) into directory file 63593.
Recovering orphaned file WER1479.tmp.WERInternalMetadata.xml (69324) into directory file 63593.
Recovering orphaned file WER-22~1.XML (69378) into directory file 69121.
Recovering orphaned file WER-224017-0.sysdata.xml (69378) into directory file 69121.
Recovering orphaned file WER6FD~1.XML (69415) into directory file 65364.
Recovering orphaned file WER6FD2.tmp.WERInternalMetadata.xml (69415) into directory file 65364.
Recovering orphaned file WER6FD~1.XML (75040) into directory file 69121.
Recovering orphaned file WER6FD2.tmp.WERInternalMetadata.xml (75040) into directory file 69121.
13 unindexed files scanned.

Recovering orphaned file Report.wer (75072) into directory file 69121.
0 unindexed files recovered.

CHKDSK is verifying security descriptors (stage 3 of 3)...
415232 file SDs/SIDs processed.

Cleaning up 1693 unused index entries from index $SII of file 0x9.
Cleaning up 1693 unused index entries from index $SDH of file 0x9.
Cleaning up 1693 unused security descriptors.
Security descriptor verification completed.
56735 data files processed.

CHKDSK is verifying Usn Journal...
36229608 USN bytes processed.

Usn Journal verification completed.
Correcting errors in the Volume Bitmap.
Windows has made corrections to the file system.

719886335 KB total disk space.
215805736 KB in 352438 files.
153032 KB in 56736 indexes.
0 KB in bad sectors.
540567 KB in use by the system.
65536 KB occupied by the log file.
503387000 KB available on disk.

4096 bytes in each allocation unit.
179971583 total allocation units on disk.
125846750 allocation units available on disk.

Internal Info:
00 56 06 00 61 3e 06 00 28 b8 08 00 00 00 00 00 .V..a&gt;..(.......
1c 01 01 00 4c 00 00 00 00 00 00 00 00 00 00 00 ....L...........
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................

Windows has finished checking your disk.
Please wait while your computer restarts.
</Data>
</EventData>
</Event>

Edited by caitiebugg87, 18 February 2012 - 03:37 AM.

  • 0

#4
Macboatmaster

Macboatmaster

    7k

  • Member
  • PipPipPipPipPipPipPipPip
  • 7,237 posts
The chkdsk results are really NOTHING reatly wrong here, most of those corrections are I think cuased by the unexpected shutdowns.which of course always result in errors, as the HDD is in use when it is shut down.

You certainly need to find the cause of this, as sooner or later, it will shutdown whilst the drive is being written to and then you may have more serious problems.

If for instance it was in the middle of installing updates, they would fail and it may well cause errors that would stop windows from booting.

YOU SHOULD certainly NOT attempt to install a Vista driver.

Here is the spec from AOC

http://us.aoc.com/su...f/documents/320

I suggest TWO actions
1. Do as I said please you have given no indication of whether you have or not

the recommended resoltuon for that monitor is

Recommended Resolution: 1366×[email protected]<LI>Display Colours: 16.7M

Have you so set it.

Control Panel
Display
left hand pane change display settings
and also on that window advanced settings.
then monitor tab
screen refresh rate and colour set as above 60Hz at 16
then Adapter tab
properties
Does it report working properly

Exit clicking apply and Ok as required.



HOWEVER I am not sure which driver you have now for that monitor, so go display as above, left hand pane, change display settings, advanced settings, monitor tab, properties, driver tab and update driver, or if you have now installed the vista one roll back driver. - then continue as above for settings of resolution etc.



FINALLY if this all fails contact AOC support and ask if it is compatible with 7.
Although as I said you should not need a driver that you install Windows should find its own.

Here is the list of known compatability for AOC monitors
http://www.microsoft...sults=50&page=2
  • 0

#5
caitiebugg87

caitiebugg87

    Member

  • Topic Starter
  • Member
  • PipPip
  • 33 posts
AOC 831W version 1.0.0.0 is the driver and it says it is up to date.

the recommended resoltuon for that monitor is

Recommended Resolution: 1366×[email protected]<LI>Display Colours: 16.7M

Have you so set it.

Control Panel
Display
left hand pane change display settings
and also on that window advanced settings.
then monitor tab
screen refresh rate and colour set as above 60Hz at 16
then Adapter tab
properties
Does it report working properly

Exit clicking apply and Ok as required.


I just did all this and all was set correctly except it was on 32 bit for color, so I changed it to 16 bit.

So we will see if it works, so far so good, hopefully it doesn't freeze up like it did last time.
  • 0

#6
Macboatmaster

Macboatmaster

    7k

  • Member
  • PipPipPipPipPipPipPipPip
  • 7,237 posts
Thanks for posting, please do let us know at your convenience, after testing for a few days.
  • 0

#7
Macboatmaster

Macboatmaster

    7k

  • Member
  • PipPipPipPipPipPipPipPip
  • 7,237 posts
caitiebugg87

How is the situation please.
  • 0

#8
caitiebugg87

caitiebugg87

    Member

  • Topic Starter
  • Member
  • PipPip
  • 33 posts
Still works! thank you so much!
  • 0

#9
Macboatmaster

Macboatmaster

    7k

  • Member
  • PipPipPipPipPipPipPipPip
  • 7,237 posts
Thanks for replying.
  • 0

#10
caitiebugg87

caitiebugg87

    Member

  • Topic Starter
  • Member
  • PipPip
  • 33 posts
Okay, we'll the power went out this morning cause of snow, and now it's back to doing the same thing, won't boot normally or in safe mode and won't do windows repair. :(
  • 0

Advertisements


#11
ThomasAnderson

ThomasAnderson

    New Member

  • Member
  • Pip
  • 3 posts
I have also face this problem when i change my dead motherboard Asus G31 to new Intel G41.
I try to repair it because of some important software install in HDD, but unable to repair.

Edited by Macboatmaster, 01 March 2012 - 06:08 PM.
Link to fee charging repair service - deleted.

  • 0

#12
Macboatmaster

Macboatmaster

    7k

  • Member
  • PipPipPipPipPipPipPipPip
  • 7,237 posts
caitiebugg87

Well, I am sorry you have had to return to us with such bad news.

Have you tried connecting another monitor again.

"I plugged my computer into my sisters monitor"
  • 0

#13
caitiebugg87

caitiebugg87

    Member

  • Topic Starter
  • Member
  • PipPip
  • 33 posts
Okay, well I switched keyboards, I plugged the one that came with my computer in and got a different result, although it still doesn't work. When I turned it on I went to system repair instead of start normally. As soon as it was done loading windows files i got BSOD. I took a picture of it, although it won't let me post it from my phone so when I get on a computer I will try. So after that I rebooted and tried to start in safe mode with networking and got one log continuous beep, so I restarted again and tried safe mode without networking and got one short beep. Restartd again and still couldn't get it to work so I have given up for tonight. I am going to try plugging it back Ito my sisters computer and hopefully that will work.
  • 0

#14
Macboatmaster

Macboatmaster

    7k

  • Member
  • PipPipPipPipPipPipPipPip
  • 7,237 posts

am going to try plugging it back Ito my sisters computer


Monitor?
Will wait to hear from you
  • 0

#15
caitiebugg87

caitiebugg87

    Member

  • Topic Starter
  • Member
  • PipPip
  • 33 posts
Oops yeah I meant monitor, will do it today, been moving the past couple of days. I'll let you know.
  • 0






Similar Topics

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users

As Featured On:

Microsoft Yahoo BBC MSN PC Magazine Washington Post HP