Bsod new install
- Thread starter asutch
- Start date
- Status
Route44
Posts: 12,015 +82
Your error is Bug Check 0x109: CRITICAL_STRUCTURE_CORRUPTION
This indicates that the kernel has detected critical kernel code or data corruption.
There are generally three different causes for this bug check:
a. A driver has inadvertently, or deliberately, modified critical kernel code or data.
b. A developer attempted to set a normal kernel breakpoint using a kernel debugger that was not attached when the system was started. Normal breakpoints (bp) can only be set if the debugger is attached at start time. Processor breakpoints (ba) can be set at any time.
c. A hardware corruption occurred. For example, the kernel code or data could have been stored in memory that failed.
Unfortunately the minidump states the analysis was inconclusive. Since hardware is one of the possibilites and the fact that some post on the 'net that the cause was due to corrupted memory, then run memtest on your RAM:
1. Go to www.memtest.org and download the latest ISO version. It is free and perfectly safe.
2. Burn to a CD.
3. Place CD in your drive and reboot with CD in drive. (You might have to place your drive as first bootable in your BIOS) The test will take over.
4. Let it run for a LONG time. The rule is a minimum of 7 Passes. There are 8 individual tests per Pass. Many people will start this test before going to bed and check it the next day.
5. If you have errors you have corrupted memory and it needs to be replaced.
6. Also, with errors you need to run this test per stick of RAM. Take out one and run the test. Then take that one out and put the other in and run the test. If you start getting errors before 7 Passes you know that stick is corrupted and you don’t need to run the test any further on that stick.
This indicates that the kernel has detected critical kernel code or data corruption.
There are generally three different causes for this bug check:
a. A driver has inadvertently, or deliberately, modified critical kernel code or data.
b. A developer attempted to set a normal kernel breakpoint using a kernel debugger that was not attached when the system was started. Normal breakpoints (bp) can only be set if the debugger is attached at start time. Processor breakpoints (ba) can be set at any time.
c. A hardware corruption occurred. For example, the kernel code or data could have been stored in memory that failed.
Unfortunately the minidump states the analysis was inconclusive. Since hardware is one of the possibilites and the fact that some post on the 'net that the cause was due to corrupted memory, then run memtest on your RAM:
1. Go to www.memtest.org and download the latest ISO version. It is free and perfectly safe.
2. Burn to a CD.
3. Place CD in your drive and reboot with CD in drive. (You might have to place your drive as first bootable in your BIOS) The test will take over.
4. Let it run for a LONG time. The rule is a minimum of 7 Passes. There are 8 individual tests per Pass. Many people will start this test before going to bed and check it the next day.
5. If you have errors you have corrupted memory and it needs to be replaced.
6. Also, with errors you need to run this test per stick of RAM. Take out one and run the test. Then take that one out and put the other in and run the test. If you start getting errors before 7 Passes you know that stick is corrupted and you don’t need to run the test any further on that stick.
- Status
